How to set up a virtual card for fleet and fuel spend

Read summarized version with:

ChatGPT Claude Grok Perplexity Gemini

Why fleet and fuel spend needs its own control system

A virtual fleet card is a Visa card issued to one vehicle or driver, with its own spending cap, an optional merchant restriction, and a dashboard record of every charge, so fuel and maintenance spend stays sorted by vehicle instead of blending into one shared statement.

Most small fleets start simply: one or two shared company cards passed between drivers, or a single fuel account tied to the business's main bank account. That works until the fleet grows past a couple of vehicles. Once several drivers share a card or a login, a fuel purchase, a maintenance charge, and an unrelated errand can all land on the same statement line, and figuring out which vehicle actually needed that spend turns into real reconciliation work at month end.

Virtual cards for fleet and fuel expenses solve that narrower problem: giving each vehicle or driver a card that is capped, restricted, and tracked on its own, so the sorting happens as charges come in. For the fuller product case, see virtual cards for fleet expenses.

Give every vehicle or driver its own card

The card boundary is the first decision, and it is the one that gives every other control something to attach to. Issue one card per vehicle or one card per driver, whichever matches how your fleet is actually run, rather than handing out a single card that several people use.

• A leaked or compromised card number is limited to that one vehicle's fuel and maintenance history.
• Every statement line already tells you which vehicle it belongs to, since it can only be that one card's charge.
• Cancelling one driver's card does not touch fuel access for the rest of the fleet.

Use a general Visa card, billed to the company, for vehicle-assigned cards where no single person is the long-term owner. Use an employee card, issued to a named driver, when you want that driver's name attached to every charge on the statement. The Cardholder Name field has a 26-character limit, so a short vehicle number or a driver's first name and last initial usually fits better than a full description; put the longer description in the card's label field instead, which exists for exactly that kind of internal tagging.

Size the cap to how your fleet actually spends

A cap set without looking at a vehicle's real fuel and maintenance history is the most common setup mistake. Size the cap to a monthly fuel and maintenance budget for that specific vehicle, based on its normal mileage and maintenance schedule, since the limit interval resets monthly. A flat number copied onto every card in the fleet ignores how differently a delivery van and a long-haul truck actually spend.

• If a charge would put the card over that cap, it is intended to be declined, and that decline appears in your dashboard as its own transaction.
• A fuel pump commonly places a temporary hold for more than the actual fill-up, often in the $75 to $175 range, before settling the real amount later. Build that headroom into the cap, or a card can decline at the pump even when the vehicle's real spend is well under its monthly cap.
• Revisit the cap whenever a vehicle is reassigned to a different route or its maintenance schedule changes, and any time declines start showing up that don't match a real increase in spend.

Restrict where a fleet card can be used

Beyond the cap, card controls include an optional merchant restriction, off by default so a new card works at most merchants where Visa is accepted, subject to merchant support and network conditions. Turning that restriction on narrows a card to specific merchants if your account's controls support it, which matters most for a fuel card that should not also be paying for something unrelated to the vehicle.

A merchant restriction scoped to a category like fuel stations works at the terminal level, not the line-item level: it approves or declines the whole ticket based on how that pump or register is coded, not each item a driver buys there. A driver filling up at a station that also sells snacks or a car wash still gets one approved charge for the full total, since the card cannot separate the fuel from the rest of that same transaction. Confirm what category-level restriction your account's controls actually support before relying on it as your only safeguard against off-purpose spend, and pair it with the spending cap above for the strongest combination.

How to set up a virtual card for a vehicle or driver

1. Choose the card type.

   Pick a Visa card for a company-billed, vehicle-assigned card, or an employee card if you want the card issued and its statement tied to a named driver.

2. Pick the funding source.

   Choose which wallet funds the card. That wallet is charged whenever the card is used.

3. Set the spending limit and interval.

   Enter a dollar cap sized to that vehicle's normal fuel and maintenance spend. The limit interval confirmed in the dashboard refreshes the cap monthly.

4. Name the cardholder and label the card.

   Put the driver's name on the card, and use the card label field to tag it by vehicle number, route, or unit ID, so every future statement line already carries that context.

5. Add restrictions where they matter.

   Apply a merchant restriction if your account offers it, and a time restriction if the card should only be active during scheduled routes or shifts.

6. Issue the card and hand it to the driver.

   Use the card number directly for online and account-based fuel purchases, or add it to a driver's phone wallet where mobile wallet provisioning is available, to tap where contactless is accepted.

See who spent what, vehicle by vehicle

Once cards are labeled by vehicle, the dashboard does most of the reconciliation work by itself. Every charge appears in your dashboard under the card that made it, with the merchant name, category, and category code attached to that transaction. A fuel purchase and an unrelated charge look different at a glance instead of blending into one undifferentiated list, the same problem a shared company card creates for anyone trying to stop overspending on a general company card.

• The Transaction Categories view breaks down spend by category across the whole fleet. Fuel and maintenance costs show up as their own slice instead of folding into general business spend.
• The Recent Transactions table filters and exports, letting a fleet manager building a monthly cost report by vehicle pull the data instead of rebuilding it from paper receipts.
• A category rule can watch for a specific merchant name and automatically categorize or tag future charges from it, so a driver stopping at the same station repeatedly does not need relabeling by hand every time.
• Attach a receipt directly to a transaction. A maintenance charge that needs backup documentation has it on file at the transaction level.

The IRS expects businesses to keep records that support vehicle-related deductions. See IRS Publication 463, Travel, Gift, and Car Expenses for what documentation to retain for vehicle and travel expenses. Fleets running commercial motor vehicles also have separate federal recordkeeping duties under the FMCSA's vehicle inspection and maintenance rules, which is a useful reference alongside your own spend records.

Cancel a card the moment a driver or vehicle leaves

A driver who leaves or a vehicle that gets sold should not keep an active fuel card. Cancel the card from your dashboard to stop it from being used again. A charge already authorized just before you cancel, like a pump hold, can still settle afterward, so cancel as soon as you know a driver or vehicle is leaving rather than waiting until end of day. Because the card was scoped to one vehicle or driver in the first place, cancelling it does not affect fuel access for the rest of the fleet, and there is no physical card to track down or destroy first. Issue a replacement card, capped and restricted the same way, for whoever or whatever takes that vehicle's place.

What a fleet virtual card does not do

This is a general-purpose virtual Visa card with fleet-relevant controls, per-vehicle caps, merchant restrictions, and dashboard visibility, not a dedicated fuel card network product. It does not provide per-gallon rebates or pump-level fuel data, the kind of detail a fuel-specific card network is built around.

What it gives you instead is a spending boundary and a visibility layer: a cap sized to the vehicle, a restriction if your account supports it, and a dashboard record of every charge. A fleet that already depends on fuel-network rebates for its highest-mileage vehicles can keep that program for those vehicles and add a virtual card for the ones it does not cover, technicians and service vans included, the same population covered in virtual cards for field service businesses. For a related look at controlling spend across routes and drivers, see virtual cards for logistics companies.

Frequently asked questions