verify[402]
snapshot · block — Run free check

Receipts · evidence · verification

An agent payment receipt should be checkable, not just printable.

verify402 returns two kinds of proof. The free gate issues an HMAC-signed receipt bound to the exact intent and request. Paid checks return an evidence bundle with request and response hashes. Both are records you can recompute — neither is a promise that the trade was safe or profitable.

01 · The free receipt

Bound to the intent, the request and the block.

Every POST /preflight verdict carries a receipt with an intentHash, a requestHash, a pinned block and an HMAC signature. It expires after 90 seconds by default; 15–300 seconds are configurable. If the chain cannot be read, there is no receipt at all.

The receipt proves the gate answered that normalized intent and that request body at that block. It does not prove the bytes were executed, that a seller was honest, or that a token is safe.

02 · Local verification

No chain call. No trust in a dashboard.

POST /preflight/verify with the receipt, your original request and the normalized intent recomputes the HMAC, checks expiry, and re-hashes what you sent. A tampered signature returns bad_signature; an altered request returns request_mismatch. Require both intentBound and requestBound before your signer moves.

Executor rule

Refuse on BLOCK. Refuse on a missing, expired or unverifiable receipt. Treat CAUTION as an explicit decision, not a pass. The reference guard implements that order and holds no key.

04 · What it does not mean

Not settlement, not reputation, not profit.

A verified preflight receipt does not mean the x402 facilitator settled the payment, that the seller delivered the resource, that the payee wallet is controlled by the seller, or that the quoted trade would make money. Those facts are either outside the gate's reach or listed in notChecked.

Receipts are short-lived by design. Re-call the gate for a fresh decision instead of caching a PASS. For the broader policy, read AI agent payment security.

Next

Store the request with the receipt.

A receipt without the request it was bound to is hard to audit. Keep them together, then verify before you act.