Mastercard has picked a side in how AI agents should pay. On its Q3 earnings call on October 29, CEO Michael Miebach said virtual card numbers should be "only a bridge." The destination, in his words, is "fully tokenized all the way through agentic pay or an equivalent."
On the same call he named a large early deployment of that model: Shopify, through Shop Pay.
If you sell on Shopify, much of this is being decided for you. If you run an open commerce stack like Medusa, you have to answer it yourself. I think that is an advantage, as long as you start before agent volume shows up.
What Mastercard Actually Said
This is not a ban. Miebach called a virtual card "a processor decision that is a bridge to get ready for a fully tokenized transaction." He also said Mastercard is working with processors to keep it that way. What he rejected is the one-time card as a permanent layer "fronting a transaction," which he said "fundamentally breaks a transaction."
The difference matters because of what each model tells the network. Tokens let an authorized agent pay from the user's own card, while a single-use virtual card sits in between. Card companies are wary of the second model because a purchase is harder to tie to a specific person — and that linkage is what preserves fraud protections, rewards, and dispute evidence.
The two models compared:
- One-time virtual card — the agent pays with a separate single-use card; the link to the cardholder is harder to establish; Mastercard's position: a bridge only
- Network token — the agent pays with a token standing in for the user's own card; the cardholder link is preserved; the user keeps their rewards and fraud protections; Mastercard's position: the way to go
Tokens answer one question: is this credential legitimate? Mastercard's Verifiable Intent goes after the next one: what did the buyer actually authorize? It is an open specification, developed with Google, that links the cardholder, their instructions, and the agent's interaction with the merchant in one tamper-resistant record.
Shop Pay Went First, and That Was Predictable
Miebach said Shopify, "through Shop Pay, is using Agent Pay and our network tokens." Shopify has reportedly added token technology from Visa and American Express as well. The agent never sees the real card number, and the buyer keeps their rewards and fraud protections.
Shopify could move early because it controls the pieces that matter: the checkout, the saved credentials, and a large base of buyers. One integration covers a very long tail of stores.
That convenience has a price, and it isn't only the fee line. The platform sits between the merchant and the record of how an agent came to buy. When agents become a real channel, that record will decide who wins disputes and whose fraud models get better.
What This Means on an Open Stack
Open-platform merchants aren't locked out, but the work moves to them. For app-authorized wallet access, a Shopify merchant gets a session that runs on Shopify. A non-Shopify merchant can receive an encrypted card number or a network token with a cryptogram, then process the payment itself — which requires PCI compliance.
Medusa shows the building blocks arriving. Version 2.22.3, released November 4, added off-session payments to its Adyen provider, days after Adyen became an official provider. Medusa built this for recurring and subscription flows, and it isn't agentic tokenization. But charging when the customer isn't at checkout is the same situation an agent creates.
Here is where an open stack can do better than a closed one. You can decide that the token reference, the agent's identity, the buyer's authorization, and the settlement result all live on one order record that you own. I build on a simple belief: verified state should control the movement of money. Agentic checkout is that idea under the hardest conditions, with nobody present when the money moves.
What to Do Before the Volume Arrives
There is time, but not much. Miebach said the numbers "are not yet significant in the grand scheme," while growing quickly week to week, and he expects that to build through the holidays. Five things are worth doing now:
- Ask your processor which model it uses. If agent transactions run on virtual cards, ask what the plan is when the bridge ends.
- Check your payment layer for token support. Confirm it can accept a network token and cryptogram, and know your PCI position if you process them yourself.
- Keep the authorization evidence with the order. Verifiable Intent is built to share only what a fraud check or dispute needs, so plan where that record will live.
- Decide when an agent purchase needs a human. Mastercard says merchants can use verification data to require extra confirmation. Set those thresholds yourself instead of inheriting someone else's.
- Don't rebuild checkout around agents. Mastercard's own CFO said, "I don't think agentic is going to be the only mode of commerce." Treat agents as one more channel on the same payment record.
The networks are deciding how agents prove who they are. Merchants still get to decide who holds the proof. That is the part I would not hand over.