Do not activate too early
Separate manufacturing, fulfilment and activation states so inventory loss does not create live credentials.
CPO and eMSP issuance programme
CPO & eMSP Credential Programmes
White-label cards and keyfobs prepared around your brand, identifier format, platform import, launch volume and repeat-order workflow.
Programme outcome
A repeatable issuance programme connecting physical stock, token records, brand assets and replenishment.
Review recommended productDesigned for
Charge point operators, eMobility service providers and white-label mobility brands
01
Programme role
CPO, eMSP or combined operation
02
Token handoff
Issuer record, identifier and status
03
Platform layer
CSMS, customer platform and roaming links
04
Supply model
Launch stock, fulfilment and repeat batches
Operating model / 01
Follow the credential across the complete authorization chain.
The physical card is one controlled input. Reader behaviour, platform records and operating rules determine whether the correct account is authorized and traced.
A repeatable issuance programme connecting physical stock, token records, brand assets and replenishment.
- 01
Subscriber or account
The service provider owns the commercial relationship, entitlement and activation status for the driver or organisation.
- 02
Issued card or keyfob
The physical credential carries the approved brand, visible serial and reader-compatible identifier.
- 03
Station and CSMS
The station reads the credential; the CSMS applies local, cached or central authorization behaviour according to its implementation.
- 04
eMSP customer platform
The credential record is created, assigned, activated and exposed to customer-service and replacement workflows.
- 05
Roaming connection
Where contracted, token data and status are shared with CPO partners bilaterally or through a roaming hub.
Specification matrix / 02
Decisions to close before production.
A production-ready brief states what must be decided, how it will be implemented and what evidence will count as acceptance.
DecisionWhat to defineAcceptance evidence
01
Operator role
What to define
State whether the programme acts as CPO, eMSP, fleet service, white-label issuer or a combination.
Acceptance evidence
Ownership of token, customer, station and support records is unambiguous.
02
Token namespace
What to define
Define issuer, country/party references, token type and uniqueness rules used by the target platform.
Acceptance evidence
A sample record is accepted without collision or silent reformatting.
03
Station compatibility
What to define
Document reader technology and the OCPP versions and authorization features used by the CSMS.
Acceptance evidence
Sample credentials complete the intended online and offline station tests.
04
Data exchange
What to define
Approve UID representation, customer reference, visible serial, status and import-file schema.
Acceptance evidence
Production export passes platform validation and row-count reconciliation.
05
Issuance state
What to define
Choose whether stock is delivered inactive, pre-assigned, packaged per customer or supplied in bulk.
Acceptance evidence
Activation responsibility and custody are recorded at every handoff.
06
Brand system
What to define
Control artwork versions, language variants, support details, legal marks and variable-data zones.
Acceptance evidence
A signed artwork proof and physical colour/sample approval are retained.
07
Replenishment
What to define
Reserve identifier ranges and define minimum stock, lead-time and repeat-order controls.
Acceptance evidence
A repeat batch can be produced without recreating the specification or duplicating records.
Failure controls / 03
Design out the common failure points.
Most failed launches are not caused by print quality. They come from unclear identifiers, untested readers, incomplete data ownership or weak lifecycle control.
Reconcile every data file
Quantity, UID, visible serial, package assignment and import result should balance before customer issue.
Version the brand and data brief
Treat artwork, token rules and packaging as one controlled release; a partial change can invalidate the programme record.
Retain the golden sample
Keep an approved credential and encoded record as the comparison point for production and future replenishment.
Delivery path / 04
Move from brief to controlled operation.
Each phase should close with evidence that can be reviewed by operations, platform and procurement teams.
- 01
Programme definition
Confirm roles, markets, user groups, token ownership and support workflows.
EvidenceSigned operating and data brief
- 02
Credential engineering
Select form, chip, identifier handling, visual serial and packaging route.
EvidenceReader-tested credential samples
- 03
Platform pilot
Import sample token records and test activation, authorization, blocking and replacement.
EvidenceAccepted import and test log
- 04
Launch fulfilment
Produce, reconcile and package the first controlled issue batch.
EvidenceBatch QC, data manifest and dispatch record
- 05
Replenishment
Monitor stock, reserve ranges and repeat the approved build under change control.
EvidenceVersioned repeat-order pack
Responsibility boundary / 05
Separate manufacturing from platform operation.
A precise boundary prevents the card from being blamed for configuration, entitlement or settlement decisions that live elsewhere.
ChargeRFID / manufacturer
Controls the approved material, chip, antenna, artwork, encoding, variable data, batch QC and production record.
CPO, eMSP or CSMS team
Defines accepted identifier format, reader behaviour, token import, authorization states, security application and technical acceptance.
Programme owner
Owns assignment, activation, contracts, access policy, tariffs, customer support, replacement approval and end-of-life decisions.
Credential options / 06
Physical formats to evaluate after the system brief is clear.
OCPP Workflows / idTag / idToken / UID Formatting
RFID Cards for OCPP Charging Networks
RFID credentials prepared for the identifier and authorization workflow used between EV charger readers and OCPP charging-management systems.
Review recommended product
Recycled PVC / Custom RFID / UID Mapping
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.
Review recommended product
Custom Engineering / OEM/ODM / Prototype Validation
Custom EV Charging Solutions
Custom RFID credentials engineered around your charging readers, token data, security model, form factor, artwork and fulfilment workflow.
Review recommended productTechnical library / 07
Continue the implementation research.
These sources define the surrounding technology and operating interfaces. ChargeRFID manufactures physical credentials; platform configuration, roaming contracts and charging-station certification remain with the relevant operators and vendors.
EV Infrastructure / 6 min read
White-Label RFID Cards for E-Mobility Service Providers: The eMSP Playbook
An e-mobility service provider lives or dies by the moment a driver taps a card at a stranger's charger and it just works. Here is how white-label RFID cards, OCPI tokens, and clean UID provisioning let an eMSP put its brand on a credential that roams across hundreds of thousands of charge points.
Read More
Technology / 9 min read
RFID Cards for EV Charging: How They Work and How to Choose One
What an RFID card for EV charging actually does, how it authenticates against OCPP stations and roaming hubs, the chip technologies used, and how to choose the right card for fleets, networks, or personal use.
Read More
Technology / 7 min read
Choosing an RFID Credential for EV Charging
A vendor-neutral method for choosing a 13.56 MHz EV charging credential by reader behavior, identifier format, authentication, backend controls and roaming requirements
Read MorePrimary implementation references
Programme questions / 08
Questions procurement and technical teams usually resolve.
01Who creates the customer and token record?
The CPO, eMSP or its platform creates and controls the commercial token record. ChargeRFID can encode the agreed credential data and provide a reconciled import file, but it does not activate subscriptions or grant network entitlement.
02Can cards be delivered inactive?
Yes. Bulk inactive stock, pre-assigned packs and customer-level fulfilment are different operating models. The activation state and custody handoff should be specified before production.
03Is an RFID card itself OCPP compliant?
No. OCPP connects the charging station and management system. The card must be compatible with the station reader and its identifier must fit the authorization rules implemented through OCPP.
04What should be retained for repeat orders?
Retain the approved material, chip, antenna, artwork, colour target, identifier rules, data schema, packaging, QC criteria and a golden sample under one programme version.
Other operating programmes
Fleet Authentication
RFID credentials for depot, workplace and public charging, with controlled driver or vehicle assignment, platform-ready identifiers and replacement records.
Network Roaming
Physical RFID credentials for roaming programmes where token records, identifier formats and lifecycle status stay consistent across eMSP, CPO and hub systems.
Site & Member Access
Credential programmes for workplaces, depots, residential sites and destinations that need controlled access by employee, resident, visitor or account.
Secure RFID Migration
A controlled route from legacy or UID-only credentials to reader-matched card technology with a practical pilot, data plan and phased reissue.
Automotive & Premium Membership
Branded credentials for vehicle delivery, dealership charging, loyalty and premium member programmes—with controlled serialization and presentation.
Turn rfid cards for ocpp charging networks into a controlled programme specification.
Share the reader estate, identifier rules, security requirement, platform handoff, volume and rollout markets. We will return the questions needed for samples and production approval.