Single-Use Virtual Cards: When to Use Them Instead of Multi-Use

A single-use virtual card is a digital card number generated for one specific transaction, then closed. A multi-use virtual card is a digital card number issued to a vendor or workflow and reused across multiple payments. Both sit inside the same card program. They just handle different kinds of work.

The decision isn't which card type wins. It's which fits the vendor relationship and the invoice in front of you. Single-use cards give you tight, per-invoice control and the cleanest possible reconciliation. Multi-use cards reduce the administrative lift of constantly re-enrolling vendors and keep subscription and recurring-payment workflows simple. Most AP teams running a mature virtual card program end up using both.

Key Takeaways

• A single-use virtual card is issued for one transaction and dies after it clears. A multi-use virtual card lives across multiple payments to the same vendor or inside the same workflow, controlled by spend limits and expiration dates instead of single-transaction termination.

• Single-use cards are the natural fit for AP workflows where the invoice amount, the vendor, and the payment window are all known in advance. One card, one transaction, one ledger entry.

• Multi-use cards fit ongoing vendor relationships, subscription management, and any workflow where re-issuing a new card for every invoice would create more friction than it's worth.

• Fraud exposure differs by type but isn't one-directional. Single-use cards close the post-transaction exposure window almost entirely. Multi-use cards rely on merchant locks, amount caps, and expiration dates to control the exposure surface.

• Virtual card payment volume in the United States hit roughly $662 billion in 2025, up about 25% year over year (Bottomline Technologies, 2025), with single-use cards carrying the strongest growth inside AP automation workflows.

What Is a Single-Use Virtual Card?

A single-use virtual card is a 16-digit card number, with its own CVV, expiration date, and billing address, generated for exactly one transaction. Once that transaction settles, the card number is dead. Any second attempt to charge it declines. The card exists for hours or days rather than years, and it carries controls — a merchant lock, an amount cap, a tight date window — that make it almost useless outside its intended purpose.

The point isn't just security, though that's usually the feature vendors sell on. The more interesting point is that a single-use card ties one payment to one vendor to one invoice with zero ambiguity. When the card clears, the accounting entry practically writes itself. There's no reconciliation exercise to figure out which invoice a charge was for, because the card was built for exactly that invoice.

How does a single-use virtual card actually work?

An AP manager approves an invoice of, say, $8,432.17 from a vendor. The AP system calls the card-issuer API and generates a new virtual card capped at that amount, locked to that vendor's merchant ID, and set to expire in 72 hours. The card number is pushed to the vendor through a portal, email, or a direct API handoff, the vendor runs the charge, and the transaction settles. The card closes automatically after that. Any later attempt to charge it — from the vendor's billing department, a breach of the vendor's database, or a rogue employee — declines because the card is already done.

The whole cycle takes seconds on the issuing side and looks like a normal card payment on the vendor side. No vendor enrollment in a special payment program, no handoff to a new rail. It's just a card charge, minus the ability to run it a second time.

What's the Difference Between Single-Use and Multi-Use Virtual Cards?

Here's the direct side-by-side most guides skip over:

Both run on the same card networks. Both earn the same underlying interchange-based rebates. Both can be configured with merchant locks and spend controls. The difference is how long the card lives and how many transactions it's meant to process before it closes.

Where do single-use cards win?

Single-use cards win anywhere the invoice amount, the vendor, and the timing are all knowable in advance. That covers most traditional AP work. A controller paying 80 invoices in a month doesn't need 80 persistent card numbers floating around — she needs 80 clean payments that tie back to 80 approved invoices. Single-use cards give her exactly that, with no leftover card numbers to manage, no vendors holding a card that could be misused, and no reconciliation exercise to match transactions to invoices.

They also reduce one of the most expensive vendor-payment mistakes — paying the wrong amount or the wrong vendor. A finance team that runs over 1,500 vendor templates in its bank portal eventually pays the wrong one. Single-use cards compress that error surface. The card only works at the merchant it was built for, for the amount it was built for. An accidental misroute declines.

Where do multi-use cards make more sense?

Multi-use cards make more sense anywhere re-issuing a card for every transaction would create more friction than value. Think of a SaaS vendor your company pays $2,400 a month. You could issue 12 single-use cards a year, one per invoice. Or you could issue one multi-use card locked to that merchant, capped at a monthly limit, with a 12-month expiration. Same vendor, same controls, a lot less administrative ceremony.

Multi-use cards also fit situations where the exact amount isn't known at the time of issuance — utilities, usage-based cloud services, variable telecom bills. You want the card to work, within guardrails, without a human generating a new card for every billable event. That's what multi-use cards are for.

When Should Your Business Use a Single-Use Virtual Card?

Use single-use cards when you already know what you're paying for, who you're paying, and how much it costs. The common scenarios:

• Approved invoices from known vendors. This is the bread-and-butter AP use case. Invoice comes in, gets approved, card gets generated, payment clears, card dies.

