Returns 403 instead of 402

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

Gates the resource with 403 Forbidden instead of 402.

Explanation

The paywall responds 403 Forbidden rather than 402 Payment Required. To an x402 client this looks like a hard authorization failure, not an invitation to pay, so no permit is ever signed. Fixing the status code is the merchant's responsibility.

What to watch

Looks like a hard authorization failure, so the client never sees a payment challenge.

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