EV Charging Station With Payment Terminal Shared and Dedicated Terminal Design

A payment terminal can be installed on every charger, mounted beside each unit, or shared by several charging points. All three designs can support public charging, but they produce different capital costs, driver journeys, failure modes, accessibility requirements, and operating workloads.

For a multi-bay EV charging station with payment terminal access, the architecture should be decided during concept design—not after chargers have been ordered. The terminal location affects civil works, data cabling, bay identification, payment-session mapping, queuing, signage, monitoring, and regulatory evidence.

This guide helps CPOs, charging-hub investors, EPC contractors, parking operators, and commercial site owners compare dedicated and shared payment-terminal designs.

First define the charging pool

A project team should draw a boundary around the charging points intended to operate as one site or charging pool. Record:

• each parking bay and its accessible route;

• charger, dispenser, connector, and cable arrangement;

• expected driver entry and exit paths;

• terminal and kiosk locations;

• electrical cabinets and network equipment;

• canopy, lighting, bollards, kerbs, drainage, and snow-clearance zones;

• areas that remain publicly accessible after the host business closes;

• responsibility boundaries between CPO, landlord, utility, and service providers.

This site map becomes the foundation for terminal-count, walking-distance, signage, networking, and redundancy decisions. A “shared terminal” is only convenient when a driver can easily understand which bays it serves.

Dedicated versus shared payment terminals

Decision factor	Dedicated terminal on each charger	Shared terminal for several points
Driver mapping	Usually direct and intuitive	Requires bay or connector selection
Terminal hardware count	Higher	Lower
Failure impact	Normally limited to one charger	May affect the entire pool or terminal zone
Queue risk	Low at the payment step	Depends on arrivals, transaction time, and terminal count
Civil and data design	Repeated at each charger	Central infrastructure, sometimes with longer cable routes
Accessibility	Must be achieved at every interface	Can concentrate investment in one accessible interface, but route and reach must work from served bays
Retrofit flexibility	Charger enclosure may constrain terminal model	Kiosk or pedestal can offer more space and easier replacement
Customer support	Charger and terminal are naturally paired	Support team needs exact bay and terminal identifiers
Operating cost	More terminal fees, inspections, and spares	Lower device count but higher consequence of one failure
Expansion	Add a terminal with each new charger	Shared system must have capacity and mapping for new bays

The lowest terminal count is not always the lowest-cost design. If a single shared device becomes unavailable at a high-utilization hub, lost charging revenue and driver abandonment may exceed the saved hardware cost.

When a dedicated terminal is usually stronger

A terminal on each charger often suits:

• highway or petrol-station sites where drivers expect a direct walk-up transaction;

• dispersed chargers that are not visible from one central kiosk;

• high-throughput locations where simultaneous arrivals are common;

• sites where losing one terminal should not stop other chargers from accepting cards;

• layouts with several entrances, levels, or physically separated parking zones;

• charging units whose screens already guide the complete payment and charging flow.

The main procurement challenge is scale. Ten chargers may mean ten terminal subscriptions, ten merchant-terminal records, ten devices to inspect, and a larger spare inventory. Software and terminal management must support bulk configuration without creating inconsistent tariffs or firmware versions.

A dedicated design also requires confirmation that the terminal integration preserves the charger’s environmental and safety performance. Every interface must be reachable and readable, including at designated accessible bays.

When a shared payment terminal is usually stronger

A shared terminal or kiosk can work well for:

• compact charging hubs where all bays are visible from a central point;

• car parks with a controlled pedestrian route;

• sites using simple, prominent bay numbering;

• projects seeking a larger screen, multiple payment interfaces, or additional languages;

• retrofits where modifying every charger enclosure is impractical;

• charging pools where a CPO wants to centralize terminal maintenance.

The design must answer three questions clearly:

1. Which charger or connector is the driver selecting?

2. Can more than one driver pay at the same time or within the expected arrival peak?

3. What happens if the shared terminal, its power supply, or its network link fails?

For a large hub, “shared” does not have to mean “one.” Two or more centrally located terminals can provide capacity and redundancy while still reducing device count relative to one terminal per charger.

Determine how many shared terminals the site needs

There is no reliable universal ratio such as one terminal for every eight chargers. Terminal demand depends on arrivals, not only on the number of connectors.

Model at least:

• peak vehicles arriving per five-minute interval;

• average time to read instructions, select a bay, present a card, and obtain authorization;

• percentage of declined payments or repeated attempts;

• additional time for chip-and-PIN, language selection, or receipt retrieval;

• terminal downtime and planned maintenance;

• walking distance from the furthest served bay;

• likelihood that new chargers will be added;

