Agent payment rails, explained

Last verified: 9 August 2026

The question nobody had to answer before

Card networks are built on a chain of accountability. A cardholder authorizes a purchase. A merchant presents evidence of that authorization. A network arbitrates when the two disagree. Every fraud rule, chargeback right, and liability shift in the system assumes a human made a decision at a knowable moment.

An agent breaks that assumption. When an assistant buys a lamp, who authorized it? The customer authorized something — but what, exactly, and how far does it extend? Did they approve this specific purchase, or a budget, or a category? If it goes wrong, who eats it?

That's the problem this entire layer exists to solve. It's not really a payments problem. It's an evidence problem — proving, after the fact and to a skeptical party, that an agent acted within authority a human actually granted.

Everything below is a different answer to that question. This guide is the settlement half of the story; the discovery-and-cart half lives in Agentic commerce protocols, explained.

What changed in 2026: a neutral venue appeared

For most of 2025, every major player had its own approach. Google had one. Visa had one. Mastercard had one. OpenAI and Stripe had one. Each was credible, and none of them interoperated.

On 28 April 2026, Google donated the Agent Payments Protocol to the FIDO Alliance. That's the single most consequential thing that happened in this layer, and it happened quietly.

FIDO immediately stood up two technical working groups:

• Agentic Authentication, chaired by CVS Health, Google, and OpenAI, with vice-chairs from Amazon, Google, and Okta.
• Payments, chaired by Mastercard and Visa.

The card networks now co-chair the payments group. OpenAI chairs the authentication group. Mastercard contributed its Verifiable Intent work into the same venue. FIDO — the organization that standardized passkeys and spent a decade making authentication work across companies that compete — became the neutral ground.

If you were waiting for the agentic payments space to stop being a land grab before you invested, that's the signal. It happened in April.

The pieces

AP2 — Agent Payments Protocol

Google announced AP2 in September 2025 and donated it to FIDO in April 2026. Currently at v0.2, Apache 2.0, with 60+ supporting organizations.

AP2 is built as an extension of A2A, the agent-to-agent communication standard, which means it inherits A2A's identity and messaging model rather than inventing one. It integrates with UCP for commerce flows and supports x402 as an alternative settlement path.

Its core idea is the mandate — a cryptographically verifiable record of what a human actually authorized, which the agent carries and the merchant can check. Not "trust me, the user said yes," but a signed artifact that survives a dispute.

Visa Trusted Agent Protocol (TAP)

Introduced 14 October 2025. Built on HTTP Message Signatures (RFC 9421) and aligned with Web Bot Auth, developed in collaboration with Cloudflare.

TAP uses three signatures that answer three different questions:

• Agent Recognition — is this a known, registered agent, or an anonymous bot?
• Consumer Identity — is there a real, identifiable customer behind it?
• Payment Container — is the payment instrument valid and authorized for this use?

Launch partners included Adyen, Ant International, Checkout.com, Coinbase, Cybersource, Elavon, Fiserv, Microsoft, Nuvei, Shopify, Stripe, and Worldpay. Closed-beta pilots ran through late 2025 in the US, with APAC and Europe following, and a live deployment in the UAE.

One thing to be careful about: Visa has not donated TAP to a standards body. It's published on GitHub and Visa's developer platform, and Visa co-chairs the FIDO Payments working group — but TAP itself remains Visa's. Anyone telling you otherwise is guessing.

Mastercard Agent Pay

Unveiled in April 2025 — earlier than most coverage suggests. It became usable on OpenAI's ACP in late September 2025, starting with Citi and US Bank cardholders, then broadening. Latin America and the Caribbean followed in December 2025.

In June 2026 Mastercard launched Agent Pay for Machines, aimed at a different problem: very high-frequency, low-value transactions between machines. Multi-rail — cards, bank accounts, stablecoins — with 30+ partners including Adyen, Ant International, Checkout.com, Cloudflare, Coinbase, Global Payments, Stripe, and Tempo.

x402 and the machine-payments category

Coinbase originally contributed x402, a protocol that revives HTTP's long-dormant 402 Payment Required status code for machine-to-machine payment.

