Skip to content

Virtual cards explained: how they work, use cases, and how they are funded

A virtual card is a card number with no plastic. Learn how virtual cards are issued, controlled and funded from a balance, a credit line or stablecoins.

A virtual card is a card number issued digitally, with no plastic, that works anywhere the card network is accepted online. It can be single-use or reusable, with spending limits and merchant controls. Businesses issue virtual cards through an issuer or a program manager and fund them from a balance, a credit line or stablecoins.

This guide explains what a virtual card is, who is involved in issuing one, the main use cases, the four funding models, the controls that make virtual cards useful, and what to ask an issuing partner. It reflects card network pages and BlindPay's documentation as of early November 2026. For how card types differ, see credit, debit, prepaid and virtual cards.

Key takeaways

  • A virtual card is a real network card. It has a card number, an expiry date and a security code, and it authorizes, clears and settles like any card.
  • Issuing takes several roles. A card network, a sponsor bank, an issuer processor and a program manager all sit behind one card.
  • Funding is the main design decision. The card can draw on a prepaid balance, a credit line, a just-in-time source or a stablecoin balance.
  • Controls are the selling point. Single-use numbers, limits and merchant locks are set per card, through an API.
  • BlindPay does not issue cards. It moves the money around a card program: bank deposits in, stablecoins to the wallet, and local-currency payouts out.

What is a virtual card?

A virtual card is a payment card that exists only as data: a card number, an expiry date and a security code, delivered in an app, a dashboard or an API response. With no plastic to print or ship, a card can be created in seconds and closed just as fast.

Virtual describes the form, not the funding. A virtual card can be a credit, debit or prepaid card, for a consumer or a business. Three terms come up often:

  • Single-use card: a number that works for one payment and then closes.
  • Multi-use card: a reusable number, often locked to one merchant or one budget.
  • Commercial card: a card issued to a business for business spending, as opposed to a consumer card.

A virtual card is also different from a token. A token is a stand-in for a card number, created for one device or one merchant. A virtual card is the account credential itself. When a virtual card is added to Apple Pay, for example, Apple's platform security guide (2024) says a unique Device Account Number is created by the card issuer, and adds: "Full card numbers aren't stored on the device or on Apple Pay servers." Card tokenization explained covers tokens in detail.

One more distinction saves confusion: a virtual card is for spending, and a virtual account is a bank account number for receiving deposits.

How are virtual cards issued?

Each virtual card sits on a stack of regulated roles, and a business that wants cards usually rents most of that stack.

  • Card network: Visa, Mastercard or another scheme. It sets the rules and routes each transaction.
  • BIN sponsor: the licensed bank that holds the network membership and the card number range, called a BIN (bank identification number). It carries regulatory responsibility for the program.
  • Issuer processor: the system that receives each authorization request and approves or declines it against the card's balance and rules.
  • Program manager: the company that designs the card product, onboards cardholders and runs daily operations.
  • Your business: the brand the cardholder sees. You may be the program manager, or a customer of one.

The bank stays responsible even when a fintech runs the program. US banking regulators state in their Interagency Guidance on Third-Party Relationships (88 FR 37920, June 2023) that "the use of third parties does not diminish or remove banking organizations' responsibilities". That is why a sponsor bank reviews your compliance program before launch and audits it afterwards. BIN sponsor vs issuer processor vs program manager explains how the roles divide, and what stablecoin card issuing is covers the stablecoin version of the same stack.

From the builder's side, issuing one card looks like this:

  1. Verify the cardholder. Run identity checks on the person (KYC, know your customer) or the company (KYB, know your business).
  2. Create the cardholder and the card. One API call each.
  3. Set the controls. Add spending limits, allowed merchants and an expiry.
  4. Fund the card. Load a balance, assign a credit limit or connect a funding source.
  5. Decide each authorization. The issuer processor approves or declines in real time.
  6. Clear and settle. The purchase moves through the network like any card payment. How card payments work walks through those stages.
  7. Reconcile. Match each transaction to an invoice, an employee or a customer.

What are the top use cases for virtual cards?

Virtual cards win where a business wants one payment credential per purpose.

  • Supplier payments. Accounts payable teams issue a single-use card for each invoice, with the exact amount as the limit.
  • Expense management. Each employee, team or project gets its own card with a budget.
  • Ad spend and subscriptions. A separate multi-use card per vendor lets you cap or cancel one subscription without touching the others.
  • Marketplace and gig payouts. A platform can issue a card to a seller or worker so earnings are spendable right away. Stablecoin virtual cards for cross-border payouts compares this with paying into a bank account.
  • Stablecoin spend. A wallet or neobank lets users spend a USDC or USDT balance at any card merchant.

