Is an HTTP 402 Challenge Proof of Payment? No — Challenge vs. Settlement, With Live Receipts
Payment screenshots are circulating in the x402 ecosystem, and a lot of them show the same thing: an HTTP 402 response body. Here is the problem — a 402 challenge is not proof of payment. It is a price quote. We proved it today on our own production endpoint. The free exhibit This afternoon (October 14, 2026, 22:01 UTC) we sent one unauthenticated request to our Verdict Protocol: POST…
The wire material reports that circulating screenshots in the x402 ecosystem reveal an HTTP 402 response body. However, it is clarified that a 402 challenge is not proof of payment; instead, it is a price quote. This assertion is demonstrated through a live test on the Verdict Protocol, where an unauthenticated request was sent, resulting in an HTTP 402 response with a full challenge.
This challenge provided details such as x402 v2, network eip155:8453, amount 250000 ($0.25), asset USDC on Base, and payTo set to the settlement wallet. No wallet was connected, no signature was required, and no funds were moved. The challenge itself only proves the price charged by the server. The process continues with authorization, which requires an EIP-3009 authorization to prove the buyer's permission rather than fund movement.
Settlement occurs when a facilitator broadcasts the transfer, and it lands on-chain, resulting in a transaction hash and receipt. The wire material emphasizes that anything below settlement, including the 402 challenge, is merely a quote, permission, or promise, and does not constitute proof of payment. The article provides steps to verify any paid claim, starting with obtaining the transaction hash, checking the receipt status, confirming the transfer, and matching the paperwork.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
