EV Charger With Contactless Payment Procurement Guide for CPOs

A tap-to-pay symbol can make public charging look simple. Behind it, a charge point operator still has to coordinate the payment terminal, acquiring service, charger controller, charging management system, tariff engine, network connection, and customer-support workflow. That is why selecting an EV charger with contactless payment requires more than checking “NFC” on a datasheet.

For CPOs, the critical question is whether an unregistered driver can complete a secure, understandable, and reconcilable charging session in the target market. This guide focuses on that operating outcome and on the procurement evidence needed to achieve it.

Define contactless payment correctly

In EV charging, “contactless” is often used for three different experiences:

Method	What the driver presents	How the session is normally billed	Key procurement point
EMV contactless payment	Contactless bank card or supported mobile wallet	Open card transaction through a payment provider and acquirer	Verify certified terminal, card brands, currencies, wallets, and merchant setup
Charging-network RFID	CPO membership card or key fob	Contract account, roaming account, or fleet invoice	It is identification, not necessarily a bank-card payment
Phone-based QR or app payment	Smartphone browser or app	Card-on-file, wallet, or online checkout	Depends on phone, data connection, URL security, and user completion

The radio technology alone does not define the commercial function. Both a bank card and an EV charging RFID card can be presented without physical contact, but they enter different authorization, settlement, security, and customer-support processes.

Write the RFP in terms of user outcomes. For example: “An ad hoc user must be able to pay with supported contactless bank cards and mobile wallets without downloading an app or creating an account.” Then list the countries, currencies, card brands, languages, and receipt requirements.

Understand the contactless transaction path

A reliable project has a documented sequence from tap to settlement:

1. The charger or terminal displays the tariff and asks the driver to select a connector if necessary.

2. The terminal reads the contactless payment credential and sends an authorization request through the payment service.

3. The issuer approves, declines, or requests another cardholder-verification method.

4. The charging system receives the result and starts only the selected connector.

5. The EVSE meters the session and sends transaction data to the CSMS.

6. The payment system captures the final amount, reverses or adjusts the pre-authorization as applicable, and creates a transaction record.

7. The CPO reconciles the payment record with the charging-session and settlement records.

EMVCo states that EMV contactless supports contactless chip cards and NFC-enabled mobile devices, with a one-time security code generated for each transaction. That is an important security property, but it does not answer project-specific questions such as whether a particular mobile wallet is enabled, whether PIN entry is required above a threshold, or whether the acquirer will authorize a transaction during a communications outage.

Obtain those answers from the terminal solution provider, processor, and acquirer—not from a generic reader-component specification.

Match the terminal type to the site and customer journey

Contactless-only terminal

A compact contactless-only device can suit markets and projects where tap-to-pay is sufficient. It reduces slots and moving interfaces exposed to dirt or misuse. However, it may not serve cards that require insertion or a transaction that needs PIN entry. Confirm local and tender requirements before adopting this design.

Contactless plus chip and PIN terminal

This configuration supports a broader cardholder-verification journey and may be required by the acquirer or project. It needs more enclosure space, a reachable keypad, readable display, weather protection, and accessible positioning. The physical integration must maintain the charger enclosure’s safety and environmental performance.

Integrated terminal on each charger

Per-charger terminals make the driver-to-charger relationship obvious and isolate most terminal failures to one unit. They also multiply hardware, merchant-terminal records, software maintenance, and field service.

Shared contactless terminal

A shared terminal can serve several points in a charging pool and reduce terminal count. It works only if the driver can identify and select the correct bay or connector without ambiguity. The design also needs a queue model, accessible route, weather shelter where appropriate, and a strategy for the shared device becoming unavailable.

Apply payment rules by market and power level

For European public charging, payment architecture has become a core equipment decision. Under the current consolidated Alternative Fuels Infrastructure Regulation, publicly accessible charging points must support ad hoc charging. For points deployed from 13 April 2024, those rated at 50 kW or more must accept widely used electronic payments through a payment card reader or a device with contactless functionality that can at least read payment cards. Below 50 kW, secure internet-connected payment methods such as a specific QR code may be used under the conditions in Article 5. The regulation also allows one payment terminal or device to serve several points within the same recharging pool.

The consolidated AFIR text should be checked alongside national rules, accessibility requirements, funding conditions, and the project deployment date. For sites outside the EU, buyers should identify the equivalent payment, pricing, and consumer-protection requirements.

