Order callbacks and preventing duplicate fulfillment
Payment page redirects may be interrupted. Reliable payment confirmation requires both server callbacks and order queries.
What is an asynchronous callback?
When a payment result changes, the system sends a notification to the merchant's configured URL. It synchronizes order status but must not be trusted without verification: every public endpoint must check the request source and data integrity.
Signature and field verification
Verify signatures with the key stored on your server. Also check the merchant order ID, amount paid, payment status and merchant identifier. A valid signature alone does not authorize fulfillment: the order must exist and be in a state that permits completion.
Why process each order only once?
Timeout retries can deliver the same notification multiple times. Fulfilling, increasing balances or recording revenue for every callback inflates business data. Update using a unique order ID and final state condition. For orders already processed successfully, return the agreed response and log the notification content and time.
Troubleshooting exception orders
Keep order creation parameters, original callback data, signature results, status transitions and response codes. Support and technical staff should be able to trace the entire flow by order ID. Do not automatically complete orders with amount mismatches, invalid signatures or unknown IDs; send them for manual review.