x402 crossed 100 million cumulative transactions on Base through Q1 2026, according to Chainalysis. Five weeks earlier, the most honest public number anyone had was $0.11: the total revenue one data marketplace operator collected from 1,183 agent probes. Both figures are true. They were reported weeks apart.
That gap is the problem with covering this protocol in articles. An article freezes on its publish date. The protocol does not.
So we stopped writing snapshots and built the record instead. The x402 Adoption Tracker is now live at majormatters.co/x402.
Why a tracker
We have covered x402 since before it had a foundation: the full reference piece on what the protocol is, then the Linux Foundation transfer that gave it a neutral home. Each piece was accurate the day it shipped. Each started aging the day after.
The tracker is a different kind of page. One URL holds the member list, every integration with live and announced kept strictly separate, the real usage numbers, spec status, and the open questions nobody has answered yet. When something material changes, the page changes, and the changelog says exactly what moved. Every entry is fact-checked against a primary source before it lands. No source, no entry.
What the list already shows
The membership tells one story. 23 members, including every card network, and Fireblocks became the first addition since the founding cohort on May 20. The shipping record tells a sharper one. Eight integrations are verified live, and four of them landed in the past five weeks: AWS put x402 execution into Bedrock AgentCore Payments, Arbitrum switched on settlement, Fireblocks shipped its Agentic Payments Suite, and Casper Network stood up a production facilitator on mainnet.
Then the gap. Shopify and Adyen sit on the founding member list, and neither has shipped a consumer-visible x402 payment option. Infrastructure keeps arriving. Merchants keep watching.
The usage data is where it gets interesting. Transactions of $1 or more grew from 49 percent of volume in early 2025 to 95 percent by early 2026, and tester-to-payer conversion improved fourfold in six months. Set that against the $0.11 baseline: the diagnosis then was evaluation friction, agents declining to pay because they could not judge what a resource was worth. The conversion number is the one to watch against that diagnosis, and the tracker will keep watching it. This is the authorization layer of the MM Trust Layer Model playing out in public.
Simon Taylor mapped the protocol stack in his Agentic Payments Map and put the core problem plainly: the internet never got a payment layer. x402 is the leading candidate to become it. The tracker is our running answer to whether it actually does.
How it stays true
We sweep for changes weekly and faster when news warrants. Corrections get owned in the open: the tracker already fixed our own draft's error on the v2 ship date (December 11, 2025, not the foundation launch). Developers who would rather script than scrape can pull the whole dataset from majormatters.co/x402.json.
And if you are building on x402, integrating it, or running traffic through it, we want to hear from you. Entries are fact-checked before publication. That is the whole point.
Sources
What should the tracker watch for next: the first large merchant shipping x402 at checkout, or the first ratified trust-scoring spec?
Charlie Major is a Product Development Manager at Mastercard. The views and opinions expressed in Major Matters are his own and do not represent those of Mastercard.