The mechanism is straightforward. Instead of typing your actual card number into a website, you generate a proxy number from your bank's app or a service like Privacy.com, Apple Card's virtual numbers, or the virtual cards many issuers now offer. Charges to the proxy route through to your real account, but the merchant never sees the underlying number. The proxy can carry rules: locked to one merchant, capped at a spending limit, or set to expire. This is a specific application of tokenization, the same idea that lets your phone's wallet pay without handing the store your real number.
Where the Benefit Is Real: Breach Containment
The strongest case for virtual cards is what happens when a merchant gets breached, which happens constantly. When a shopping site's payment database leaks or a web-skimming script scrapes checkout forms, the attackers get the card numbers stored there. If the number they got is a merchant-locked virtual card, it is close to useless to them: a charge from any other merchant is declined, because the number only works at the one store you locked it to. Your real number was never exposed to steal in the first place.
Compare that to a real card leak, where you cancel the card, wait for a replacement, and then update every subscription and saved payment that used it. With per-merchant virtual cards, a breach means you delete one number and generate another for that single merchant. Nothing else you own is affected. That containment is the feature, and it is real.
A per-merchant card also gives you unilateral power to end a charge. The subscription that buries its cancel button, the free trial that quietly converts, the service that keeps billing after you tried to leave: freeze or delete the virtual card and the next charge simply fails. You stop being dependent on the merchant honoring your cancellation.
Where the Privacy Claim Falls Apart: Your Bank Still Sees Everything
Here is the part the marketing tends to skip. A virtual card hides your real number from the merchant. It hides nothing from your bank or the card networks. Every charge, virtual or not, flows through the same rails: your issuing bank authorizes it, Visa or Mastercard routes it, and your bank posts it to your statement with a merchant name, amount, date, and category. The virtual card is a leaf; the account it hangs from is fully visible to the institution that issued it.
So if your privacy concern is "I don't want a random e-commerce site holding my card number," virtual cards are an excellent answer. If your concern is "I don't want my bank, or anyone who can compel my bank, building a record of everything I buy," virtual cards do nothing at all. That financial record is arguably the most detailed profile of your life that exists, and it sits with your bank regardless of how many proxy numbers you layer on top.
A virtual card changes who at the checkout counter learns your number. It does not change the fact that a full, itemized history of your spending accumulates at your bank.
The Name-and-Address Leak
There is a second, subtler limit. Many merchants require a billing name and address, and virtual card numbers usually still carry your real ones unless the provider specifically supports substituting them. Some services let you send a generated name and their address instead, which genuinely reduces what the merchant learns. But a virtual card number paired with your real name and home address has leaked the two identifiers that matter most to a data broker. Check what your provider actually transmits before assuming the transaction is anonymous to the merchant. Often it is pseudonymous at best.
An Honest Accounting
| Concern | Do virtual cards help? |
|---|---|
| Merchant breach exposes my card | Yes. A locked number is near-worthless to an attacker. |
| A subscription won't let me cancel | Yes. Delete the card and the charge fails. |
| Limiting damage from a saved-card leak | Yes. Blast radius is one merchant, not your whole account. |
| Hiding my spending from my bank | No. The issuer sees and records every charge. |
| Hiding my identity from the merchant | Partly. Only if the provider also substitutes name and address. |
| Anonymity from law enforcement with a subpoena | No. The paper trail runs straight through regulated banks. |
This is not a reason to skip virtual cards. Breach containment and subscription control are worth having, and both are things the tool delivers reliably. It is a reason to be clear-eyed about which box you are checking. If real payment privacy is the goal, the conversation moves to different tools entirely, which is why we wrote separately about privacy-preserving payment systems and where cash and other rails still matter.
The wider point is the one that runs under most privacy tooling: know exactly what a tool protects against before you rely on it. A virtual card is excellent at what it does and silent about what it does not touch, and treating the first as if it covered the second is how people end up feeling protected while a complete record of their life keeps accumulating somewhere else. For the same reasoning applied to the messaging you send rather than the payments you make, our piece on what end-to-end encryption actually protects makes the identical distinction between content and metadata.