Remove orphan access
Leavers, former residents and expired visitors need a defined block process; possession of the physical item is not the entitlement record.
Site access programme
Site & Member Access
Credential programmes for workplaces, depots, residential sites and destinations that need controlled access by employee, resident, visitor or account.
Programme outcome
Controlled charging access by employee, resident, visitor, vehicle or account, with a practical offline and replacement policy.
Review recommended productDesigned for
Workplaces, depots, residential operators, hospitality groups and private charging sites
01
User groups
Employee, resident, visitor, contractor or fleet
02
Authorization
Central, cached or local-list behaviour
03
Formats
Card, keyfob or mixed issue
04
Control
Entitlement, expiry, block and replacement
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.
Controlled charging access by employee, resident, visitor, vehicle or account, with a practical offline and replacement policy.
- 01
Site user
An employee, resident, guest, contractor or fleet driver receives a credential with a defined entitlement and expiry rule.
- 02
Card or keyfob
The physical format is chosen around issue method, carrying behaviour, durability and the installed reader.
- 03
Site charging station
The station reader captures the identifier and uses central, cached or local authorization according to configuration.
- 04
Site or mobility platform
User groups, chargers, access windows, tariffs and account mappings are controlled by the operating platform.
- 05
Administration record
Issue, return, expiry, block and replacement actions are retained so physical access agrees with the live entitlement.
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
User groups
What to define
Separate employees, residents, visitors, contractors, fleets and public users where their rules differ.
Acceptance evidence
Each sample account receives only its intended charger and time entitlement.
02
Reader estate
What to define
Record charger models, reader technologies, firmware and management platforms across all sites.
Acceptance evidence
The proposed credential is recognized at representative installations.
03
Authorization path
What to define
Define central, cached, local-list and offline-unknown behaviour per charger group.
Acceptance evidence
Connected and disconnected tests match the site continuity policy.
04
Identifier mapping
What to define
Choose the platform field that connects the physical identifier to user, unit, vehicle or account.
Acceptance evidence
A tap resolves to one current entitlement and one auditable record.
05
Expiry and visitor access
What to define
Set validity windows and return/block rules for temporary credentials.
Acceptance evidence
Expired or returned credentials are rejected as designed.
06
Physical format
What to define
Use cards for visible assignment and keyfobs for compact everyday carry; validate both if mixed.
Acceptance evidence
Every format reads within the intended presentation area.
07
Cost allocation
What to define
Define whether sessions are free, billed, reimbursed or allocated to a department or property account.
Acceptance evidence
Pilot session exports contain the references required by finance or property management.
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.
Control offline lists
Local authorization can support continuity, but list age and update behaviour must be tested so revoked access does not remain indefinitely.
Avoid anonymous shared credentials
Shared site cards reduce administrative work but also weaken accountability and session attribution.
Design the return process
Replacement and return rules should cover reception desks, property handovers, lost credentials and emergency issue.
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
Policy definition
Map sites, users, chargers, entitlements, tariffs and administration owners.
EvidenceSite access policy and role matrix
- 02
Reader validation
Test proposed card and keyfob formats on representative stations and firmware versions.
EvidenceReader compatibility record
- 03
Account pilot
Create sample users for every group and test connected, offline, expiry and block behaviour.
EvidenceEntitlement acceptance matrix
- 04
Managed issue
Assign and distribute credentials with a clear activation and custody record.
EvidenceIssue register and user instructions
- 05
Ongoing control
Review leavers, resident changes, visitors, losses and reorder stock on an agreed cadence.
EvidenceLifecycle and exception log
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.
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 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
Wood · ABS · Epoxy · Crystal / Compact Credential / UID Mapping
EV Charging RFID Keyfobs
Compact RFID charging credentials in FSC wood, moulded ABS, domed epoxy and transparent crystal-acrylic constructions.
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.
Technology / 5 min read
RFID Authentication Goes Embedded: How Secure, Offline-Capable Charging Stations Are Reshaping EV Infrastructure
RFID Authentication Goes Embedded: Offline-Capable Charging Stations Reshape EV Infrastructure
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
Which RFID Chip Is Right for EV Charging? A Plain-English Guide
MIFARE Classic, Ultralight EV1, or DESFire? Neutral comparison of the three chip families EV operators actually choose from in 2026.
Read MoreProgramme questions / 08
Questions procurement and technical teams usually resolve.
01Can a site continue authorizing cards when the network is offline?
Possibly. OCPP implementations may use an authorization cache or local authorization list, but support and policy vary by station and CSMS. Test the exact disconnected behaviour before relying on it operationally.
02Should a workplace use cards or keyfobs?
Cards provide more visible space for names, numbers and instructions; keyfobs are compact and often easier for daily carry. Both can use the same identifier plan if the reader supports the selected chip and antenna format.
03Can visitor credentials expire automatically?
Expiry is normally controlled by the site or charging platform. The physical credential supplies the identifier; the platform applies the validity window and authorization state.
04Can sessions be allocated to departments or apartments?
Yes, when the platform maps each identifier to the required cost centre, unit or account and exposes that reference in its session or billing exports.
Other operating programmes
Fleet Authentication
RFID credential programmes for depot, workplace and public charging, with controlled driver or vehicle assignment, platform-ready identifier data and replacement records.
CPO & eMSP Credential Programmes
White-label cards and keyfobs prepared around your brand, identifier format, platform import, launch volume and repeat-order workflow.
Network Roaming
Physical RFID credentials prepared for roaming programmes where token records, identifier formatting and lifecycle status must remain consistent across eMSP, CPO and hub systems.
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 custom ev charging solutions 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.
