Virtual card types: which one to issue and when
Single-use, merchant-locked, employee, department, and gift cards are the same technology under five sets of rules. Here is what each one is for, how to choose between them, and the mismatch that breaks a renewal.
VirtualCardMaker.com, powered by Zil Money, is a financial technology company, not a bank. Banking and money movement services are provided through partner financial institutions and licensed service providers. FDIC insurance coverage applies only to eligible deposit products and accounts, and is subject to applicable terms, conditions, limitations, and requirements. Additional information regarding partner institutions, products, and services is available in the applicable terms and agreements.
Read summarized version with:
Every virtual card is the same thing underneath: a card number your business controls, with its own limit and its own off switch. What separates one type from another is the set of rules attached to it, and those rules are what decide whether a card is right for a purchase.
The question worth asking before you issue one is not which type is best but what should happen to this card when the spending stops. A card for a single supplier order should be dead by tomorrow. A card for a subscription should outlive the person who set it up. Those two answers point at two different card types, and getting them the wrong way round is the source of most of the mess a card program creates.
The five types, side by side
These are the shapes most virtual card programs use. A given card can combine them — an employee card can also be merchant-locked — so read the table as a starting point rather than five sealed boxes.
| Card type | Best for | Lifespan | Who usually holds it |
|---|---|---|---|
| Single-use | One order from an unfamiliar merchant | Closes after the first charge | Whoever is buying, for that purchase only |
| Merchant-locked | A subscription or an ad account billed every month | Runs until you close it | The team that owns the tool |
| Employee card | Recurring spend by one named person | Runs until the person leaves the role | The employee |
| Department or project card | A shared budget with one owner | Runs for the length of the project | The budget owner |
| Virtual gift card | Recognition, rewards, and one-off thank-yous | Until spent or expired | The recipient |
The type is a policy, not a product. Nothing physical changes between a single-use card and an employee card. Both are a number, a limit, and a set of rules. Choosing a type is choosing which rules you want enforced for you rather than remembered by someone.
- Ask how many times this card should ever be charged.
Once means a single-use card. Every month, indefinitely, means a merchant-locked card. Unpredictably, by a person you trust, means a named employee card.
- Set the limit to the expected amount, not the comfortable one.
A limit set at the real invoice total is a control. A limit set at a round number well above it is a suggestion, and it will not stop a duplicate charge or a surprise renewal.
- Lock the card to the merchant wherever the merchant is known.
For anything with a named vendor — a SaaS tool, an ad platform, a freight bill — locking the card means the number is useless anywhere else, including in the hands of whoever eventually breaches that vendor.
- Name the card after the commitment, not the person who created it.
“Design tools — Figma” survives a handover. “Priya’s card” does not, and it is the reason so many statements have line items nobody can account for a year later.
- Decide who closes it, and when.
A card with no agreed end condition is a subscription that renews forever. Write the end into the card's name or its limit so the decision does not depend on someone remembering.
A single-use card is not the right home for a subscription. It is the commonest mistake in a new program: someone issues a single-use card for the first month of a tool, the card closes after that charge, and the renewal declines a month later — usually on the morning it is needed. Subscriptions belong on a merchant-locked card that stays open.
Closes itself once the charge lands.
- The number is worthless the moment the purchase completes.
- Nothing to cancel later, and nothing to forget about.
- Best for one-off supplier orders and unfamiliar merchants.
- Wrong for anything that bills again.
Stays open until you close it.
- Handles renewals, top-ups, and variable monthly amounts.
- Can be locked to one merchant, so a leak is still contained.
- Best for subscriptions, ad accounts, and named employees.
- Needs an owner, or it quietly outlives its purpose.
Ready to issue your first card?
Start with one subscription and one merchant-locked card, then add the other types as you find you need them.
One card for everything
A single company card behind every subscription, every ad account, and every field purchase means one number to leak and one statement to unpick at month end. Cancelling a tool means asking the vendor to stop, because the card cannot be closed without breaking the twenty other things charging to it.
One card per commitment
Give each merchant, person, or project its own card and the statement sorts itself: the line item names the thing it paid for. Ending a commitment is closing its card, which takes a click and needs nobody's cooperation.
The agency runs eleven SaaS subscriptions, two ad accounts, and about a dozen one-off supplier orders a month. Merchant-locked cards cover the subscriptions and the ad accounts, one each. Single-use cards cover the supplier orders. Two account managers hold employee cards for travel. The month-end statement now reads as a list of names rather than a list of descriptors nobody recognises.
Can one card be more than one type?
How many virtual cards should a business have?
What happens to a merchant-locked card if the vendor changes its billing name?
Are virtual gift cards the same as employee cards?
Where to start
Pick the two commitments that cause the most month-end confusion — usually the biggest subscription and whatever the team buys ad hoc — and give each one the card type that matches how it ends. A merchant-locked card for the first, single-use cards for the second. That covers most of the spend and most of the risk, and the remaining types will suggest themselves as you go.
Issue a card with these rules on it.
Set the limit, restrict the merchant, choose the active window, and send the card. Every charge lands in one dashboard, already attributed.
Build one in Card StudioNext, on the same problem.
- Card types
Employee virtual cards
Issue each employee a Visa card in their own name. Set role-based spending limits, route larger charges through manager review, and see every transaction in one dashboard.
· 3 min read - Card types
Vendor virtual cards
Pay each vendor with its own virtual Visa card. Restrict the card to the intended vendor based on supported controls, cap the spend, and cancel the card when the relationship ends.
· 3 min read - Card types
Payroll cards for employees
Pay employees and contractors on a reloadable Visa card. Load wages each pay cycle with no bank account required from the recipient, then reload the same card next time.
· 4 min read
The next vendor gets its own Visa card.
Not the shared one. Its own number, its own ceiling, its own line in the ledger.