Fleet charge cards are payment and authorization credentials issued to company drivers or vehicles to access EV charging under a centralized fleet account. They enable drivers to start charging at depots, workplaces, and public networks while ensuring charging costs are billed to the fleet rather than to individuals. Fleet charge cards are commonly used across roaming networks and are a core tool for scaling multi-site fleet charging operations.
What Are Fleet Charge Cards?
Fleet charge cards function as fleet-linked charging credentials.
– Typically issued as RFID cards, sometimes combined with app-based credentials
– Linked to a fleet contract with an operator or eMSP
– Used for authorization at the charger (tap to start/stop)
– Session costs are assigned to the fleet billing account for invoicing and reporting
In many setups, the card is tied to a driver; in others, it is tied to a vehicle or cost center.
Why Fleet Charge Cards Matter
– Simplify driver experience: no personal payment, faster session start
– Centralize billing and reporting for finance teams
– Support policy enforcement: where/when charging is allowed and spending limits
– Enable cross-network access through roaming agreements
– Reduce reimbursement workload and improve cost control
– Improve traceability for carbon reporting and TCO analysis
How Fleet Charge Cards Work
Authorization Flow
– Driver taps the card on the charger RFID reader
– Charger sends authorization request to CPMS or roaming provider
– System checks whether the card is valid and which fleet account it belongs to
– If approved, charging starts and session is logged under the fleet account
Billing Flow
– Session data is aggregated in CPMS or eMSP billing systems
– Tariffs are applied (kWh, time, flat fees, idle fees)
– Fleet receives consolidated invoices and session-level detail for reconciliation
Common Fleet Card Models
– Single-network fleet cards: usable only on a specific operator network
– Roaming-enabled fleet cards: usable across multiple networks through eMSP/roaming hubs
– Depot-only cards: restricted to private fleet sites for cost control
– Mixed access cards: depot + selected public networks for route coverage
Policy Controls Often Linked to Fleet Cards
– Allowed locations or networks (whitelist/blacklist)
– Time windows (shift hours, off-peak preference)
– Limits: kWh per session, daily caps, monthly spend caps
– Vehicle group rules (vans vs cars vs heavy-duty)
– Pricing model assignment (negotiated tariffs, pass-through, fixed rates)
– Exception handling (lost card, misuse, emergency charging allowance)
Operational Considerations
Card Management
– Issuance, activation, and mapping to driver/vehicle IDs
– Replacement process for lost or damaged cards
– Rapid revocation when drivers leave the company
– Inventory tracking: which cards are active and where they are assigned
Network Coverage and Roaming
– Ensure roaming coverage matches fleet routes and operational needs
– Validate real-world compatibility: not all chargers support the same authorization flows
– Manage settlement delays and data completeness in roaming environments
Data and Reporting
– Require session exports with driver/vehicle mapping and cost center fields
– Ensure charger IDs and locations are included for reconciliation
– Support carbon reporting: kWh by country/site and emissions factors linkage
Security and Misuse Prevention
– Prevent card sharing by linking to driver identity where appropriate
– Use PIN or app confirmation for higher-risk use cases (optional)
– Monitor anomalies: repeated failed attempts, unusual kWh spikes, off-hours usage
– Maintain clear policies for personal vs business charging
Common Mistakes to Avoid
– Issuing cards without clear mapping to cost centers or vehicles, creating billing ambiguity
– Allowing unrestricted public charging access without limits, causing runaway costs
– Underestimating roaming complexity (tariffs, receipts, missing session data)
– Weak offboarding processes leading to unauthorized ongoing use
– Poor driver training, causing failed starts and higher support volume
– Not validating local fiscal requirements for receipts/invoices in key markets
Limitations to Consider
– RFID cards depend on backend connectivity unless offline allowlists are supported
– Roaming sessions may appear late or with incomplete data depending on partners
– Tariff transparency can be harder across multiple networks and currencies
– Some markets require specific receipt formats (fiscal receipts) for expense claims
– Fleet cards do not solve depot capacity constraints; load management is still needed
Related Glossary Terms
Fleet Account Authorization
Fleet Billing
Roaming Authorization
Charging Access Subscriptions
Driver Authentication
Driver ID Billing
Fiscal Receipts
EV Fleet Management