Reader-matched RFID inlay
Chip and antenna combinations are selected against the target charger reader protocol and physical presentation.
01 / 04
EV charging credential
Made to specificationRFID Cards for OCPP Charging Networks
RFID credentials prepared for the identifier and authorization workflow used between EV charger readers and OCPP charging-management systems.
OCPP WorkflowsidTag / idTokenUID Formatting
- Material
- Recycled PVC, wood-based or approved alternative body
- 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 token format, artwork and sample approval
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
What an ‘OCPP RFID card’ actually does
An RFID card does not run OCPP. It presents an identifier to the charging station's contactless reader. The charging station software then uses OCPP to send that identifier to the charging station management system (CSMS), which accepts, blocks or otherwise evaluates the charging token.
In OCPP 1.6 this identifier is commonly handled as an idTag; OCPP 2.0.1 uses the broader idToken model. A successful card programme therefore has two compatibility layers: the physical reader must recognize the chip, and the identifier representation must match what the charger and CSMS expect.
01
OCPP is a system protocol
Confirm the charging station and CSMS implementation separately; the physical card itself is not OCPP-certified.
02
Reader technology
Identify frequency, ISO protocol, supported chips and any limitations in the charger reader firmware.
03
Token representation
Document UID length, byte order, hexadecimal or decimal format, casing, padding and any prefix rules.
04
Online and offline behavior
Define how new, blocked and replacement tokens reach local authorization lists or cached station data.
Features and options / 02
What can be specified.
We manufacture the physical RFID credential and prepare its identifier data for the operator's charging-platform workflow.
4-byte or 7-byte UID workflows
Identifier length can be planned around the chosen chip family and the limits of the installed system.
Hexadecimal or decimal export
Delivery data can use the exact representation agreed for CSMS import, including byte order and formatting rules.
Visible token reference
A printed card number can be kept distinct from the electronic identifier while remaining linked in the mapping file.
Programme artwork and materials
Recycled PVC, wood-based and other card bodies can use the same approved electronic specification.
Replacement and reorder data
Controlled number ranges and batch files support new issues without duplicating active credentials.
Technical fit / 03
Four layers must agree before rollout
Most field failures come from an assumption at the boundary between the chip, reader, charger software and management system.
01
Card to reader
The reader must support the card frequency and protocol and provide adequate RF performance at the installed position.
02
Reader to charger software
The firmware decides which bytes are captured and how the credential is normalized before an authorization request.
03
Charger to CSMS
The OCPP implementation carries the token within the supported authorization and transaction flow.
04
CSMS to account
The imported token must map to the right contract, driver, vehicle or tariff and follow activation and blocking rules.
05
Security model
If authorization uses only a public UID, adding an AES-capable chip does not by itself create mutual authentication; the reader and backend design must use it.
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 SamplesPhysical
- Material
- Recycled PVC, wood-based or approved alternative body
- Size
- CR80 / ISO ID-1 nominal format (85.60 × 53.98 mm)
Technical
- Frequency
- Typically 13.56 MHz / ISO 14443A; confirm with charger reader
- Read Range
- Reader and installed antenna dependent; verify on finished samples
- Security
- UID-only or secure application according to charger reader capability
Ordering
- MOQ
- From 500 pieces, subject to material and chip
- Lead Time
- Confirmed after token format, artwork and sample approval
- Support
- Identifier-format review, mapping file and test-batch planning
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
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.
01Are RFID cards themselves OCPP compliant?
No. OCPP applies to communication between charging stations and management systems. The RFID card presents a credential to the station reader; the station then carries the resulting token through its OCPP authorization flow.
02What is the difference between idTag and idToken?
idTag is the identifier term used in OCPP 1.6 authorization and transaction messages. OCPP 2.0.1 uses idToken as a broader token object that can represent RFID and other authorization methods.
03Why do UID format and byte order matter?
The same physical UID can be represented in different byte orders and as hexadecimal or decimal text. If the charger exports one representation while the CSMS database stores another, a valid card will be rejected.
04Can one RFID card work across every OCPP charger?
Not automatically. OCPP support does not guarantee that every charger has the same RFID reader, chip support or identifier handling. Define the target estate and validate samples on representative hardware.
05Does AES-authenticated 13.56 MHz credential make OCPP authorization secure?
AES-authenticated 13.56 MHz credential supports cryptographic applications, but the security benefit exists only if the charger reader and programme are configured to authenticate that application. Many charging systems read a public UID even from a secure-capable chip.
06What should be included in an OCPP card test?
Test physical reading, exact token value at the charger, OCPP authorization through the CSMS, local or offline behavior where used, account mapping, blocking and replacement.
Further reading / 07
Build the brief with evidence.
Use the technical guide, programme examples and glossary to align procurement, engineering and operations before requesting samples.
Chip guide
Choose the RFID chip from the reader and authorization model
A practical comparison of UID-only and secure-application requirements.
Read more Technical guideRFID cards for EV charging: complete guide
Understand the end-to-end relationship between credential, charger and backend.
Read more Technical glossaryOCPP, idTag, idToken, UID and CSMS terms
Use consistent terminology in your procurement and integration brief.
Read moreIncluded 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 works01JSON data contract agreed before production
02Acceptance vectors for backend verification
03Personalization file in your backend's exact format
Related Products
Related Products
Recycled PVC EV Charging Cards
Custom RFID charging cards with a recycled-PVC card body, reader-matched chip options, programme artwork and UID-to-account data handoff.
Wooden EV Charging Cards
Wood-based RFID charging cards with laser engraving or print, reader-matched chip options and programme-specific variable data.
Biodegradable EV Charging Cards
Bio-fibre and non-PVC RFID charging-card constructions with documented material claims, custom artwork and reader-matched electronics.
Ready to test this credential?
Send the current card, reader model or programme brief and required quantity.