How to choose a backend system for public EV charging points

Choosing the right backend system for public EV charging points is critical for keeping chargers online, making sites profitable, and delivering a smooth driver experience. The backend effectively becomes your command centre: it connects chargers, apps, payments, and analytics into one operational layer. This guide walks through the key requirements to consider before you commit.

1. Mandatory technical requirements (future-proofing first)

Before looking at dashboards or apps, make sure the technical foundations are sound. If these are missing, everything else becomes harder and more expensive later.

OCPP compliance (1.6J or 2.0.1)

Your backend should support the Open Charge Point Protocol (OCPP) as a baseline. This keeps you hardware-agnostic, so you can mix charger brands, change suppliers, and still use a single backend. Without OCPP, every charger change becomes a bespoke project and you risk long-term vendor lock-in.

Cloud-based architecture

Public charging needs 24/7 visibility and control. A cloud-based backend allows remote monitoring, diagnostics, and over-the-air firmware updates without rolling trucks for every issue. This is essential for keeping uptime high and operating costs under control.

Scalability by design

Even if you start with a handful of chargers, your system should comfortably handle growth to dozens or hundreds of points across multiple sites. Ask vendors how performance and licensing scale: do you hit limits on API calls, number of connectors, or reporting once you reach a certain size?

2. Core functional features for public charging

Public sites come with specific demands: unpredictable usage, diverse vehicle types, and strict expectations around reliability and payment.

Dynamic Load Management (DLM)

When multiple vehicles are charging at once, unmanaged load can push a site over its electrical capacity or trigger demand penalties. The backend should support DLM, allocating power intelligently between chargers based on real-time conditions and priority rules. This protects your infrastructure and lowers energy costs.

Flexible payment and billing

Public users expect payment to “just work.” Your backend should support:

• Multiple payment methods (cards, app, QR, possibly contactless terminals)

• Different pricing models (per kWh, per minute, per session, and idle fees)

• Tax and invoice handling appropriate for your jurisdiction and customer types

Avoid systems that hard-code one payment method or pricing model because you’ll outgrow them quickly.

Roaming capabilities (OCPI or equivalent)

To maximise utilisation, your chargers should be discoverable and usable by drivers from other networks. Support for protocols such as OCPI enables roaming: your chargers appear in multiple apps and platforms, while the backend handles authorisation, tariff exchange, and settlement in the background. This can significantly increase revenue without extra marketing.

Real-time monitoring and remote diagnostics

You should be able to see, at a glance, whether each connector is available, in use, reserved, or faulted. At a minimum, look for:

• Live status per connector

• Event logs and error codes that are understandable

• Remote commands (restart charger, reset connector, change configuration)

This turns support from reactive firefighting into structured operations.

3. User experience for both drivers and operators

A backend needs to be a technical system that shapes how drivers and your own team interact with the network. If you want your public network to build your brand, the backend should support being able to apply your logo, colours, and naming helps build recognition and trust, especially for sites like malls, car parks, or branded locations.

Reliable, usable driver app or integration

Drivers typically discover chargers via an app or map layer. Whether the backend includes its own app or integrates with EMSPs, the experience should be:

• Simple to find the right charger

• Clear on pricing and availability

• Fast to start and pay for a session

💡Tip: Ask to see the end-user flow on a real device, not just screenshots.

Accurate data and reporting for your team

On the operator side, your backend must provide clear reporting on:

• Uptime and session success rate

• Utilisation (sessions per connector per day, kWh delivered)

• Revenue by site, tariff, or customer segment

This is how you judge whether a site is performing, justify expansion, or make changes to pricing and layout.

4. Security and compliance

Public charging touches payments, user data, and sometimes corporate networks. Security can’t be an afterthought.

Information security and data protection

Look for alignment with recognised security frameworks (e.g. ISO 27001) and data protection practices in line with your regulatory landscape (GDPR, PDPA, etc.). This includes secure data storage, role-based access controls, and clear incident-handling processes.

Support for Plug & Charge (ISO 15118) where relevant

While still emerging, ISO 15118 (Plug & Charge) allows vehicles and chargers to authenticate automatically when plugged in. If your market or vehicle mix is moving in this direction, it’s worth choosing a backend that has a roadmap or existing support, so you’re not caught unprepared.

5. Evaluation checklist for backend vendors

When you speak with vendors, use questions that reveal how the system behaves in the real world. Here are some questions you should ask:

Hardware and protocol flexibility	Can I onboard chargers from multiple manufacturers on the same platform without custom development? Which charger models have you already integrated, and can you share references?
Operations and monitoring	Do you provide automatic, 24/7 monitoring and alerting for charger faults? What can be resolved remotely versus requiring a site visit?
Payments and customer support	How do you handle failed payments, refunds, and disputes in practice? Who provides first-line user support: you, us, or a third party?
Commercial clarity	Is your pricing model transparent (e.g., per connector, per site, per kWh processed)? Are there any additional fees for roaming, new integrations, or premium support?

You can also ask about their involvement in industry bodies and working groups. Vendors actively engaged with organisations such as the Open Charge Alliance tend to stay closer to evolving standards and best practices.

A backend for public EV charging is more than a piece of software; it’s the operational heart of your network. The right system will:

• Keep chargers online and traceable

• Make payments simple for drivers and clean for your finance team

• Allow you to expand hardware, partners, and services without starting over

If you focus on open standards, clear operational capabilities, robust reporting, and a transparent commercial model, you’ll be in a strong position to grow a reliable public charging network.

At Eigen Digital, we build services that works for you. If you are ready to offer your customers the best EV charging services, reach out for a demo!