Read summarized version with:
ChatGPT Claude Grok Perplexity Gemini

Rolling out fleet fuel cards for the first time means making a few decisions before you create a single one: how you will assign cards, which card type fits that structure, what starting cap to set, and whether to turn on the optional fuel-merchant restriction. Get those right in a small pilot batch, and expanding to the rest of the fleet is mostly repetition.

Issuing a fleet fuel card is the easy step. The decisions come first.

Creating a virtual card takes a form: pick a card type, set a cap, name the cardholder, done. The part that determines whether the rollout works is everything you decide before you fill out that form. A fleet that skips straight to issuing cards usually ends up redoing the work a few weeks in, once caps turn out too tight, restrictions turn out to block the wrong things, or cards turn out to be assigned in a way that does not match how the fleet runs day to day.

For the screen-by-screen steps of creating a card once you have made these calls, see how to set up a virtual card for fleet and fuel spend.

Decide how you'll assign cards: per vehicle or per driver

A card can be tied to a vehicle or tied to a named driver, and that choice shapes everything downstream. Vehicle-assigned cards keep fuel spend attached to a specific truck regardless of who is driving it that day, which suits fleets where drivers rotate across shared vehicles. Driver-named cards keep spend attached to a person, which suits fleets where a driver might use more than one company vehicle, or where you want the spend history to follow the individual rather than the equipment.

Match the card to how the fleet actually runs
Vehicle-assigned
One card per truck
  • Fits shared vehicles where drivers rotate across shifts or routes.
  • Spend history stays with the vehicle no matter who drove it.
  • Makes sense to label by license plate, unit number, or route.
Driver-named
One card per driver
  • Fits drivers who use more than one company vehicle.
  • Spend history follows the person, not the equipment.
  • Makes sense to label by driver name from day one.

Most fleets are not purely one or the other. A common pattern is vehicle-assigned cards for the core delivery trucks and driver-named cards for a smaller group of employees who move between vehicles. Deciding this mix before you issue anything saves you from relabeling and reissuing cards later.

Choose between a general Visa card and a named employee card

Once you know your assignment structure, the card type mostly follows from it. A general Visa card, billed to your company and assigned to a vehicle, fits the vehicle-assigned structure well: the card stays with the truck, and whoever is driving that day uses the card number directly for online or account-based fuel purchases, or adds it to a phone wallet where the driver's phone supports that. A named employee card fits the driver-named structure: the card ties to a specific person rather than a piece of equipment.

Either card type supports a monthly spending cap and the optional merchant restriction described below, so this decision is mostly about who the card belongs to, not what controls are available on it.

Set a starting cap you can raise or lower later

A cap is not a number you have to get exactly right the first time. It is a field on the card that you can revisit once spend data comes in. Sizing it well on day one just means fewer awkward declines in the first week.

  1. Pull whatever fuel spend history you already have for the vehicle or driver, receipts, a fuel log, or even a rough estimate based on typical mileage and current fuel prices.
  2. Add a cushion for a pump hold. Fuel pumps commonly place a temporary authorization hold in the $75 to $175 range before the charge settles, and a cap with no room above the expected fill-up cost can decline a normal transaction.
  3. Set the cap on the card at creation, along with the monthly limit interval the dashboard uses to reset spending each period.
  4. Watch the first week of activity and adjust the cap once you see how the card is being used, rather than treating the opening number as final.

A virtual Visa card works at merchants that accept Visa, subject to individual merchant support and network conditions, so not every fuel station's terminal behaves the same way. That is part of why the cap and the merchant restriction below work together instead of relying on either one alone.

Decide whether to turn on the fuel-merchant restriction

The merchant restriction is optional and off by default. Turning it on narrows a card to specific merchants, but the restriction works at the terminal level, not the line-item level. That means it can confirm a card is being used at a fuel station, but it cannot separate the fuel charge from a snack, a car wash, or anything else rung up in the same transaction at a station that sells more than fuel.

Turning the restriction on adds meaningful control when drivers fuel up mostly at stations that sell fuel and little else. When drivers commonly stop at convenience stores or truck stops that sell a mix of goods, the restriction will still let those charges through, so the spending cap and a periodic look at cleared transactions end up doing more of the work. Decide which situation describes your fleet before you flip the setting on for every card.

Ready to create the first card?

See the exact fields, card type options, and restriction settings on the setup walkthrough.

See the setup steps

