All posts

One card per vendor: the habit that makes card breaches a non-event

Never give two merchants the same number. Ten seconds per merchant buys capped losses, a clear culprit when something leaks, and cancellation on your terms.

One card per vendor: the habit that makes card breaches a non-event

Most advice about card security is about what to do after something goes wrong: dispute the charge, replace the card, update every merchant. The one habit that prevents most of that work is boring and cheap: never give two merchants the same card number. Here is why it matters more every year, and how to make it effortless.

How card numbers actually leak

Card fraud rarely starts with someone stealing your card. It starts with a merchant. A shop's database is breached, a plugin on a checkout page is compromised and skims numbers for months, a support agent copies details, a subscription service is sold and the buyer is less careful. Every merchant that stores your card is a place it can leak from, and you have no control over any of them.

With one card everywhere, any of those events exposes everything. With one card per merchant, a breach at one shop exposes one number, with one small balance, that you close in a tap.

The habit

  1. Before paying a new merchant, create a card for it. Name it after the merchant. Load it with what this purchase or this month costs.
  2. After a one-off purchase, close the card once the order has arrived and any refund window has passed. The leftover returns to your wallet.
  3. For recurring merchants, keep the card loaded with the next charge and nothing more.
  4. Never reuse a card for a second merchant. The second merchant gets its own.

That is the whole habit. It takes about ten seconds per merchant, less time than typing a shipping address.

What you get for it

Breaches become a non-event

The email says your data was exposed at some shop. You open the dashboard, close that one card, and move on. No new card in the post, no updating twelve other services.

You know who leaked

If a charge you do not recognise appears on the card named "Furniture shop", the furniture shop leaked it. With one shared card, you would never know which merchant to stop trusting.

Merchants cannot overcharge

The card holds what the merchant should charge. A wrong amount, a surprise renewal or a "we updated our pricing" simply declines.

Cancelling is unilateral

You do not need the merchant's cooperation to stop paying. Close the card and the relationship is over from the payment side. That matters with services that make cancellation deliberately hard.

Your real details stay home

The virtual card is the only thing the merchant ever sees. Your bank account, your main card and everything attached to them are not part of any online transaction.

Where it applies beyond shopping

  • Teams: a card per vendor means each supplier has its own statement and its own ceiling, and a departing employee's card is closed without touching anyone else's.
  • Trials: a card per trial, loaded with a dollar, ends the trial when the conversion charge declines.
  • Marketplaces and unfamiliar sites: exactly the places you least want your main card. A capped, disposable card makes the risk of trying them tiny.
  • Family: a card per person for their own subscriptions, so nobody's habits show up on anyone else's statement.

The objections

Too many cards to manage. A dashboard with named cards is easier to read than a single statement with fifty merchants on it. The cards are the organisation. Fees per card. Some providers charge to issue a card, some do not, and the fee is small next to a single fraud dispute or a forgotten subscription. Merchants that refuse prepaid cards. A few do. Keep one conventional card for them and virtual cards for everything else.

Making it automatic

The habit sticks when creating a card is faster than finding your wallet. Keep the provider's dashboard one tap away, name cards consistently, and treat the card list as your list of merchants. Once a month, scan it: anything you no longer use gets closed, and the balance comes back.