ReturnCheck · Proof of payment

Someone outside this company paid for a verdict, replayed the request, and was not charged twice.

On 2026-10-06 an external integrator called /v1/check, paid 0.02 USDC over x402 on Base mainnet, and received a verdict. They then sent the identical request again. The second call returned the same answer at a cost of 0.0000 and produced no second payment. The settlement was reconciled against the chain the next day from an independent machine.

The payment

Executed2026-10-06
Protocolx402 v2 · Base mainnet
Amount0.02 USDC (20000 atomic units)
AssetUSDC 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
Payer0xE50c5212e8211639C49276dA190E248B83935763
Paid to0xbF428071027402E9b0cE85e22146EDdc028cEB3b
Transaction0xdc577f237a8502d25771baceda86738a9b2eb5f516e11f51a314f8dbfe751291
Receipt status0x1 (success)
Block52260342
Verdict returnedYES_WITH_CONDITIONS
check_idfdec5138-863e-42a2-be90-f58036bbd6d9

The replay

This is the part that matters. Charging once is easy; not charging twice for a repeated request is where payment systems break.

ResultHTTP 200
Cost of the replay0.0000
Settlement headerreplay
Same transactionyes
Same check_idyes
Second chargenone

Reconciled on the chain, not on our word

Base mainnet public RPC, read directly from an independent machine, on 2026-10-07. 1500 blocks from the settlement block were scanned, filtering by USDC contract, Transfer event, this payer and this recipient. The scan returned 1 matching transfer — the one above — and no second one in the window that covers the replay.

You do not have to take any of this from us: open the transaction in a block explorer.

What this does not prove

It is one paid call from one integrator. It is not a commercial customer, not recurring revenue, not an audit or third-party certification. We say what happened and stop there.

Executed 2026-10-06 · Reconciled on-chain 2026-10-07 · The payer is identified by their on-chain address only; their name is not published without their consent.