Order flow
Events
- No events yet.
Scenario notes
Healthy: the API remembers the request key, records an event, receives inventory and payment success, and confirms the order.
Timeout: the order stays pending when the payment response is missing. Reconciliation with the original payment reference finds a successful authorization, then confirmation is safe.
Duplicate: a second request with the same key and payload returns the recorded order. It does not create another logical order or payment attempt.
A simplified model of successful, timed-out, and repeated checkouts. Real services also need durable state, concurrency control, and compensation for failed orders.