Deposit Notification

The system sends transaction results to the callback URL provided by the merchant.

Request Information

• Request URL: The notify_url provided by the merchant when submitting the deposit request
• Method: POST
• Content-Type: application/json;charset=utf-8

Request Parameters

Parameter	Required	Type	Description
payment_id	Yes	String	System Order ID
payment_cl_id	Yes	String	Merchant Order ID
platform_id	Yes	String	Merchant ID
amount	Yes	Integer	Order amount (in cents)
real_amount	Yes	Integer	Actual received amount (in cents)
fee	Yes	Integer	Transaction fee
status	Yes	Integer	Transaction status
create_time	Yes	Integer	Creation time (in seconds)
update_time	Yes	Integer	Update time (in seconds)
sign_type	No	String	Signature type: HMAC-SHA256
sign	Yes	String	Order signature

Request Example

{
    "payment_id": "PM00000102",
    "payment_cl_id": "97a968b4a9db497c8c03198e395a38c6",
    "platform_id": "PF0014",
    "amount": 400000,
    "real_amount": 400000,
    "fee": 3200,
    "status": 2,
    "create_time": 1567614049,
    "update_time": 1567614111,
    "sign": "d2e4534fce8c1d1053bbf59fd8ae4464"
}

Merchant Response

{ "error_code": "0000" }

Response Parameters

Parameter	Type	Description
error_code	String	Returning "0000" indicates the platform has processed successfully

Remarks

• This API is implemented by the merchant. Our system will call this API when the order succeeds
• Within one hour of order completion, up to ten retry notifications will be sent. Retries stop once the merchant returns a success response
• It is recommended that merchants implement signature verification to ensure the content has not been tampered with
• This API may receive duplicate notifications. Merchants should handle idempotency to avoid duplicate crediting
• For order statuses, please refer to: Order Status
• Additional fields may be supported in the future. During integration, dynamically retrieve the returned fields for signature verification. Do not hardcode the fields