x402 payments prove money moved. They don't prove you got what you paid for.
Description and use
x402 payments confirm money transfer but not delivery. capacity‑attest records signed delivery claims in a public, append‑only history, enabling buyers to verify past service delivery before paying.
Problem
Payments via x402 confirm money transfer but do not verify that the promised metered or continuous service was actually delivered.
Outcome
A real $0.001 USDC payment on Base mainnet was followed by a signed delivery claim recorded in ~5 s, proving the system works end‑to‑end with low latency (11 ms for signing and recording).
Workflow
- 1. Buyer initiates an x402 payment to seller’s wallet.
- 2. Payment settles on Base mainnet and emits a settlement reference.
- 3. Buyer’s agent signs a delivery claim (EIP‑191) containing promise details, delivery status, and evidence hash.
- 4. The claim is recorded via capacity‑attest to a public, per‑seller append‑only history.
- 5. Future buyers can query the history before paying to verify past delivery records.
- 6. Seller can also verify the claim and evidence hash to confirm buyer’s acceptance.
Evidence
Total time from confirmed payment to a readable, signed record: about 5 seconds. The payment confirmation itself was the slow part (4.5s), everything capacity‑attest did (sign, record, read back) took about 11ms combined.
After an x402 payment settles, the paying agent signs a plain factual record with its own key: what was promised, what was delivered (yes / no / partial), a hash of the evidence, and the settlement reference.
- Record date: 2026-09-05T18:30:25.080Z