A first rollout, step by step

Rather than issuing cards to the entire fleet on day one, run the decisions above through a small pilot group first. A pilot batch turns the guesswork above into decline and spend data before you commit the whole fleet to the same settings.

  1. Pick a small pilot group, a handful of vehicles or drivers, not the whole fleet.
  2. Choose the assignment structure and card type for that pilot group.
  3. Set a starting cap for each card, with the pump-hold cushion built in.
  4. Decide whether the merchant restriction fits this pilot group's fueling habits, and turn it on or leave it off accordingly.
  5. Issue the cards, labeling each one clearly by vehicle or driver at the moment you create it.
  6. Watch the dashboard's Declined and Pending Transactions closely for the first week, since this is where a cap or restriction that is off will show up fastest.
  7. Adjust caps or the restriction based on what that first week shows, then apply the same settings to the rest of the fleet.

Labeling cards clearly at issuance pays off later. Cards labeled by vehicle or driver at issuance are easier to identify afterward in Recent Transactions and the My Cards view, which makes the ongoing review simpler than starting from unlabeled cards. Once the pilot cards are live, running them day to day is a separate skill; see managing fleet fuel expenses week to week for how that routine works.

What this fleet fuel setup does not do

This setup does not provide per-gallon rebates or pump-level fuel data the way a dedicated fuel card network product might. What it does provide is a capped, labeled card per vehicle or driver, an optional merchant restriction, and a dashboard that shows declines, pending charges, and spend by category as they happen.

Build your documentation habits into the rollout from day one rather than adding them later. See IRS Publication 463, Travel, Gift, and Car Expenses for guidance on the records vehicle expense claims typically need. If your fleet runs commercial motor vehicles, the FMCSA's vehicle inspection and maintenance rules cover separate federal recordkeeping duties worth reviewing alongside your card rollout.

Frequently asked questions

Should fleet cards be assigned per vehicle or per driver?+
It depends on how your fleet actually runs. If several drivers rotate through the same truck across shifts, a card assigned to the vehicle keeps fuel spend tied to that truck no matter who is behind the wheel. If a driver uses more than one company vehicle, or you want spend history that follows the person rather than the truck, a named card tied to the driver works better. Pick the structure that matches how assignments actually change day to day, not how they are supposed to work on paper.
What is a reasonable starting cap if I don't have fuel spend history yet?+
Start with a nearby comparable, a similar vehicle's recent fuel receipts or a rough mileage-and-fuel-price estimate, and build in room for a pump hold. Pump terminals commonly place a temporary hold in the $75 to $175 range before the real charge settles, so a cap with no cushion above the expected fill-up cost can decline a normal transaction. Treat the first cap as a starting point you will revise after a week of real declines, not a number you have to get exactly right on day one.
Does turning on the merchant restriction guarantee only fuel purchases go through?+
No. The restriction narrows a card to certain merchants at the terminal level, not the line-item level, so it cannot separate a fuel purchase from a snack or a car wash rung up in the same transaction at a station that sells both. Treat the restriction as one control among several, not a guarantee, and use the spending cap and a periodic transaction review as backup.
Can a card be switched from vehicle-assigned to driver-named later?+
The card type is set when you issue the card. If your operational structure changes and a vehicle-assigned card needs to become a driver-named one, cancel the existing card and issue a new one under the structure you actually need. Because cards are virtual with no physical plastic to track down, retiring one and issuing its replacement does not involve a shipping cycle.
How many vehicles should be in a first rollout batch?+
A small pilot group, a handful of vehicles or drivers rather than the whole fleet at once, gives you a week of real decline and spend data before you commit caps and restriction settings across every vehicle. Expanding after that first week means every later card benefits from what the pilot group's declines already taught you, instead of every vehicle hitting the same cap-sizing mistakes on day one.
What happens if a new driver's first fill-up gets declined?+
Check the dashboard first. A decline on a brand-new card almost always means the starting cap did not leave enough room for a normal fill-up plus the pump's temporary hold, not that anything is wrong with the driver's purchase. Raise the cap for that card once you confirm the spend is legitimate, and use what you learned to size the next card in the batch more accurately.
Do I need to pick a funding source before I issue the first card?+
Yes. Each card draws from a funding source you select at creation, so decide which wallet or account will be charged before you start issuing cards to the pilot group. Getting this settled first also means you are not stopping mid-rollout to sort out funding while a driver is waiting on a card.