Alipay callback with no order after a database restore: quarantine and recovery
A successful database restore does not recover every later order, delivery or refund. Preserve verified notification evidence without inventing a new order or asking the customer to pay again. These are merchant recovery recommendations.
Continue by topic
1. Define the recovery gap
Record the restore point, recovery method, missing interval and payment or delivery systems still running. Backup and log-archive methods have different prerequisites; a completed tool run is not proof of accounting consistency.
Pause affected fulfillment where needed while preserving incoming evidence. Handle suspected credential compromise separately; never disable signature checks for convenience.
2. A missing row does not decide authenticity
Verify the actual signature, merchant ownership and payment state under the agreed protocol. Check order namespaces, archives and the recovery interval. Missing local data proves neither payment nor forgery.
Quarantine verified but unmatched notifications durably, with a deduplication reference, receipt time and redacted evidence. Follow the real acknowledgement contract only after reliable persistence; this guide supplies no universal success-response string.
3. Recover the original snapshot and check delivery first
Fictional example: restore point 14:00, order R paid and delivered at 14:05, callback repeated after recovery at 14:20. Missing R locally is not permission to deliver twice. Compare payment queries, trustworthy original snapshots, fulfillment and refund records.
Rebuild the original identity only after confirming merchant, buyer, product, amount and previous delivery. Today's catalog cannot reconstruct yesterday's price or recipient. Missing evidence remains under review; never assign funds to the latest logged-in user.
4. Recover every side effect in order
Compare data in isolation, restore order/payment/delivery links, then process only confirmed unfinished work. Restoring an idempotency table does not roll back an external shipment. Query the original execution when its result is unknown.
Use local transactions and persistent uniqueness against concurrent claims, alongside external checks. Simulate delivered, undelivered, repeated, already-refunded and snapshot-missing cases; retain approvals and before/after differences.
Frequently asked questions
Can the amount create a new top-up automatically?
No. It does not prove buyer, product or previous delivery. Recover trusted order evidence or perform an auditable manual review.
Is restoring the idempotency table enough?
No. Reconcile payments, entitlements, delivery and refunds, particularly external actions after the restore point.