Fleet RFID Charging Cards: A Guide for Commercial EV Operations

Running a commercial fleet on electric vehicles changes the economics of charging. Instead of one driver swiping a personal credit card at a forecourt, you have 50, 500, or 5,000 drivers charging across depots, public stations, and home chargers — each session generating cost, kWh, and tax-relevant data that has to land cleanly in fleet management software. Fleet RFID charging cards are how that data gets captured at the source.

This guide covers what makes a fleet RFID charging card different from a consumer card, how the authentication and reporting chain works, and what to specify when issuing cards across a commercial EV program.

What Makes a Fleet RFID Charging Card Different

A consumer EV charging card identifies the driver. A fleet card identifies the vehicle, the driver, the depot, and the contracted CPO relationship — and feeds all of that downstream into the fleet's accounting and tax workflows.

The card itself is usually MIFARE DESFire EV3, the same chip technology used in modern consumer cards. The difference is in how the card's data is structured, how it's encoded, and how it integrates with the back-end:

•

Per-vehicle kWh tracking: — the card's UID is mapped to a specific vehicle in the fleet management system, so every charging session can be allocated to a vehicle.

•

Driver attribution: — paired with vehicle telematics, the card lets the fleet attribute energy spend to the driver assigned to that vehicle on that day.

•

Diversified keys per depot: — each depot's cards can carry a different cryptographic key, so a stolen depot batch can be revoked without invalidating the whole program.

•

HMRC-compliant cost allocation: — UK fleets need clean per-mile and per-vehicle energy reporting for benefit-in-kind and corporate tax. The card's audit trail underpins this.

How Fleet RFID Authentication Works on OCPP Stations

The OCPP flow is the same as for any other RFID charging card, but the data hooks are richer.

When a driver taps a fleet card at a depot or public station:

1.The station extracts the UID and sends `Authorize.req` to the Central System.

2.The Central System checks the UID against the fleet's allow list (often filtered by depot, driver group, or vehicle group).

3.On approval, the station starts the transaction with `StartTransaction` containing the UID, station ID, timestamp, and meter start value.

4.At session end, `StopTransaction` records the meter stop value, total energy, duration, and CDR (Charge Detail Record).

5.The CDR flows from the Central System to the fleet's reporting backend — Webfleet, Geotab, Mix Telematics, or a custom data warehouse.

For fleets running mixed depot + public charging, OCPI roaming feeds CDRs from external CPOs back through the fleet's MSP into the same reporting pipeline.

Per-Vehicle vs Per-Driver Card Models

Most fleets choose between two architectures:

**Per-vehicle cards** sit with the vehicle (in the glovebox or attached to a key fob). Pros: simple driver experience, easy reassignment when drivers swap. Cons: stolen with the vehicle, can't isolate driver behavior.

**Per-driver cards** travel with the driver across whatever vehicle they're using that day. Pros: clean driver-level reporting, supports HMRC personal-use allocation. Cons: requires reliable telematics to know which vehicle the driver is in for accurate kWh attribution.

Many large fleets issue both — a per-driver card for cost allocation, a per-vehicle key fob for redundancy and ease of access.

Multi-Depot Key Management

For fleets running multiple depots — utility companies, last-mile logistics, regional bus operators — the cards need to enforce who can charge where. DESFire EV3 supports diversified keys per application, meaning each depot's cards can carry a unique cryptographic key derived from a master.

The practical effect: if a depot's cards are compromised, the fleet revokes that depot's key without affecting the rest of the program. New cards for the affected depot are encoded with a fresh diversified key. Total program downtime is hours, not weeks.

This matters because the alternative — one shared key across all 5,000 fleet cards — means a single compromise forces a full reissue.

Reporting: From OCPP CDR to HMRC-Ready Output

The card is just the entry point. The reporting chain is what makes a fleet program work financially.

A typical UK fleet workflow:

1.Driver taps card → station authorizes → session runs → CDR recorded.

2.CDR is enriched with driver, vehicle, and depot metadata from the fleet management system.

3.Energy cost is calculated using the contracted tariff (often time-of-use or pass-through).

4.Per-mile and per-vehicle kWh figures are computed for HMRC benefit-in-kind reporting.

5.Output flows to payroll (for personal-use allocation) and to corporate tax filings.

The card-to-report chain has to be auditable end to end. That's why DESFire EV3 with cryptographic transaction logging is the standard — anyone questioning a charge entry can trace it back to a specific card UID, station, and timestamp.

Roaming for Mixed Depot + Public Charging

Most commercial fleets can't operate on depot-only charging. Long-haul drivers, last-mile operators with route variance, and any fleet with home-charging policies all need public network access via the same card.

This is where the card's roaming registration matters. Through Hubject, GIREVE, or direct OCPI agreements, a fleet card issued by an MSP can charge across:

•Octopus Electroverse (1.3M+ chargers across 40 countries)

•Shell Recharge

•Ionity (high-power along TEN-T corridors)

•Allego, Vattenfall, EnBW, Ionity, FastNed

•Local CPOs with OCPI agreements

The CDRs come back to the fleet's MSP, get re-priced if the contract uses a markup model, and flow into the same reporting pipeline as depot sessions.

What to Specify When Issuing Fleet RFID Charging Cards

For a 1,000-vehicle fleet starting an EV program in 2026, a typical card spec looks like:

•

Chip: MIFARE DESFire EV3, AES-128, with diversified keys per depot

•

Material: recycled PVC (most common) or FSC wooden for ESG-led programs

•

Form factor: ISO 7810 ID-1 cards plus key fobs for vehicle attachment

•

Print: full-color with vehicle/driver ID, fleet logo, anti-tamper laser engraving

•

Encoding: pre-encoded UID, idTag aligned with MSP format, depot-specific diversified key

•

Roaming: registered with Hubject + at least one OCPI MSP for cross-network access

•

Reissue policy: 5–8% annual reissue rate; budget accordingly

•

MOQ: 500 PVC / 250 wooden; volume discounts kick in at 5,000+

Common Mistakes in Fleet Card Programs

•

Issuing cards before the MSP integration is live: — drivers tap and get rejected because the idTag isn't registered yet.

•

One depot, one shared key: — sounds simple, becomes a liability the first time a card is lost.

•

No reissue budget: — fleet operators consistently underestimate replacement volume by half.

•

Public-charging blind spots: — assuming "we'll just install more depot chargers" instead of designing roaming in from day one.

•

Mismatched UID format: — different MSPs expect different idTag formats (4-byte, 7-byte, hex vs decimal); get this aligned before encoding 5,000 cards.

Where to Go From Here

A fleet RFID charging card program is a four-axis spec: chip security, encoding format, roaming reach, and reporting integration. Get those right and the cards become invisible infrastructure — drivers tap, energy flows, data lands cleanly in the fleet's books.

Browse our recycled PVC and FSC wooden EV charging cards or read how we built fleet card programs with LetzCharge and RightCharge. Talk to us about your fleet's charging program — we'll help you spec the right card and align it with your MSP.