x402receiptsPeriod statement

September 2026

Final
This statement's fingerprint is on the public ledger and cannot be revised.
Statement fingerprint83bbeea3b6befe90aab69fb22e3809bda061373fcc3d2d22cd8a8bc20df62064
Ledgermainnet · topic 0.0.10889260 · message #13
Consensus time01/10/2026, 05:17:14 UTC
Open on HashScan ↗Read it from the ledger ↗
Spent1.069 USDC19 receipts · 19 delivered
Signed on the ledger19/199 daily groups · 8 supplier-signed
Payments with no receipt4listed in this statement

Completeness

Each wallet was read from the chain itself — api.mainnet-beta.solana.com, base.blockscout.com, mainnet.base.org — and every outgoing payment was matched to a receipt. What did not match is stated below, with its settlement reference.

WalletPayments on-chainWith a receiptUnmatched
0x6310…423d
eip155:8453
66—
0xaa12…c56d
eip155:8453
303
4wAYQj…9Upk
solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp
321

Payments with no receipt

Money left a wallet and nothing was recorded against it — usually an agent running without the SDK, or a transfer that was not a purchase. They are listed here so the statement is complete, not because they are necessarily wrong.

WhenToAmountSettlement
25/09, 20:020x63100a3a…9e423d0.1 USDC0xee449bc7…bc91a0
27/09, 17:140x63100a3a…9e423d1.1 USDC0x3f804aab…b605af
27/09, 17:170x6310973e…b7423d0 USDC0xae7501d7…54b411
30/09, 15:216srFz6v3mS…UDCvbK0.005 USDC4pEszvUvJF…pocQ7s

Daily groups in this period

89e8f55a…0112 · 1 receipt · root 02eb0e46…8b081c#6 ↗
2521ceb5…d319 · 2 receipts · root a4dcb982…045f3f#1 ↗
14907ff8…7fd7 · 4 receipts · root dc257efb…4a4ab5#2 ↗
3ea3c6fb…d26b · 4 receipts · root 9f183b68…30e1c4#3 ↗
86a240c0…620b · 2 receipts · root ef608f7d…7d8971#4 ↗
57d051c2…97d3 · 4 receipts · root 91df07c7…0df96f#5 ↗
632e68a8…d73a · 1 receipt · root 4dc4e362…04ad20#7 ↗
77a4d2f3…12a5 · 1 receipt · root 9da363d4…7d2e49#8 ↗
f28c947c…9deb · 5 receipts · root bd9b2731…108f55#10 ↗

Format: ARR-1 §10, issued by x402receipts. Generated 01/10, 05:17; covers 01/09, 00:00 to 01/10, 00:00. To verify independently: hash the statement JSON in its canonical form and compare with the fingerprint above, then read that fingerprint from the ledger at the coordinates given.