Technical demonstration
The payment timed out. Did it go through?
Follow a fictional checkout request through a lost response. This reference design uses a simulated payment provider.
INTERACTIVE DEMONSTRATION · ORDER 1042
Try losing the reply.
This simulation runs in your browser. Compare what the provider recorded with what checkout knows, then choose how to recover the order.
- Checkout requests
- 0
- Provider charges
- 0
- Payment status
- Ready
- Order releases
- 0
Start by sending the order and dropping the provider’s reply.
THE SCENARIO
One order, one intended payment.
A checkout sends order 1042 for processing. The provider accepts the request, but the response is lost. The customer sees a spinner and tries again. The checkout service now has two requests and an unknown outcome.
Record intent before sending.
The service assigns a payment ID and saves the request fingerprint, retry key, and dispatch event in one database transaction. A unique constraint on the merchant and retry key makes concurrent retries resolve to the same payment. A reused key with a different amount or currency is rejected.
The worker sends that same payment ID as the provider’s idempotency key. This example assumes the provider supports that key and an authoritative status lookup.
EXPLORE THE FAILURE PATHS
What happens next?
The customer retries checkout
The service finds the matching payment record and returns its current status. While the outcome is unknown, checkout shows “Confirming payment.” A lookup or a verified provider event can move the record to its confirmed state.
The provider sends the success event twice
After verifying the sender, the consumer records the provider event ID and updates the payment in one transaction. A repeated event ID leaves the payment unchanged. The order service also deduplicates fulfillment by order ID.
No confirmation arrives
A reconciliation job looks up the payment by its original reference. A confirmed result updates the order. An unavailable lookup leaves the payment pending and schedules another check. If the recovery window expires, the payment enters manual review before another charge can be attempted.
How to test the design
Have a provider stub accept the payment and drop its response. Replay the checkout request, then deliver the success event twice. Check the provider ledger for one charge, the order history for one fulfillment, and the payment record for the confirmed outcome.
Repeat with the status lookup unavailable. The expected result is a pending payment with a recovery task. The retry policy must account for how long the provider retains its idempotency keys.
Explore fintech and payments expertise →KEEP EXPLORING
Explore another scenario.
Try a different engineering decision with fictional records in your browser.
Authorize a report delivery
Approve a recipient, change the destination, and try executing the revised proposal with the original approval.
Open demonstration →Cloud & Enterprise ArchitectureRecover a stalled export
Hand a job to a second worker, then return a late result from the first. Watch which worker can publish the file.
Open demonstration →Digital Product EngineeringTest a booking release
Book the only appointment, interrupt cancellation, and check when another customer can claim the slot.
Open demonstration →OUR WORKCompare all scenarios
See what fails in each scenario, what the system must protect, and how to check the outcome.
View comparison →Fintech & Payments
Does your team face a similar problem?
Bring a redacted sequence of events for one payment with an uncertain outcome. Include what the customer saw, which references survived the timeout, and how operations resolved it.