Do not add “AFIR compliant” to an RFP without turning it into testable requirements. State the charger power, public-access status, deployment location and date, payment device class, price display, ad hoc journey, and responsibility for future software or regulatory updates.

Procure the payment service as carefully as the hardware

The terminal cannot settle funds by itself. The CPO needs a merchant and acquiring arrangement compatible with unattended EV charging. Ask potential payment partners to provide a country-by-country acceptance matrix covering:

• supported card schemes and mobile wallets;

• settlement currencies and foreign-card handling;

• merchant onboarding requirements and lead time;

• pre-authorization, incremental authorization, completion, reversal, refund, and chargeback processes;

• fees by transaction, terminal, currency, and settlement route;

• rules for declined or interrupted transactions;

• online and any permitted offline behavior;

• receipt and tax-document capabilities;

• terminal management, software deployment, certificates, and key lifecycle;

• customer and CPO support hours.

Avoid assuming that a terminal certified in one region can be boarded by any acquirer in another. Hardware model, payment application, firmware, processor certification, key setup, and merchant configuration normally form a specific approved combination.

Separate payment-device approval from CPO PCI scope

An outdoor payment terminal should use payment-industry-approved hardware and software appropriate to the intended deployment. PCI PIN Transaction Security requirements address the physical and logical security of payment interaction devices. Yet the PCI Security Standards Council explicitly notes that a PTS-approved device does not, by itself, make the merchant PCI DSS compliant or automatically reduce PCI DSS scope.

The procurement team should document where account data is read, encrypted, transmitted, logged, stored, or tokenized. Confirm whether a validated point-to-point encryption solution is being used and what the CPO must still operate, monitor, and assess. If the charger or CSMS receives tokens rather than card data, state that boundary in the architecture and verify it during implementation.

Physical security matters too. Require tamper alerts, secure mounting, controlled access to service compartments, asset inventory, terminal replacement procedures, and a process for inspecting signs of tampering. A damaged or substituted terminal should trigger an operational incident, not merely a maintenance ticket.

Design for outdoor usability and accessibility

Payment success begins before the card is read. Drivers must be able to locate the terminal, understand the price, reach the interface, select the correct connector, and see whether the payment was accepted.

Review these physical factors at design stage:

• mounting height and reach range for the target accessibility rules;

• clear approach space and an unobstructed route from parking bay to terminal;

• screen contrast, text size, glare, and readability in direct sunlight;

• tactile keypad or alternative cardholder-verification method where required;

• audible and visual feedback that does not rely on color alone;

• weather, dust, impact, condensation, drainage, and operating-temperature ratings;

• location of contactless target, card slot, receipt instructions, and help contact;

• consistency between bay labels, terminal menu, charger screen, and CSMS records.

Test the design with a first-time user. Operators and installers who know the system can unconsciously skip steps that will confuse an occasional driver.

Engineer connectivity and degraded modes

A contactless charging transaction may depend on at least three communications paths: terminal to payment host, charger to CSMS, and internal charger-to-terminal or site-controller communication. Each path can fail independently.

The National Renewable Energy Laboratory’s Best Practices for Payment Systems at Public Electric Vehicle Charging Stations recommends a site survey and careful planning for network availability, hardware exposure, integration, and software updates. For a high-value public site, consider wired service where practical, resilient cellular coverage, properly positioned antennas, monitored routers, and a tested backup path.

Define degraded behavior before commissioning:

Failure	Required decision
Payment host unavailable	Decline safely, use an acquirer-approved offline mode, or offer an approved alternative?
CSMS unavailable	Can the charger start an authorized session locally, and how is it reconciled later?
Terminal unavailable	Is another terminal available, and can drivers see that before parking?
Charger controller unavailable	Can the terminal cancel or reverse the authorization promptly?
Network recovers after a timeout	How are duplicate authorizations and late messages prevented?

Offline acceptance should never be assumed. It depends on acquirer policy, terminal functionality, card rules, transaction limits, and the operator’s risk tolerance.

Integrate tariffs, receipts, and reconciliation

The terminal experience is incomplete if the CPO cannot explain a charge on a customer’s statement. Define how the system handles energy charges, time charges, session fees, occupancy fees, taxes, and any temporary pre-authorization. The tariff shown before payment should match the tariff used for final capture.

Every transaction needs stable identifiers that link:

• site and merchant;

• terminal ID;

• charger and EVSE ID;

• connector or bay;

