Withdrawal Transaction Result 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 creating the withdrawal order
• Method: POST
• Content-Type: application/json;charset=utf-8

Request Parameters

Parameter	Required	Type	Description
payout_id	Yes	String	System Order ID
payout_cl_id	Yes	String	Merchant Order ID
platform_id	Yes	String	Merchant ID
amount	Yes	Integer	Order amount (in cents)
fee	Yes	Integer	Transaction fee
status	Yes	Integer	Transaction status
error_msg	No	String	Failure reason
create_time	Yes	Integer	Creation time (seconds)
update_time	Yes	Integer	Update time (seconds)
sign_type	No	String	Signature type: HMAC-SHA256 or MD5 (only returned for HMAC-SHA256 orders)
sign	Yes	String	Order Signature

Request Example

{
    "payout_id": "POT00000102",
    "payout_cl_id": "97a968b4a9db497c8c03198e395a38c6",
    "platform_id": "PF0014",
    "amount": 400000,
    "fee": 3200,
    "status": 3,
    "create_time": 1567614049,
    "update_time": 1567614111,
    "sign": "d2e4534fce8c1d1053bbf59fd8ae4464"
}

Merchant Response

{ "error_code": "0000" }

Response Parameter Description

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

Remarks

• This API is implemented by the merchant. The system will call this API when the order succeeds/is cancelled/fails
• Within one hour of order completion, the system will retry up to 10 times. Retries will 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 accordingly
• For order status reference, see: Order Status
• More fields may be supported in the future. During integration, please dynamically retrieve returned fields and generate signature verification. Do not hardcode the fields