Mastercard Agent Pay vs Stripe ACP vs Visa Intelligent Commerce vs x402: A 2026 Update
In our January 2026 protocol comparison, the field was three protocols: Stripe, Coinbase, and Google. That is no longer accurate. By March 2026, Mastercard and Visa had both deployed live agentic payment infrastructure — Santander and Mastercard completed Europe’s first live end-to-end agent payment on live bank infrastructure — and the mastercard agent pay comparison now requires a six-way table. This post updates that picture.
The short answer
Six distinct protocols now handle agent-initiated payments: Mastercard Agent Pay, Visa Intelligent Commerce, Stripe ACP, Coinbase x402, Google AP2/UCP, and ATXP. They differ on trust model, crypto support, target user, and deployment status. No single protocol has achieved universal merchant acceptance. Fragmentation is increasing, not consolidating.
The fragmentation is the story. Every major payment network and developer platform now has a position, but they are not interoperable. An agent built for Stripe ACP cannot natively transact on Mastercard Agent Pay. An x402 agent has no path to Visa merchants. Developers building agents that need to transact across ecosystems are being forced to choose — or to use infrastructure that works across all of them.
What Changed Since January 2026
Three things changed in the first quarter of 2026 that make the January landscape obsolete.
Mastercard went live. Agent Pay moved from announced to operational. The Santander-Mastercard transaction — executed on Santander’s live payments infrastructure, not a sandbox — proved the model works at bank grade. Mastercard also launched Agent Suite, a broader toolkit for enterprises integrating agentic commerce.
Visa published its Trusted Agent Protocol. Visa’s collaboration with Cloudflare produced a formal technical protocol for agent identity and authorization, aligned with OpenAI’s Agentic Commerce Protocol. Visa’s Intelligent Commerce initiative now has over 100 global partners and 30 active sandbox builders.
Stripe shipped ACP. Stripe’s agentic commerce suite moved from preview to live. The single-purpose merchant token model is now available to any Stripe developer. The trust model — scope-limited tokens that expire after a single use — is the most developer-accessible option in the field.
The result is a landscape that is more capable and more fragmented simultaneously.
The Six Protocols: Quick Reference
For a full protocol deep dive, see our complete comparison. This table is the March 2026 update.
| Protocol | Launched by | Trust model | Crypto support | Target user | Status |
|---|---|---|---|---|---|
| Mastercard Agent Pay | Mastercard | Verifiable Intent | No | Enterprise/banks | Live |
| Visa Intelligent Commerce | Visa | Agentic Ready program | No | Banks/merchants | Early |
| Stripe ACP | Stripe | SPT merchant tokens | No | Developers | Live |
| Coinbase x402 | Coinbase | Crypto-native | Yes | Crypto builders | Live |
| Google AP2/UCP | A2A authorization | No | Google partners | Beta | |
| ATXP | ATXP | Compatible with all | Yes | Developers | Live |
No protocol covers all cells. Mastercard and Visa have the merchant reach but require bank relationships. Stripe has the developer reach but is Stripe-specific. x402 has the crypto infrastructure but no fiat path. Google AP2 has enterprise scale but is beta and partner-gated. ATXP is the only option in the table with both crypto support and compatibility across the others.
Mastercard Agent Pay: Trust-First, Bank-Grade
Mastercard Agent Pay is built around a single principle: no transaction clears without verifiable proof of authorization. The Verifiable Intent model requires an agent to present a signed record of what it was instructed to do before Mastercard’s network processes the payment. An agent told to book a flight under $400 cannot book a $600 ticket without a new authorization event — the mismatch is detected at the network level, not in application code.
This is enterprise-grade by design. Mastercard is selling to banks, not developers. The integration path runs through financial institution relationships, not API keys. That is a strength for enterprises and a hard barrier for small teams.
The Santander transaction matters because it was not a demo. It ran on Santander’s production payments infrastructure. Enterprise customers evaluating agent payment infrastructure now have a bank-grade reference case.
Visa Intelligent Commerce: Existing Rails, Agentic Ready
Visa’s bet is that agents should use existing payment rails, not new infrastructure. Visa Intelligent Commerce extends Visa’s existing tokenization, security, and merchant network to AI agents without requiring agents to interact with new systems. If a merchant already accepts Visa, they can accept Visa agent payments.
The Trusted Agent Protocol, co-developed with Cloudflare, handles identity and authorization at the protocol level. Visa has aligned it with OpenAI’s Agentic Commerce Protocol and x402 — a meaningful commitment to interoperability that Mastercard has not yet matched.
The early-stage designation in the table reflects real limitations. Sandbox participants are active but wide deployment is months away. Visa’s global merchant network is the long-term advantage; the short-term gap is that the agent-specific infrastructure is still being built on top of it.
Stripe ACP vs Coinbase x402: The Developer Choices
These two are the practical options for developers building agents today who do not have bank relationships and need something that works now.
Read our Stripe ACP breakdown and how x402 works for full technical detail. The short version:
Stripe ACP issues single-purpose tokens (SPTs) scoped to one merchant, one session, one amount range. An agent shopping on a Stripe-enabled merchant gets a token that has no value outside that context. The trust model is scope limitation rather than behavioral verification. It is clean, developer-friendly, and entirely within the Stripe ecosystem.
Coinbase x402 uses the HTTP 402 status code — “payment required” — to gate API access behind onchain micropayments. An agent hits an endpoint, receives a 402 with a payment address and amount, pays from its crypto wallet, and gets access. No fiat rails, no bank relationship, no form to fill out. The fastest path to agent-to-agent payments is x402.
The two protocols serve different use cases. Stripe ACP is for agents transacting with human-facing merchants. x402 is for agents transacting with other APIs and services. They are complementary, not competitive — which is why both appear in ATXP’s compatibility layer.
| Feature | Stripe ACP | Coinbase x402 |
|---|---|---|
| Token type | Single-purpose merchant token | Crypto payment |
| Fiat support | Yes | No (crypto-native) |
| Merchant coverage | Stripe merchants | x402-enabled APIs |
| Developer setup | Stripe API | Open protocol |
| Best for | Consumer merchant transactions | API access, agent-to-agent |
Google AP2/UCP: The Infrastructure Play
Google AP2 explained covers the technical architecture. The summary: Google’s Agent-to-Agent (A2A) protocol and Universal Commerce Protocol (UCP) target the infrastructure layer — how agents authenticate with each other and with services, not specifically how payments clear.
AP2/UCP is in beta, gated by Google partnership, and not yet available for arbitrary developer use. The long-term play is that Google’s ecosystem — Workspace, Cloud, Search — creates enough surface area that AP2/UCP becomes the de facto standard for agents operating within Google’s orbit. Whether that orbit is large enough to matter outside Google partnerships is the open question.
For developers building outside the Google ecosystem, AP2/UCP is not yet a practical choice. Watch it.
Why ATXP Sits Above All of Them
Protocol fragmentation is not a problem that will be solved by one protocol winning. Mastercard serves banks; x402 serves crypto developers; Stripe serves its own merchant ecosystem. These are different markets with different requirements. The winner of the bank market will not displace the winner of the crypto-native API market.
That fragmentation makes compatibility more valuable, not less. An agent that can only transact via Stripe ACP is locked out of any merchant or service that does not use Stripe. An agent built on ATXP credits can transact via x402, virtual cards, and any payment method the merchant accepts — without the agent needing to know which protocol is in play.
As Kenny, ATXP’s co-founder, puts it: “We partner with x402 and virtual cards — ATXP can be leveraged across all payment methods. That’s the point of being compatible with and partnering with everyone.”
That position gets stronger as fragmentation increases. In January 2026, there were three protocols. In March 2026, there are six. There is no sign that this converges to one before Mastercard and Visa finish competing with each other, let alone before x402 and Stripe settle their respective ecosystems. Developers who want their agents to work across all of them need an abstraction layer, not a bet on one protocol.
Orium’s analysis of agentic payments reaches a similar conclusion: the practical engineering challenge for 2026 is building agent payment logic that does not need to be rewritten every time a new protocol enters the field.
ATXP credits are that layer. They are not a new protocol competing with Mastercard or Stripe. They are the account and budget infrastructure that sits above all protocols and routes through whichever payment method the downstream counterparty accepts.
FAQ
What is Mastercard Agent Pay? Mastercard Agent Pay is an enterprise-grade agent payment system using tokenization and Verifiable Intent — agents must present proof of authorization before a transaction clears. It is live and designed for bank and enterprise deployments. Santander completed Europe’s first live end-to-end agent payment using it in March 2026.
How does Stripe ACP work? Stripe ACP issues single-purpose merchant tokens (SPTs) scoped to a specific merchant, session, and amount. An agent gets a token that has no value outside that context. It is developer-friendly and integrates with Stripe’s existing API. It does not support crypto and is limited to Stripe-enabled merchants.
Can I use multiple agent payment protocols in one agent? Technically yes, but practically complex. Each protocol has different integration requirements, trust models, and credential types. Most teams will choose one protocol and accept the coverage limitations, or use an abstraction layer — like ATXP — that handles the protocol routing automatically.
Is x402 production-ready in 2026? Yes. Coinbase launched x402 as an open protocol and it is live. It handles agent-to-API payments via crypto micropayments at the HTTP level. It is production-ready for developers building in the crypto-native or API-access use case. It is not a path to fiat merchant payments.
What is Visa’s Trusted Agent Protocol? Visa’s Trusted Agent Protocol, developed with Cloudflare, handles agent identity and authorization for Visa Intelligent Commerce. It is aligned with OpenAI’s Agentic Commerce Protocol and x402. It is currently in early deployment with partner banks and merchants, with broad availability expected later in 2026.