Managing WEX Cards in One Platform Instead of a Separate Portal
Running a card portal alongside your fleet system means reconciling two records of the same fuel. Here is what consolidating them changes day to day.
The card portal is not the problem. Card portals are generally fine at what they do — issuing cards, setting limits, producing transaction reports.
The problem is that it is a second place. Your vehicles, drivers, maintenance history, and fuel site data live in one system, and the card program lives in another, and every question that spans both requires a person to bridge them.
01 What the two-system arrangement actually costs
Not much per instance. A lot per year.
A new driver needs setting up in two places. A departing driver needs deprovisioning in two places, and the second one is the one that gets missed.
Transaction data has to be exported and reconciled to vehicles, which means someone matching card numbers to assets on a schedule that slips whenever the month is busy.
Odometer readings captured at the pump sit in the card system doing nothing, while the fleet system runs maintenance schedules off mileage entered manually somewhere else — two mileage records for the same vehicle, diverging.
And cost per mile, the number that justifies the whole exercise, requires assembling fuel spend from one system and mileage from another.
02 What consolidation changes
When cards are issued and managed inside the fleet platform, several things stop being tasks.
A driver is provisioned once, with a card assigned to them, their vehicle, or their department
Transactions post to the vehicle as they happen, with cost attached to the asset record
Pump odometer readings update vehicle mileage, advancing maintenance schedules automatically
Cost per mile recalculates continuously rather than being assembled
Retail purchases appear alongside private site fueling in the same reporting
Deprovisioning is one action, so a leaver’s card does not survive them
None of those individually justifies a platform change. Together they remove a recurring manual reconciliation that most fleets have quietly accepted as the cost of having fuel cards.
03 The card lifecycle, practically
Cards need constant small administration. Issuing for new hires, replacing damaged and lost ones, locking when something looks wrong, cancelling when someone leaves, reassigning when a vehicle changes hands.
The friction in a separate portal is not the individual action — it is the context switch and the credential. The person best placed to notice that a card should be locked is often the person with no portal login, so the request goes through someone else, and the delay is when the exposure sits.
Managing cards where vehicles and drivers are already managed puts the action next to the person who noticed the problem.
04 Assignment structures that match how you operate
Cards can be assigned to a driver, to a vehicle, or to a department, and the choice changes what your reporting can answer.
Driver assignment attributes spend to people, which suits operations where drivers move between vehicles. Vehicle assignment attributes spend to assets, which is what cost per mile and total cost of ownership require. Department assignment suits cost allocation and chargebacks.
Most fleets need more than one of these views, which is an argument for holding the card, the driver, and the vehicle in the same system rather than picking one dimension in a card portal and living with it.
05 What you still need the issuer for
Consolidation does not remove the issuer relationship, and it should not be sold as though it does. Account terms, credit, billing, network acceptance, and dispute resolution remain with the card program.
What moves is the operational layer — issuing, controlling, assigning, and everything that happens to a transaction after it clears.
06 Where EKOS fits
EKOS manages the full fuel card lifecycle in the platform: view active cards, issue and replace, lock, cancel, and monitor status, alongside the rest of your fueling operation. Cards associate to drivers, vehicles, departments, or other structures, matching how your organization actually runs.
Because the cards are issued through the EKOS WEX program rather than integrated after the fact, transaction data arrives natively — posted to the right vehicle, with cost and odometer attached, in the same system that schedules the maintenance that mileage triggers. Reporting lives in fuel card analytics.
Frequently asked questions
Why manage fuel cards inside a fleet platform?
Because every question that spans cards and vehicles otherwise requires manual reconciliation. Consolidating means drivers are provisioned once, transactions post to the vehicle automatically, pump odometer readings update maintenance schedules, and cost per mile is continuous rather than assembled.
Should fuel cards be assigned to drivers or vehicles?
It depends what you need to answer. Driver assignment attributes spend to people and suits operations where drivers change vehicles. Vehicle assignment is what cost per mile and total cost of ownership require. Department assignment suits cost allocation. Holding cards, drivers, and vehicles in one system lets you have more than one view.
Do I still deal with the card issuer if cards are managed in a platform?
Yes. Account terms, credit, billing, network acceptance, and dispute resolution stay with the issuer. What moves into the platform is the operational layer — issuing, controlling, assigning, and what happens to transaction data after it clears.
What is the risk of managing cards in a separate portal?
The most common one is a departing employee deprovisioned in the fleet system but not the card portal, leaving a live credential. The delay between noticing a problem and locking a card is also longer when the person who noticed does not have a portal login.
THE BOTTOM LINE
EKOS manages the entire fuel card lifecycle — issue, assign, lock, replace, cancel.
In the same platform that runs your vehicles and private fuel sites.
FUEL CARD MANAGEMENT IN EKOS
The whole card lifecycle, next to your vehicles.
EKOS manages the entire fuel card lifecycle — issue, assign, lock, replace, cancel — in the same platform that runs your vehicles and private fuel sites.
