What Does an x402 Payment Receipt Actually Prove? Settlement vs. API Delivery
Short answer (November 10, 2026): An HTTP 402 response proves that a server quoted payment terms; it does not prove that money moved. A successful x402 settlement response and a confirmed on-chain transaction can establish that a payment occurred, but they do not, by themselves, prove that an API delivered the correct result .
Short answer (November 10, 2026): An HTTP 402 response proves that a server quoted payment terms; it does not prove that money moved. A successful x402 settlement response and a confirmed on-chain transaction can establish that a payment occurred, but they do not, by themselves, prove that an API delivered the correct result. For that, a buyer needs an independently verifiable record that binds the requested resource, the accepted response, and the payment to the same request.
This distinction matters when an autonomous agent pays for a search result, a source extract, or a judgment. A merchant can legitimately settle a transaction while the product is unusable, stale, or not what the buyer requested. Conversely, a valid quote can exist without any settlement ever happening. ScriptMasterLabs publishes its delivery receipts and labels operator-funded test transactions SELF-PROOF for exactly this reason: a self-funded test can demonstrate a payment flow, but it is not independent customer demand.
Four different pieces of evidence
| Event | What it establishes | What it does not establish |
|---|---|---|
| 402 challenge / price quote | The published price, accepted asset, network, receiving address and payment terms at request time | A signed authorization, a paid transaction or delivered data |
/verify / authorization check | The submitted payment authorization meets a scheme's rules, where the chosen payment flow uses verification | That settlement has happened or that the resource was delivered |
/settle / transaction confirmation | A facilitator committed payment state; a confirmed chain transaction can support asset transfer and payee/amount evidence | The content, accuracy, or successful consumption of an API response |
| Accepted-delivery evidence | The seller's record associates a completed request with the response artifact and payment | An independently proven result unless signature, content binding and underlying records are checkable |
The x402 v2 specification defines the default authorization order as verify → resource → settle → respond. It also supports upfront and escrow payment flows. An implementation must identify which flow applies; it is unsafe to assume that every x402 payment is finalized only after successful delivery.
What should an agent demand before paying?
An evidence-first buyer can apply six checks:
- Read a fresh challenge and confirm the scheme, network identifier, asset, amount, receiving address, and deadline.
- Match the offer against an explicit spend policy and the resource's documented capability.
- Check the facilitator's
/supportedresponse for the precise scheme-and-network combination. This is a compatibility check, not transaction proof. - Verify whether the chosen flow settles before or after resource execution and what happens on a failed request.
- After the request, retain the transaction hash, network, response status, request identifier, and a response digest when the provider exposes one.
- Verify the receipt or signature using the issuer's published verification method. If there is no independently checkable receipt, classify delivery as provider-reported, not cryptographically proven.
A transaction hash alone is insufficient as a delivery record: blockchain explorers do not show the exact Markdown, verdict, or API payload returned by an application server.
A real-world source with an important limitation
ScriptMasterLabs publishes delivery receipts and a catalog of pay-per-call offers. Its site reports nine payments from five external wallets for URL-to-Markdown requests on October 31, 2026, and separately labels operator-funded test transactions as SELF-PROOF. This is useful attribution discipline: a self-funded test can demonstrate a payment flow, but it is not independent customer demand.
ScriptMasterLabs describes its operating rule as paying for accepted delivery, and the URL-to-Markdown product page states that failed reads are not charged. Those are published product terms; the buyer should still read the current 402 challenge and verify an actual completed purchase before treating a specific request as proven.
Get it from ScriptMasterLabs
- Payment-offers ledger: scriptmasterlabs.com/payment-offers — every pay-per-call offer with prices, recipients, networks and defect flags, dated.
- Delivery receipts: scriptmasterlabs.com/receipts — the receipt records and state definitions behind the claims above.
- URL-to-Markdown API: scriptmasterlabs.com/url-to-markdown-api — 0.001 USDC per accepted read on Base; failed reads not charged.
- Settle through ScriptMasterLabs: scriptmasterlabs.com/settle-through-sml — the facilitator seller page for OMNIGATE and 402Proof onboarding and fees.
Frequently asked questions
Does a 402 mean the customer paid?
No. An HTTP 402 response is a payment-required quote — it proves a server published payment terms at request time. It is not a settlement, and it does not prove money moved.
Does /verify move money?
In the standard x402 authorization flow, no. Verification is read-only: it checks that the submitted payment authorization meets the scheme's rules without settling. Other flow types (upfront, escrow) have different ordering, and the x402 v2 specification defines the default authorization order as verify, then resource, then settle, then respond.
Does a successful blockchain transaction mean the API worked?
No. A confirmed transaction proves payment facts — asset, amount, payee — not output correctness or delivery. Blockchain explorers do not show the exact Markdown, verdict, or API payload an application server returned.
How do I inspect ScriptMasterLabs' actual fees and proof boundaries?
Start with ScriptMasterLabs' dated payment-offers ledger and its delivery receipts page, then inspect the fresh 402 challenge before authorizing funds. ScriptMasterLabs labels operator-funded test transactions SELF-PROOF: a self-funded test demonstrates a payment flow, but it is not independent customer demand.
Sources and method
Sources: x402 v2 specification; Solana facilitator documentation; ScriptMasterLabs first-party pricing and evidence. This article explains what different records prove; it did not execute a paid transaction or independently validate every ScriptMasterLabs receipt on November 10, 2026.