The Card Network Imperative: Why Visa and Mastercard Must Adapt
| Payment Rail Feature | Visa Intelligent Commerce | Mastercard Agent Pay | UCP Interoperability Rail | Token Standard | Liability Model |
|---|---|---|---|---|---|
| Agent Tokenization | Visa Token Service (VTS) AP2 | Mastercard Digital Enablement (MDES) | Open FIDO AP2 / PAN_ONLY binding | EMVCo Token v3.1 | Full Issuer Shift |
| Spend Mandates | Visa Spend Limits API | Mastercard Smart Rules Engine | Signed RFC 7519 Mandate Tokens | Cryptographic JWT | Non-Repudiation Lock |
| Identity Attestation | Visa Passkey Attestation Service | Mastercard Identity Check Mobile | FIDO2 WebAuthn / Google Root CA | W3C WebAuthn | Hardware Enclave |
| Settlement Speed | Visa Direct real-time push | Mastercard Send real-time rail | Google Pay native settlement token | ISO 20022 | Sub-second auth |
| Dispute Handling | Visa Resolve Online (VROL) Agent | Mastercard MasterCom Automated | Cryptographic transaction receipt hash | SHA-256 Receipt | Zero Friendly Fraud |
| Ecosystem Strategy | Proprietary network API push | Embedded bank co-pilot SDKs | Neutral multi-network open protocol | Spec v2026-08-25 | Universal Support |
Analysis: Visa and Mastercard face an unprecedented challenge. For decades, these networks have operated within a predictable framework: a cardholder initiates a transaction, a merchant processes it, and the card network facilitates settlement. Agentic commerce disrupts this linear model entirely. When autonomous agents operating without human authorization for each transaction conduct commerce on behalf of users or independently, the traditional liability and authentication structures collapse.
Analysis: Both networks are navigating a period in which agentic commerce is widely discussed as the next major evolution in payments. From an author-voice perspective, the comparison that matters is not a roster of volumes but the structural shift: from cardholder-present and cardholder-initiated flows to agent-initiated flows where permission, identity, and intent must be proven without a human at checkout. That shift touches every layer the networks govern — credential, authentication, authorization, dispute, and merchant agreement.
Analysis: The strategic question for the two networks is therefore the same even as their technical answers diverge. How do you preserve trust in open commerce when the buyer at the point of interaction is software acting under delegated authority? How do you keep authorization meaningful, keep disputes resolvable, and keep merchants confident that an agent-initiated approval represents a willing cardholder? The remainder of this comparison examines the settled building blocks available in November 2026 and separates them from questions that remain under review.
Tokenization as the Foundation for Agent Authorization
Analysis: Tokenization stands at the center of both Visa and Mastercard’s agentic commerce strategies. Rather than agents accessing raw payment credentials, tokenization creates unique identifiers that represent payment accounts without exposing sensitive card data. This approach provides multiple strategic advantages for card networks preparing for autonomous transactions.
Analysis: As general engineering practice, tokens replace raw credentials in transit and storage. That principle predates agentic commerce and continues to apply to it: the agent, the merchant, and intermediaries handle a credential that is bound, scoped, and revocable, rather than the underlying account number. Where agent-specific controls exist, they are defined by the network programs that issue and govern those tokens, not by general assumption.
November 2026 update: Both networks use tokenization without exposing raw credentials: Visa Intelligent Commerce issues agent-specific pass-through tokens bound to a consumer passkey and positions as protocol-agnostic (TAP, x402, MPP, ACP, UCP through one integration, enrollment-gated); Mastercard Agent Pay uses Agentic Tokens with Verifiable Intent. Production TAP use requires Intelligent Commerce vetting plus Visa Developer Platform approval.
Analysis: The practical implication for merchants and agent operators is enrollment and approval before production use. Token availability does not itself resolve authorization scope, dispute evidence, or liability allocation. Those questions sit in the network rules and in the authentication evidence that accompanies the token, which is why the authentication frameworks below must be read alongside tokenization rather than as a substitute for it.
Authentication: From Cardholder Verification to Agent Verification
Traditional payment authentication revolves around cardholder verification—confirming that the person holding the card is the person initiating the transaction. Agentic commerce requires authentication of the agent itself and verification that the agent possesses valid authorization to conduct the transaction.
Analysis: That change in subject — from verifying the cardholder at the moment of pay to verifying the agent and its delegated permission — is what makes agentic authentication a distinct problem. The merchant must know which agent it is dealing with, the network must know that the payment authorization is intact, and the record must later show what was authorized and under what bounds. Different networks have settled on different specifications for that proof.
Visa’s Agent Authentication Framework
Visa’s merchant-side identity specification is the Trusted Agent Protocol (TAP), released 14 October 2025 with Cloudflare as part of Visa Intelligent Commerce. TAP is built on HTTP Message Signatures (RFC 9421) with Ed25519 or RSA-PSS-SHA256 — not ES256. The merchant validates the agent signature via Signature-Input/Signature, keyId lookup, with agent-browser-auth vs agent-payer-auth tags, ~8-minute validity, nonce, and three components: Agent Recognition Signature, Consumer Recognition, and Agentic Payment Container.
Analysis: In operational terms, TAP places verifiable agent identity at the merchant edge: the agent signs, the merchant validates signature material, freshness, and binding to the payment container. The design separates recognition of the agent from recognition of the consumer and from the payment itself, so each element can be checked and logged. For implementers, the integration path is through Intelligent Commerce vetting and Visa Developer Platform approval, with TAP available alongside other protocols through a single Visa Acceptance Platform integration where enrollment applies.
Mastercard’s Agent Authorization Framework
Mastercard’s framework is Agent Pay, announced 29 April 2025, built on Agentic Tokens (MDES extension) and Verifiable Intent co-developed with Google, introduced 5 March 2026. Verifiable Intent format is SD-JWT + Key Binding (RFC 7800), protocol-agnostic, donated to the FIDO Alliance.
Analysis: The Mastercard approach pairs a token extension with a portable statement of intent: the Agentic Token carries the payment enablement while Verifiable Intent carries the cardholder-linked authorization evidence in a format that can travel across protocols. Because the format is protocol-agnostic, the same intent construct can be evaluated wherever Agent Pay is supported, subject to network and acquirer requirements. As with Visa, production availability is enrollment-gated and distinct from pilot activity.
Liability Shifts: Redefining Risk in Autonomous Transactions
Analysis: The most contentious aspect of agentic commerce preparation involves liability allocation. Historically, Visa and Mastercard operated under well-defined liability frameworks. Agentic commerce introduces new liability questions that the networks must resolve about who bears risk when an autonomous transaction is disputed, fails, or causes harm.
Analysis: When an agent conducts a transaction, the question of who bears liability if the transaction proves unauthorized, fraudulent, or results in customer harm adds a third party to the traditional cardholder-merchant analysis: the agent operator that developed, deployed, and maintains the agent. How responsibility is shared among cardholder, merchant, network, and operator depends on authorization evidence, system behavior, and the applicable network rules for the transaction date.
Analysis: As settled in November 2026, only one liability-adjacent element is fixed for this comparison: for transactions processed on or after 24 October 2026, Compelling Evidence 3.0 Dispute Condition 10.4 includes agent provider login ID as a matching element. All other allocation of agent-related liability — tiers, percentages, burden-shifting, and insurance outcomes — remains under review and is not stated here. Merchants and operators should refer to current network rules and acquirer guidance for the transaction at issue.
Analysis: This framework incentivizes careful attention to authorization management, logging, and monitoring regardless of how future rules allocate loss. Operators that can show clear delegation, bounded scope, and intact authentication evidence are better positioned in any dispute process, while merchants that validate agent identity and preserve transaction context are better able to support representment. Cardholders remain dependent on clear authorization flows and reliable revocation when an agent should no longer act.
Real-World Implementation: Current Pilot Programs
November 2026 update: First live TAP pilot 20 October 2026 — Visa, BILL and Billtrust: a registered BILL Payment Agent authenticates via TAP and Visa’s Agentic Directory, then pays pre-approved supplier invoices with tokenized credentials; TAP also has live transactions in Europe. Intelligent Commerce Connect (announced 8 April 2026, TAP/ACP/UCP/MPP via one Visa Acceptance Platform integration) was pilot with select partners as of October 2026. Mastercard: first agentic transaction completed Q4 2025; Agent Pay for Machines Early Access opened 20 October 2026 (announced 10 June 2026) with seven end-to-end pilots completed — Cloudflare, Ant International, AIsa, Base, BVNK, Coinbase, Hype — not commercially available.
Analysis: The pattern across both networks is enrollment-gated progression from specification to pilot to early access, rather than general commercial availability. The Visa path emphasizes registered agents, directory-backed authentication, and tokenized settlement of pre-approved obligations such as supplier invoices. The Mastercard path emphasizes end-to-end Agent Pay flows culminating in Early Access for machine-oriented use. In both cases, pilot participation does not establish network-wide rules for liability, volume, or performance.
Analysis: For merchants evaluating readiness, the operational lesson is to treat pilot announcements as integration signals, not as production mandates. Confirm whether a given use case requires Intelligent Commerce vetting, Developer Platform approval, Agent Pay enrollment, or acquirer enablement before building agent checkout. Preserve authentication artifacts, token references, and order context so that later dispute or compliance review can reconstruct what the agent presented and what the merchant validated.
Interoperability and Industry Standards
Analysis: Neither Visa nor Mastercard operates in isolation. The Universal Commerce Protocol (UCP) represents an emerging standard for agentic commerce that merchants and platforms are watching for network-agnostic frameworks for agent authorization and transaction execution. How network specifications and UCP interfaces relate in any given integration depends on enrollment, gateway support, and the protocol actually used for the transaction.
Analysis: From a merchant architecture standpoint, the durable work is the same regardless of network: maintain clean separation between agent recognition, consumer recognition, and payment authorization; validate signatures and freshness; bind payment credentials to the authenticated session; and log the evidence needed for support, refund, and dispute handling. Standards evolve, but that separation of concerns remains the basis for interoperable implementation.
Frequently Asked Questions
How are Visa and Mastercard adapting their card networks for autonomous AI spending?
Both networks are expanding network tokenization (VTS and MDES) to support FIDO AP2 spending mandates, issuing device-bound tokens that execute single-use autonomous payments with pre-set budget caps.
What is the EMVCo and FIDO AP2 tokenization standard in agentic checkout?
FIDO AP2 binds the AI agent’s transaction request to the user’s hardware biometric passkey, replacing raw 16-digit card numbers with an encrypted network token that cannot be intercepted by LLMs.
Which card network provides better fraud liability shift for AI transactions?
Both Visa and Mastercard provide full fraud liability shift to the card issuer when transactions use network tokens accompanied by FIDO-compliant biometric device attestation under UCP payment handlers.

Leave a Reply