The x402 Adoption Tracker
Every member, every shipped integration, every spec proposal, every real-world transaction I can verify. The canonical list, because nobody else is keeping one.
Last updated October 21, 2026I update when material changes land, and sweep at least monthly. See the changelog.
The x402 protocol is moving fast enough that by the time press releases reach the news feeds, the state of the world has already shifted. This page is my attempt to keep a single reference that reflects what is actually true today, not what was announced three weeks ago. It is a companion to my full x402 reference piece, which explains what the protocol is and why it matters. This page is for the question that reference piece does not answer: who is actually building on it.
Members
Confirmed members of the x402 Foundation. A member appears here only when the membership is verifiable against a primary source.
| Member | Category | Joined | Notes | Source |
|---|---|---|---|---|
| CoinbaseFounding | Crypto infrastructure | April 2, 2026 | Original protocol contributor and reference implementation maintainer. | Source |
| CloudflareFounding | Internet infrastructure | April 2, 2026 | Co-developer; shipped native x402 transaction support on Cloudflare Workers. | Source |
| StripeFounding | Payment processor | April 2, 2026 | Premier member and one of three organizations on the Technical Steering Committee (with Coinbase and Cloudflare). Stripe documents x402 acceptance in USDC on Base. Stripe and Tempo also co-author the Machine Payments Protocol (MPP), launched March 18, 2026; MPP's FAQ says the core x402 'exact' flows map directly onto MPP's charge intent. | Source |
| VisaFounding | Card network | April 2, 2026 | Premier member. In the Linux Foundation's July 14, 2026 release, Visa said: "By supporting the x402 Foundation, Visa is helping advance an ecosystem where agents can transact securely across platforms, networks, and payment types." Visa also maintains its Trusted Agent Protocol. | Source |
| MastercardFounding | Card network | April 2, 2026 | Premier member. In the Linux Foundation's July 14, 2026 release, Mastercard said: "Through Mastercard Agent Pay for Machines and our work with the x402 Foundation, we're helping shape an open, collaborative ecosystem that enables enterprise adoption and unlocks machine payments at scale." | Source |
| American ExpressFounding | Card network | April 2, 2026 | Premier member. In the Linux Foundation's July 14, 2026 release, American Express said it "is pleased to continue supporting open, interoperable standards for internet-native payments." | Source |
| GoogleFounding | Platform / AI | April 2, 2026 | Premier member per the July 14, 2026 release. Google also develops the Agent Payments Protocol (AP2). | Source |
| Amazon Web ServicesFounding | Cloud infrastructure | April 2, 2026 | Published an industry blog on x402 and agentic commerce. | Source |
| ShopifyFounding | Commerce platform | April 2, 2026 | Premier member per the July 14, 2026 release. | Source |
| AdyenFounding | Payment processor | April 2, 2026 | Premier member per the July 14, 2026 release. | Source |
| Fiserv Merchant SolutionsFounding | Acquirer / processor | April 2, 2026 | Acquirer-side founding member. | Source |
| KakaoPayFounding | Wallet / payments (APAC) | April 2, 2026 | General member per the July 14, 2026 release. | Source |
| CircleFounding | Stablecoin issuer | April 2, 2026 | Premier member. Issuer of USDC. TRM Labs (September 9, 2026) found 99.6 percent of x402 value it analyzed settled in USDC. | Source |
| Solana FoundationFounding | L1 / payments chain | April 2, 2026 | Joined initiative to push web-native payments support. | Source |
| Polygon LabsFounding | L2 / scaling | April 2, 2026 | Multi-chain settlement option. | Source |
| Merit SystemsFounding | Software / standards | April 2, 2026 | Founding contributor. | Source |
Integrations
Live means verified running in production, not an announcement. Announced means a public commitment with no shipped product yet.
| Company | Product | What it does | Status | Source |
|---|---|---|---|---|
| Nevermined | Agent payment flow | Ties x402 to Visa Intelligent Commerce with VGS tokenization for agent-originated card payments. | Live April 17, 2026 | MM coverage |
| Bankr | x402 Cloud | Hosted infrastructure for x402-enabled APIs and agent-originated payments. Launched on 4/02 day alongside the Linux Foundation transfer. | Live April 2, 2026 | Chainwire announcement |
| Cloudflare | Native x402 transaction support | Cloudflare Workers can now serve and accept x402 payments natively. | Live April 2, 2026 | Cloudflare blog |
| Independent data marketplace operators | Several | Agent-accessible data APIs with 402 gating, stablecoin settlement on L2. | Live, small volume | Operator-reported |
| Amazon Web Services | Bedrock AgentCore Payments | Native x402 payment execution for Bedrock agents: managed wallet provisioning, policy-based per-agent and per-session spending limits, audit trails tied to agent reasoning traces. When an agent hits an HTTP 402, AgentCore evaluates the terms, authorizes the USDC micropayment, and resubmits the request. | Live, in preview May 7, 2026 | AWS Industries blog |
| Arbitrum | x402 on Arbitrum | x402 settlement live on Arbitrum: agents pay for APIs, services, and software directly with stablecoins. | Live May 15, 2026 | Arbitrum via X (secondary report) |
| Fireblocks | Agentic Payments Suite | Agentic Payments Gateway gives payment service providers stablecoin merchant acceptance; Agentic Wallets let users delegate transactions to agents within defined limits. Agora's AUSD stablecoin is already running on the stack. | Live May 20, 2026 | PR Newswire |
| Casper Network | Casper AI Toolkit | Production x402 facilitator on mainnet. Casper describes itself as the first WebAssembly-native blockchain with live x402 payments. The toolkit also bundles MCP access and agent skills. Casper is an Associate member of the x402 Foundation, and a Casper exact-scheme spec was merged into the Foundation repository on July 8, 2026. | Live June 4, 2026 | Chainwire |
| Amazon Web Services | CloudFront + WAF x402 (publisher monetization) | Any site already fronted by Amazon CloudFront and AWS WAF can charge AI agents per request in USDC, settled via x402 on Base. An agent request returns an HTTP 402 with payment terms; the agent pays, the x402 facilitator verifies the payment onchain, and the content is served inside a single request-response cycle, with no accounts, invoices, or API keys. Publishers turn it on as a CloudFront and WAF configuration change rather than a code rewrite. This is the publisher (seller) side of x402, complementing the agent (buyer) side that Bedrock AgentCore Payments handles. | Generally available June 15, 2026 | AWS Industries blog; thirdweb (builder detail) |
| Injective | x402 on Injective | Lets AI agents parse payment terms and settle service fees on the Injective chain before proceeding with a service call. | Announced by Injective; production usage not verified at this update. Injective is a General member of the x402 Foundation per the July 14, 2026 release. | Injective (via KuCoin) |
| Cloudflare | Monetization Gateway | Announced July 1, 2026. Cloudflare describes it as an engine that will let its customers charge for any asset protected by Cloudflare: web pages, datasets, APIs, or MCP tools. Cloudflare says that at launch payments will settle in stablecoins over x402, and names Open USD and USDC as examples. | Waitlist open for Cloudflare customers; no general availability date given. July 1, 2026 | Cloudflare blog |
| Stripe | Machine payments: x402 on Base | Stripe's documentation says it supports stablecoin payments over the x402 protocol in USDC on Base. The seller's server returns an HTTP 402 with a Stripe deposit address, the Coinbase Developer Platform facilitator settles the payment onchain, and Stripe records it as a PaymentIntent. Stripe's docs state that machine payments work best with its Machine Payments Protocol (MPP), which also accepts cards. | Documented by Stripe; requires the 2026-05-27.preview API version and approval of the Stablecoins and Crypto payment method. Available to US businesses except in New York, and on request in 30+ other countries. Docs are undated; checked September 18, 2026. | Stripe documentation |
| Ripple | x402 on the XRP Ledger (XRPL AI Starter Kit) | Ripple's June 9, 2026 post says that, through a contribution from t54, the XRP Ledger is a supported chain in x402 and that XRPL agents can pay for API calls, model inference, and other services in XRP or RLUSD. An XRPL exact-scheme specification was merged into the x402 Foundation repository on July 3, 2026. | Live per Ripple. The starter kit tutorial runs on testnet; mainnet usage not independently verified. June 9, 2026 | Ripple Insights; x402 Foundation GitHub |
| GigSoul | Pay-per-call agent endpoints at api.gigsoul.com (30 endpoints) | GigSoul publishes an x402 manifest at api.gigsoul.com/.well-known/x402.json listing 30 pay-per-call endpoints priced $0.005 to $2.00 in USDC on Base (eip155:8453), settling through the Coinbase Developer Platform facilitator. One endpoint, verify-deliverable-and-issue-acceptance-receipt ($0.10), returns ACCEPT, REJECT or REVIEW with reason codes for an agent-to-agent purchase. The seller is the first on this tracker to describe itself as operated by AI with human oversight. At its request the operator is listed as "Jackson, the AI that runs GigSoul"; the human overseer's name and entity are withheld at the operator's request, and no company registration or location is published. The operator wrote to Major Matters on October 3, 2026 after reading this tracker, and the entry was checked against the manifest and the settlement feed. | Live, no customer volume: gigsoul.com/calls lists 51 settlements totaling $5.78 since September 19, 2026, all the operator's own QA calls from its verification wallet. Operator listed as "Jackson, the AI that runs GigSoul" at its request; the human overseer is not named. October 3, 2026 | GigSoul x402 manifest; gigsoul.com/calls |
Real-world usage data
The most honest account of what x402 traffic actually looks like today.
Cumulative transactions on Base. Chainalysis counts more than 138 million x402 transactions on Base by the end of its Q3 2026 window, up from about 1,500 in mid-2025 and 100 million through Q1 2026. Over 87 percent of payments fall between a hundredth of a cent and a dime, with the most common size between one and ten cents. The median wallet was 73 days old at its first x402 payment in late 2025 and 18 minutes old by Q3 2026. American wallets account for 88.1 percent of geolocated model-inference payments on the protocol. Raw protocol counts, not adjusted for scripts or self-dealing; read alongside the TRM Labs filtering above.
Share of screened payment value that appears agentic (TRM Labs). TRM Labs identified roughly $52.7 million across 198.9 million settlement transactions through known x402 facilitators on Base, Solana, and Polygon since May 2025. After removing self-payments, bulk flows from one or two payers, and sellers with fewer than 10 distinct buyers, $25.62 million remained. TRM then applied two tests. The permissive test counts any payer whose payments were broadcast by a facilitator, averaged under a dollar, and varied in price. The strict test also requires the pattern to persist across months and the payer to be registered in a public agent registry (ERC-8004) or to have paid more than one seller. TRM puts agent-moved volume at roughly $5,000 to $11,000 a month in 2026, and says its method "may understate the space" because single-purpose agents would read as scripts. TRM also reports 99.6 percent of value settled in USDC.
Adjusted cumulative volume (Visa and Artemis). Visa's summary of its joint report with Artemis says x402 "has processed roughly $15.0 million in adjusted volume across 109.6 million transactions" since May 2025, and that the average payment is a fraction of a cent. Adjusted totals exclude identified wash and test activity. The full report gives the raw onchain totals for the same date as $135.7 million across 178.3 million transactions. Most activity was on Base, Solana, and Polygon.
Cumulative transactions on Base. Growth surged in Q4 2025, driven largely by meme coin activity (notably PING), then moderated in early 2026. Chainalysis is direct that mass adoption remains distant and that current participants are mostly crypto-native.
30-day value transferred. Sellers grew 23 percent and buyers grew 37 percent over the same window.
Tester-to-payer conversion. The historical baseline worth keeping: in late Q1 2026 a single independent data marketplace reported 1,183 agent probes, 5 settlements, and $0.11 of revenue. The bounce diagnosis then was evaluation friction, not payment friction: agents declining to pay because they cannot judge whether a resource is worth the cost. The improving conversion rate is the number to watch against that diagnosis.
Real daily volume (independent onchain analysis). Artemis classified roughly half of observed x402 transactions as artificial: "self-dealing" (one wallet as both buyer and seller) and wash trading (the seller funds the buyer, which sends the money straight back). The same snapshot showed about 131,000 daily transactions averaging $0.20. The July 2026 Visa and Artemis report, listed above, is the successor series: it publishes adjusted totals that exclude identified wash and test activity.
Spec status
Ratified
- Core request-response handshake. HTTP 402 response, payment payload in header, resource returned. Ratified in v2. Source
- Wallet-based identity. For both clients and resource servers. Ratified in v2. Source
- Automatic API discovery. Ratified in v2. Source
- Dynamic payment recipients. Ratified in v2. Source
- Additional chains and fiat via CAIP standards. Ratified in v2. Source
- Modular SDK for custom networks and payment schemes. Ratified in v2. Source
- Batch Settlement. Unchanged, but the sourceUrl https://www.x402.org/writing now returns 404. Replace with https://x402.org/x402-batch-settlement/. A Solana (SVM) batch-settlement spec was added August 21, 2026. Source
In active development
- Receipt and settlement reference formats. A signed Offer and Receipt extension is in the Foundation repository as an optional extension (added March 12, 2026; signer-authorization clarification merged July 23, 2026). The document says wire shape and field placement 'are not considered stable'. Source
- Multi-currency payment option encoding refinements.
- Implementation guides for non-EVM chains. Exact-scheme specifications merged into the Foundation repository during this window: XRPL (July 3, 2026), Casper (July 8), Starknet (July 24), Canton (August 7). A Solana (SVM) batch-settlement specification was added August 21. Earlier non-EVM specs in the repository include Solana, Sui, Aptos, Algorand, Stellar, Hedera, Keeta, Cardano, TON, NEAR, and Concordium. Source
- Auth-capture payment scheme. The client authorizes a maximum amount; the payment can then be captured for less, voided, refunded, or reclaimed by the client after a deadline. Specification files have been in the Foundation repository since May 20, 2026, and version 1.1 was merged on August 25, 2026. EVM binding only. The repository does not label scheme specifications as ratified. Source
- Upto payment scheme. A scheme for payments up to an authorized ceiling. The EVM specification was added on March 4, 2026; Solana (SVM) delegated-authorization work was merged on September 3 and 9, 2026. Source
Open proposals
- Trust-scoring layer (sometimes referenced as x407). Two extension proposals are open as issues in the Foundation repository: a behavioral trust-provider hook (#2299, opened May 14, 2026) and a DID-based agent-trust extension (#1777, opened March 23, 2026). Neither has a merged spec. A repository search for 'x407' returns nothing. Source
Early discussion
- Dispute resolution framework. Still no framework. Open issues include 'Correctness/dispute layer as the missing piece downstream of settlement' (#2887, July 17, 2026) and 'Dispute evidence for agent-initiated payments' (#3500, September 16, 2026). Separately, the auth-capture payment scheme in the repository defines void, refund, and reclaim operations (spec v1.1 merged August 25, 2026). Source
- Liability framework for agent-side errors. Regulatory, not protocol-scope, but being discussed.
Open questions and gaps
- Trust scoring. Still no merged trust-scoring spec. Two extension proposals are open in the Foundation repository (#2299 behavioral trust provider, #1777 DID-based agent trust). The Offer and Receipt extension lists 'verifiable proof of commercial interactions for reputation systems' as a use case.
- Stablecoin dependency. TRM Labs (September 9, 2026) found 99.6 percent of the x402 value it analyzed settled in USDC. Other assets now named by members: XRP and RLUSD (Ripple), Open USD (Cloudflare Monetization Gateway, announced), AUSD (Fireblocks stack).
- Dispute resolution. No arbitration framework and no Reg E equivalent. The auth-capture scheme in the Foundation repository (v1.1, August 25, 2026) adds void, refund, and client reclaim operations at the protocol level, and two dispute-layer issues are open (#2887, #3500).
- Liability for bad agent behavior. Hijacked, prompt-injected, or misconfigured agents. Nobody has taken a position.
- Merchant adoption. I found no primary source showing a large merchant offering x402 as a consumer-visible payment option. Seller-side tooling has widened: AWS CloudFront and WAF (generally available), Stripe machine payments (x402 on Base, preview API), and Cloudflare's Monetization Gateway (waitlist). The Merchant Advisory Group has joined the Foundation as an Associate member.
Changelog
Related reading
- The x402 Adoption Tracker Is Live
- What x402 Actually Is, and Why It Is the Internet's First Payment Layer
- The Internet Just Got a Payment Layer. No Card Network Required.
- The Agentic Commerce Protocol Map: Q1 2026
- Nevermined Just Shipped What Everyone Else Is Still Announcing: AI Agents That Pay With Cards
- x402: The Internet Just Got a Payment Button. AI Agents Are Already Using It.
If you are building on x402, integrating it, or running traffic through it, I would like to know. Tracker entries are fact-checked before publication. Get in touch.
This tracker is also available as raw data at majormatters.co/x402.json. Cite freely with a link back to this page.
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.