Skip to main content

​
Learning objectives

  • Define virtual cards in the context of global payment systems
  • Understand where they sit in the card ecosystem
  • Distinguish between physical, virtual, and tokenized cards
  • Recognize the business and technical reasons to use them
  • Explain where they’re commonly used and how they’re issued

​
What is a virtual card?

A virtual card is a payment card that exists entirely in software. Just like a physical debit or credit card, it has: But unlike a physical card, you won’t receive anything in the mail. It’s created and delivered digitally, usually through:
  • APIs,
  • Wallet apps,
  • Banking apps,
  • B2B platforms.
It is used mainly for online payments (websites, in-app checkouts, subscriptions, and e-commerce), often called card-not-present (CNP) transactions. Any licensed card issuer, like a bank or fintech company, can issue virtual cards, if they’re connected to a card scheme. Virtual cards today are issued on:
  • Visa, global reach, most common
  • Mastercard, also global, widely used for corporate and prepaid solutions
  • Verve, dominant in Nigeria and West Africa
  • UnionPay, dominant in China and growing globally
  • Discover, AmEx, and local scheme integrations
Even some closed-loop systems (e.g. PayPal, Apple, Google) issue card-like virtual instruments for use inside specific ecosystems. So the concept of a virtual card is not brand-specific. It’s an industry-standard abstraction over a payment credential that happens to be non-physical.

​
How virtual cards fit into the card ecosystem

There are three types of payment cards: Virtual cards are great for:
  • Online purchases
  • Digital onboarding
  • Budgeting and spend control
  • Issuing at scale
They are not ideal for:
  • In-store purchases (unless tokenized into Apple/Google Pay)
  • ATM withdrawals (unless explicitly supported)

​
Where are virtual cards used?

​
Why virtual cards are useful

  1. Security
    • Each card can be frozen at any time, and terminated once it is 24 hours old
    • Cards can be restricted by category (e.g., block betting, crypto)
    • Merchants never store your main account number
    • Reduced risk of skimming or POS compromise
  2. Control
    • Per-card limits
    • Category-specific usage
    • Short-lived cards
    • Full visibility and transaction history via API
  3. Programmability
    • Cards can be created or destroyed by software
    • You can issue cards dynamically: for each campaign, project, department
    • You can run experiments without financial or operational friction

​
How virtual cards are created

Behind the scenes, when you issue a virtual card:
  • A request goes to a card issuer’s system
  • They reserve a unique PAN (card number), expiry, CVV
  • The card is created in a card processing system
  • It becomes active and ready to use
  • The system (API, app, etc.) securely returns the card details to the user or platform
Most of this happens in under 5 seconds.

​
Limitations of virtual cards

​
Recap: Key takeaways

  • A virtual card is a digitally issued payment card designed for online use
  • It’s issued by a licensed issuer under a card scheme (Visa, Mastercard, Verve, etc.)
  • It has all the components of a physical card, but lives only in software
  • You can program how and when it’s used: limits, lifecycle, spending patterns
  • It’s ideal for modern, API-first financial products, and replacing clunky manual processes

​
Exercise

Write down 3 real use cases where virtual cards would save your team time or money, and what kind of control you’d want (per-user, per-department, per-merchant, etc.) Then think: would you want to build this into your product, or offer it as a service?