• acceptable wait and acceptable share of the site disabled by one failure.

A basic queue calculation can estimate average demand, but design should also test short bursts—for example, several vehicles arriving after a motorway incident clears or at a fleet shift boundary. If one terminal would operate near saturation during peaks, add capacity. If the business cannot tolerate all card-paying users being blocked, add redundancy even when average utilization is low.

Make charger and connector selection unambiguous

Shared terminals fail at the user-experience layer when identifiers are designed by different teams. The same bay may be called “A3” on a sign, “EVSE 104” in the CSMS, “Charger 2B” on the terminal, and “Connector 7” in a support tool.

Create one identifier register before configuration. It should map:

Customer-facing item	Operational record
Site name and address	CPO site ID and merchant location ID
Bay label	Parking asset or wayfinding ID
Charger label	EVSE ID, charger serial number, and CSMS identity
Connector label	Connector number, plug type, and physical cable
Terminal label	Terminal ID, merchant terminal ID, and network asset
Receipt reference	Charging-session ID and payment authorization/capture reference

Use labels that remain visible when a vehicle is parked. Apply them consistently to ground markings, overhead signs, charger displays, the payment menu, remote-support dashboard, receipt lookup, and field-service documentation.

At commissioning, initiate a payment for every selectable item and verify that only the intended connector starts. Repeat after any terminal or charger replacement.

Design the shared-terminal user journey

A practical sequence is:

1. Park in a clearly numbered bay and connect the vehicle, or follow the site’s stated order.

2. Go to the terminal and select the same bay or connector identifier.

3. Review the tariff and any pre-authorization information.

4. Tap or insert a supported payment card and complete cardholder verification if requested.

5. Receive a clear authorization result and confirmation that the selected charger is starting.

6. Return to the vehicle and verify charging status.

7. End the session using the stated method.

8. Retrieve a receipt using a secure reference or online process.

The terminal should prevent a driver from paying for a connector already in use by someone else. It should show unavailable, faulted, reserved, or blocked connectors accurately. If status data is delayed, the system needs a conservative rule that avoids taking payment for a session it cannot start.

Keep instructions short. Site signs can explain the overall process, while the terminal presents one decision at a time. A help number or intercom should identify both the site and the selected bay to the support agent.

Check regulatory and accessibility implications

In the European Union, the current consolidated Alternative Fuels Infrastructure Regulation requires ad hoc charging at publicly accessible points and sets electronic-payment requirements based partly on rated power and deployment date. For publicly accessible charging points of 50 kW or more deployed from 13 April 2024, operators must accept electronic payments through a payment card reader or a contactless-capable device that can at least read payment cards. Article 5 also states that one terminal or device may serve several charging points within the same recharging pool.

That permission supports shared architectures, but it does not eliminate design obligations. Review the current AFIR text, national measures, consumer-price information, accessibility rules, and funding conditions. A terminal may be legally present yet practically unusable if the route is blocked by kerbs, the screen is unreadable, or a wheelchair user cannot reach the card interface.

Accessibility planning should cover parking-bay dimensions, level access, slopes, kerbs, reach ranges, screen angle, tactile or audible feedback where required, clear space in front of the terminal, and cable management. Use applicable national standards and involve accessibility specialists early.

Build resilience into a shared design

A shared-terminal station concentrates several dependencies. Treat the following as distinct failure domains:

• terminal hardware and payment application;

• terminal power supply;

• payment-host connectivity;

• local terminal-to-site-controller network;

• charger-to-CSMS connectivity;

• CSMS availability;

• gateway, processor, and acquiring service;

• site controller or connector-selection service.

Possible mitigations include two terminals, independent network paths, monitored uninterruptible power for low-voltage systems, resilient routers, multi-network cellular service, spare preconfigured terminals, and a clearly approved alternative payment journey. The CPO should know which mitigation actually works under each outage. An app is not a useful backup for an ad hoc driver if the app requires lengthy registration or lacks coverage at the site.

The National Renewable Energy Laboratory’s 2024 payment-systems best-practices report emphasizes site connectivity, rugged outdoor hardware, integration testing, coordinated software updates, and clear driver instructions. These concerns become more important when one device serves multiple revenue-producing points.

Keep payment security outside unnecessary systems

A shared kiosk can contain more computing and networking functions than a small terminal, which can broaden the security surface. Define where payment account data is read, encrypted, tokenized, transmitted, and logged. Charger and CSMS systems should receive only the information they need to authorize and reconcile sessions.

