X402's transaction volume has dropped 77% from its November 2025 peak of $5.15 million to $1.19 million by May 2026. But the number of transactions tells a different story: after falling 41% from a December 2025 high of 4.85 million, it rebounded to 2.89 million in May — up 12.5x from a February trough. The average transaction is now $0.52, suggesting the network is being used for high-frequency, low-value agent payments. That's where the problem lives.
The $0.52 problem
Each x402 transaction requires manual wallet confirmation, taking 5 to 15 seconds. That adds up to 4,000 to 12,000 user-hours of friction per month, costing $0.03 to $0.10 per confirmation. For a $0.52 transaction, that's material. It's the kind of overhead that makes sense for a swap or a loan — but not for a micropayment an agent makes on your behalf every few minutes.
Protocols tackle the delegation gap
A handful of industry efforts are converging on the same answer: move authorization from the wallet level to the policy level. In April 2026 Google donated its AP2 authorization framework to the FIDO Alliance. AP2 uses cryptographically signed mandates that define what an agent can do — price ceilings, time windows, action scope — so the agent can act without the user present. Mastercard's Verifiable Intent creates a tamper-resistant record linking user authorization to execution, providing an audit trail.
Stripe and Tempo's Machine Payments Protocol (MPP) requires only two on-chain transactions per session, regardless of how many payments happen inside it. Stripe's documentation describes pay-per-use models starting at 0.01 USDC per agent invocation. Cloudflare treats both x402 and MPP as HTTP infrastructure: agents discover services, receive 402 Payment Required challenges, and retry with credentials. Visa's Intelligent Commerce Connect, in pilot with AWS, Diddo, Highnote, Mesh, Payabli, and Sumvin, adds tokenization and spend controls.
All of these protocols push authorization to a policy layer — one user decision governs many agent actions.
Base MCP launches but with limits
Base MCP went live on May 26. It enables agents to propose x402 payments but still requires wallet approval for execution. That's fine for large actions like swaps and lending, where the approval gate is a safety feature. For recurring micropayments of $0.52 or less, it creates the same friction as at the wallet layer. The delegation disconnect remains unresolved.
The next concrete milestone: whether any of these frameworks will be adopted by the wallets and agents that use x402 today. The transaction rebound suggests demand is real. The friction numbers suggest the current approach won't scale.
