Payments and Trust in Agentic Commerce
How agents pay without holding card numbers: tokenization, delegated payments, mandates, SCA and 3DS, network agentic tokens, wallets, and disputes.
In short: Agentic payments rest on one idea: the agent should be able to pay without ever seeing the shopper’s real card number, and every party should be able to prove what the shopper authorized. Tokens scoped to a merchant, amount, and time window do the first job. Signed mandates and intent records do the second. Card networks, wallets, and payment processors have each built versions of both.
The problem
Online card payments assume a person is at the keyboard: they type or select a card, and an authentication step such as a one-time code confirms it is them. An agent breaks both assumptions. It is software acting for the person, possibly when the person is not present, and it may deal with merchants the person has never visited.
Three questions follow:
- Credential safety. How does the agent pay without storing or exposing the card number?
- Authorization. How does the merchant, the issuer (the bank that issued the card), and later a dispute reviewer know what the shopper actually approved?
- Accountability. When something goes wrong, who bears the loss?
Tokenization
Tokenization replaces a card number (the primary account number, or PAN) with a substitute value that is useless if stolen outside its intended context. Network tokens, issued by Visa, Mastercard, and others, already power mobile wallets and stored cards. Agentic commerce adds tighter scoping: a token may be valid only for one merchant, one maximum amount, one currency, and a short expiry.
Delegated payment tokens
Under the Agentic Commerce Protocol, the agent platform does not process payment itself. Its Delegated Payment Spec sends the shopper’s payment details to the merchant’s payment service provider (PSP), which returns a narrowly scoped token. The token carries an allowance with a maximum amount, currency, checkout session ID, merchant ID, and expiry, and the only supported reason is a one-time payment. The merchant then charges it like any other payment. OpenAI’s documentation states that OpenAI is not the merchant of record.
Stripe’s implementation is the Shared Payment Token (SPT). In December 2025 Stripe launched its Agentic Commerce Suite, which handles SPTs and lets businesses sell through several AI agents with one integration. Platforms named at launch included Squarespace, Wix, Etsy, WooCommerce, commercetools, and BigCommerce.
Network agentic tokens
The card networks issue tokens bound to a specific agent:
- Mastercard Agent Pay issues “agentic tokens” that tie a card credential to a registered agent and the consumer’s chosen limits. In March 2026 Mastercard published Verifiable Intent, an open-source framework, designed to work with Google’s AP2 and UCP, that links the consumer’s identity, their instructions, and the transaction outcome in a tamper-resistant record. On September 30, 2026 it began US testing of a score estimating how likely it is that an AI agent initiated a transaction. See Mastercard Agent Pay.
- Visa Intelligent Commerce provides agent-specific tokens, spending controls, and the Trusted Agent Protocol for agent recognition. On June 10, 2026 Visa and OpenAI announced that tokenized Visa credentials can power agent-initiated checkout in ChatGPT and Codex, with spending limits enforced before authorization. In April 2026 Visa announced Intelligent Commerce Connect, a single integration that supports several agent protocols. See Visa Intelligent Commerce.
- American Express launched its Agentic Commerce Experiences (ACE) developer kit on April 14, 2026, covering agent registration, card member enrollment, purchase intent, tokenized credentials, and optional cart context from merchants.
One-time virtual cards
Some agents pay with single-use virtual card numbers generated per purchase. Meta’s Muse, launched in September 2026, pays through Stripe’s Link, which issues one-time virtual cards.
Mandates and proof of intent
A token answers “can this agent pay?” A mandate answers “what did the user agree to?”
The Agent Payments Protocol (AP2), started by Google and donated to the FIDO Alliance in April 2026, uses cryptographically signed verifiable digital credentials. Its current documentation describes two mandate types, each with an open and a closed stage:
| Mandate | Shared with | Open stage | Closed stage |
|---|---|---|---|
| Checkout mandate | Merchant | User’s goals and constraints before a cart exists | Approval of a specific, final checkout |
| Payment mandate | Credential provider, network, processor | Budget and allowed payment methods | Authorization of a specific amount |
AP2 supports “human present” flows, where the user approves the final cart, and “human not present” flows, added in v0.2, where the agent buys within limits the user set in advance, such as buying tickets the moment they go on sale. The signed records create an audit trail for disputes.
Card-network work follows the same direction. EMVCo, the body that manages EMV chip, tokenization, and 3-D Secure specifications, published a draft EMV Agentic Payments – Framework for Specifications on September 4, 2026. It proposes “intent services” so that payment participants can register and retrieve a consumer’s authorized purchasing intent throughout a transaction, alongside agent identification and transaction indicators. Comments closed September 30, 2026.
Strong customer authentication and 3DS
Strong customer authentication (SCA) is the EU and UK requirement that most electronic payments be confirmed with two of three factors: something the payer knows, has, or is. 3-D Secure (3DS) is the card-network protocol most often used to meet it, typically through a banking-app prompt or one-time code.
Agents raise practical questions: who completes the challenge, and can a prior authentication cover later purchases? Current approaches include:
- Authenticating the user when they set up the agent’s credential or mandate, often with a passkey or biometric in a wallet, then relying on scoped tokens for later purchases.
- Sending the user a confirmation prompt at the moment of purchase for higher-value or unusual transactions.
- Using network data (agent identity, intent records) to support risk-based exemptions where regulation allows.
EMVCo has said it is examining how EMV 3DS, payment tokenization, and Secure Remote Commerce can be adapted for agent payments. In the EU, the PSD3 and Payment Services Regulation package, provisionally agreed in November 2025, would tighten SCA and fraud rules but was not yet fully in force as of mid-2026. See consumer protection and liability.
Wallets and payment platforms
Wallets already hold verified credentials, addresses, and authentication, which makes them natural agent payment layers:
- Google Pay funds UCP-powered checkout in AI Mode and Gemini, using cards in Google Wallet.
- PayPal launched agentic commerce services in October 2025, including Agent Ready, to let existing PayPal merchants accept payments on AI surfaces, and powers checkout in Perplexity and Copilot.
- Shop Pay handles agent checkout on Shopify stores, including the WebMCP checkout tools Shopify released for browser agents in September 2026, which cannot enter new card details: agents can pay only with a buyer’s saved Shop Pay card, and must show the buyer the order and total and get permission before submitting.
- Adyen announced Adyen Agentic on June 16, 2026, supporting ACP, UCP, and AP2 through one integration.
Stablecoin and micropayment rails, such as x402, target machine-to-machine payments where card fees and minimums are a poor fit.
Liability and disputes
As of October 2026 card networks have not created dispute categories specific to agents. Agent-related disputes fall under existing reason codes: unauthorized transactions, items not received, and items not as described. Practical consequences:
- The merchant of record usually carries the dispute. ACP and UCP both keep the merchant as seller of record, so refunds and chargebacks run through the merchant’s existing processes.
- Evidence matters more. Signed mandates, intent records, and agent identity give merchants and issuers something to point to when a shopper says “I didn’t order this.”
- Some issuers are stepping in. American Express announced Agent Purchase Protection, covering card members when a registered agent’s transaction deviates from authenticated purchase intent.
The legal question of whether an agent’s mistake counts as an authorized transaction is unsettled. See consumer protection and liability and agent identity and fraud.
Sources
- Delegated Payment Spec — OpenAI Developers
- Stripe launches the Agentic Commerce Suite — Stripe
- Mastercard unveils open standard to verify AI agent transactions — PYMNTS
- Mastercard advances agentic commerce with new trust and intelligence services — Business Wire via FinancialContent
- Visa partners with OpenAI to let AI agents make payments for users — SiliconANGLE
- Visa opens the door to AI-driven shopping for businesses worldwide — Visa
- American Express launches developer kit, purchase protection for agentic commerce — Digital Commerce 360
- Agent Payments Protocol — AP2
- Google donates Agent Payments Protocol to FIDO Alliance — FIDO Alliance
- EMVCo drafts framework for agentic card payments — FinTech Global
- EMVCo working on how global specifications can support agentic payments — EMVCo
- PayPal launches agentic commerce services — PayPal
- Meta launches Muse AI agent with Stripe-powered checkout — The Paypers
- Shopify opens checkout to browser-based AI agents — TechCrunch
- Shopify extends WebMCP support to checkout for browser agents — Unite.AI
- PSD3 and PSR: from provisional agreement to 2026 readiness — Norton Rose Fulbright