EN For most public EV charging sites in Europe, the practical answer is not to choose just one payment method. Offer an easy ad hoc option for occasional drivers, such as contactless card payment or another method permitted for the site, and add RFID or an app for regular and roaming users. Plug & Charge can make compatible vehicles even easier to use, but it does not replace every other payment route.
The difficult part is that a bank card, an RFID charging card, an app, a QR code, and Plug & Charge do not all perform the same job. Some take payment directly. Some identify the driver and send the bill to an existing account. Some do both through several connected systems.
Make ad hoc payment obvious and easy. Then offer RFID, apps, and Plug & Charge as additional choices.
RFID, apps, or automatic vehicle identification may be more useful than a retail bank-card terminal.
Specify the complete payment journey, not just a charger with a card-reader icon on its datasheet.
Which EV Charging Payment Method Is Best?
The best method depends on who uses the site. A motorway driver wants to arrive, see the price, tap a familiar card, and leave. A fleet manager wants every session assigned to the right vehicle or cost centre. A regular network customer may prefer an RFID card or app tariff. A Plug & Charge user wants the session to begin automatically after connecting the cable.
| Method | What the driver does | Best for | Main limitation |
|---|---|---|---|
| Contactless bank card | Taps a debit card, credit card, phone, or supported wallet at a payment terminal. | Visitors and ad hoc public charging. | Requires payment hardware, a payment provider, reliable integration, and clear receipt/refund handling. |
| RFID charging card | Taps a registered charging card or key fob. | Repeat users, fleets, employees, residents, subscriptions, and roaming. | The card identifies an account; it is not automatically a bank-card payment and is not universally accepted. |
| Mobile app | Selects the charger or scans a code, then starts the session in an app. | Account users who want maps, live status, tariffs, receipts, and history. | App installation, registration, phone battery, mobile coverage, and user-interface problems can create friction. |
| QR or web payment | Scans a charger-specific code and pays on a secure web page. | Occasional users and eligible lower-power public charging sites. | Depends on mobile internet and careful protection against damaged, replaced, or misleading QR labels. |
| Plug & Charge | Connects the vehicle; compatible systems authenticate it automatically. | Drivers with a supported vehicle and charging contract. | Requires compatible vehicle, charger, certificates, backend, and mobility-service arrangements. |
Payment and Authorization Are Not the Same Thing
Before comparing hardware, separate two questions:
- Who is allowed to start charging? This is authorization.
- How will the operator receive money? This is payment and billing.
A contactless bank card can authorize a one-time payment. An RFID card may only provide an account identifier; the charging management system then calculates the tariff and bills that account later. An app can hold the user’s payment details and request a remote start. Plug & Charge uses digital certificates to identify an eligible vehicle or charging contract, with billing completed through the connected commercial systems.
This distinction matters when a charging session fails. A payment terminal can approve a card while the charger still cannot start because of a connector, vehicle-communication, electrical, or backend problem. The opposite can also happen: the charger is healthy, but the session is blocked by an expired account, failed roaming request, or payment-provider response.
What Do European Rules Require?
The EU Alternative Fuels Infrastructure Regulation, commonly called AFIR, requires operators of publicly accessible charging points to let drivers charge on an ad hoc basis. In plain language, a driver must be able to buy the charging service without first entering a longer-term contract with the charging operator or a mobility service provider.
For publicly accessible charging points deployed from 13 April 2024, AFIR says ad hoc charging must be possible using a payment instrument widely used in the EU. The permitted equipment depends on charging power:
| Publicly accessible charging point | AFIR payment route for points deployed from 13 April 2024 | Practical buyer meaning |
|---|---|---|
| 50 kW or more | A payment card reader or a device with contactless functionality that can at least read payment cards. | Plan card-payment hardware or a compliant shared terminal for the charging pool. |
| Below 50 kW | A card reader, a contactless payment device, or a secure internet-payment device such as one generating a specific QR code. | A secure web-payment flow may be an option, but the complete implementation still needs legal and technical review. |
| No payment required | The Article 5(1) payment-terminal requirements do not apply where the public charging service is free. | Document that no payment is required and confirm any other applicable obligations. |
A single payment terminal may serve several charging points in one charging pool. If that design is used, the driver must be able to identify the correct charger and connector without confusion.
From 1 January 2027, publicly accessible points rated at 50 kW or more along the TEN-T road network or at safe and secure parking areas must meet the card-reader or contactless-payment requirement, including points installed before 13 April 2024. This date is important for retrofit planning, but the rule should not be misreported as applying to every older charger in Europe.
AFIR also requires clear and transparent pricing and preserves an ad hoc option when automatic authentication is offered. Plug & Charge can therefore be an excellent user experience, but a public operator cannot treat it as the only route where AFIR requires an ad hoc alternative.
Contactless Cards: The Simplest Option for Occasional Drivers
Contactless bank-card payment is familiar because it resembles paying at a shop or fuel station. A driver does not need the operator’s app, subscription, or RFID card. This is especially useful for tourists, rental-car users, and drivers who rarely use the network.
The visible action is simple, but the operator needs more than a card reader. The full system may include a terminal, payment service provider, acquiring bank, charger or kiosk, charging management system, tariff engine, receipt page, refund process, and customer-support workflow.
What Buyers Should Check
- Which physical cards and mobile wallets are accepted in the target countries?
- Is the terminal built into each charger or shared across several chargers?
- How does the user select the correct connector at a shared terminal?
- Is the price visible before the driver commits to the session?
- Does the screen show useful progress, charging cost, and final status?
- How are pre-authorisation holds, final settlement, refunds, failed sessions, and chargebacks handled?
- How can the customer retrieve a receipt or VAT invoice where applicable?
- What happens if the payment terminal, charger backend, or mobile connection is unavailable?
- Who owns the merchant agreement and who answers payment disputes?
A temporary card hold can surprise drivers. Some payment flows reserve an amount before charging and settle the actual charge later. The value, release time, and customer message depend on the operator, payment provider, card issuer, and project setup. The charger screen and support page should explain this clearly rather than leaving the driver to assume they were charged twice.
RFID Cards: Strong for Regular Users and Roaming
An RFID charging card usually identifies a driver or account. The account may belong to a charging network, employer, fleet, leasing company, building, or e-mobility service provider. The resulting session can be billed later, deducted from a prepaid balance, or assigned to an internal cost centre.
RFID is useful because it is fast, works without opening an app, and can support repeat users across a roaming network. It is also practical for underground car parks or other locations where phone reception is unreliable. However, the card must be readable by the charger and authorized by the relevant operator or roaming arrangement.
RFID should not be described as universally compatible. A card from one provider may not work at another network, and the price for the same charger can vary by mobility provider and tariff. Operators should make the applicable price easy to find before the driver starts.
For a detailed explanation of card readers, compatibility, security, and offline authorization, see how RFID works on an EV charger.
Apps and QR Codes: Flexible, but Easy to Get Wrong
A good charging app can show station locations, live availability, connector status, prices, receipts, charging history, and account information. For regular customers, those functions provide more value than payment alone.
For a first-time visitor, an app-only journey can be frustrating. The driver may need to download software, create an account, verify an email address, enter payment details, find the correct station, and wait for the backend before charging begins. A dead phone, poor signal, foreign app-store setting, or inaccessible interface can stop the session completely.
A QR code can remove the app-installation step by opening a secure web-payment page. It still needs careful design:
- The code should clearly belong to the charger or connector being used.
- The web address should be recognizable and use a secure connection.
- The label and charger should be checked for tampering or replacement stickers.
- The page should show the station, connector, tariff, and operator before payment.
- The journey should work on common phone sizes, browsers, languages, and accessibility tools.
- The operator needs a fallback and support process when mobile coverage is poor.
Under AFIR, secure internet payment such as a charger-specific QR process is listed as an option for publicly accessible charging points below 50 kW deployed from 13 April 2024. It is not presented as a universal replacement for payment-card acceptance at every public fast charger.
Plug & Charge: Automatic Identification, Not Magic Payment
Plug & Charge allows a compatible electric vehicle to present a digital contract certificate after it is connected to a compatible charger. The function is based on ISO 15118 communication between the vehicle and charger. The charging system can then authenticate the contract and authorize the session without the driver tapping a card or opening an app.
The certificate is best understood as a secure digital membership credential stored for the vehicle. It does not contain cash and does not make charging free. The driver still needs a valid charging contract, and the operator still needs connected systems that can authorize the session, record energy use, calculate the price, and send the bill.
A working Plug & Charge journey depends on several parties:
- a vehicle that supports the relevant ISO 15118 function;
- a charger with compatible hardware, firmware, and configuration;
- certificate installation and lifecycle management;
- a Public Key Infrastructure, or PKI, that establishes digital trust;
- a charging management system and mobility provider that support the workflow;
- a valid customer contract and billing relationship;
- successful interoperability testing across the complete chain.
ISO 15118 covers communication between the electric vehicle and charging equipment. OCPP covers communication between the charger and the charging management system. They solve different parts of the journey. OCPP 2.0.1 includes support for ISO 15118-related workflows, but OCPP compatibility alone does not prove that Plug & Charge is ready across every connected party.
For the protocol relationship and certificate workflow, read the EVB OCPP Standards Hub.
Where CPOs, eMSPs, and Roaming Fit
A charge point operator (CPO) operates the charging infrastructure. An e-mobility service provider (eMSP) gives drivers charging access through a contract, app, or RFID credential. One company can perform both roles, but they are still different jobs.
Roaming connects participating operators and mobility providers so a driver can use one account across more than one network. The driver may tap the same RFID card at several brands of charger, but the session can pass through the charger, CPO backend, roaming platform, and eMSP before the final bill is issued.
This creates convenience, but it also creates commercial questions. The tariff for direct bank-card payment may differ from an app, subscription, or roaming tariff. The checkout should make the price and any relevant fees clear before charging begins.
Which Payment Mix Fits Your Charging Site?
| Site type | Practical payment and access mix | Why |
|---|---|---|
| Public DC fast-charging hub | Ad hoc card/contactless payment plus RFID/app; add Plug & Charge where supported. | Serves visitors, subscribers, roaming users, and compatible vehicles without forcing one journey on everyone. |
| Public AC street or destination charging | Compliant ad hoc route plus app/RFID for account users. | Below-50 kW sites may have more payment-device options under AFIR, but convenience, security, and national rules still matter. |
| Retail, hotel, or commercial car park open to the public | Easy visitor payment plus optional loyalty/app/RFID access. | “Private property” does not automatically mean the charger is not publicly accessible. |
| Workplace with employees and approved visitors | RFID or app accounts; add visitor payment if public or paid guest access is offered. | Internal access control and cost allocation may matter more than retail card payment. |
| Closed fleet depot | RFID, app, vehicle assignment, or automatic identification linked to fleet records. | Drivers normally charge under a company account rather than make individual retail payments. |
| Apartment building | Resident RFID/app accounts with monthly allocation or billing. | The main need is separating users and energy records, not serving unknown public drivers. |
Before deciding that a site is private, restricted, or publicly accessible, examine who can enter the parking area and use the charger. AFIR’s public-access concept is based on access to the location, not simply ownership of the land.
The Charger Is Only One Part of the Payment System
A buyer can purchase a charger with a payment-terminal option and still fail to deliver a usable payment service. Hardware, software, contracts, and support must be commissioned as one system.
- Define the users. Separate visitors, members, employees, residents, fleet drivers, and roaming customers.
- Define the legal site type. Confirm whether each charging point is publicly accessible and which national rules apply.
- Select the driver journeys. Decide how each user starts, pays, receives a price, retrieves a receipt, and gets help.
- Confirm charger functions. Check the exact model, payment-terminal interface, RFID reader, display, metering, firmware, and OCPP functions.
- Select the backend. Confirm tariffs, users, roaming, receipts, refunds, reporting, remote support, and payment integration.
- Arrange payment services. Define the merchant, acquirer, payment service provider, settlement currency, fees, and dispute ownership.
- Test failures. Simulate rejected cards, interrupted sessions, lost connectivity, failed starts, refunds, and payment-terminal outages.
- Test real users. Commission with different cards, phones, languages, vehicles, accounts, and accessibility needs.
OCPP is important, but it is not a complete card-payment standard. The Open Charge Alliance notes that the interface between a payment terminal and the charging management system is outside the core scope of OCPP. Ask the charger supplier, backend provider, and payment integrator to document the actual interface and division of responsibility.
Do Not Treat Accessibility as a Final Cosmetic Check
A payment method is not genuinely convenient if a driver cannot reach the terminal, read the instructions, identify the connector, understand the price, or recover from an error. European guidance encourages accessible placement, usable interfaces, and contactless options. The European Accessibility Act has applied across the EU since June 2025 to covered products and services, including payment-related services and terminals.
During design review, check terminal height and reach, screen contrast, text size, glare, tactile controls where relevant, audio or multisensory support, cable handling, wheelchair space, language choice, and the clarity of support instructions. A shared terminal should be placed where it can be found and reached from all charging bays it serves.
Common EV Charging Payment Mistakes
Specifying Only “RFID and Credit Card Supported”
That does not define card compatibility, payment provider, roaming, tariff display, receipt delivery, offline behavior, or who owns failed transactions.
Assuming Every Public Charger Needs the Same Hardware
AFIR distinguishes power levels, deployment dates, free charging, and certain 2027 retrofit cases. National requirements and the site’s public-access status must also be checked.
Making the App the Only Practical Route
An app may be excellent for members but difficult for a one-time visitor. Public-site design should not hide the ad hoc option behind registration or unclear menus.
Calling RFID a Bank-Card Payment
An RFID charging card normally identifies an account. A contactless debit or credit card uses the payment system. Both may use a tap, but the transaction path is different.
Buying Plug & Charge as a Single Charger Feature
Plug & Charge is an ecosystem function. A compatible charger is necessary, but the vehicle, contract certificate, PKI, backend, and mobility provider must also support the journey.
Testing Only Successful Sessions
Real customer frustration happens during failure. Test incorrect connector selection, payment approval followed by no charge, duplicate-looking holds, session interruption, missing receipt, refund, and network outage.
How EVB Supports European Charging Projects
EVB provides AC and DC charging solutions across a portfolio spanning approximately 3.7 kW to 2,000 kW for residential, commercial, fleet, and public charging applications. Across the wider EVB portfolio and project configurations, available capabilities include RFID, app operation, credit or payment-card integration, contactless payment, MID-compliant metering, OCPP 1.6J, OCPP 2.0.1, and ISO 15118 Plug & Charge support.
These are portfolio-level and project-level capabilities, not a statement that every EVB charger includes every function. The exact payment hardware, metering option, protocol version, certification, backend, CPO integration, and Plug & Charge readiness must be confirmed for the selected model, firmware, destination country, and operating platform.
For publicly accessible European projects, EVB can work with project partners to define charger configuration, payment-terminal integration, RFID and app access, OCPP communication, metering, and public charging service requirements. Buyers should provide the target countries, charger power, number of connectors, expected users, CPO or backend, payment provider, roaming requirements, and required certifications before final configuration.
Sites planning on-charger card payment can review the EVB floor-mounted AC charger with a POS terminal. For higher-power projects, explore EVB DC charging solutions for commercial and public sites, or review the EV charging management software guide for backend, billing, and operating functions.
For a European public charging site, design payment as a choice of journeys rather than a single feature. Give occasional drivers a clear ad hoc route, regular users an account-based RFID or app option, and compatible vehicles Plug & Charge where the complete ecosystem is ready. Then test pricing, receipts, refunds, roaming, accessibility, and failure recovery before the site opens.
Conclusion
Contactless cards, RFID, apps, QR payment, and Plug & Charge each solve a different problem. Contactless bank cards reduce barriers for visitors. RFID and apps help operators manage repeat users, tariffs, roaming, and records. QR payment can provide an app-free web route in suitable designs. Plug & Charge offers the least visible driver effort, but only when the vehicle, charger, certificates, contract, and backend are compatible.
The safest procurement approach is not to ask, “Does this charger support payment?” Ask who will use the site, which journeys are legally required, how each session is authorized and billed, what the driver sees before and after charging, and who resolves a failed transaction. That turns a hardware checkbox into an operable charging service.
FAQ: EV Charging Payment Methods in Europe
Can I pay for EV charging in Europe with a debit or credit card?
Many public chargers accept debit or credit cards, but availability still varies by charger, network, power level, installation date, and country. For publicly accessible charging points deployed from 13 April 2024, AFIR requires an ad hoc electronic payment route and specifies card or contactless devices for points rated at 50 kW or more.
Do I need an app to charge an EV in Europe?
Not always. A charger may allow contactless bank-card payment, RFID authorization, QR or web payment, or Plug & Charge. Apps remain useful for finding stations, checking prices and availability, managing an account, and retrieving charging history.
Is an RFID charging card the same as a contactless bank card?
No. An RFID charging card normally identifies a charging account, subscription, employee, resident, or fleet user. A contactless bank card connects to a payment terminal and payment-processing service. Both are tapped, but they perform different jobs.
What is ad hoc EV charging?
Ad hoc charging means a driver can purchase the charging service without first entering a longer-term contract with the charging-point operator or a mobility service provider. It is intended to give occasional users a practical way to charge.
Can one payment terminal serve several EV chargers?
Yes. AFIR allows one payment terminal or device to serve several publicly accessible charging points within a charging pool. The interface must make it clear which charger and connector the driver is paying for.
Does Plug & Charge charge my bank card automatically?
Not necessarily. Plug & Charge uses a digital contract certificate to identify and authorize a compatible vehicle. Billing is then handled through the linked charging contract and connected commercial systems, which may use the customer’s chosen payment arrangement.
Is OCPP a payment protocol?
OCPP connects charging stations with charging management systems and supports authorization and transaction data. It is not, by itself, the complete interface between a payment terminal, payment provider, bank, and backend. Those integrations must be specified separately.
What payment methods should a European public fast-charging site offer?
A practical mix is ad hoc card or contactless payment for visitors, RFID and app access for registered or roaming users, and Plug & Charge for compatible vehicles and contracts. The final design must meet AFIR, national rules, and the site’s operating model.
Sources and Further Reading
Official standard pages are linked to verify titles, editions, and published scope. Full standard documents may require purchase or licensed access.
- EUR-Lex — Consolidated Regulation (EU) 2023/1804 on alternative fuels infrastructure (accessed September 4, 2026).
- European Commission — Questions and answers on Regulation (EU) 2023/1804 (accessed September 4, 2026).
- European Alternative Fuels Observatory — Guidelines on accessibility of electric recharging infrastructure in the EU (accessed September 4, 2026).
- European Commission — European Accessibility Act (accessed September 4, 2026).
- Open Charge Alliance — Open Charge Point Protocol overview (accessed September 4, 2026).
- Open Charge Alliance — Integrating OCPP Chargers at Filling Stations (accessed September 4, 2026).
- Open Charge Alliance — What Is New in OCPP 2.0.1 (accessed September 4, 2026).
- ISO — ISO 15118-2:2014 published scope (accessed September 4, 2026).
- CharIN — Implementation Guide to Plug & Charge (accessed September 4, 2026).