• CSMS session or transaction ID;

• payment authorization and capture reference;

• meter start, meter stop, and billed quantity;

• receipt and settlement record.

The CPO finance team should participate in acceptance testing. A technically successful session that cannot be reconciled at month end is not a complete payment solution.

Use a practical factory and site test matrix

Testing should include more than a successful tap. At minimum, perform:

• approved and declined contactless card transactions;

• supported mobile-wallet transactions;

• cardholder-verification or alternate-interface prompts where applicable;

• all connectors on every terminal mapping;

• pre-authorization, final capture, reversal, cancellation, and refund;

• user stop, vehicle stop, emergency stop, timeout, and cable disconnect;

• repeated tap and abandoned-session behavior;

• terminal reboot, charger reboot, router reboot, and CSMS interruption;

• primary-to-backup network transition and recovery;

• correct tariff, tax, receipt, and settlement data;

• remote monitoring, alarm, firmware, and terminal-replacement processes.

Use the intended charger firmware, terminal hardware, payment application, CSMS release, merchant configuration, and country settings. Record version numbers and test evidence in the handover pack.

Procurement checklist for an EV charger with contactless payment

Before award, confirm that the proposal states:

• charger model, rated power, connectors, and target electrical standard;

• terminal model, payment application, firmware, and mounting method;

• supported contactless cards, wallets, currencies, and countries;

• whether chip, PIN, magstripe, or accessibility interfaces are required;

• payment provider, acquirer, merchant-onboarding owner, and commercial fees;

• CSMS and OCPP version, plus the proprietary or standard interfaces used for payment coordination;

• encryption, PCI responsibilities, logging boundaries, and tamper process;

• online, backup, and degraded-mode behavior;

• tariff, pre-authorization, refund, receipt, and reconciliation workflows;

• environmental and impact ratings for the installed assembly;

• factory and site acceptance tests;

• spare terminals, support ownership, update policy, and service levels.

How Luxman Energy can support the equipment layer

Luxman Energy supplies AC and DC charging equipment for commercial and public projects. Selected Luxman DC configurations list POS or wireless payment options together with OCPP 1.6J and Ethernet, Wi-Fi, or 4G connectivity. Its public charging solution also describes operator-oriented charging networks and smart energy management.

Payment functions, terminal certifications, card acceptance, acquirer availability, connector standards, and regulatory evidence should be confirmed for the selected model and country. Project requirements may call for an integrated terminal, a shared device, or coordination with a CPO-nominated payment provider.

Frequently asked questions

Does contactless payment mean the charger accepts Apple Pay or Google Pay?

Not automatically. A contactless-capable terminal may support NFC mobile wallets, but actual acceptance depends on its payment application, processor, acquirer, card schemes, wallet provisioning, and deployment country. Require a written acceptance matrix.

Can the same reader accept bank cards and charging RFID cards?

Some hardware can contain or coordinate both functions, but they remain different transaction types. Verify which antenna, application, security certification, and back-office workflow handles each credential.

Does a contactless charger work without mobile coverage?

It may use wired connectivity, cellular service, or a combination. Offline card acceptance is not guaranteed and must be approved by the acquirer and tested. The charger and CSMS also need defined behavior during their own connectivity loss.

Is a shared contactless terminal suitable for a large charging hub?

It can be, especially where chargers form one clearly identified pool. The design should address driver walking distance, connector selection, simultaneous arrivals, accessibility, redundancy, and the operational impact of one terminal failure.

Is contactless bank-card payment required on every public charger in Europe?

No single answer covers every point. AFIR requirements depend on factors including public accessibility, rated power, deployment date, and location. National and funding rules may add obligations. Review the current regulation and obtain project-specific compliance advice.

What is the most important commissioning test?

End-to-end testing on every connector is essential. It should prove that the correct tariff, payment authorization, charging session, final capture, receipt, and settlement record remain linked under normal and failure scenarios.

Conclusion

An EV charger with contactless payment should be procured as an operating payment service, not as a reader accessory. Success depends on a clear ad hoc user journey, a market-approved terminal and acquiring combination, reliable session mapping, resilient communications, accessible outdoor installation, and support ownership across vendors.

To assess a Luxman configuration, provide the charger power, connector type, number of points, site layout, deployment country, OCPP and CSMS requirements, preferred acquirer or payment provider, card and wallet requirements, and installation environment. Those inputs allow the equipment and payment interfaces to be reviewed before commercial commitment.