Read summarized version with:

Petty cash and shared cards are how fuel receipts go missing and mileage claims get inflated. Issue each driver a wallet-funded virtual Visa, cap it to the daily or weekly fuel budget, lock it to fuel merchants, and every route expense reconciles itself. The driver spends what the job needs. Nothing more.

Petty cash floats for drivers are how small logistics businesses lose money without noticing it. The float goes out, receipts come back in pieces, and the reconciliation at month-end is a guessing game. Shared company cards are not better: one card for multiple drivers means no per-driver accountability and no visibility into which route consumed which expense.

A virtual card per driver is a different infrastructure. The driver gets a Visa number, emailed to them to add to their mobile wallet, with a hard limit that matches the job's expected expense. The card is locked to relevant merchant categories. When the shift ends, the card's history is the route's expense record, clean and ready to match against the job.

How virtual cards work for logistics driver spend

A virtual card for a logistics driver is a wallet-funded Visa issued per driver, per route, or per vehicle. You create the card, cap it to the expected route expense, optionally lock it to fuel or transport merchant categories where supported, and email the card to the driver or share the details so they can add it to their phone's mobile wallet. The driver uses the card at fuel stops, toll stations, or wherever the job requires. Every charge clears up to the cap and posts under the card label in your dashboard.

The cap is the hard limit. A charge that exceeds it, whether an attempt to exceed the fuel budget or a stop at a non-route merchant, is declined at authorization. The driver cannot overspend silently. You see the decline, and the driver contacts dispatch if they need more. That is the accountability loop petty cash can never create.

Driver spend, five controls
1
Daily cap
Set the cap to the expected fuel budget for the shift or route. Over-limit charges are declined.
2
Fuel-category lock
Restrict the card to fuel or transport merchant categories where supported.
3
Driver label
Name each card with the driver and route so every charge maps back to the right job.
4
Receipt on charge
Attach the fuel receipt to the card charge for a clean expense record.
5
Instant cancel
Cancel a driver card immediately when the shift ends or when the driver leaves.
Issue card to driverSet cap + fuel lockDriver fuels within capReconcile by route

Comparing your payment options

Card vs petty cash vs fleet card for driver expenses.

MethodSpend controlReceipt trackingReconciliationDriver accountability
Petty cashNone after handoutPaper receipts, often lostManual; missing receipts commonLow: cash is anonymous
Shared company cardNone per driverMixed; no per-driver viewHard to split by driver or routeLow: one card for everyone
Dedicated fleet cardCategory locks; cap variesDecent; card-level recordsGood for fuel; weak for other expensesMedium: one card per driver but provider-locked
Virtual card per driverHard cap per card; declines overagesPer-card receipts, digital1:1 card-to-driver, label-drivenHigh: every charge tied to one driver

A real example

Worked example
"Route 12 / Rivera" driver card for a $150/day fuel budget

How the card is set

  • Card label: Route 12 / Rivera
  • Spend cap: $150.00, the daily fuel budget for the route
  • Merchant lock: restricted to fuel merchant categories where supported
  • Funding: from the company Zil Money wallet, no credit check

What clears

  • Approved Rivera fills up for $68.40. Inside the cap, clears. Charge posts under Route 12 / Rivera with the fuel station receipt.

What gets declined

  • Declined Rivera tries to charge $155.00 at a second fuel stop. Exceeds the $150.00 daily cap, so it is declined. Dispatcher reviews before reloading.

At reconciliation

One card, one driver, all charges for the day under Route 12 / Rivera. Reconcile route fuel spend to the job without chasing receipts.

Do not treat the merchant lock as a guarantee that only fuel charges will clear. The fuel-category lock depends on how the merchant's acquirer codes the transaction. Some fuel stations also sell convenience items coded under a different MCC. The spend cap is your primary control; the category lock is a backup.

Do not cancel a driver card while an authorization is pending at the pump. Cancelling stops new charges, but a pending pump authorization can still settle. Check the dashboard for pending activity before cancelling at the end of a shift.

Virtual cards for logistics companies in India

Indian logistics and transport operators face a version of this problem that is specifically acute. Drivers often do not have business credit cards, and handing out cash for fuel creates reconciliation problems at scale. A virtual Visa issued from the company wallet and added to the driver's Google Pay or other mobile wallet gives the driver a real payment instrument without a credit application or a bank account requirement on their part.

For logistics companies paying vendors, including fuel suppliers, maintenance contractors, and toll operators, virtual cards work the same way as for driver spend: issue a card to the vendor, cap it to the expected charge, and the vendor charges within the cap. The same Zil Money wallet funds driver cards and vendor payments, so all logistics spend consolidates in one dashboard.

Virtual cards alongside fleet cards and existing payment rails

You do not have to replace your existing fleet card program to use virtual cards. Virtual cards work best for the spend that falls outside the fleet card's scope: maintenance vendors who do not accept the fleet card network, one-off equipment rentals, depot supply runs, or driver expenses in areas where the fleet card network has no coverage. Issue a virtual card for those specific situations and keep the fleet card for fuel on-network.

For companies that do not use fleet cards, virtual cards cover the full driver expense picture. Issue one card per driver with a fuel cap, and a second card per driver for non-fuel route expenses if the jobs require it. Both cards draw from the same wallet and both post to the same dashboard.

Building the program

The compound effect of a card-per-driver program is that route-level expense visibility becomes automatic. You stop asking "how much did Route 12 spend last week?" and start reading the answer directly from the card labeled Route 12. No receipt chasing, no petty cash reconciliation, no month-end spreadsheet archaeology. The card is the record.

Run the whole operation from one Zil Money wallet. Driver cards, vendor payments for fuel suppliers, maintenance contractor payments: all draw from the same balance and all post to the same dashboard. Logistics spend stops being scattered across cash, cards, and bank rails and becomes one thing you manage in one place.

People also ask

Can drivers use virtual cards at fuel pumps?

Yes. The virtual card is a Visa and works at any merchant that accepts Visa, including fuel pumps that allow card-not-present or mobile payments. For pay-at-the-pump, the driver can use their phone's mobile wallet.

What if a driver needs more fuel than the cap allows?

The charge over the cap is declined. The driver contacts the dispatcher, who can reload the card or issue a new one from the dashboard.

Can I issue cards to all drivers at once?

Yes. Upload a spreadsheet with each driver's name and route, and issue cards for all of them in one run.

How do I handle toll payments?

Issue a separate card for toll accounts or add tolls to the driver's card with a cap that covers both fuel and expected tolls for the route.

What happens when a driver leaves the company?

Cancel their card immediately from the dashboard. Cancelling stops all future charges. Any pending authorization at the time of cancellation can still settle.

Is there a credit check to issue driver cards?

No. Cards are wallet-funded. You fund your Zil Money wallet and draw from it to issue cards, with no credit application or personal guarantee.