Serves before settlement (verify/settle gap)

Quirk · GET /api/x402/serve-before-settle · Replay / Idempotency / Race

Returns 200 immediately and settles in the background.

Explanation

The server returns 200 immediately and only settles in the background, so the resource leaves before the charge is confirmed and a failed settle means free access. The merchant must settle before serving. This interacts badly with the edge: if an origin timeout fires while settlement is still in flight, the buyer can be charged on-chain yet receive an error — an ambiguous paid state (see the edge-timeout-settle scenario in Edge / CDN Controls).

What to watch

The resource leaves before the charge is confirmed.

Facilitator

Settled against the live Radius testnet facilitator (https://facilitator.testnet.radiustech.xyz). A valid payment runs a real /verify and /settle on-chain.

Metadata

Back to catalog