Callback

Callback Notification
When a deposit order or withdrawal order is successfully processed, the system will initiate a callback request to the merchant’s preconfigured callback endpoint for notification.

Request Method: POST

Parameter Format: JSON

3. Parameters:

Parameter Name	Type	Description
OrderNo	string	Order ID
MerchantNo	string	Merchant ID
MerchantOrderNo	string	Merchant Order ID
PayTime	string	Payment timestamp
State	int	State(withdrawal order only, succes=4,refuse=5 )

4. Examples:

Encrypted parameters (pre-decryption)

{
  "encryptedData": "BQDDdGq...（Base64 string）"
}

Decrypted parameters

{
  "OrderNo": "123",
  "MerchantNo": "456",
  "MerchantOrderNo": "no123",
  "PayTime": "2025-01-01 12:00:00"
}

5. Response:

{  
    "code": 200  
}

or
success

6. Notes:

Merchants must return {"code":200} or the string "success" upon receiving notifications. Failure to do so will be interpreted as an unsuccessful notification delivery, triggering the following retry strategy:
15s‒3m‒10m‒30m‒1h‒2h‒6h‒15h (15 seconds, 3 minutes, 10 minutes, 30 minutes, 1 hour, 2 hours, 6 hours, 15 hours).

If no successful response is received within the retry period, the merchant’s service will be deemed abnormal. Notification for this order will be terminated, and the order status can be queried on the Merchant Portal.

Asynchronous notifications only occur after successful order completion. Thus, notification failure does not indicate payment failure.

3. Parameters:#

4. Examples:#

5. Response:#

6. Notes:#

3. Parameters:

4. Examples:

5. Response:

6. Notes: