Stripe Issuing virtual cards for client expenses in 2026

Stripe Issuing lets a small business create virtual cards through a dashboard or API. Give each client project its own card with a spending limit, and every software subscription, ad spend or contractor payment is already sorted by client when the month ends. Virtual cards cost 10 cents each.

The problem it solves

By the end of year two, a service business often runs twenty or more subscriptions, some charged to a personal card "just for now", and a January spent working out which ones belonged to which client. The usual fix is a spreadsheet kept up to date out of guilt, which lasts until the first busy month.

The failure is not discipline. It is that the payment itself carries no information about the client. If the card does carry that information, because it was created for one project, sorting happens at the moment of spend and not afterwards.

The IRS does not tell small businesses how to do this. Its recordkeeping guidance says you may choose any system that clearly shows your income and expenses, and that good records help you keep track of deductible expenses. A card per client is one system that meets that description. It does not replace an accountant, and tax treatment depends on where you live, so check it with yours.

What Stripe Issuing does

Stripe Issuing creates cards that you control programmatically. According to Stripe's virtual card documentation, you can create virtual cards in the Dashboard or through the API, and a new card is generated immediately and available for use. Cards can be added to Apple Pay, Google Pay and Samsung Pay.

Stripe's launch post for self-serve Issuing describes spending limits that you can set on every card, with the option to approve or decline each charge in real time. A card for client A with a $150 monthly limit cannot quietly pay for client B's tools.

The result is a real Visa or Mastercard-style card number that works at merchants that accept those networks. It is a card program, not a spreadsheet trick.

What it costs

Stripe's documentation lists virtual cards at 0.10 USD each in the US, 0.10 GBP in the UK and 0.10 EUR in the EU. The launch post listed physical cards at $3 each, and stated that transaction fees were waived for the first $500,000 in volume, then 0.2 percent plus 20 cents per card transaction. That post is older than 2026, so check Stripe's current Issuing pricing page before you rely on the transaction fee.

For a business spending $30,000 a year across a dozen client projects, card fees are likely to be a few dollars. Compare that with the 2.9 percent plus 30 cents that Wise's guide to Stripe fees lists for ordinary card payments you accept: issuing is a different product with a different price, and it should not be confused with the fees you pay to get paid.

A per-client workflow

This is the setup that makes the card worth having.

1. When a client signs, create a virtual card named after the project. Set a monthly limit equal to what you budgeted for software, ads or subcontractors on that job.
2. Put every cost that belongs to that client on that card: the stock library subscription, the extra hosting, the contractor you hired for a day.
3. At month end, export the transactions for that card and attach them to your invoice if you bill costs at cost, or add a handling margin if your contract allows it. Ten to twenty percent is common, but it must be written in the agreement.
4. When the project ends, cancel the card. No later charge can slip through, and nobody has to remember which subscription belonged to which job.

The invoice then has a paper trail for each pass-through line. Clients like it because their own finance team can check it. Your accountant likes it because the categorization was done at the point of sale.

Stripe Issuing compared with the alternatives

Business credit cards from banks give you rewards and a float, but all spend lands on one card unless you pay for employee or virtual sub-cards. Business bank accounts with debit cards work the same way. Spend-management tools offer more automation, though many are aimed at larger companies and charge for the extras.

Stripe Issuing is closest to "build your own", which suits you if you already use Stripe, want many cheap cards and are happy to work from the Dashboard or API. It is a poor fit if you want cashback or a credit line. For the money side of the business, see the Stripe vs PayPal vs Wise comparison and the Wise vs Revolut vs Mercury guide.

Who can use it

Availability is the first thing to check. At launch, Stripe stated that any business in the US could activate Issuing from the Dashboard, and that businesses elsewhere could sign up to be notified. Stripe's pricing documentation now lists the UK and EU alongside the US, so coverage has grown, but it does not cover every country. If your business is registered in the Gulf, Asia or Latin America, confirm Issuing is open to you before you plan around it.

Onboarding involves verification of your business and the people behind it. Expect to provide a registered business, an address and identity details. Plan a day or two for this rather than doing it the afternoon you need a card.

What it does not solve

A few honest limits:

It does not do bookkeeping. You still reconcile, categorize for tax and keep receipts. A good export makes this faster, nothing more.

It does not replace a credit card. If rewards or a credit line matter to you, keep a credit card for the categories where they pay off.

It is built for developers first. The card controls are in the Dashboard and API. Managing cards for several subcontractors takes more setup than a consumer app would.

It does not protect you from provider risk. When Bench Accounting shut down abruptly in December 2024, thousands of small business owners had to look for a new bookkeeping solution and found it hard to pull their data out. Whatever you use, export your records on a schedule and keep a copy you control.

How Delivvo fits around the cards

Delivvo does not issue cards and does not connect to Stripe Issuing. It handles the client side of the same problem, which is showing the client what they are paying for and getting paid.

1. Quote the project in Proposals from packages and add-ons, with expenses that you pass through listed as an add-on or stated in the quote.
2. Send the contract with the quote, so the terms for pass-through costs and any handling margin are signed before the first charge.
3. Share each month's card export as a file in the client's portal, next to the invoice, so the client can see where the money went.
4. Issue the invoice from the invoicing page flow with your own number format and sequence.
5. Get paid through your own gateway. Stripe is one of the processors Delivvo connects to, along with PayPal and Square.

Delivvo takes 0 percent of what your clients pay and is never the merchant of record. Stripe Issuing and Delivvo are separate products. Nothing about one requires the other, and you can use your Stripe account for cards while clients pay through any supported gateway. Every invoice and contract carries a verification code, so a finance team can confirm a document against what you issued. The client portal also keeps messages and approvals with the project, so a question about a charge sits next to the file that answers it and not in a long email thread. If you run a team, team structure lets you give people only the access they need to the client records.

This sits inside Delivvo's CRM for service businesses. More on how payments work.

FAQ