Single-use virtual cards for vendor payments: one card, one invoice.

Read summarized version with:

ChatGPT Claude Grok Perplexity Gemini

A single-use virtual card pays one vendor invoice and nothing more. On VirtualCardMaker you create one card per invoice and set its spend cap to the exact amount due, so a charge over that figure is declined and the card cannot fund a second invoice. After the charge settles you cancel the card, which closes it to any new use. The spend cap is the deterministic control here. There is no automatic self-destruct; "single-use" is how you operate the card (exact cap, then cancel), not a separate feature. Cards are wallet-funded with no personal bank link and no credit check, the number is emailed to your vendor or added to your wallet, and each card maps to one invoice for a clean 1:1 reconciliation.

If you pay a vendor once or rarely, the worry is always the same: hand over a card number and you lose control of it. The contractor saved your details after the job was done. The supplier added a fee you never approved. You got charged twice for the same bill. A single-use card flips that, because the card you give the vendor can only do exactly one thing: pay this invoice, up to this amount, this once.

This guide assumes you have already decided single-use is the right call and goes deep on the vendor mechanic itself: how to lock a card to one invoice, what the controls actually do, and the step-by-step playbook. If you are still weighing the choice, start with the neutral comparison of single-use vs reloadable virtual cards. For the broader program of running supplier payments with virtual cards across your whole back office, see virtual cards for accounts payable.

What is a single-use virtual card for vendor payments

A single-use virtual card is a real Visa card number you create for one bill. You fund it from your wallet, cap it to the invoice total, give the number to the vendor, and retire it once that one charge has cleared. Nobody mails you plastic, and the number is not tied to your operating account or a credit line, so a leaked or saved number cannot reach the rest of your money.

The point of "single use" is containment. A reusable card that touches many vendors is a single number that, if compromised or quietly saved, exposes every payment behind it. A card scoped to one invoice has a blast radius of exactly that invoice. The vendor gets a number that only works once, for one amount, and that is the whole appeal for an accounts payable team paying someone they may never use again.

How "single use" actually works here: exact cap, then cancel

Here is the honest mechanic, because it matters. There is no button that makes a card detonate after one swipe. What makes a card single-use on this platform is two deliberate steps you take.

First, you set the spend cap to the exact amount on the invoice. That cap is the deterministic control: the network checks every charge against it, and a charge over the cap is declined, full stop. Because the cap equals one invoice, the card physically cannot fund a second bill. Second, after the vendor's charge moves from pending to settled, you cancel the card. Cancelling closes it to any new charge. Cap plus cancel is what "single use" means in practice, and framing it that way is more truthful, and more reliable, than promising a self-destruct feature that does not exist.

How an exact-amount cap stops overbilling and duplicate charges

The cap is the part that does the policing, so set it to the exact figure on the invoice, not a rounded-up number. If the bill is $2,480.00, the cap is $2,480.00. When the cap equals the amount due, the agreed charge clears and anything larger is declined at authorization. A vendor that tries to add a fee you never approved runs straight into the cap, and you find out at the moment of the charge instead of weeks later on a statement.

Duplicate charges hit the same wall. If a vendor accidentally, or otherwise, tries to charge the invoice twice, the first charge consumes the cap and the second has no room left, so it is declined. You are not relying on catching the double-bill in review; the cap simply does not leave the headroom for it. This is the deterministic guarantee, and it is the reason the cap, not any optional lock, is your primary control.

Authorization vs settlement: what cancelling does and does not stop

This is the one place people get burned, so it is worth being precise. A card charge has two moments. First the vendor authorizes the charge, which places a hold against the cap. Later the charge settles, which is when funds actually move. Cancelling a card stops new authorizations, but it does not reach back and undo an authorization that is already in flight.

In plain terms: if you cancel the card before the vendor's already-approved charge settles, that pending charge will still settle and still count against the cap. Cancelling stops the next charge, not the one already authorized. So the rule is simple. Confirm the expected charge has settled before you treat the card as done, then cancel to close it to anything new. That order keeps you honest about what the control actually does.

When to use single-use vs a reloadable or recurring vendor card

Single-use is not always the answer. It shines when you pay a vendor once, or rarely, and you want the tightest possible control and record for that one bill. It is the wrong tool for a vendor you pay every month, where spinning up a fresh card each time is just friction. The table below is the quick read; for the full side-by-side, see single-use vs reloadable virtual cards.

How to issue a single-use vendor card step by step

The flow is short and repeatable. If you do this for a one-off vendor, the whole thing fits on a single screen. For the broader vendor workflow, including approvals and recurring suppliers, see how to pay vendors with virtual cards.

1. Create the card and fund it from your wallet. Name it for the invoice, such as MP-2480 Meridian Print Co. There is no credit check and no personal bank link.
2. Set the spend cap to the exact invoice amount. Match the cap to the figure on the bill, not a buffer. This is the control that declines overbilling.
3. Email the number to the vendor or add it to your wallet. Send the card details to the vendor for this invoice, or add it to a wallet to charge the vendor yourself.
4. Let the vendor charge within the cap. A charge inside the cap is approved; anything over is declined. Partial charges are fine as long as the running total stays within the cap.
5. Cancel the card after the charge settles. Once the charge moves from pending to settled, cancel it so no new charge can land.
6. Reconcile 1:1. Match the one settled charge to the invoice, attach the receipt, and close the bill.

How single-use cards give a clean 1:1 match for reconciliation

This is the quiet payoff. Because each card carries one invoice and ends with one settled charge, reconciliation stops being detective work. One card, one bill, one charge, one receipt. You are not staring at a shared account trying to remember which of fifteen charges belonged to which vendor, and there is no leftover balance sitting on a card asking what it was for.

That tidiness compounds at month-end and at audit. A reviewer can trace any payment from invoice to card to settled charge in one straight line, and the card cannot have been quietly reused for something else, because it was scoped to one bill and then cancelled. If reconciliation across many suppliers is your real pain, this same one-to-one discipline is what powers running supplier payments with virtual cards at scale.

Other locks you can add, and how reliable each is

The cap is your primary control, but you can layer other locks on a card. Be clear-eyed about which are guarantees and which are best-effort.

• Spend cap. Deterministic. A charge over the cap is declined every time. This is the one you rely on.
• Merchant or category lock (where supported). Restricts the card to a given vendor or merchant type.
• Location lock (where supported). Restricts charges by geography.
• Time window (where supported). Restricts when the card can be charged.

The honest caveat: merchant, category, location, and time locks are probabilistic, not deterministic. They are checked at authorization using the data the vendor's acquirer passes through the network, and that data is not always complete or correctly coded. Treat them as useful extra layers where supported, but let the exact-amount cap, plus cancelling after settlement, be the controls you trust.

A real example: one vendor invoice, one capped card

Here is a single bill walked end to end so the mechanic is concrete. You owe Meridian Print Co. one invoice, MP-2480, for $2,480.00.

Mistakes to avoid

People also ask