Do x402 sellers settle a payment before validating the request?
The short answer
Some do. Among the paid-panel routes that never answered with content because the request lacked an input, most never took the payment, but a few settled it and then returned the error.
As published in the issue
Of the 141 routes that never answered with content and whose errors trace to an input our request lacked, 132 never settled a payment and nine settled before returning the error (35 calls).
(3) The PANEL population: the 400 x402 routes on the published paid panel drawn on 6 September, called once a week with one fixed request carrying no inputs; every paid figure describes those calls and the order in which each route handled and settled them, never a delivery rate.
The sentence above is quoted from a published issue and is not re-written here. Its date, its population and the record behind it are below.
Why it matters
Whether a seller validates a request before or after settling it cannot be seen until a payment is attempted. A seller that settles before it validates charges the buyer for a request it was always going to refuse.
What we measured
The published paid panel's weekly calls through September, each one fixed request carrying no inputs, and, for every route whose errors trace to a missing input, whether a payment settled before the error came back. The exact population rule is quoted beside the figure below.
What the evidence shows
- Sealed days behind the archive figures
- 27
- Observations in that window
- 315,315
- Issue
- Machine Commerce Reality Index: #002 — September 2026
- Published
2026-09-04 · 2026-09-05 · 2026-09-06 · 2026-09-07 · 2026-09-08 · 2026-09-09 · 2026-09-10 · 2026-09-11 · 2026-09-12 · 2026-09-13 · 2026-09-14 · 2026-09-15 · 2026-09-16 · 2026-09-17 · 2026-09-18 · 2026-09-19 · 2026-09-20 · 2026-09-21 · 2026-09-22 · 2026-09-23 · 2026-09-24 · 2026-09-25 · 2026-09-26 · 2026-09-27 · 2026-09-28 · 2026-09-29 · 2026-09-30
27 of the 27 sealed days behind these figures are on the head table at /chain (9 re-derived from an off-vendor replica and 18 anchored from the archive as stored). Each day's manifest is served at /chain/<date>.
What this does not say
- What the record establishes is about request handling and settlement order, not a delivery rate.
Method and reproduction
The runs behind the figures, the record each one produced, and the terms this question uses.
What ran, when, and the record it produced.
| What ran | When | Record |
|---|---|---|
| The paid outcomes on the published panel: for every route called in September, what came back on each weekly call, whether and when a payment settled, whether the response named the transaction, and the terms quoted at call time against the terms drawn. | 1cb85af4060afcd3358d4dc024c7bc2dd58fed3c64d98b17140fc2de5f2698da |
The terms
The terms this question uses are defined in the glossary.
Corrections and disputes
Corrections to this issue are on the corrections register, and this answer reads from the record rather than from a copy.