Payment succeeded: why has the site not recorded it?
When a user says payment is complete but your site still shows unpaid, the issue is often a callback your system did not receive or handle correctly. Follow these checks instead of repeatedly switching channels.
1. Did the callback URL actually receive the request?
Confirm that the callback URL is publicly accessible over HTTPS or the agreed protocol, and not blocked by a firewall, CDN verification or an incorrect path. Logs should show the original notification, arrival time and your response code.
2. Did signature and field checks pass?
Verify the signature, merchant order ID, amount and payment status. Do not automatically fulfill orders with invalid signatures, amount mismatches or unknown IDs; route them to manual review.
3. Did you discard a repeated notification?
Upstream providers retry after a failed first attempt. An endpoint error, or marking an order as exceptional and ignoring later notifications, can look like a missed order. Apply the successful state only once, while still allowing a valid later success notification to complete an order after an earlier failure.
4. Use queries to supplement callbacks
Callbacks are not the only source of truth. Actively query incomplete timed-out orders, update local status from the results and record each query. Return the agreed success response after processing to avoid unnecessary retries.