Agentspay

Explainer

Visa Intelligent Commerce vs Mastercard Agent Pay: Agentic Payments Networks Compared

Visa Intelligent Commerce and Mastercard Agent Pay are the two big card networks racing to let AI agents pay. They take different routes to the same idea, and neither one decides whether a given purchase should have happened.

Last updated July 2026

Agent Payments Console

Pick an agent

Payment intent

intent:

Policy evaluation

Human approval required

This spend is over your approval threshold. Approve it to issue a scoped card, or deny it.

Scoped virtual card issued

Agentspay

single-use

Wallet budget

spent of

Audit trail

In short

Visa Intelligent Commerce and Mastercard Agent Pay are the two major card networks programs for letting AI agents make payments. Both issue scoped, tokenized credentials an agent uses at checkout, and both added machine-to-machine payments in June 2026. Visa leads with a single integration across four agent protocols; Mastercard leads with agent-to-agent settlement across cards, bank accounts and stablecoins. Neither one decides whether an agent was allowed to spend.

What Visa Intelligent Commerce is

Visa Intelligent Commerce is Visa program for letting AI agents pay with a Visa credential inside an agent experience. First announced in April 2025, it expanded in June 2026 with Intelligent Commerce Connect, a single integration through the Visa Acceptance Platform that gives merchants, agent builders and payment enablers one place to plug in. It handles payment initiation, tokenization, spend controls and authentication. The design choice Visa is pushing hardest is breadth of interoperability: Intelligent Commerce Connect supports payments initiated through four agent protocols (the Trusted Agent Protocol, the Machine Payments Protocol, the Agentic Commerce Protocol and the Universal Commerce Protocol) and can route transactions across both Visa and non-Visa cards. Visa also plugged its network into ChatGPT in June 2026, so an agent can complete a purchase at any Visa-accepting merchant. The credential an agent receives is a Visa-tokenized, merchant-specific token with scoped permissions, so a token minted for a flight is only usable with that airline for that trip window.

What Mastercard Agent Pay is

Mastercard Agent Pay is Mastercard agentic payments program, announced in April 2025 and built on Mastercard Agentic Tokens. Those tokens extend the same tokenization that already powers contactless, secure card-on-file and Payment Passkeys, so the trust model is familiar to issuers. Citi and US Bank were the first issuing banks to support it, with the program expanding through 2026. In June 2026 Mastercard added Agent Pay for Machines, a service that lets AI agents and connected systems pay one another automatically across the network, with some payments as small as fractions of a cent. Mastercard leaned into ecosystem breadth on the settlement side: more than 30 partners signed on, including Stripe, Adyen, Coinbase, Cloudflare, OKX, Ripple, Polygon and Solana, and settlement is supported across cards, bank accounts and stablecoins. Where Visa is emphasizing one integration across many protocols, Mastercard is emphasizing many rails a machine payment can settle over.

Where the two programs actually differ

On the fundamentals they rhyme. Both are card-network programs, both replace raw card numbers with scoped agentic tokens, both launched their agentic effort in April 2025, and both shipped machine-to-machine capabilities on the same day in June 2026. The differences are in emphasis. Visa Intelligent Commerce is positioned as one integration that speaks four agent protocols and reaches any Visa-accepting merchant, which is attractive if your priority is checkout coverage across the open standards. Mastercard Agent Pay is positioned around agent-to-agent settlement and a wide set of partners and settlement rails including stablecoins, which is attractive if your priority is machines paying machines for API calls, data and compute at high frequency. Neither is a walled garden: both can touch non-native cards, and both intend to interoperate with the emerging protocol stack rather than replace it.

What both networks give you, and what neither does

Both programs solve the credential problem well. An agent no longer needs a real card number pasted into a config file; it gets a token scoped to a merchant, an amount or a window, which is a genuine security upgrade. What neither program solves is the buy-side decision. Visa and Mastercard tell a merchant how to accept an agent payment and how to tokenize it. They do not tell the company whose agents are doing the buying which agent may spend, up to what amount, with which counterparties, how often, and who has to approve above a threshold. That is not a gap in their design; it is out of scope by design, because those are your policies, not the network policies. The risk is that a protocol-compliant, correctly tokenized transaction can still be a purchase you never wanted, made by an agent that looped on a retry, misread a quantity, or was steered by prompt injection.

Agentic tokens versus a shared corporate card

The honest comparison is not Visa versus Mastercard; it is either agentic-token program versus what most teams do today, which is hand an agent a shared corporate card number. On that comparison both networks win decisively. A shared card gives every agent the full credit line, no per-agent attribution, and a card statement at month end that nobody can reconcile to a specific process. A scoped agentic token limits blast radius and keeps the real number out of the agent context. But a token scoped to a merchant is not the same as a budget. It caps what one credential can do at one seller; it does not cap what a fleet of agents can spend across many sellers, nor does it pause anything for a human when an agent tries to renew a contract or buy compute far outside its normal pattern. That is where a control plane comes in.

How Agentspay governs spend on either rail

Agentspay is the rail-neutral control plane that sits in front of whichever network moves the money. You do not pick Visa or Mastercard and inherit their governance; you keep one policy layer that works across both. Every agent gets its own funded wallet with hard limits instead of a slice of a shared card. Each intended purchase is checked against policy before a credential exists: per-transaction ceiling, budget over a window, merchant allowlist, velocity rules. Spend above your threshold pauses for a human approval instead of going through. The agent then receives a scoped virtual card or delegated credential valid for that one purchase, riding Visa or Mastercard rails underneath, and every decision lands in an immutable audit trail tied to the agent, its human owner, the intent and the policy that allowed it. Adopt the network program that fits your merchants and settlement needs, and keep one place that never moves money without policy. The same logic applies whether the buyer is a shopping agent or a procurement agent.

