Returns 401 instead of 402

Quirk · GET /api/x402/status-401 · 402 / Challenge Construction

Gates the resource with 401 Unauthorized instead of 402 Payment Required.

Explanation

The server gates the resource with HTTP 401 instead of 402. Clients key their payment state machine on the 402 status, so they never recognize this as a payment challenge and the flow stalls. The merchant must return 402 from its paywall middleware.

What to watch

Clients that key on a 402 never start the payment flow.

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