Did money move?
Yes. Facilitator-linked USDC transfers are visible.
This page separates payments we can see from the parts the chain cannot tell us: who made the choice, who allowed it and who fixes a mistake.
Over 30 days, known x402 payment helpers—services that complete a USDC transfer inside a web request—were linked to 18,753,628 transfer records on Base and Solana. Those records carried 266,550 USDC. That proves settlement activity. It does not count agents, customers, purchases or delivered services.
Settlement record through 2026-09-17 · Service list checked 2026-09-19
Follow the proof. The line stops where the record stops.
A transfer can be smaller than one cent and repeat thousands of times. Count and amount must be read side by side.
91.6% of the records were below 0.01 USDC. They carried only 13.9% of the amount. The headline count mostly describes repetition, not spending power.
Solana supplied 99.8% of the transfer records but 94.0% of the USDC amount. The gap matters.
Remove Solana and Base still shows 45,918 records carrying 16,100 USDC. Activity survives the removal test, but the giant count does not. The other network held 0.2% of records and 6.0% of amount.
On 2026-09-17, the two-network total reached 18,847 records. Keep the wallet and seller observations beside that number.
That is about 27 records for each paying-wallet observation on the latest day. One wallet can appear more than once across networks, so even 690 is not a count of people.
The service list shows machine-readable prices: software can see the price, pay and continue. It is a shelf, not a receipt book.
The middle listed USDC price is 0.010 USDC, and 34.6% of priced USDC choices are below one cent. Tiny prices fit data lookups and model calls. They do not prove those services were bought.
The harder questions are who allowed the choice and what happens when the choice is wrong. Payment routes answer them differently.
Yes. Facilitator-linked USDC transfers are visible.
Yes in named trials. The anonymous wallet record cannot show it.
Not visible in the wider onchain record.
Some systems record limits or signed instructions. Coverage is uneven.
Card routes have disputes. A confirmed chain transfer has no built-in reversal.
| Payment system | Who or what pays | What allows it | How money moves | If it goes wrong | Still unclear |
|---|---|---|---|---|---|
| Visa Intelligent Commerce | Named agent | Customer-set limits | Card network | Card dispute process | A poor product choice may not count as a payment error |
| Mastercard Agent Pay | Registered agent | Recorded instructions | Card network | Card dispute process | The agent still needs clear authority to choose |
| x402 | Paying wallet | Wallet approval | Blockchain | No built-in reversal | Wallet approval does not prove that AI was allowed to choose |
| Stripe MPP | Seller's account rules | Limited-use payment token for cards | Card or stablecoin | Depends on payment route | Controls differ with the payment route |
| Google AP2 | Signed identity | Signed buying instructions | Uses another payment route | Depends on payment route | The legal effect may differ by country |
These named card-network cases are bounded examples. They show a controlled agent purchase completing under stated rules. They do not measure market-wide use.
AI agents completed purchases at independent merchants under cardholder-set limits.
Read the official accountAn authenticated Agent Pay transaction booked and paid for a real experience.
Read the official accountA successful payment does not prove that the product choice was good. A refund or card dispute may fix a payment problem; it may not fix a poor decision the owner had already allowed.
No. One wallet can transfer thousands of times, and the same wallet may appear on more than one network.
No. It proves that a wallet key approved the transfer. A person, a fixed script or an AI system could have caused it.
The chain does not say why. Small data purchases are one possible explanation. Testing, repeated software activity or other transfers through the same helper could produce the same pattern.
The confirmed transfer cannot be cancelled. The receiver can send money back, or a separate agreement can provide a refund, but the original record remains.
The settlement route is active. The missing proof sits before and after payment: permission, AI choice, delivery and recovery.
Continue through Charlie’s researchResearch by Ananda Banerjee for Charlie Quant Lab · Updated