EV Charging Payment Terminal Supplier Evaluation Guide

Selecting an EV charging payment terminal supplier is not the same as buying a standalone card reader. The required result is a working commercial chain: a driver pays through the production merchant account, the correct connector starts, the final energy charge is captured, settlement reaches the operator, and support teams can resolve exceptions without exposing card data.

This guide gives CPO procurement teams, OEM partners, charging integrators, EPC contractors, and importers a practical RFP framework. Luxman Energy publishes charger configurations that include POS or wireless payment on selected products, while exact terminal, acquirer, card-scheme, certification, and market availability should be confirmed for each project.

Define what the supplier is responsible for

The phrase payment terminal supplier can refer to several different businesses. One company may manufacture the terminal hardware. Another may provide the payment application, gateway, terminal management system, acquiring connection, charging integration, or field service. The charger supplier may integrate the enclosure and interface but not act as the merchant acquirer.

Ask every bidder to mark its role in a responsibility matrix.

Scope	Evidence required	Typical accountable party
Terminal hardware	Model, environmental rating, lifecycle status, approvals	Terminal manufacturer or solution supplier
Charger integration	Mechanical fit, power, networking, connector mapping, start logic	Charger OEM and system integrator
Payment application	Version, supported kernels and schemes, update process	Payment application provider
PSP and gateway	Authorization, tokenization, capture, reversal, refund, reporting	Payment service provider
Acquiring	Merchant onboarding, scheme access, settlement, chargebacks	Acquirer
Terminal management	Configuration, certificates, keys, remote updates, inventory	TMS provider or acquirer
Charging backend	Tariffs, sessions, meter records, receipt references, APIs	CPO or CSMS provider
Site service	Installation, inspection, swaps, spares, escalation	EPC or field-service partner

A proposal that says payment supported without assigning these responsibilities is incomplete. Require named subcontractors and interfaces. If one party changes after award, the certified or tested combination may also change.

Confirm the complete market ready combination

A terminal demonstration in one country does not prove readiness in another. Payment acceptance depends on the complete combination of hardware, application, acquirer, merchant entity, card schemes, currency, network, and regional configuration.

The supplier should confirm in writing:

• Terminal model and hardware revision

• Payment application and firmware versions

• Contactless and contact-chip functions required by the market

• Supported international and domestic card schemes

• Mobile-wallet acceptance through supported schemes

• Acquirer and PSP available to the merchant entity

• Transaction currency and settlement currency

• Local language, tax, receipt, and fiscal requirements

• SIM, telecom, and terminal-management coverage

• Preauthorization, capture, reversal, refund, and chargeback behavior

• Production lead time for merchant onboarding and terminal activation

Do not accept a global card logo list as evidence. Ask for the status of each required combination: generally available, certified, pilot, integration work required, or unavailable. Record assumptions in the commercial offer and acceptance plan.

Verify security claims precisely

Payment-security terms are often compressed into one claim such as PCI compliant. Buyers should separate device approval from the merchant’s broader compliance duties.

The PCI Security Standards Council explains that PCI PTS standards address the physical and logical security of payment devices. A PTS-approved terminal may facilitate PCI DSS compliance, but it does not by itself guarantee compliance or automatically reduce the merchant’s cardholder-data environment. Scope depends on the application, encryption, connected systems, terminal management, and actual data flows.

Request these items where applicable:

• The exact PCI PTS device listing and approval expiry information

• Evidence for the installed payment application

• Whether SRED is enabled in the deployed combination

• Details of any validated PCI P2PE solution

• A data-flow diagram showing where account data, tokens, and references travel

• Remote-access and terminal-management controls

• Patch, vulnerability, key, and certificate management processes

• Device inventory and anti-tampering procedures

• Allocation of PCI DSS responsibilities among merchant and service providers

The charging system should normally receive a non-sensitive payment token or transaction reference, not full card data. Contracts should prohibit sensitive account data from appearing in charger logs, OCPP payloads, support tickets, or general analytics.

Assess EMV and scheme readiness

The word EMV also needs detail. EMVCo manages specifications and approval processes for payment technologies, while card schemes, acquirers, and local market rules add further requirements. Ask which EMV functions, contactless kernels, terminal configuration, and Level 3 integration tests apply to the proposed deployment.

EMVCo’s EV Open Payments work aims to support a consistent card-based experience for charging and discusses how open payment can coexist with ISO 15118 Plug and Charge. It does not remove the need to validate the production terminal, processor, acquirer, merchant, and charging workflow.