On 14 July 2026 the x402 Foundation launched under the Linux Foundation with forty member organizations. The premier members are the tell: Adyen, AWS, American Express, Circle, Cloudflare, Coinbase, Fiserv, Google, Mastercard, Monad Foundation, MoonPay, Ripple, Shopify, Solana Foundation, Stellar Development Foundation, Stripe, and Visa.

Separately, Stripe and Tempo shipped the Machine Payments Protocol (MPP) in March 2026. Stripe supports both MPP and x402 through PaymentIntents.

This is a genuinely distinct category from consumer agentic commerce. It's about agents paying for API calls, compute, inference, and data — thousands of tiny transactions where card rails don't economically work. If your business sells anything an agent might consume programmatically, this layer matters to you sooner than the shopping one does.

EMVCo

Worth knowing what hasn't happened. EMVCo — which owns EMV 3-D Secure, payment tokenization, and Secure Remote Commerce — has published no agentic specification. Its stated 2026 plan is to evolve the existing specs to support card-based agentic payments, with a Digital Payment Credentials schema as a priority.

That's meaningful because EMVCo is where card-based standards eventually become mandatory rather than optional. Nothing there yet means the current landscape is still voluntary.

How to think about the layers

These aren't competing for the same slot. Stacked, they look like this:

• Identity and intent — who is the agent, and what did the human actually authorize? AP2 mandates, Visa TAP's three signatures, Mastercard Verifiable Intent, FIDO's working groups.
• Instrument — what payment method, tokenized how, with what liability terms? Mastercard Agent Pay, Visa's payment container, existing network tokenization.
• Settlement — how does value actually move? Card rails for consumer purchases. x402 and MPP for machine-to-machine.

A complete consumer transaction touches all three. A machine-to-machine API payment might skip the middle entirely.

What merchants actually need to do

Almost nothing, urgently — and that's the point. Most of this layer is being built to work without merchants re-platforming. Visa TAP rides on HTTP signatures your infrastructure already speaks. Mastercard Agent Pay works through existing acquirer relationships. AP2 hands off to payment methods you already accept.

The real work is in three places:

Decide your agent policy before someone decides it for you. Do you accept agent-initiated orders? All of them, or only from recognized agents with verified consumer identity? What's your position when an agent-originated order goes into dispute? These are answerable now, and the answers get harder once volume arrives.

Ask your payment provider what they support. Adyen, Stripe, Checkout.com, Worldpay, Fiserv, and Global Payments all appear across the partner lists above. Your provider probably has an agentic roadmap. Most merchants haven't asked.

Watch the fraud and dispute picture, not the protocol picture. The protocols will settle. What won't settle quickly is how liability allocates when an agent buys the wrong thing, or the right thing at the wrong time, or something the customer says they never approved. That's where the cost lands, and it's under-discussed relative to the technical layer. It's also why we treat verification and trust as its own layer of the stack rather than a checkout detail.

What we're watching

Whether FIDO holds. A neutral venue only works if the participants keep using it. Visa keeping TAP proprietary while co-chairing the FIDO payments group is a thing to watch, not a criticism.

Whether EMVCo moves. When card-based agentic payments get an EMVCo specification, the voluntary phase ends and the compliance phase starts. Nothing published yet.

Whether machine payments outgrow consumer payments. The x402 Foundation's member list is more impressive than anything on the consumer side. Agents buying compute and data may end up the larger volume story, and it's getting a fraction of the attention.

Whether anyone solves evidence. There are early efforts at standardizing tamper-evident audit trails across an agentic transaction — discovery through fulfillment. None are mature. But when an agent-originated dispute reaches a real arbitration process, evidence is what the argument will be about.

Sources

Google donates AP2 to the FIDO Alliance · FIDO Alliance: standards for trusted AI agent interactions · ap2-protocol.org · Visa introduces the Trusted Agent Protocol · Visa TAP specifications · Mastercard unveils Agent Pay · Mastercard Agent Pay for Machines · Linux Foundation launches the x402 Foundation · Stripe: Machine Payments Protocol · EMVCo on agentic payments