Home/All Products/EV Fleet Charging Cards

01 / 04

EV charging credential

Made to specification

EV Fleet Charging Cards

Branded RFID fleet charging credentials with unique token data, driver or vehicle numbering, bulk platform import and controlled replenishment.

Fleet OperationsBulk Token DataReplenishment

Material: Recycled PVC, standard PVC or approved alternative
Size: CR80 / ISO ID-1 nominal format (85.60 × 53.98 mm)
MOQ: From 500 pieces, subject to material and chip
Lead Time: Confirmed after data format, artwork and sample approval

Request Samples Request a Quote

Compatibility is confirmed against your reader and token workflow. MOQ and timing depend on the approved material, chip, personalization and finish.

01Reader and chip match

02Identifier format

03Finished-sample approval

04Batch data handoff

Product overview / 01

Physical credentials for managed EV fleets

An EV fleet charging card is a physical token issued to a driver, vehicle, depot or cost centre so charging sessions can be assigned and controlled by a fleet or e-mobility platform. The card identifies the account; session records, prices, limits and reporting are normally handled in the backend rather than stored on the card.

A fleet card can be used on an operator's own estate or in a roaming programme. Roaming is created by commercial and technical relationships between eMSPs, CPOs and hubs—not by printing a logo or selecting a particular card body. The credential data must be registered and routed through the platform that manages those relationships.

Assignment model

Decide whether each token belongs to a driver, vehicle, pool, depot or cost centre and how transfers are recorded.

Network scope

List depot, workplace, public and roaming environments and identify the platform responsible for authorization.

Lifecycle controls

Define issue, activation, suspension, loss, replacement, expiry and return procedures before distributing cards.

Reconciliation fields

Align visible card numbers, token records and fleet-system references so exceptions can be traced quickly.

Features and options / 02

What can be specified.

The physical card can be structured to reduce support work and integrate cleanly with fleet onboarding and replenishment.

Driver or vehicle numbering

Visible references can follow the operator's assignment model without exposing the electronic UID as the support identifier.

Bulk token data

Structured delivery files support import, assignment and activation in the fleet or e-mobility platform.

Custom programme artwork

Brand, support instructions, emergency details and required legal text can be organized on the card.

Durable card materials

Recycled PVC and alternative bodies can be selected around wallet, vehicle and depot handling patterns.

Card and keyfob options

Mixed form factors can serve different driver groups while following one controlled token-data workflow.

Scheduled replenishment

Number ranges, artwork masters and packing rules can be retained for replacement and growth batches.

Technical fit / 03

The card is one layer of fleet charging control

Useful reporting and roaming depend on the systems around the credential. The card must give those systems a stable, traceable token.

Assignment lives in the platform

Per-driver, per-vehicle and per-cost-centre reporting comes from mapping the card token to the right fleet record.

Roaming requires platform registration

A manufactured card only works across networks after its token is registered and accepted through the relevant eMSP, CPO or roaming relationship.

Replacement must create a new credential

Lost cards should be blocked and replaced with a new unique token; reprinting the same visible number does not require reusing the electronic UID.

Offline authorization needs governance

Where chargers use local token lists, define synchronization timing and what should happen after a card is blocked.

Data formats should be tested at batch scale

Validate headers, delimiters, leading zeros and identifier representation before importing the production file.

Full specification / 04

Separate the physical card from its credential data.

Values below are the available product route, not a substitute for reader validation. The final quotation records the exact construction, electronic configuration and data deliverables.

Request Samples

Physical

Material: Recycled PVC, standard PVC or approved alternative
Size: CR80 / ISO ID-1 nominal format (85.60 × 53.98 mm)

Technical

Frequency: Typically 13.56 MHz / ISO 14443A; confirm with fleet reader estate
Read Range: Reader and installed antenna dependent; sample validation required
Security: UID-only or secure application according to platform and reader design

Ordering

MOQ: From 500 pieces, subject to material and chip
Lead Time: Confirmed after data format, artwork and sample approval

Production route / 05

Approve the complete workflow before volume.

The sample should prove construction, print, electronic behavior and data handling together. That approved reference then controls production and reorders.

01
Technical brief
Reader, current credential, platform, quantity and operating environment
02
Production sample
Proposed material, inlay, artwork, encoding and variable data
03
System validation
Physical read, exact token capture, data import and live authorization
04
Production and QA
Approved masters, controlled data, batch checks and packing review
05
Delivery and reorders
Final mapping file, shipment record and retained repeat-order reference

Request a Quote Learn More

Frequently asked / 06

Questions buyers ask before ordering.

Answers are based on the physical credential and production scope. Your charging platform remains responsible for account, tariff and authorization rules.

What information is stored on a fleet charging card?

Many programmes use only a chip identifier as the token. Driver details, vehicle data, tariffs and session history remain in the backend. Secure applications can store additional data when the reader and system are designed to use them.

Can one fleet card work on multiple charging networks?

Yes when the fleet's e-mobility provider or platform has the required roaming or bilateral network relationships and registers the token correctly. The physical card alone does not create network access.

Should cards be assigned to drivers or vehicles?

Use the entity your fleet needs to control and reconcile. Driver assignment suits personal responsibility; vehicle assignment can simplify shared routes; pool cards need stronger checkout and exception controls.

How are lost cards replaced?

Block the lost token in the authorization platform, issue a replacement with a new unique credential, update the driver or vehicle assignment and keep an audit trail linking the change.

Can card data be imported in bulk?

Yes. Agree the required columns and token representation first. A delivery file can map UID, visible card number, batch and other approved fields for bulk platform import.

Does the card itself track kWh and charging cost?

Usually no. The charging station and management platform create the session record and billing data. The card supplies the token used to associate that session with a fleet account.

Build the brief with evidence.

Use the technical guide, programme examples and glossary to align procurement, engineering and operations before requesting samples.

Fleet guide

Commercial EV fleet RFID card guide

Plan assignment, network scope, reporting and replacement before issuing cards.

RightCharge fleet credential programme

See a physical card programme built for a fleet-focused charging platform.

How multi-network RFID access works

Understand the roles of token, eMSP, CPO, hub and charging backend.

Included with every order

Every order ships with a data contract and acceptance pack.

Before production starts, we fix the identifier format with your backend team: byte length, representation, byte order, leading-zero policy. The order then ships with a machine-readable data contract and acceptance vectors your engineers can test against before the first card arrives.

See how the acceptance pack works

01JSON data contract agreed before production

02Acceptance vectors for backend verification

03Personalization file in your backend's exact format