What is OCPP?

OCPP stands for Open Charge Point Protocol. It is the open communication protocol used between an EV charging station and its management software, usually called a CSMS or CPMS.

 

An OCPP charger can report its status, send session and meter data, receive settings and respond to remote commands. Because the protocol is not tied to one manufacturer, operators can combine charging hardware and management software from different suppliers. OCPP is maintained by the Open Charge Alliance. The charger and the CSMS exchange JSON messages over a WebSocket connection. OCPP 1.6 also exists in an older SOAP version.

How does OCPP work?

When a charging station connects, it identifies itself to the management system and reports whether it is available, charging or experiencing a fault. During a session it sends transaction and energy data. The management system can return instructions, such as authorising a driver, changing a power limit, restarting the charger or installing new firmware.

The main message types are:

  • Boot notification: the charger identifies itself when it connects.
  • Status notification: the charger reports if a connector is available, charging or faulted.
  • Authorisation: the CSMS checks the driver’s RFID card or app token.
  • Transactions and meter values: the charger reports the start, the stop and the energy of each session.
  • Remote commands: the CSMS can start or stop a session, change a power limit or restart the charger.
  • Firmware and diagnostics: the CSMS can install new firmware and collect log files.

OCPP defines the messages exchanged. The CSMS or CPMS decides what to do with them, including monitoring, pricing, customer access and reporting.

OCPP 1.6, 2.0.1 and 2.1

The Open Charge Alliance currently maintains three main versions:

Version Released Main functions Compatibility
OCPP 1.6 2015 Core operations, firmware updates, local authorisation and smart-charging profiles. JSON (OCPP 1.6J) and SOAP versions. Remains widely used
OCPP 2.0.1 2020 Stronger security, improved device management, better transaction handling and support for ISO 15118. Edition 3 of OCPP 2.0.1 became IEC 63584 in 2024. Not directly compatible with OCPP 1.6
OCPP 2.1 2025 Support for ISO 15118-20, bidirectional charging, distributed energy resources and improved smart charging. Builds on OCPP 2.0.1

The newest version is not automatically the right version for every deployment. Operators need matching support in the charger, firmware and management platform, followed by testing of the functions they intend to use.

 

Our comparison of OCPP 1.6, 2.0.1 and 2.1 explains the functional and compatibility differences in more detail.

Close-up of engineering software used in amina EV charger development, showing control logic and firmware programming for reliable charging performance.
OCPP defines the messages exchanged between charging stations and management software.

Why does OCPP matter?

OCPP gives charge point operators more choice. A compatible charger can connect directly to a chosen management platform, making it possible to build a mixed-hardware network or change software provider without automatically replacing the chargers.

 

That flexibility is not automatic. Operators still need access to charger credentials, compatible protocol versions, suitable firmware and a planned migration. An extra manufacturer cloud may also remain a dependency even when OCPP is used.

What does OCPP not guarantee?

“OCPP compatible” does not mean that every charger will perform every function with every CSMS. Implementations can support different versions, profiles and optional features. Our guide to OCPP compliance and certification explains what the terminology and certificates actually prove. Integration testing is still required.

 

OCPP also covers only the charger-to-management-system connection. It does not itself provide payment processing, invoices or a driver app. Communication between the vehicle and charger is handled by standards such as ISO 15118.

How does amina use OCPP?

amina C and C2 use local OCPP 1.6J to connect directly to charge point management systems. Their current hardware is also prepared for OCPP 2.0.1. Availability of a particular function still depends on the charger generation, firmware and chosen CPMS. amina S2 is also AFIR ready and ISO 15118-20 compliant.

OCPP questions

What does OCPP stand for?

OCPP stands for Open Charge Point Protocol. The Open Charge Alliance maintains it.

Which EV chargers are OCPP compatible?

Check three things: the OCPP version the charger supports (1.6J, 2.0.1 or 2.1), whether it has an Open Charge Alliance certificate for that version, and whether it is tested with the CSMS you want to use. amina C and C2 use OCPP 1.6J. Our guide to OCPP compliance and certification explains what a certificate proves.

Can any OCPP charger connect to any CPMS?

Not automatically. Both sides need compatible versions and functions, and the exact combination should be tested.

Is OCPP free?

The specification can be downloaded free of charge. Development, testing and certification still involve costs.

Does a private home charger need OCPP?

Not necessarily. OCPP matters when a charger needs central management, remote operation or integration with a chosen backend.

Sources

  • Open Charge Alliance, OCPP versions and release years (read 12 November 2026): openchargealliance.org
  • IEC 63584, the IEC standard based on OCPP 2.0.1 edition 3 (2024)