Pay one vendor, once, with a single-use card
Not every vendor is a standing relationship. When you only expect to pay someone a single time, a virtual card built for exactly one invoice keeps your everyday company card out of a billing system you will probably never touch again, and you cancel it once the job is done.
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:
Why a one-off vendor payment fits a single-use virtual card
Most businesses have two kinds of vendors: the ones they pay on a schedule, and the ones they pay exactly once. A rental company for a single weekend job. A freelancer for one project. A supplier you use for a single order and have no plan to reorder from. That second group rarely gets a second thought about payment method, so the everyday company card ends up covering it by default. A single-use virtual card for a vendor payment is built for exactly this situation: one number, scoped to one invoice, for a vendor you may never bill again.
The problem is that handing over your everyday card number creates a standing relationship you never intended. The vendor's billing system now holds a live number that can be charged again, whether from a data breach, a mistaken duplicate charge, or a support agent processing something unrelated months later. A card scoped to one invoice removes most of that tail risk, since the number goes back to being useless to that vendor once you cancel it.
Three things stop happening the day you switch to a capped single-use card for these payments:
- Your everyday card number stops sitting in a vendor's system you will likely never buy from again.
- A one-time invoice stops being able to turn into a surprise later charge, because the card that paid it no longer works after you cancel it.
- Reconciling a one-off purchase stops requiring you to search your main card statement for a single line among every other vendor's charges.
What a virtual card actually is
A virtual card is a Visa card number, expiration date, and security code issued without a physical card printed, drawing from a wallet you fund rather than a separate bank account. Every card you create can carry its own spending limit instead of sharing the limit on your main card, which is the mechanic that makes the one-off use case work: nothing about the card format is special, only the fact that you scope this one to a single vendor's invoice.
It is still a full Visa card number, so it works at most merchants where Visa is accepted online, subject to merchant support and network conditions. Nothing stops you from requesting a physical card later if a one-off vendor turns into a repeat relationship worth keeping.
There is no separate "single-use" card type. It is a regular virtual Visa card that you create for one invoice, cap to the exact amount, and cancel once the charge settles, so it behaves like single-use even though nothing about the card itself expires on its own.
How to issue a single-use vendor card, step by step
- Add the vendor as a payee, even for a one-time purchase.
Set the vendor up in the Payees module with their contact and company details, so this one purchase has a record attached to it even if you never buy from them again.
- Create a card capped to the exact invoice.
Choose the Visa Card type, select the funding source, and set the spending limit to the exact invoice amount instead of a rounded-up buffer. Label the card with the vendor's name and the invoice number so it is easy to find later.
- Hand the vendor the card number instead of your everyday card.
Enter the number, expiration, and CVV in the vendor's billing portal, or share the details the way you would any payment method. A charge above the cap is declined.
- Cancel the card once the charge settles.
Confirm the charge moved from pending to settled on your dashboard, then cancel the card. Cancelling stops new authorizations, so the number cannot be used again for anything else.
Ready to pay a vendor you'll likely only pay once?
See the full cap-and-cancel mechanic, a worked invoice example, and the settlement details on the complete guide.
Paying a one-off vendor with and without a capped card
One number ends up covering every vendor you'll never see twice.
- Your everyday company card number sits in a vendor's system you may never buy from again.
- There is no natural moment to turn off access once the one-time job finishes.
- A one-off purchase blends into hundreds of other line items on your main statement.
- A later breach at the vendor's end exposes your everyday card along with it.
- Approving a rounded-up amount instead of the exact invoice figure becomes the default habit.
Each one-off vendor gets a number that belongs only to their invoice.
- The vendor only ever sees a number tied to this one purchase.
- Cancelling the card after settlement is the built-in off switch.
- The charge sits on its own card, so matching it to the invoice takes one look, not a search.
- A later breach at the vendor's end exposes a card that no longer works, not your everyday spend.
- Capping to the exact invoice amount becomes the default, since the form asks for it every time.
Three one-off vendor payments, three capped cards
These examples are illustrative, not real customer accounts, but they follow the same cap-and-cancel pattern described above.
A single weekend equipment rental
Hartwell Grounds Co. needs a mini excavator for one weekend job and picks a rental yard it has never used before, for a project it does not expect to repeat. The rental agreement comes to $640 for the deposit and two-day rate. Instead of putting that on the company card, the office manager caps a card to $640, hands the number to the yard's billing desk, and cancels it once the equipment is returned and the final charge settles. When the yard's system tries to add a $45 late-return fee a few days later, on a card already cancelled, the charge simply does not go through, so the fee has to come as a separate conversation instead of an automatic add-on to the original number.
A single product photo shoot
Driftwood Creative books a freelance photographer for one product shoot rather than a standing retainer. The agency caps a card to the photographer's quoted rate and sends the number for the invoice. If the same photographer gets booked again next quarter, a fresh card goes out for that job instead of reusing the old number, so each booking has its own clean record.
A single fundraiser's AV setup
Cedar Grove Youth Center hires an audio-visual vendor to run sound and livestreaming for one fundraiser night. The card is capped to the vendor's quote, the vendor charges it the day of the event, and the center cancels the card the following week once the invoice settles, well before the vendor's system could bill it again for anything unrelated to that night.
Nonemployee vendor payments and year-end reporting
A one-off vendor is often an individual or small business you are paying for services rather than goods, which can put the payment in scope for Form 1099-NEC nonemployee compensation reporting once your total payments to that vendor for the year cross the current IRS reporting threshold. Check the current threshold and filing rules on the IRS Form 1099-NEC instructions before year-end.
Because the card, the invoice, and the payee record all sit together when you add the vendor to the Payees module, a one-off payment is easier to pull at tax time than a charge buried inside hundreds of other line items on your main card statement. One card mapped to one invoice is effectively a clean, self-contained record for that vendor's full-year total.
Why accounts payable teams prefer capping one-off vendor cards
Finance and accounts payable teams end up reviewing fewer live card numbers when one-off vendors get their own capped cards instead of the shared company card. There is nothing to monitor long after the fact, because the card itself stops working once it is cancelled, rather than staying active and needing to be remembered.
Audits get simpler for the same reason. A reviewer looking at a single-vendor, single-invoice card does not need to separate that vendor's charge from a mixed statement of dozens of other purchases. The card's own transaction history is the audit trail.
Set up your first one-off vendor card
- Create your account.
Cards are wallet-funded with no credit check, so there is no lending decision standing between you and your first card.
- Fund your wallet from a connected bank account.
Link a bank account and move funds into your wallet, the source every card draws from.
- Go to Cards and choose the Visa Card type.
Select the funding source, set the spending limit to the invoice amount, and add the cardholder name.
- Label the card by vendor and invoice.
A clear label makes it obvious which one-off vendor the card belongs to when you review your dashboard later.
- Hand it over, then cancel it after settlement.
Once the vendor's charge settles, cancel the card. The next one-off vendor gets a fresh card of its own.
Mistakes to avoid with a one-off vendor card
Don't set the cap higher "just in case." Extra headroom above the invoice is exactly what lets an unexpected second charge clear. Match the cap to the figure on the invoice.
Don't forget to cancel once the charge settles. An uncancelled card is still a live number sitting in a vendor's system, which defeats the point of scoping it to one payment.
Don't skip the payee record because it's "just a one-time thing." If that vendor comes back next year, you will be glad the contact details and history are already saved instead of starting from scratch.
Frequently asked questions
Is a single-use virtual card a different card type from a regular virtual card?
What if the vendor's final charge is a little different from the invoice I capped the card to?
Is it worth adding a vendor as a payee if I only plan to pay them once?
Do I need a credit check to issue a one-off vendor card?
I have several one-off vendors to pay for the same event. Do I need to create each card by hand?
Is a single-use vendor card linked directly to my bank account?
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.
- Vendor payments
Single-use virtual cards for vendor payments: one card, one invoice.
Paying a vendor once and worried they will overbill, double-charge, or save your number for later? Create one virtual Visa card per invoice and cap it to the exact amount due. A charge over that figure is declined, the card cannot fund a second invoice, and once the charge settles you cancel the card so it cannot be used again. Each card maps to one bill, so reconciliation is a clean 1:1 instead of guesswork on a shared account.
June 15, 2026 · 11 min read - Vendor payments
New vendor payments: how a single-use virtual card limits your first-invoice risk
Paying a vendor you have never paid before is the riskiest invoice you will approve, because you have no history to check the request against. Verify the vendor through a channel you already trust, then cap a single-use virtual card to the exact amount due, so a padded bill or an impersonated vendor has a hard ceiling on what it can cost you.
July 11, 2026 · 7 min read - Vendor payments
What to do when a vendor's contract amount change
A vendor card carries the limit you set when you created it, not the limit written into a revised contract. When a supplier raises a rate, adds a fee, or the scope of work grows, the old cap stays in place until someone updates it, and the next invoice can bounce before anyone notices the agreement changed.
August 10, 2026 · 8 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.