For each card brand or domestic scheme, require evidence that the production path has been approved or tested. Include physical contactless cards, phone wallets, foreign-issued cards, declined cards, and any required contact-chip fallback. If PIN entry is required for some transactions, verify the user interface, accessibility, and environmental suitability.

Evaluate charger and backend integration ownership

The supplier must explain how a payment authorization becomes permission to energize one connector. That explanation should identify the integration boundary and message ownership.

A robust design preserves these relationships:

Identifier	Why it matters
Site and station ID	Groups assets, tariffs, merchant settings, and reports
Charger and EVSE ID	Identifies the charge point presented to users and systems
Connector ID	Prevents an authorization from starting the wrong outlet
Terminal and lane ID	Identifies the payment device and merchant configuration
Payment reference	Links authorization, capture, reversal, refund, and chargeback
Charging transaction ID	Links start, meter values, stop reason, and energy total
Tariff version	Proves which price rules applied at the session time
Receipt or invoice ID	Connects customer evidence to the underlying records

Ask whether orchestration occurs inside the charger, at a site controller, in the CSMS, or through a payment gateway. Each pattern can work, but the accountable vendor must own timeouts, duplicate requests, connector status changes, and recovery after a restart.

OCPP connects a charger with a charging management system. OCPP 2.1 includes explicit support for ad hoc payment through a built-in or stand-alone card terminal, according to the Open Charge Alliance. OCPP 1.6 remains widely used and can participate in payment-enabled solutions through an agreed integration, but a generic OCPP claim does not prove that the required payment workflow is portable or standardized.

Request an evidence pack before award

Good supplier evaluation replaces marketing statements with reviewable evidence. The RFP should require an evidence pack for the proposed country and configuration.

Include:

1. Product datasheets and controlled model numbers

2. Approval and certification identifiers with validity dates

3. Supported acquirer, PSP, scheme, currency, and merchant combinations

4. Architecture and data-flow diagrams

5. Interface specifications and version compatibility

6. Responsibility and subcontractor matrix

7. Payment and charger state diagrams

8. Cybersecurity and remote-management documentation

9. Environmental and mechanical installation requirements

10. FAT and SAT procedures with expected results

11. Service, spares, end-of-life, and update policies

12. Sample reports for settlement, reconciliation, refunds, and terminal inventory

Review documents against the exact ordered configuration. A certificate for a related terminal family, older firmware, different application, or different acquirer may not cover the proposed deployment. The Open Charge Alliance maintains an OCPP certification program and certified-product list, which can help buyers verify OCPP conformance claims independently.

Compare lifecycle service rather than unit price

The terminal purchase price is only one cost. A commercial comparison should include integration, certification, merchant onboarding, software licenses, SIMs, gateway fees, scheme and acquiring fees, terminal management, security assessments, replacements, site visits, refunds, chargeback handling, and end-of-life migration.

Ask suppliers to price a common scenario and separate one-time from recurring charges.

Cost area	Buyer question
Hardware	Are mounting, enclosure, antenna, cabling, and spare units included
Integration	Which charger, CSMS, and payment interfaces are included in the fixed price
Certification	Who pays for changes required by terminal, application, or acquirer updates
Transactions	Which fixed, percentage, minimum, cross-border, and refund fees apply
Connectivity	Is the terminal SIM separate from charger connectivity
Operations	Are TMS, monitoring, reports, and remote support recurring services
Field service	What are response time, swap process, travel, and out-of-warranty rates
Lifecycle	What happens when the terminal, payment application, or network is retired

Low-cost hardware can create high switching cost if the integration is proprietary or the acquirer cannot be changed. Request data export, configuration ownership, API access, and a termination-assistance clause where commercially appropriate.

Define service levels for unattended infrastructure

An EV terminal may operate outdoors around the clock without staff. The supplier should state how failures are detected, classified, and resolved. Service levels should distinguish remote response, remote restoration, dispatch, spare delivery, and final repair.

Require monitoring for terminal online state, application health, certificate expiry, storage, tamper alerts, transaction failures, and configuration drift. Define who receives each alarm and which system is authoritative. Confirm how a terminal is safely taken out of service while affected chargers remain available through another approved payment method.

