Cacheable 402 challenge

Quirk · GET /api/x402/edge-cacheable-challenge · Edge / CDN Controls

Sends the 402 with Cache-Control: public, max-age, so a shared cache stores and replays a stale challenge.

Explanation

The server sends the 402 challenge with Cache-Control: public, max-age, so a shared cache stores it and replays the same challenge to other clients. The challenge carries a nonce, a quote, and a price that go stale, so later payers sign against requirements the origin no longer honors. Challenges must be no-store; setting the cache headers correctly is the merchant's edge-configuration responsibility.

What to watch

curl -i: the 402 carries public, max-age=300; the nonce, quote, and price go stale in cache.

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