Business cards also have different economics. In the EU, commercial cards sit outside the consumer interchange caps under Article 1(3)(a) of Regulation (EU) 2015/751, which is part of why issuers can offer rebates on business card spend.

Stablecoin spend is the newest of the five. Visa's stablecoin-linked cards page, last updated March 31, 2026, reports about $5.2 billion in stablecoin-linked card volume in 2025 across more than 130 programs in more than 50 countries. Visa adds that "a stablecoin-linked card functions like any other Visa card". How stablecoin-linked cards work follows one payment from wallet to merchant.

How are virtual cards funded?

A virtual card needs money behind it before the issuer will approve a purchase. There are four common funding models, and a program can combine them.

Funding modelHow it worksBest forTrade-off
Prepaid balanceMoney is loaded in advance into an account at the issuing bank, and each purchase draws it downExpense cards, payouts, fixed budgetsCash sits idle, and a top-up must arrive before the cardholder can spend
Credit lineThe issuer extends credit and the business repays on a statement cycleSupplier payments and working capitalNeeds underwriting, and the issuer prices in the credit risk
Just-in-time fundingEach authorization triggers a real-time check against a source account or ledger, and funds move only for approved purchasesPlatforms that already hold customer balancesYour systems must answer every authorization in time, or the purchase is declined
Stablecoin balanceThe program manager checks the wallet balance through a smart contract integration or an API, reserves the amount and converts it as needed for settlement, per Visa (2026)Users who hold USDC or USDT, and cross-border spendNeeds on-ramps, a custody model, conversion and a clear regulatory footing

The first three models are long established. Just-in-time vs prefunded stablecoin cards and prefunding and collateral in card issuing compare how much cash each one ties up.

The stablecoin model changes what sits behind the card, not what the merchant sees. Visa describes two ways these programs settle: the program manager converts stablecoins to fiat before settling with Visa, or the issuer settles with Visa directly in a supported stablecoin such as USDC. Mastercard announced plans on June 3, 2026 to add on-chain card settlement using regulated stablecoins. Either way, the merchant is paid in local currency.

Where does the money come from in the first place?

Every funding model has a step before the card: getting money from a bank account into the balance the card spends, and getting unspent money back out. BlindPay does not issue cards and is not a card network member. It is a stablecoin payout and collection API that runs three flows around a card program:

  • Collect bank deposits as stablecoins. Virtual accounts give a customer a US account in their own name that accepts ACH, wire and SWIFT deposits and converts each one to USDC or USDT in a linked wallet. There are also SPEI CLABE accounts in Mexico and Bre-B accounts in Colombia.
  • Accept local payment methods. Payins over Pix, SPEI, Argentina's Transfers, PSE and card deliver stablecoins to the customer's wallet.
  • Pay out to bank accounts. When a cardholder withdraws or a refund is due, a payout delivers local currency over Pix, SPEI, ACH, wire, RTP, SEPA, Faster Payments or SWIFT (POBO/COBO), with UETR tracking and MT103 confirmations on cross-border wires.

A quote locks the rate and the fees for 5 minutes, and KYC, KYB and sanctions screening run inside the same API. The stablecoins land in the wallet you link for each customer. Whether that wallet can be the one the card spends from depends on your issuer's custody model, so confirm it with the issuer before you design the flow. How to fund a stablecoin card program maps the full sequence.

What controls and security do virtual cards offer?

Controls are set per card and take effect at once, which is the main advantage over plastic.

  • Single-use numbers. The card closes after one payment, so a leaked number has no value.
  • Spending limits. Caps per transaction, per day, per month or over the life of the card.
  • Merchant rules. Lock a card to one merchant or to a merchant category, such as software or travel.
  • Instant freeze and close. Turn a card off from a dashboard or an API call, with no plastic to recover.

Tokenization adds a layer when a virtual card is stored with a merchant or added to a mobile wallet. Visa said in an August 2022 release that, across more than 8,600 issuers and 800,000 merchants, Visa tokens "have led to a 28 percent reduction in fraud rates and a 3 percent increase in approval rates".

Virtual cards are not immune to fraud. Every online purchase is a card-not-present transaction, so phishing, account takeover and disputes still apply. 3-D Secure authentication and transaction monitoring remain part of the program.

Should you build or buy a virtual card program?

