Returns 400 instead of 402

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

Gates the resource with 400 Bad Request instead of 402.

Explanation

An unpaid request is answered with 400 Bad Request, which makes a perfectly valid call look malformed. The client has no reason to start the payment flow. The merchant's middleware is emitting the wrong status.

What to watch

A valid call looks malformed, so the client never starts paying.

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