← Blog

OCPP vs OCPI: how to plan a charging network integration?

Start with the right technical framework for collaboration by separating the scopes of discovery, live status, sessions and payment.

Editorial image representing the business topic
KEEP IN MIND
  • Showing a network on the map and starting a charge on that network require different responsibilities. Determining which need you will meet in the first discussion makes the technical and commercial scope clear.
  • Prepare the supported protocols and versions, sample data fields, the test environment and the technical owner. State clearly whether the goal is station data sharing, session management or remote commands. On which screen the user will start the action and from whom they will get support are also part of the technical scope.

The starting point is the user's need

Showing a network on the map and starting a charge on that network require different responsibilities. Determining which need you will meet in the first discussion makes the technical and commercial scope clear.

Station discovery, showing current status, session management and payment records should be treated as separate capabilities.

Make the scope of data sharing concrete

Location, station/EVSE/connector ID, power, tariff and timestamps are mapped to a common model. Static station information and frequently changing connector status may have different update patterns.

It is considered in direct API and OCPI operator/mobility connections. OCPP, on the other hand, is the communication layer between the device and the charging management system.

Verify the transaction and the physical outcome separately

A start command being accepted does not mean energy is flowing. Authorization, command, physical session and financial outcome should be tracked as separate states.

Retries, connection interruptions and cancellations are part of the test scenarios. The same transaction not generating a charge again matters as much for record consistency as for user experience.

What information should you bring to the first meeting?

Prepare the supported protocols and versions, sample data fields, the test environment and the technical owner. State clearly whether the goal is station data sharing, session management or remote commands. On which screen the user will start the action and from whom they will get support are also part of the technical scope.

In pilot acceptance, do not test only the successful transaction. Define together how situations such as a connection outage, a repeated message, wrong time information, a tariff change and an interrupted session will be handled. Beyond technical success, operations must be able to manage these situations.

Define the operations and support model together

The data owner, who is responsible for collection, the invoice flow and user support are defined from the start. A CDR record and a financial document do not serve the same purpose; reconciliation bridges the two.

When starting an integration discussion with eBattery, you can share your organization, the countries you operate in, your API/protocol structure and your target scope. A technical documentation link makes the initial assessment more concrete.

Sources and further reading

Last editorial check: 11.10.2026. The source news report and eBattery's assessment are presented under separate headings in the text.

Explore the topic on eBattery →

Search eBattery

Search for a feature, guide or topic.

Starting pointsFinding a charging station →Sample RWA project →Guides and news →