Platform order number
Notification
The system pushes order updates to the merchant's configured callback URL whenever the status changes.
POST
Merchant callback URLReturn HTTP 200 with a plain-text OK body after receiving the callback so the system stops retrying.
Callback Strategy
- The system sends a notification when the order status changes.
- The merchant must return
HTTP 200with a plain-textOKresponse body. - If the merchant restricts incoming IPs, please inform us in advance.
Signature Verification
- The
signaturefield in the callback is the notification signature and follows the same signing rule as API requests. - Sort all non-empty fields in the callback JSON body except
signatureina-zorder, concatenate them askey=valuepairs joined with&, append the merchant secret key, then calculateSHA256and convert the result to lowercase hexadecimal. - Compare the calculated result with
signature, and verify thattimestampis within the valid time window. Return a non-OKresponse if signature verification or business processing fails.
Retry Strategy
If a valid acknowledgment is not received (HTTP 200 with response body OK), the system will automatically retry:
- Maximum Retries: 8 times within 24 hours
- Retry Intervals:
2s → 5s → 10s → 30s → 1h → 3h → 3h → 3h
Request Method
POSTJSON
Request Parameters
Merchant order number
Actual transaction amount
Order status: SUCCESS, PENDING, FAILED, EXPIRED, CANCELLED, REFUNDED
Status description message
Transaction completion time (YYYY-MM-DD HH:mm:ss), returned on successful transactions
Millisecond timestamp
Callback signature