Spare strategy should account for activated merchant configuration. An unconfigured terminal in a warehouse may not be a usable spare. Ask how device identity, keys, certificates, application, acquirer parameters, and connector mapping are transferred without exposing credentials or delaying service.

Test production conditions before volume rollout

Factory acceptance should use the intended terminal model, charger software, integration version, CSMS, payment test environment, and representative cards. Site acceptance should use the production merchant, acquirer, network, tariff, and physical installation.

Minimum tests include:

• Every required card and wallet on every terminal type

• Correct selection of each EVSE and connector

• Price and hold disclosure before authorization

• Approved, declined, timeout, cancellation, and repeated-tap paths

• Charger unavailable before and after authorization

• Very short and normally completed charging sessions

• Correct final capture and release of unused authorization

• Reversal after a failed charger start

• Refund and receipt retrieval

• Loss and restoration of each network path

• Terminal reboot, charger reboot, and backend restart

• Reconciliation across charger, CSMS, PSP, acquirer, and bank settlement

Do not treat one successful tap as acceptance. The evidence should include transaction IDs, timestamps, expected state changes, screen messages, and final financial results.

Review Luxman payment capable configurations

Luxman’s commercial DC charger with advertising display lists 60 kW, 80 kW, 120 kW, 160 kW, and 180 kW options, 43-inch or 55-inch displays, Ethernet, Wi-Fi, 4G, OCPP 1.6J, and wireless or POS payment. The same page lists CCS2, CCS1, and GB/T charging interfaces.

These published details provide a starting point for an RFP. Buyers should request confirmation for the selected model, terminal hardware, payment application, card schemes, acquirer, merchant country, currency, approvals, connector configuration, communications, and installation environment. Project requirements should be confirmed with the supplier, and availability may vary by model or market.

EV charging payment terminal supplier scorecard

Score evidence, not presentation quality.

Evaluation category	Suggested evidence
Market readiness	Production references for the same country, acquirer, and payment combination
Technical integration	Controlled interface documents and successful end-to-end test results
Payment security	Applicable device, software, encryption, and PCI evidence
Charging interoperability	Supported OCPP version, profiles, certification status, and CSMS test results
Operations	Monitoring, TMS, inventory, alarms, remote tools, and incident workflow
Service	Named service locations, spares, response targets, and escalation contacts
Commercial clarity	Complete one-time and recurring costs plus change-control rates
Lifecycle	Support dates, update commitments, component substitution, and migration plan

Weight categories according to project risk. A national CPO may prioritize multi-acquirer portability and lifecycle governance. A smaller commercial site may give more weight to a complete managed service and local field support.

Frequently asked questions

Does a payment terminal supplier also provide acquiring?

Sometimes, but not always. The terminal vendor, PSP, gateway, acquirer, charger supplier, and system integrator may be separate parties. Require a named responsibility matrix and production merchant path.

Is a PCI PTS approved terminal automatically PCI DSS compliant?

No. PCI SSC states that a PTS-approved device can support compliance but does not by itself guarantee PCI DSS compliance or remove connected systems from scope.

Does OCPP certification prove that card payment works?

No. OCPP certification addresses conformance between the charger and charging management system for the certified version and profiles. Card acquiring and end-to-end payment integration require separate evidence and tests.

Can one terminal model be used in every country?

Not automatically. Acquirers, card schemes, languages, currencies, fiscal rules, telecom services, approvals, and payment applications vary by market.

What should be tested before placing a volume order?

Test the exact charger, terminal, software, CSMS, PSP, acquirer, merchant, tariff, and network combination. Include failure recovery, refunds, settlement, and reconciliation, not only a successful authorization.

How should buyers compare supplier price?

Compare total lifecycle cost over the intended contract period. Include integration, recurring services, transaction fees, field support, replacements, security work, certification changes, and end-of-life migration.

EV charging payment terminal supplier conclusion

An EV charging payment terminal supplier should be evaluated on the complete operational and financial outcome. The strongest bid identifies every party, proves the market-specific combination, limits sensitive-data exposure, owns the charger interface, supports the installed fleet, and produces evidence from authorization through bank settlement.

For a technical and commercial review, send Luxman Energy the target country, charger model and power, connector count, station architecture, required cards and wallets, merchant entity, preferred PSP and acquirer, OCPP platform, tariff and hold rules, receipt requirements, communications, service coverage, and project schedule. Luxman Energy can then confirm available charger and payment configurations and the responsibilities that must be coordinated with local payment partners.