There are three routes, from the most control to the least work.

  1. Become the issuer. Hold your own network membership and licenses. This gives full control and the full compliance burden.
  2. Run the program on a sponsor bank. Contract a BIN sponsor and an issuer processor directly and act as the program manager, under the bank's oversight.
  3. Use an issuing platform. A platform bundles the bank, the processor and the network connection behind one API. This is the fastest route, with less control over economics.

Many fintechs and software platforms start with the third route and take on more of the stack as volume grows. Build vs buy for a stablecoin card program covers the trade-offs, and stablecoin card issuing platforms compared reviews the documented options layer by layer.

Whichever route you take, the funding and payout layer is a separate decision. BlindPay shows its fees in the live quote before you execute, and its plans are on the pricing page.

What should you ask a virtual card issuing partner?

Use this checklist before you sign.

  1. Who holds which role? Name the BIN sponsor, the issuer processor and the program manager.
  2. Which networks and countries are live today? Ask for the current list, not the roadmap.
  3. Which card types can you issue? Consumer or commercial, credit, debit or prepaid.
  4. Which funding models are supported? Prepaid, credit, just-in-time or stablecoin, and how much must be pre-funded.
  5. How do authorizations work? Ask whether your system can decide in real time.
  6. Who runs KYC, KYB and transaction monitoring? Get the split of duties in writing.
  7. How are card details displayed? A hosted display keeps card numbers off your servers, which limits your scope under PCI DSS, the card industry's data security standard.
  8. How do disputes and chargebacks flow? Ask who handles them and who carries the loss.
  9. How does money get in and out? Ask how bank deposits reach the card balance and how unspent funds return to a bank account.

How to choose a stablecoin card issuing provider expands each question for stablecoin programs.

Sources

  • Visa, "How stablecoin-linked cards are modernizing money movement," last updated March 31, 2026: visa.com
  • Visa, press release on Visa token performance, August 24, 2022: usa.visa.com
  • Mastercard, "Mastercard expands settlement capabilities to include stablecoin," June 3, 2026: mastercard.com
  • Apple, Apple Platform Security guide, Apple Pay card provisioning, December 2024: support.apple.com
  • Regulation (EU) 2015/751 on interchange fees for card-based payment transactions, Article 1(3), text adopted March 2015: consilium.europa.eu
  • US federal banking agencies, Interagency Guidance on Third-Party Relationships: Risk Management, 88 FR 37920, June 9, 2023
  • BlindPay, virtual accounts, payins and bank accounts documentation

What to do next

Decide the funding model first, then shortlist issuers that support it. To test the money-movement side, create a virtual account and a payout on a free BlindPay development instance, starting with the virtual accounts docs. For the stablecoin route, read how stablecoin-linked cards work, how to fund a stablecoin card program and the best stablecoin card and payment infrastructure providers.

This article is general information, not legal, tax, or financial advice.

FAQ

One API.
Multiple payment rails.

Blind Pay, Inc. (“BlindPay”) is a United States-based financial technology and payments infrastructure company, incorporated in the State of Delaware on May 2, 2024. BlindPay is duly registered as a Money Services Business (“MSB”) with the Financial Crimes Enforcement Network (“FinCEN”) under registration number 31000277566153. BlindPay is not a state-licensed money transmitter and does not, in its own capacity, engage in regulated money transmission services. All such regulated activities are conducted exclusively through, and under the licenses of, duly authorized financial institution partners. BlindPay's role is limited to providing financial technology, virtual account management, payment processing, and related payments infrastructure services that facilitate payment flows and account functionalities. These services are provided in coordination with its licensed partners and in compliance with applicable federal MSB requirements and relevant state regulatory frameworks.

Blind Pay, LLC (“BlindPay”) is a Delaware limited liability company formed on June 24, 2025. BlindPay is duly registered as a Money Services Business (“MSB”) with the Financial Crimes Enforcement Network (“FinCEN”) under registration number 31000318334247 and is listed in the Nationwide Multistate Licensing System (“NMLS”) under NMLS ID #2745309.

BLIND PAY SOCIEDADE PRESTADORA DE SERVIÇOS DE ATIVOS VIRTUAIS LTDA. (“BlindPay”) is a Virtual Asset Service Provider (“VASP”) operating in Brazil. The company is presently completing the regulatory adaptation process required of Virtual Asset Service Provider Companies (SPSAV) under Central Bank of Brazil Resolution No. 520/2025, and remains subject to the transitional regime set forth in Article 88 of that Resolution. Registered address: Avenida Princesa Isabel, nº 15, Sala 1405, Edifício Martinho de Freitas, Centro, Vitória/ES, 29010-361.

BlindPay is a stablecoin API that enables individuals and businesses to move money worldwide.