Skip to content

Mastercard Agent Pay

Mastercard's agentic payments program: Agentic Tokens, agent registration, the Agent Pay Acceptance Framework, Verifiable Intent, trust services and partners.

Updated October 4, 2026 5 min read .md

In short: Mastercard Agent Pay is Mastercard’s program for letting registered AI agents pay with a cardholder’s Mastercard credential within limits the cardholder sets. It uses Agentic Tokens, which are network tokens bound to a specific agent. Merchants recognize agents through the Agent Pay Acceptance Framework, which builds on Web Bot Auth. In 2026 Mastercard added Verifiable Intent, an open record of what the user authorized, and trust services such as a score estimating whether a transaction was agent-initiated.

Origins

Mastercard announced Agent Pay on April 29, 2025. Launch partners included Microsoft (Azure OpenAI Service and Copilot Studio), IBM (watsonx Orchestrate, for business-to-business use) and the processors Braintree and Checkout.com. The program was presented as three pieces: Agentic Tokens, registration and verification of agents before they can pay, and consumer authentication, including on-device biometrics.

Agentic Tokens

An Agentic Token extends Mastercard’s existing network tokenization through the Mastercard Digital Enablement Service (MDES). In ordinary tokenization a card number is replaced by a token tied to one device or merchant. Agentic Tokens are tied to an AI agent, and the cardholder’s controls (for example spending limits or merchant scope) apply to them.

Because they run on existing tokenization and authorization rails, merchants and acquirers receive them as standard tokenized card transactions. The agent never sees the real card number, and the cardholder or issuer can revoke the token without reissuing the card.

Agent registration and the Acceptance Framework

Before an agent can transact, it must be registered and verified by Mastercard. Registration links the agent to a known operator and to cryptographic keys.

On October 16, 2025 Mastercard introduced the Agent Pay Acceptance Framework, which helps merchants recognize registered agents with little or no code. It is built on Web Bot Auth, which uses HTTP Message Signatures (RFC 9421), and was developed in collaboration with Cloudflare:

  • Registered agents sign their HTTP requests to merchant sites. Mastercard hosts a directory of agent public keys.
  • A tag in the signature shows whether the agent is browsing or paying, so a merchant can apply different policies to each.
  • A nonce and timestamps guard against replayed requests.
  • Merchants, or their CDN, bot-management provider or processor, verify the signature to separate registered agents from unknown bots.

Visa’s Trusted Agent Protocol uses the same underlying mechanism, so edge providers can check both with one verification approach.

Verifiable Intent

On March 5, 2026 Mastercard introduced Verifiable Intent, an open-source, standards-based framework co-developed with Google. It creates a tamper-resistant record that links three things:

  1. the consumer’s identity
  2. the instructions the consumer gave the agent
  3. the outcome of the transaction

It uses selective disclosure, so each party (merchant, issuer, network) sees only the information it needs. It builds on specifications from the FIDO Alliance, EMVCo, the IETF and the W3C, and is designed to work with Google’s AP2 and UCP. The problem it addresses is that an agent may act hours or days after the user’s instruction. When that happens, a signed record of the instruction becomes the main evidence in a dispute. Launch collaborators included Google, Fiserv, IBM, Checkout.com, Basis Theory and Getnet. On April 28, 2026 Mastercard contributed Verifiable Intent to the FIDO Alliance, alongside Google’s contribution of AP2.

Trust services

On September 30, 2026 Mastercard added risk services to Agent Pay:

  • a probability score estimating how likely it is that a transaction was started by an AI agent, being tested in the US
  • trust and intelligence signals that flag unusual agent activity for review
  • an Agent Pay Trust Framework that combines identity, intent, behavior and fraud insights to inform authorization decisions

The score is useful because not all agent traffic will be registered or tokenized. Issuers and merchants need a way to estimate agent involvement even when nothing declares it.

Agent Pay for Machines

On June 10, 2026 Mastercard announced Agent Pay for Machines, aimed at payments between agents and small machine-to-machine payments. According to Fortune, it records the permissions a human has granted an agent on public blockchains (Polygon, Solana and Base), so multiple parties can check that the agent stays within them. Adyen, Coinbase and Cloudflare were named as collaborators. This places Mastercard alongside x402 and Stripe and Tempo’s Machine Payments Protocol in the machine-payments space.

Rollout and partners

DateDevelopment
Apr 29, 2025Agent Pay announced with Microsoft, IBM, Braintree and Checkout.com
Oct 16, 2025Agent Pay Acceptance Framework introduced
Oct 28, 2025PayPal agrees to integrate Agent Pay into its wallet and trial the Acceptance Framework
Jan 2, 2026Fiserv integrates the Acceptance Framework into its merchant acceptance platform
Jan–Feb 2026Launches in Australia and New Zealand, as reported
Mar 2, 2026Santander and Mastercard complete what they describe as Europe’s first live end-to-end payment by an AI agent within a regulated banking framework. It was a pilot, not a commercial rollout.
Mar 5, 2026Verifiable Intent introduced
Apr 28, 2026Verifiable Intent contributed to the FIDO Alliance
Jun 10, 2026Agent Pay for Machines announced
Sep 30, 2026Trust services and agent-transaction score announced, with US testing

How it fits with other protocols

Agent Pay is a network program, not a checkout protocol. In practice:

  • The identity layer is Web Bot Auth, shared with Visa and recognized by CDNs such as Cloudflare.
  • The credential (the Agentic Token) can be the payment method behind an ACP delegated payment, a UCP payment handler, or an AP2 payment mandate.
  • Verifiable Intent supplies the proof of authorization, in a format designed to work with AP2.

Mastercard’s public messaging stresses support for multiple protocols rather than tying Agent Pay to one.

Practical notes

  • Merchants usually need no new checkout code. The work is configuring bot management to recognize signed agents, and making sure the processor supports Agentic Tokens and passes agent indicators.
  • Agent developers register with Mastercard (directly or through an enabler such as a PSP or wallet), manage signing keys, and request tokens through Mastercard’s APIs.
  • Issuers decide how agent-flagged transactions are authenticated and how disputes are handled. See consumer protection and liability.

Sources

The newsletter

Agentic commerce, explained as it happens.

New protocols, launches and what they mean for you. Plain language, no hype.

I'm a…