Edge timeout during settle

Quirk · GET /api/x402/edge-timeout-settle · Edge / CDN Controls

Settlement is slow and the edge returns 504 while the charge may have completed on-chain — an ambiguous paid state.

Explanation

Settlement is slow and the edge gives up with 504 Gateway Timeout while the settle is still in flight, so the charge may have completed on-chain even though the client received an error — an ambiguous paid state. The merchant must align edge origin timeouts with settlement latency and reconcile in-flight settlements rather than leaving the buyer unsure whether they were charged.

What to watch

The paid call returns 504 after a valid verify — the charge may still settle on-chain.

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