What Is Mastercard Agent Pay?
Mastercard Agent Pay is Mastercard's card-network protocol for AI-agent-mediated transactions. It is the Mastercard counterpart to Visa's TAP and serves the same purpose: defining how an AI agent can authorise transactions on behalf of a Mastercard cardholder, within issuer-defined and user-defined constraints, with the transaction carrying agent-context metadata that downstream parties can recognise and handle.
Mastercard announced Agent Pay through 2025 alongside Visa TAP, with both networks coordinating on similar timelines. By April 2026, Agent Pay is in production with select issuers and agent platforms, with broader rollout planned through 2026. It is one of the five major agent payment protocols (alongside x402, MPP, TAP, and AP2) that brands and publishers should plan for.
Why Mastercard Agent Pay Matters
The strategic logic behind Agent Pay mirrors TAP's. Card networks need a protocol-level mechanism to keep agent traffic on their rails rather than seeing it migrate to crypto or account-to-account alternatives. Without Agent Pay, Mastercard-issued cards would be either over-blocked (losing volume) or under-governed (taking on fraud risk) in the agent commerce era.
For brands and publishers, Agent Pay matters because Mastercard's issuer base is global and large. Outside the US, Mastercard's share is significant in Europe, Latin America, and parts of Asia. Brands operating internationally cannot optimise only for Visa TAP; they need agent-readiness across both card networks. Agent Pay's production timeline is the gating factor for how quickly that double coverage becomes operationally clean.
How Mastercard Agent Pay Works
The flow is structurally similar to TAP. An agent registered under Agent Pay holds credentials tied to a specific cardholder and a specific set of constraints. When transacting, the credentials are presented alongside the card data. Mastercard's processing layer recognises the Agent Pay credentials, evaluates against constraints, and routes for authorisation with agent-context metadata.
The differences from TAP are mostly in the issuer pilot composition, the specific metadata schema, and the integration tooling. Functionally, merchants accepting both networks see broadly similar agent-context information on transactions across the two protocols. The two networks have signalled intent to converge on metadata schemas where possible to reduce merchant integration complexity.
In Practice
As of April 2026, Agent Pay is being piloted by a different set of issuers from TAP (HSBC, Standard Chartered, several European and Latin American banks). Agent platform participation overlaps significantly with TAP, since most major agent platforms intend to support both networks. Merchants do not need separate integration for Agent Pay if they accept Mastercard at all; the protocol-specific handling is the only optional layer.
For publishers and brands, the practical implication is that agent-mediated card payments through both Visa TAP and Mastercard Agent Pay should be treated as production-relevant by mid-2026, with international brands needing both. Single-network bets are operationally simpler short-term but carry tail risk: the network that does not get optimised for is a blind spot for any agent-mediated traffic in regions where it dominates.
Commonly Confused With
Agent Pay is not the same as Apple Pay or Google Pay despite the naming similarity. Apple Pay and Google Pay are wallet-level abstractions over card credentials, designed for human-checkout convenience. Agent Pay is a network-level protocol designed for AI-agent-mediated transactions. The two layers can compose (an Apple Pay wallet could in principle hold Agent Pay-credentialed instruments) but they address different problems.
