Finance Index

Physical vs virtual corporate cards - what's the difference and when do you use each?

Reference guide to physical vs virtual corporate cards, including card controls, policy design, employee spend workflows, receipt capture, and reconciliation.

A virtual card is a card number with no plastic - created instantly, configurable per use, and killable without replacing anything in someone's wallet. Physical cards exist for in-person spend: travel, field purchases, anywhere a terminal or a wallet is involved. The default should be virtual; physical is the exception you justify.

At a Glance

Aspect Short Answer Why It Matters
Corporate card policy A virtual card is a card number with no plastic - created instantly, configurable per use, and killable without replacing anything in someone's wallet. Reduces payment errors, timing issues, and reconciliation cleanup.
Card control One virtual card per vendor. Keeps vendor records and payment decisions reliable.
ERP alignment A number valid for one authorization (or one merchant for a short window), ideal for one-off purchases and vendor payments - the control expires with the transaction. Keeps evidence clear and reduces control risk.
Vendor impact A card that only authorizes at one merchant. Keeps vendor records and payment decisions reliable.
Lifecycle Name by vendor and purpose, assign a human owner, set an expiry or review date on every card, and require the inventory to live in the card platform - not a spreadsheet. Keeps vendor records and payment decisions reliable.

How should we use virtual cards for software subscriptions?

One virtual card per vendor. Each subscription gets its own number with a merchant lock and a limit sized to the contract, so you can kill any subscription instantly without breaking others, see exactly what each vendor charges, and survive employee departures without a subscription archaeology project. This single practice eliminates most of the subscription chaos that shared department cards create.

What is a single-use / one-time virtual card?

A number valid for one authorization (or one merchant for a short window), ideal for one-off purchases and vendor payments - the control expires with the transaction.

What is a vendor-specific or merchant-locked virtual card?

A card that only authorizes at one merchant. It collapses fraud exposure (a stolen number is useless elsewhere) and overspend risk (the limit is sized to that vendor) at the same time.

Best practices for virtual card naming, ownership, and lifecycle?

Name by vendor and purpose, assign a human owner, set an expiry or review date on every card, and require the inventory to live in the card platform - not a spreadsheet. Orphaned cards are a naming-and-ownership failure, not a tooling failure.

We have 300 active virtual cards with no inventory - how do we audit and clean up?

Pull 90 days of activity per card: cancel anything dormant, identify each active card's merchant and owner from the transaction data, and reissue unknowable cards with proper naming rather than investigating them indefinitely. Then institute expiry-by-default so the pile never rebuilds.

Replacing shared department cards with individual virtual cards - what changes?

Accountability becomes per-person (every transaction has an owner), coding improves, and fraud exposure drops; what breaks is any card-on-file relationship tied to the old shared number, so inventory those before cutting it.

How do virtual cards work with mobile wallets?

Most virtual cards can be provisioned to Apple Pay or Google Pay, which gives employees in-person purchasing without plastic - useful for occasional in-person needs that don't justify a physical card.

What is card tokenization and does it matter?

Tokenization replaces the card number with a merchant- or device-specific token, so a breach of that merchant doesn't expose the underlying number. It matters; it's also table stakes in modern card platforms rather than a differentiator.

A vendor won't accept our virtual card or requires a physical card on file - workarounds?

Provision the virtual card to a mobile wallet for in-person use; for card-on-file holdouts, some platforms issue long-lived merchant-locked numbers that behave like physical cards. If the vendor genuinely can't take cards, that's a signal the relationship belongs on invoices and ACH anyway.

Stampli perspective

Stampli Card supports both physical and virtual cards under the same controls - spending limits by cardholder, merchant category, or vendor - with employee-initiated requests and finance-owned configuration. Virtual card validity dates can be extended on request, and cardholders can suspend or unsuspend their own cards, keeping lifecycle management out of finance's queue.