Use terminal hardware and payment software approved for the intended processor and market. PCI PIN Transaction Security approval addresses the payment interaction device, but the PCI Security Standards Council notes that a PTS-approved device alone does not make the merchant environment PCI DSS compliant. The CPO should obtain a documented PCI scope and responsibility model.

Protect service doors, network ports, cables, and mounting bolts. Monitor tamper states and terminal health remotely. Field procedures should require identity checks, chain of custody, and post-replacement validation for any terminal swap.

Compare total cost and revenue risk

Create a lifecycle model rather than comparing only purchase prices.

Dedicated-terminal cost factors

• terminal hardware for every charger;

• enclosure integration and repeated installation labor;

• per-terminal software, connectivity, or acquiring fees;

• larger spare stock and more inspection points;

• more individual firmware and asset records;

• lower shared-failure exposure.

Shared-terminal cost factors

• kiosk or pedestal enclosure and foundation;

• central power, network, canopy, lighting, and signage;

• connector-selection and site-controller integration;

• queue capacity and possible second terminal;

• higher business impact per terminal outage;

• more complex driver support and identifier mapping;

• potential savings in hardware and terminal-management count.

Estimate lost contribution margin during each failure scenario. If a shared device controls payment for eight DC chargers, its recovery time and spare availability may matter more financially than the cost difference between one and two terminals.

RFP requirements for an EV charging station with payment terminal

Ask bidders to provide:

• a site drawing with every bay, charger, connector, terminal, accessible route, and sign;

• the number of simultaneous payment interactions supported;

• charger-selection and identifier-mapping logic;

• exact terminal, kiosk, charger, controller, router, and software versions;

• payment provider, acquirer, country, card, wallet, currency, and PIN support;

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

• interfaces among terminal, site controller, charger, CSMS, and finance system;

• environmental, impact, electrical, EMC, radio, and payment evidence for the installed assembly;

• primary, backup, and degraded connectivity behavior;

• accessibility assessment against local requirements;

• monitoring, tamper alert, update, spare, and replacement procedures;

• factory and site acceptance test plans;

• fault ownership, response times, and escalation contacts.

The offer should state whether the solution is mechanically prepared, terminal-fitted, integration-tested, or delivered as an end-to-end payment service.

Commission the complete charging pool

Factory testing should prove connector selection, authorization, start, stop, capture, reversal, refund, receipt, restart, monitoring, and error recovery using the intended charger, terminal, CSMS, and payment configurations.

Site acceptance should then test:

• every terminal-to-bay-to-connector combination;

• two or more near-simultaneous users where supported;

• declined cards and abandoned selections;

• charger unavailable after payment authorization;

• shared terminal restart during an active session;

• failure and recovery of primary and backup networks;

• terminal replacement and remapping;

• tariff and receipt correctness;

• reconciliation from payment settlement to metered charging session;

• accessibility and legibility under real lighting and parking conditions.

Do not accept only one successful transaction as evidence for a multi-point station.

Applying the design to Luxman Energy equipment

Luxman Energy supplies AC and DC charging equipment and describes operator-oriented network, customer-service, and smart-energy functions for public charging. Its public charging solution can be evaluated as the equipment layer within either a dedicated-terminal or shared-terminal site architecture.

Selected Luxman DC configurations list POS or wireless payment options and OCPP 1.6J connectivity, with communications options varying by model. Confirm the exact terminal arrangement, connector standards, power level, payment-service interface, certifications, and market availability during project design. A shared terminal may require additional site-control and integration scope beyond the charger itself.

Frequently asked questions

Can one payment terminal serve multiple EV chargers?

Yes, if the driver can select the correct point and identifiers reliably link terminal, connector, session, and payment. Include queue capacity, accessibility, communications, and a shared-failure plan.

How many chargers should one payment kiosk serve?

There is no fixed ratio. Size capacity using peak arrivals, transaction time, retries, walking distance, expansion, downtime, and tolerable failure impact. High-throughput hubs may need two or more terminals.

Is a shared terminal permitted under AFIR?

Yes. AFIR Article 5 permits one terminal or device to serve several points within the same recharging pool. Applicable ad hoc payment, pricing, accessibility, national, and deployment-date requirements remain.

Can a shared terminal work with chargers from different manufacturers?

Potentially, if the terminal, site controller, CSMS, and each charger have compatible interfaces and consistent identifiers. Require end-to-end testing for every charger type and connector.

Conclusion

An EV charging station with payment terminal access should balance driver simplicity, capacity, accessibility, maintainability, and revenue risk. For a Luxman Energy review, provide the bay layout, charger quantity and power, connector mix, peak arrivals, country, accessibility constraints, CSMS and OCPP, payment provider, network, and expansion plan so an integrated, adjacent, or shared design can be assessed.