← All articles

commit_unknown: why we never retry a checkout blind

A timeout after Place order doesn't mean the order failed. Here is how we handle the moment nobody can see.

Most failures in checkout are easy. The address is invalid, the card is declined, the item went out of stock. The merchant tells you, and you can fix it and try again.

The hard failure is silence. You submit the order, and the response never arrives.

Submission may have happened

Once the order is submitted, the merchant may have accepted it even if we never saw the confirmation. A network drop, a slow page or a crashed browser all look the same from our side. Retrying could place a second order. Reporting failure could hide a real one.

So we don't guess. An attempt becomes commit_unknown when submission may have reached the merchant but no trustworthy confirmation was observed.

One fence per approved purchase

Every approved purchase revision gets exactly one commit fence. Only the attempt holding that fence may submit the order. A timeout after submission marks the attempt commit_unknown; it does not release the fence. No other attempt can submit until the unknown is resolved.

Reconcile, then decide

Resolving the unknown means finding evidence: the merchant's order history, a confirmation email, a tracking lookup. If an order exists, it becomes the confirmed order. If there is clear evidence that none was placed, the session can move on. Until then, it waits.

What your agent sees

Your agent gets a clear state rather than an error to retry. It can tell the shopper the order is being confirmed, and it gets the outcome when reconciliation finishes. And an order is only billed once the merchant confirms it.