Fleet and mobility companies migrate from RFID-based charging access to open-loop card payments by introducing issuing and processing infrastructure capable of routing transactions through global card schemes like Visa and Mastercard.
The transition is driven mainly by the AFIR mandating card payment terminals be installed at the charging stations, and by the need for greater interoperability, scalability and control as fleets expand beyond EV charging into fuel, tolls, parking and wider mobility spend.
Open-loop infrastructure allows fleets to operate across charging networks, support physical and virtual cards, and apply real-time spend controls without relying only on proprietary charging identifiers or complex roaming arrangements.
What changes in the payment architecture?
The move towards EMV card payments reshapes the payment stack.
In a traditional RFID or mobile app model:
- The RFID tag or a mobile app user account acts as an access credential and account identifier
- Charging sessions are linked to backend fleet contracts
- Settlement typically happens later through invoicing
In an EMV card present model:
- The driver or vehicle identity is separated from the payment method
- Physical, virtual or tokenised cards authorise transactions in real time
- Settlement happens through card scheme rails
This isn’t a requirement for card acceptance itself. A CPO or eMSP can simply accept cards like any other merchant. It becomes relevant when a fleet, mobility provider, CPO or eMSP wants to keep issuing its own payment card (for example to retain the customer relationship), build loyalty, or bundle EV charging with fuel, parking and car washing into one consolidated, controlled account with expense management.
In that case, it requires an issuing processing platform capable of tokenisation, authorisation decisioning, scheme connectivity and transaction reconciliation.
For example, a fleet driver may start a charging session using a token linked to a vehicle card, while the backend maps the session to a fleet account and applies policy rules instantly.
The result is a more scalable and programmable payment infrastructure that supports broader mobility use cases beyond EV charging alone.
How to migrate to open-loop card payments
For most operators, this is simpler than a card-to-card migration. It looks like standing up a new card programme from scratch, with drivers and vehicles onboarded at whatever pace suits the business. Many still run a hybrid approach alongside RFID during the build-out, to reduce operational risk and maintain continuity for drivers.
Key design and implementation considerations include:
- Align internal teams: Operations, finance, risk, customer support and legal teams need a shared understanding of how payment flows, reporting and customer journeys will change.
- Define the target customer profile and value proposition: Operators need clarity on who the card programme is for, whether that’s fleet drivers, private EV drivers or wider mobility customers, and what value it delivers to them, before designing the product around them.
- Map and validate business and functional requirements: This covers pricing models, invoicing models, data needs, VAT receipt requirements, acceptance network coverage, and the restrictions and controls the programme needs to support. One of the harder parts here is linking charging session data (Charge Detail Records) with the payment transaction, so operators can issue accurate VAT invoices and full session details to customers. Mature, ready-made solutions for this are still emerging across the industry, so it’s worth planning for it early in the process.
- Integrate charging and payment systems: Operators connect EV charging infrastructure, mobile apps, fleet platforms and external partners to card-processing infrastructure.
- Test edge cases thoroughly: This includes roaming scenarios, failed charging sessions, offline terminals, token provisioning and settlement adjustments.
- Run a controlled pilot: Operators typically launch with a limited group of vehicles or drivers before scaling in phases.
- Monitor through hypercare: Early live monitoring helps identify transaction issues, customer support gaps and reconciliation problems quickly.
EV charging considerations for open-loop payments
EV charging introduces operational and payment complexities that fleets and mobility providers must account for when moving to open-loop infrastructure.
EV charging sessions are dynamic and consumption-based, which creates different payment and settlement requirements from traditional fixed-value transactions. Operators often need to pre-authorise a payment before charging begins, adjust the final amount when charging ends, and handle partial or interrupted charging sessions.
Connectivity also matters. Charging stations may operate in areas with unstable network coverage, making fallback mechanisms such as deferred authorisation or stand-in processing important operational safeguards.
Interoperability is another key consideration. Charge Detail Records (CDRs) must reconcile accurately with payment transaction data so fleets can match charging activity, billing, driver permissions and expense reporting across multiple charging networks and payment providers.
Fleet operators also need to rebuild policy control at the authorisation layer. Open-loop payments alone behave like standard card payments unless fleet-specific controls are added.
Common controls include:
- MCC filtering for EV charging transactions
- Charger or merchant whitelists and blacklists
- Cross-border spend rules
- Vehicle-level or driver-level permissions
- Spend, time and transaction limits
These controls are what make open-loop payments fleet-ready rather than simply card-enabled.
Common challenges
Many problems are operational rather than purely technical.
Common issues include:
- Mismatched charging and payment data
- Incorrect merchant category coding
- Failed token provisioning to mobile wallets
- Poorly configured pre-authorisation amounts
- Driver confusion during hybrid RFID and card phases
- Heterogenous charging point and payment terminal configurations
Legacy charging hardware can also increase costs if terminal upgrades are required. Connected payment terminals introduce additional cybersecurity exposure, requiring stronger fraud prevention, monitoring and compliance controls.
Finally, energy systems and financial systems operate using different underlying logic. Aligning charging session data with payment transaction standards can require careful backend redesign.
How Enfuce supports the transition to open-loop card payments
Enfuce provides the issuing and processing infrastructure that enables fleet and mobility companies to switch from closed-loop or RFID-based models towards open-loop, multi-mobility payment infrastructure.
Our platform supports one card for fuel, EV charging and wider mobility spend, combining open-loop acceptance with real-time controls, detailed transaction visibility and reconciliation across charging and payment data. This includes support for different types of hybrid products, such as EMV + RFID on one card, and open + closed loop applications on one card.
Enfuce helps fleet and mobility providers manage cross-network payments, enforce spend policies, support multimodal mobility use cases and migrate from closed-loop infrastructure without operational disruption.
Our cloud-native infrastructure also supports operational resilience through capabilities such as stand-in processing, helping maintain transaction continuity during connectivity or system disruptions.
Key capabilities for fleet and mobility companies include:
- Real-time advanced spend controls
- Vehicle and driver-level permissions
- Merchant and region-based rules
- Network-agnostic payment acceptance
- Integration with fleet, charging and mobility platforms
- Fraud monitoring and dispute support
- Physical, virtual and tokenised cards
Our migration support includes a dedicated transition team and a proven seven-step framework covering internal alignment, project setup, data mapping, testing, pilot validation, migration execution and hypercare.
Key takeaway
The transition from RFID to open-loop payments is not simply a charging upgrade. It is a shift from closed access systems to programmable mobility payment infrastructure.
Operators that treat the transition as a strategic infrastructure project, rather than a standalone payment change, are better positioned to improve interoperability, expand into wider mobility spend and build long-term operational scalability.
FAQs
What is the difference between RFID and mobile apps and open-loop EV charging payments?
RFID charging relies on proprietary identifiers linked to closed billing systems. Open-loop payments use physical, virtual or tokenised cards that authorise transactions through card scheme rails, enabling broader acceptance, real-time payment controls, and higher security standards, resulting in reduced fraud.
Why are fleet operators moving away from RFID and mobile apps?
Fleet operators are moving away from RFID because it is mainly designed for charging access, while modern fleets increasingly need one controlled payment method for EV charging, fuel, tolls, parking and wider mobility spend. At the same time, growing interoperability expectations and regulations supporting easier payment access at public charging infrastructure are accelerating the shift towards open-loop payments.
Do fleets replace RFID and mobile apps immediately?
Usually not. Most operators use a phased or hybrid migration strategy, keeping RFID active during the transition while open-loop payment infrastructure is introduced gradually.
Enfuce is a global card issuing payment processor built for banks and mid-to-enterprise-level fintechs, lenders, and fleet and mobility providers looking to scale existing card programmes or launch new ones.