Whatever standard moves the money, Agentspay is the rail-neutral control plane that keeps it governed. See how it works and the control surfaces that enforce policy, approvals, and audit on every transaction.

Side by side

Visa Intelligent Commerce vs Mastercard Agent Pay

How the two card-network agentic programs compare, and where a buy-side control plane still fits.

Dimension Visa Intelligent Commerce Mastercard Agent Pay
First announced April 2025, Intelligent Commerce Connect added June 2026. April 2025, Agent Pay for Machines added June 2026.
Core credential Visa-tokenized, merchant-specific tokens with scoped permissions. Mastercard Agentic Tokens, built on existing tokenization.
Emphasis One integration across four agent protocols; any Visa-accepting merchant. Agent-to-agent settlement and a wide partner and rail set.
Settlement rails Card rails, can route Visa and non-Visa cards. Cards, bank accounts and stablecoins.
Machine-to-machine Supported via the Machine Payments Protocol. Agent Pay for Machines, payments down to fractions of a cent.
Buy-side spend limits Out of scope; token scope is not a fleet budget. Out of scope; token scope is not a fleet budget.
Human approval and audit Not provided by the network. Not provided by the network.

Frequently asked

Questions people ask about Visa Intelligent Commerce vs Mastercard Agent Pay

What is Visa Intelligent Commerce?

Visa Intelligent Commerce is Visa program for letting AI agents pay with a Visa credential. Through Intelligent Commerce Connect, a single integration on the Visa Acceptance Platform, it handles payment initiation, tokenization, spend controls and authentication, supports four agent protocols, and lets an agent complete a purchase at any Visa-accepting merchant using a scoped, merchant-specific token.

What is Mastercard Agent Pay?

Mastercard Agent Pay is Mastercard agentic payments program, built on Mastercard Agentic Tokens that extend its existing tokenization. Citi and US Bank were the first issuing banks. In June 2026 it added Agent Pay for Machines, letting AI agents and connected systems pay one another automatically across cards, bank accounts and stablecoins, with some payments as small as fractions of a cent.

What is the difference between Visa Intelligent Commerce and Mastercard Agent Pay?

Both are card-network programs that give AI agents scoped, tokenized credentials, and both launched in April 2025 with machine-to-machine features added in June 2026. Visa emphasizes one integration across four agent protocols and reach across any Visa-accepting merchant. Mastercard emphasizes agent-to-agent settlement and a wide partner set that settles across cards, bank accounts and stablecoins.

Can AI agents pay with a credit card?

Yes. Both Visa Intelligent Commerce and Mastercard Agent Pay let an AI agent pay with a card by issuing a scoped, tokenized version of it rather than the real number. The token is limited to a merchant, amount or window, so it is safer than pasting a card into an agent config. It still does not enforce a per-agent budget or require human approval on its own.

Are agentic payments safe?

Agentic tokens make the credential safer, because a scoped token limits what a single payment can do if it leaks. They do not make the spending safe on their own. An agent can still complete a fully compliant, correctly tokenized purchase it should never have made. Safety at the business level comes from spend limits, merchant allowlists, velocity caps, human approval above a threshold and an audit trail.

Do Visa and Mastercard agent payments stop overspending?

No. Both networks scope a token to a merchant or a transaction, but that is not a fleet budget. Neither program decides which of your agents may spend, up to what total, or who signs off above a threshold, because those are buy-side policies. If your agents are the ones spending, you need a control plane that enforces policy and pauses for approval before any credential is issued.

Keep reading

More explainers

Agentic payments

Agentic Payments

Agentic payments move money with no human at the checkout. The rails to do it all shipped during 2026. The part most teams have not solved is deciding, before the money moves, whether the agent was allowed to spend it.

Read

Agent payment platforms

AI Agent Payment Platforms

Five different kinds of product now call themselves an AI agent payment platform, and they solve five different problems. Picking the wrong category is the expensive mistake, not picking the wrong vendor inside a category.

Read

Universal Commerce Protocol

the Universal Commerce Protocol (UCP)

Google and Shopify shipped UCP as an open standard so an AI agent can check out at any merchant that supports it. Here is what the specification actually defines, where it is live for US buyers, and the one thing it deliberately leaves to you.

Read

MCP Payments

MCP Payments

MCP payments are how an AI agent discovers a payment tool and calls it to move money. The catch: the Model Context Protocol carries the tool call, not the spending decision, so nothing in the stack asks whether the purchase should have happened.

Read

Agentic Commerce Protocol

the Agentic Commerce Protocol

ACP is the open standard behind agentic checkout in ChatGPT. It tells a merchant how to sell to an AI agent. It says nothing about whether your agent should have made the purchase.

Read

AP2 vs ACP vs x402

AP2 vs ACP vs x402

AP2, ACP, and x402 are the three standards shaping how AI agents pay. They solve different layers of the problem, and most real systems will touch more than one.

Read

Machine payments protocol

Machine payments protocol

As software starts paying software, machine payments protocols define how value moves without a human at the keyboard. The harder question is how to keep that spending governed.

Read

Know Your Agent (KYA)

Know Your Agent

KYA, or Know Your Agent, extends the idea of customer due diligence to autonomous software. When an agent spends, you need to know which agent, on whose authority, and under what limits.

Read

Keep agent spending governed

Add policy, hard limits, human approval, and an immutable audit trail across any protocol or rail. Start in the sandbox today.

Never moves money without policy