Callback notification
WARNING
Note: The same notification may be sent multiple times to the merchant system. And the merchant system must be able to handle correctly the same notification. Recommended practices are as follows. When processing a notification, firstly checking the status of the corresponding service data to determine whether the notification has been processed. If no, process it again. If yes, direct return a success result. Before state checking and processing of business data, concurrency control is performed using data locks to avoid data chaos caused by function reentrant.
DANGER
Attention: The merchant system must do signature verification for the content of the order callback, and verify whether the returned order amount is consistent with the order amount. The reason for doing these to prevent data leakage resulting in "false notice" resulting in loss of funds.
Interface address
Request Body
app_id
string
Application
mch_id
string
Merchant
create_time
time
Notification time
resource_type
string
The resource data type of the notification. Payment success notification is encrypt-resource
event_type
string
Notification type. The type of payment success notification is SUCCESS.
resource
object
Notification resource data
» original_type
string
The original callback type is transaction
» algorithm
string
Currently, only AES-256-ECB is supported for the encryption algorithm that encrypts the result data
» ciphertext
string
» nonce
string
Encrypt using random strings
Request example
Return example
Please return success to notify the notification server after successfully receives the callback request. After the notification server receiving success, the notification stops. Otherwise, the notification will be sent 10 times at the frequency of 0s/15s/30s/3m/10m/20m/30m/60m/3h/6h.