• One-off vendor engagements. A vendor you'll use once. A consultant, a contractor for a specific project, a travel booking made centrally. No reason to leave a persistent card number in their system.

• Unfamiliar or higher-risk vendors. New vendors you haven't built trust with yet. A single-use card lets you pay the invoice without handing over anything that would survive the transaction.

• Audit-sensitive payments. Year-end vendor payments, grant disbursements, regulated payments where the auditor will later want to match one charge to one approval. Single-use cards leave a trail that's hard to argue with.

• Subscription trials you're not sure about. Many finance teams use single-use cards to test a new SaaS vendor without giving them a recurring payment method. If the trial works, you roll it over to a multi-use card or an ACH relationship. If it doesn't, there's nothing to cancel.

Why single-use cards are the default for automated AP

When AP automation generates cards programmatically, single-use is usually the right default. Every approved invoice becomes a card. The card number goes to the vendor, the payment clears, the card closes. The AP system already knows the invoice amount and the vendor, so the card's controls are trivial to set. You get per-invoice reconciliation at scale, without humans in the middle generating cards.

If you're running AP through spreadsheets or email approvals, the math changes — generating cards by hand gets old fast, and multi-use cards sometimes win just because they're easier to administer. If your team is planning a move toward AP automation and wants to know whether a virtual card program would earn enough rebate to justify it, ask your card issuer for a rebate review, or talk to a Corpay specialist about a side-by-side at your current AP spend.

When Is a Multi-Use Virtual Card the Better Choice?

Multi-use cards are better whenever the administrative overhead of generating a new card per transaction outweighs the control benefit. That's more common than it sounds. Four situations stand out:

• Recurring vendor relationships. Your insurance carrier, your office cleaning vendor, your payroll platform, your managed IT provider. Monthly or quarterly invoices, known vendor, predictable amount. One multi-use card per vendor, capped at an appropriate limit, with an annual expiration, keeps the accounting clean without per-invoice card generation.

• Subscription management. Software subscriptions, telecom, cloud services. Usage varies month to month, but the vendor is stable and the spend is governed by a policy cap. A multi-use card is the cleaner fit.

• Project-level spend. A marketing team running a three-month campaign across multiple vendors. A procurement lead managing a plant commissioning with a set of related vendors. The project has a budget; the card has a cap. When the project ends, the card deactivates.

• Card-not-present recurring charges. Hotel chains your sales team books with repeatedly. Travel management companies. Any vendor that will attempt repeat charges against the same card on file.

• Running multi-use cards well depends on tight configuration. Amount caps and expiration dates matter more than they do with single-use, because the card is alive longer. A multi-use card with a $50,000 monthly limit and no merchant lock is effectively a physical corporate card without the plastic — not much of a control improvement over what came before.

Are Single-Use Virtual Cards Safer Than Multi-Use?

Single-use cards close the post-transaction exposure window almost completely. Once the card has been charged and the transaction settles, the card is effectively uncharged-able. If the vendor's database gets breached three months later and your card number is in it, a thief trying to use that number runs into a card that's been closed since the week you paid the invoice. Multi-use cards don't get that protection. They're alive until they expire, so they carry real exposure for as long as they exist.

Calling single-use cards "safer" without qualifying it overstates the advantage, though. Both card types can still be intercepted during the legitimate transaction itself — the single-use card is exposed to card-not-present fraud during the window between issuance and settlement, same as a multi-use card. What single-use cards reduce is the aftermath: the chance that a card number leaked or stolen from a vendor's systems gets used later. That's a big category of B2B fraud, and single-use cards eliminate it cleanly.

Context matters here. The 2024 AFP Payments Fraud and Control Survey found that roughly 80% of organizations reported attempted or actual payments fraud. Virtual cards — single-use especially — are one of the few tools that reduce the attack surface for card-based B2B fraud, because the card is only valuable for the narrow window in which it's meant to be used. That's why single-use card issuance paired with AP automation reduces fraud exposure further than either approach does alone.

What's the real fraud advantage of single-use cards?

The real advantage is that the card's useful lifespan is compressed to roughly the time between issuance and settlement. A thief who gets the number a day later can't do anything with it. A thief who gets the number during that window still has to defeat merchant locks, amount caps, and (often) a closed-loop vendor relationship. Everything that makes a card useful to a thief — persistence, flexibility, reuse — is turned off by default on a single-use card.

What single-use cards don't protect against

Single-use cards don't protect against the initial transaction being fraudulent. If you approve an invoice that's part of a business email compromise attack, and the invoice directs payment to a fake vendor, a single-use card will clear that payment the same as any other card. The card's controls assume the invoice is legitimate. If the upstream approval process is broken, single-use cards don't save you.

They also don't protect against insider misuse by the person generating the card. Someone with authority to issue virtual cards can issue one to a vendor they control. That's a policy and access-control problem, not a card-type problem.

