Analysis
A virtual card lets an agent pay safely, but it changes who pays the merchant, what the statement shows, and what happens to rewards and disputes.

Virtual card numbers have been around since the early days of online shopping, when people were nervous about typing their real card into a website. The idea was to let a stand-in card take the risk and keep the real one safe.
When AI agents needed a way to pay, virtual cards were an obvious choice: give the agent a card of its own, and if anything goes wrong, the damage is limited to that card. This works, but it also changes who is making the purchase.
For example, if an agent buys a $90 pair of headphones with a virtual card, the store charges the virtual card, and the card's provider then charges the user's real card to settle up. The user's statement shows the provider rather than the store, any extra cashback the card gives on electronics may not apply, and if the headphones never arrive, the user has to go through the provider's process before their bank's.
For purchases made on a person's behalf, we think the better default is the user's own card, used through a one-time network token. This post explains why.
Three ways an agent can pay by card
A new virtual card. A provider issues a card for the agent, often one per purchase, and pays for it by charging the user afterwards, from a prepaid balance or from a company account.
The user's real card, stored. The user saves their card once, and the provider sends the card details to the merchant when the agent buys.
A network token on the user's real card. Visa and Mastercard now issue tokens made for agents. Each one is tied to the user's own card but only works at one store, for one amount, for a short time.
All three keep the card number away from the AI model. Where they differ is in what happens after the purchase.
What changes when an agent pays with a virtual card
These differences all come from the fact that a virtual card is a separate card from the one the user chose.
The provider pays the merchant. The provider's card pays, and the user pays the provider back. Stripe's Link puts it plainly in its terms for agent purchases: the user will reimburse Link for purchases it makes on their behalf.
The statement shows the provider. The user's bank sees the provider, not the store. With Link, the line reads LNKAGNT* followed by the merchant's name.
Rewards may not apply. The user's card paid the provider, not the store, so category rewards may not apply. Link's terms say that in some cases the user won't receive their card's offers, benefits or rewards.
Disputes go through the provider first. The purchase sits on the provider's card, so problems go through the provider first. Under Link's terms, refunds for agent orders are decided case by case.
Identity checks may be required. Issuing a new card can mean collecting identity details. Link's virtual card terms allow it to collect a Social Security number and date of birth.
Prepaid cards need funding first. Prepaid agent cards need money loaded first, from a balance, a wallet or stablecoins, before the agent can spend.
None of this makes virtual cards unsafe, but it does make them a different product from the card the user chose. For a detailed example, see How Stripe Link works for AI agents.
How a network token differs from a stored card
A stored card and a network token both keep the user's own card in charge: the merchant charges it, rewards work as usual, and disputes go to the user's bank.
The difference is who enforces the limits. With a stored card, the merchant receives the real card details, and only the software holding them can stop a wrong purchase. With an agentic network token, the card network enforces the limits: if the token is used at a different store or for a different amount, the network declines it. The token also tells the network that an agent made the purchase with the user's approval, which matters if a purchase is questioned later.
How Prava uses the user's own card
Prava uses network tokens on the user's own card. The user adds their card once in your app and approves each purchase with a passkey, or sets limits once for repeat orders. Each purchase gets a one-time token for that merchant and amount, the merchant charges the user's card directly, and Prava is never the merchant of record. Prava runs on Visa Intelligent Commerce and Mastercard Agent Pay.
Prava also handles the buying. Its Shop API finds products across UCP (Universal Commerce Protocol) stores and merchants like Macy's, and checkout takes 5 to 20 seconds on UCP stores, all in the same API. See how the pieces fit together.
When a virtual card still makes sense
Virtual cards remain a good fit in a few cases:
Company spending, where an agent buys for a business under that company's spending policies.
An agent with its own budget, such as a prepaid balance with a hard limit that is separate from anyone's personal card.
Crypto-funded agents that pay in stablecoins.
Summary
There are three ways to let an agent pay by card: issue it a new virtual card, store the user's real card, or use a network token on the user's real card.
A virtual card is a separate card. The merchant charges it instead of the user's card, so rewards, statements and disputes change, and issuing it can mean identity checks.
A network token keeps the purchase on the user's own card, and the card network itself limits it to one store and one amount.
To try Prava, create sandbox keys in the dashboard and follow the quickstart.
FAQ
Are virtual cards unsafe for agents? No. Single-use virtual cards are well scoped. The trade-off is ownership: the purchase is no longer on the user's own card.
Do network tokens work at every store? They work wherever the card is accepted online, as long as the user's bank supports agentic tokens. Coverage is growing quickly. Prava supports cards issued in 13 countries today and is adding ways to support more.
Does the user still earn rewards with a network token? Yes. It's an ordinary purchase on their own card at that store, so it earns what that card normally earns.
What about subscriptions? With Prava, the user approves a mandate once, with limits on the store, amount and frequency, and each renewal gets its own one-time token. With virtual cards, it depends on the provider: some issue recurring cards, others one card per purchase.
Sources
Link terms, including the Link Agentic Terms and Link Virtual Card Terms, effective Oct 20, 2026

Prava team

