Callback Description
Please note:
๐ก
During back-end notification interactions, if the platform receives a response from the merchant that does not comply with the specifications or times out, the platform will consider this notification as failed and will resend it until successful (in cases where the notification repeatedly fails, the platform will make multiple notification attempts at a frequency of 60 seconds each, but the platform does not guarantee that the notification will eventually succeed).
In cases where the order status is unclear or the payment result notification has not been received, it is advisable for the merchant to proactively contact the platform.
Special reminders:
๐ก
When handling notifications, first check the status of the corresponding business data to determine whether the notification has already been processed. If it has not been processed, proceed with the handling; if it has been processed, return the result as successful. Before performing status checks and processing of business data, use data locks for concurrent control to avoid data confusion caused by reentrant functions.
Java example:
Get the verification parameters and verify the signature
Respond to requests
After receiving the callback notification, please return the reply OK value (both upper and lower case), and then the platform will judge that the merchant has correctly received the response callback. All other fields will be treated as failures. Please pay attention to the spaces and ignore the case. Otherwise, the platform will retry to notify the merchant of the callback.
๐