RFID Cards for EV Charging: How They Work and How to Choose One

An RFID card for EV charging is a contactless smart card that identifies a driver to a charging station and authorizes a charging session. Hold the card to the reader, the station verifies the card with its backend, and energy starts flowing. Despite the rise of app-based payments and ISO 15118 Plug and Charge, RFID cards remain the most reliable, universal, and operator-controlled way to start a charge across Europe, the UK, North America, and beyond.

This guide explains how RFID cards for EV charging work end to end, what chip technologies sit inside them, how they connect to roaming networks, how to compare cards, and what to expect when ordering them in volume.

What Is an RFID Card for EV Charging?

An RFID card for EV charging is a plastic, wood, or bio-based card embedded with an RFID chip and antenna. The chip stores a unique identifier (the idTag) and, on more secure cards, encrypted application data. When a driver presents the card to a charging station's reader, the station extracts that identifier, sends it to a Central System over OCPP, and waits for an authorization response.

Most cards used for EV charging operate at 13.56 MHz (High Frequency, ISO 14443A) — the same frequency used by contactless payment cards, transit cards, and modern access control. A few legacy systems still use 125 kHz Low Frequency cards (EM4100, HID Prox), but these have largely been retired for new charging deployments because they cannot be encrypted.

How an RFID Charging Session Authenticates

The authentication flow has been the same since the first OCPP-based networks went live:

1.The driver taps the card on the station reader.

2.The reader extracts the card's UID or the relevant application data.

3.The station sends an OCPP `Authorize.req` message to the Central System with the idTag.

4.The Central System checks the idTag against its authorization list and contracts.

5.If the card is valid, the Central System returns `Authorize.conf: Accepted`.

6.The driver plugs in (or has already plugged in) and the station starts the transaction.

For fleet and roaming use cases, that authorization check often hops out to a roaming platform — Hubject, GIREVE, or e-clearing.net — which routes the request to the home Charge Point Operator that issued the card. The driver charges at a station owned by Operator B but pays through Operator A's contract.

Chip Technologies Inside an EV Charging Card

Not every RFID card for EV charging is built the same. Three families dominate:

MIFARE Classic 1K / 4K

The cheapest option. Stores an idTag in 1 KB or 4 KB sectors. Adequate for low-risk fleet deployments where the worst case of cloning is a small, traceable energy theft. Avoid for any program processing payment data or roaming across CPOs — Crypto-1 has been broken for over a decade.

MIFARE DESFire EV2 / EV3

The de facto standard for serious EV charging deployments in 2026. AES-128 encryption, mutual authentication, diversified keys, and transaction MAC verification. Anti-cloning is strong enough that even a determined attacker can't copy a card without physical destruction. This is what major roaming networks expect when issuing branded cards.

NTAG 424 DNA

Asymmetric cryptography with per-tap unique signatures. Useful for premium consumer cards where each tap should be cryptographically auditable. Less common in fleet but growing for branded operator cards that want unforgeable receipts.

For most charging operators today, **DESFire EV3 is the right answer** unless you have a specific reason to choose otherwise.

OCPP, OCPI, and How a Single Card Roams

The reason one RFID card can charge across hundreds of networks is protocol standardization. Three matter:

•

OCPP (Open Charge Point Protocol): — between the station and the Central System. Versions 1.6 and 2.0.1 are dominant; both handle RFID authorization the same way.

•

OCPI (Open Charge Point Interface): — between Charge Point Operators (CPOs) and Mobility Service Providers (MSPs). The card's idTag is exchanged here.

•

OICP (Open InterCharge Protocol): — Hubject's roaming protocol. Functionally similar to OCPI; widely used in DACH and Northern Europe.

When you issue an RFID card for EV charging, the card's idTag must be registered with at least one MSP, and the MSP must have roaming agreements with the CPOs you want to support. Octopus Electroverse, Shell Recharge, Ionity Passport, and Allego cards all work this way under the hood.

How to Choose the Right RFID Card for EV Charging

Five questions decide the card spec:

1.Who is the user?: Fleet driver, public consumer, or both? Fleet typically wants tighter access control and per-vehicle reporting; public cards prioritize roaming breadth.

2.Which networks must it work on?: This determines the MSP / roaming hub registration, not the card itself — but the card must support DESFire if any modern operator is in the list.

3.What's the brand requirement?: Custom artwork, embossed serial numbers, QR codes for self-service, NFC tap-to-portal? Card material (recycled PVC, FSC wood, bio-based) is often dictated by brand sustainability commitments.

4.What's the volume?: MOQs typically start at 250 wooden / 500 PVC. Above 10,000 cards a year, expect tiered pricing and dedicated production slots.

5.What's the lifecycle?: EV charging cards typically last 3–5 years in daily-use conditions. Plan reissuance into the program from day one.

Sustainability: Why the Card Material Matters

A typical roaming network issues 50,000 to 500,000 RFID cards per year. At that volume, the carbon difference between virgin PVC and recycled PVC, FSC-certified wood, or bio-based PPH is not trivial. Recycled PVC reduces emissions by up to 75% versus virgin PVC; wooden cards are functionally carbon-negative because the wood stores carbon for the card's lifetime.

For operators with public ESG commitments — most of the large European MSPs by now — material choice is no longer cosmetic. It's a procurement decision with reportable carbon impact.

Pricing and Lead Times

For DESFire EV3 cards in custom-printed batches, expect:

•

Recycled PVC: typical MOQ 500, lead time 2–3 weeks

•

FSC wooden: MOQ 250, lead time 3–4 weeks

•

PPH Bio: MOQ 500, lead time 2–3 weeks

•

Pre-encoded with idTag: add 0.5–1 week for encoding setup

•

Express production: available at premium for urgent rollouts

Common Mistakes When Specifying an RFID Card for EV Charging

•

Picking MIFARE Classic to save €0.10 per card: — then realizing it can't roam to networks that require DESFire.

•

Skipping pre-encoding: — having a 50,000-card box arrive blank and discovering encoding in-house takes three months.

•

Not aligning with your MSP early: — the card must be registered in the right format, with the right idTag length, before it ever ships.

•

Forgetting reissue logistics: — issuing 50,000 cards is easy; replacing 500 lost cards a month is the real operational cost.

Where to Go From Here

If you're spec'ing an RFID card for EV charging, start with the chip (DESFire EV3 unless there's a strong reason to deviate), then the material (sustainability choice), then the encoding (idTag format aligned with your MSP), and only finally the artwork.

Browse our EV charging cards — recycled PVC, FSC wooden, PPH Bio, and key fobs — or read how we built fleet authentication and roaming solutions for Octopus Electroverse, LetzCharge, and EEZY Charge. Contact us for a sample kit and quote.