How Do Single-Use Cards Fit Into AP Automation?

AP automation and single-use virtual cards fit together almost as if they were designed for each other. The AP system already knows the approved vendor, the approved amount, and the approval window. Those are exactly the parameters a single-use card needs. The automation loop looks like this: invoice arrives, routes through approval, lands as approved in the AP system, system calls the card API, card is issued with the right controls, card is pushed to the vendor, vendor charges the card, card closes, accounting entry posts.

Every step is clean. There's no manual card generation. There's no manual matching of transactions to invoices, because each card only ever clears one transaction. The rebate side of the equation works the same way it would on a physical card program — card spend earns rebate based on total program spend, and virtual card volume counts toward the same tier as physical card volume when the program is set up under one issuer.

This is where running a mature virtual card program pays off twice. You get the fraud and reconciliation benefits of single-use card issuance, and the rebate economics of card-based B2B payments at scale. The payback shows up on the P&L as lower AP processing costs (AP automation combined with virtual cards tends to drop per-invoice cost from around $9 to around $2 based on industry benchmarks) and on the rebate side as quarterly earnings. Pair that with the pillar context in the complete guide to virtual cards and the mechanics make sense.

How Corpay Runs Single-Use and Multi-Use Virtual Cards in One Program

Finance teams that split their virtual card program across issuers deal with exactly the problems an integrated program is built to solve — fragmented reporting, split rebate tiers, two sets of card controls, and a reconciliation process that relies on spreadsheets to stitch the sides together.

Corpay issues both single-use and multi-use virtual cards through a single commercial card program, with shared controls, unified reporting, and one consolidated rebate structure. Corpay Virtual Cards support per-invoice single-use issuance for AP workflows and multi-use issuance for recurring vendors, subscriptions, and project-level spend — without finance teams managing two separate systems. On the physical side, the same program covers T&E and in-person spend, so the same rebate pool captures everything. Teams running both physical and virtual cards side by side earn a single rebate tier across all card-based spend.

The single-program advantage shows up most clearly at month-end. When someone asks what total card spend looks like, or where single-use card volume landed for the quarter, the answer comes from one report. See how a combined single-use and multi-use virtual card program runs at your spend tier, or schedule a consultation to walk through the rebate math specific to your vendor mix.

Frequently Asked Questions

The questions below come up most often from finance teams deciding between single-use and multi-use virtual cards. Answers are short for quick reference — the sections above have the full context.

Are virtual cards single-use by default?

Not by default — it depends on the issuer and the configuration. Many virtual card programs let you choose between single-use and multi-use at the moment you generate the card. Some programs default to multi-use for flexibility; others default to single-use for security. For B2B AP workflows, most teams set single-use as the default and use multi-use intentionally where recurring vendor payments make sense.

Can you reuse a single-use virtual card?

No. The whole point of a single-use card is that it's configured to clear exactly one transaction before closing. Once the transaction settles, the card declines any further charges. If you need to pay the same vendor again, you generate a new single-use card.

What is a ghost card payment?

A ghost card is a multi-use virtual card issued for a specific vendor or purpose, with no physical card ever printed and no named cardholder attached. It lives as a card number on file with the vendor and gets charged repeatedly over time. Ghost cards are essentially the "multi-use virtual card" category, with the "ghost" label signaling that no human is the cardholder — it's tied to an account or a workflow instead.

What is the difference between single-use and multi-use virtual cards?

Single-use virtual cards clear one transaction, then close. Multi-use virtual cards clear many transactions over a longer lifespan, controlled by amount caps, merchant locks, and expiration dates. Single-use cards fit invoice-level AP work. Multi-use cards fit recurring vendor relationships and subscription management. Most mid-market programs use both.

How do I create a single-use virtual card?

Through your card issuer's platform or API. Enterprise card programs typically generate cards programmatically from an AP automation system — the approved invoice triggers a card API call, and the card number is pushed to the vendor. Smaller programs generate cards manually through an issuer portal. Either way, the card exists seconds after you request it.

Can I get a single-use virtual card instantly?

Yes. Virtual card issuance is near-instantaneous because no physical card is being printed or shipped. The card number is generated in the issuer's system and immediately available for use. This is one of the reasons single-use cards fit AP automation well — there's no waiting period between invoice approval and payment.

Will my vendors accept a single-use virtual card?

From the vendor's side, a single-use card looks identical to any other card payment. They run the charge, it clears, the money lands in their account. Vendors that accept card payments of any kind will accept single-use virtual cards without any special enrollment. The only exceptions are vendors that don't accept cards at all and require ACH or check — that's a card vs non-card question, not a single-use vs multi-use question.

David Luther

Product Marketing Program Manager

David Luther, MBA is a product marketing program manager with years of experience in commercial banking, finance, and technology sectors, with research and writing appearing in financial publications.

Commercial Cards