Key takeaways
- x402 is backed by a broad industry group: the x402 Foundation launched under the Linux Foundation on April 2, 2026, with AWS, American Express, Cloudflare, Coinbase, Google, Mastercard, Shopify, Stripe and Visa among its premier members.
- Headline settlement counts overstate real use. Visa and Artemis put adjusted volume at roughly $15 million through April 21, 2026, and TRM Labs estimated that only 0.6% to 7.5% of screened x402 commerce came from AI agents.
- A USENIX Security 2026 study found 49 security-rule violations across the 15 x402 facilitators it tested, and every one violated at least one rule; the affected parties acknowledged the issues and adopted mitigations, including Coinbase.
- In the base protocol, verifying a payment does not lock the funds, payment and delivery are separate steps, and there is no built-in dispute or refund process.
- If you sell with x402, pick a facilitator that has adopted the published mitigations, settle before you deliver, and decide who handles refunds. Platforms such as Qatom bind payment, delivery and the record into one transaction.
What is x402 in 2026?
x402 is an open payment protocol that revives the HTTP 402 "Payment Required" status code. A server answers a request with a price, the client signs a stablecoin payment and retries, and a payment facilitator verifies and settles it onchain.
Coinbase created x402 and announced it in May 2025. On April 2, 2026, Coinbase contributed the protocol to the x402 Foundation, which operates under the Linux Foundation. Forty organizations joined at launch. Its premier members are Amazon Web Services, American Express, Cloudflare, Coinbase, Google, Mastercard, Shopify, the Solana Foundation, Stripe and Visa.
That backing makes x402 a serious standard. It also means the protocol now gets the scrutiny that comes with being one. In 2026, analysts and security researchers published the first independent measurements of how x402 is used and how safe it is.
How much real volume does x402 process?
Raw settlement counts are large. Filtered counts are much smaller. Every independent analysis in 2026 reached that conclusion, with different methods:
| Source | What it measured | Finding |
|---|---|---|
| Visa and Artemis, data through April 21, 2026 | Adjusted x402 volume since launch | Roughly $15.0 million across about 109.6 million transactions, an average of about $0.14 |
| Visa's Cuy Sheffield, via The Defiant, July 2026 | Adjusted volume | About $19 million across about 134 million transactions; about 4,000 wallets made about 90% of adjusted spending |
| TRM Labs, via Decrypt, September 2026 | Settlements by known facilitators on Base, Solana and Polygon since May 2025 | 198.9 million settlements, about $52.7 million; $25.62 million left as likely commerce after screening |
| Ling, Zhou, Wu and Wang, July 2026 | 136.7 million settlements on Base over 280 days | 21.20% fictitious; 63.78% settled within a linked cluster |
| Artemis, via CoinDesk, March 2026 | Daily activity | About $28,000 and 131,000 transactions a day in recent snapshots; about half of transactions judged artificial |
The share that came from AI agents is smaller still. TRM Labs estimated that 0.6% to 7.5% of screened commerce by value came from agents, and noted its models cannot conclusively tell agents from scripts. The July 2026 Base study put it bluntly: "Settlement count measures manufacturability, not adoption."
Two factors make counts easy to inflate. Payments are tiny, and facilitators often pay the gas fee on the buyer's behalf, so a single operator can generate millions of settlements at little cost.
What did security researchers find?
In July 2026, Qinying Wang and Mathias Payer of EPFL, Yong Yang and Shouling Ji of Zhejiang University, and independent researcher Yuan Chen published When HTTP 402 Meets the Blockchain, accepted to the 35th USENIX Security Symposium. They defined eight security rules for x402 facilitators and tested 15 major facilitators, which serve more than 60,000 sellers and 360,000 buyers and cover about 99% of observed x402 transactions. They also analyzed more than 119 million recent Base and Solana transactions.
The researchers found 49 security-rule violations, which mapped to 31 previously unknown vulnerabilities, and every facilitator violated at least one rule. The risks fall into four attack types:
- Free Shopping, where a buyer gets the service without paying
- Asset Theft
- Service Denial
- Gas Abuse
The authors disclosed the findings responsibly. The affected parties acknowledged the issues and adopted mitigations, including changes by Coinbase. Some fixes were complete at publication and others were still in progress.
Why do these problems happen?
They come from how the base protocol splits the work. Four Pillars Research identifies three design gaps:
- Verifying does not lock the funds. The
verifystep checks a payment but does not lock the money or use up its nonce, so a payment that passes verification can still fail to settle. - Verification and settlement do not share state. They are separate calls, and the seller usually delivers in between.
- Facilitators often pay gas. That makes them a target for abuse and makes fake volume cheap.
A separate paper, A402, makes the same point from the seller's side: x402 "fails to enforce end-to-end atomicity across service execution, payment, and result delivery." In plain terms, a seller can deliver and still not be paid.
There is also no built-in way to dispute a charge. A refund is simply a new transfer, and Four Pillars argues that refunds and disputes have no clear owner today.
Is x402 still worth using?
For many builders, yes. The fair reading of the 2026 research is that x402 is early, not broken:
- The problems were disclosed and fixed. The security study was a responsible disclosure, and facilitators, including Coinbase, adopted mitigations.
- Usage is expected to mature. Artemis expects the share of gamed activity to fall as teams move from testing to production.
- The industry is committed. The x402 Foundation brings card networks, cloud providers and payment companies together around one open standard.
- The proposed fix builds on the protocol. Four Pillars argues for accountable operators, each clearly responsible for its payment route and competing under the same open standard, that settle before the business logic runs and handle refunds and disputes. That keeps x402 open while giving each payment an owner.
How to sell with x402 safely
If x402 fits your API, these steps reduce the risks the researchers found:
- Ask your facilitator which mitigations it has deployed for the issues in the July 2026 study, and get the answer in writing.
- Settle before you deliver. Do not release data or run the paid work on a verified-but-unsettled payment.
- Treat each payment as single use. Reject a payment you have already seen, even if it still verifies.
- Decide who handles refunds and disputes before you launch, since the protocol does not.
- Judge demand by distinct buyers, not settlement counts. Counts are easy to inflate.
How Qatom approaches the same problem
Qatom takes the other route the research points to: one accountable platform where payment, delivery and the record are a single transaction. It is a platform you sign up to rather than an open protocol you implement, so compare it on that basis.
- Payment and delivery together. A purchase settles USD-TDN, a US-dollar token, between wallets in under one second, and the seller can verify each fulfilment call with its transaction id (seller check).
- Proof that travels with the payment. Each payment is a file built on the TODA file protocol that carries its own history, so it can be verified anywhere, even offline, with no public ledger. See cryptographic proof of payment.
- Spending controls on the buyer side. Agent wallets have their own budget, and purchases above an auto-approve limit wait for the owner's approval.
- No gas and no transaction fees. Qatom charges a flat subscription with a 0% take rate, so there is no gas to sponsor or abuse.
For a side-by-side view of x402, AP2, ACP, Visa, Mastercard and Qatom, read agent payment protocols compared. Risk and security teams can start with proof and assurance.