If you are planning to purchase EV chargers, whether for personal use or commercial deployment, you need to pay attention to the OCPP version listed in the specifications; This directly affects whether your chargers can connect to a CSMS(Charging Station Management System), qualify for public EV charging tenders, or even meet government subsidy requirements.
OCPP is a communication protocol that connects a charge point with a Charging Station Management System . It helps you better manage your EV chargers. Learn more about OCPP EV charger.
OCPP 1.6 provides core functions such as remote start/stop charging, status monitoring, meter data upload, fault alerts, and smart charging.
It has two branches: OCPP 1.6J (JSON, mainstream) and OCPP 1.6S (SOAP, a transitional branch that is now rarely used). These represent different transport protocols and data formats.
Thanks to its lightweight implementation cost, OCPP 1.6 still occupies a major share of the market.
However, with large-scale deployment of public charging infrastructure, requirements for functionality, security, authentication, and compliance are increasing. OCPP 1.6j is gradually becoming insufficient.
OCPP 2.0.1 was released in 2020 and is the first widely deployed version of the OCPP 2.x series. It is the mainstream standard for modern public charging station.
It introduces mandatory TLS encryption, X.509 certificate-based mutual authentication, signed firmware, a hierarchical device model (charging station → EVSE → connector), and a unified TransactionEvent message.
Most importantly, it supports ISO 15118-2, also known as Plug & Charge — the vehicle is plugged in, and authentication and payment are completed automatically, which is very convenient.
However, deploying OCPP 2.0.1 requires higher-spec hardware and a completely new architecture, so the cost of OCPP 2.0.1 chargers is higher than OCPP 1.6.
In 2024, OCPP 2.0.1 became the IEC 63584 international standard. If a tender document or product requirement states “compliant with IEC 63584”, it means the EV charger must use OCPP 2.0.1.
Here we also mention the latest version, OCPP 2.1 (released in January 2025, standardized as IEC 63584-210 in 2026). Compared to 2.0.1, it adds four new functional modules: bidirectional energy transfer (V2X), distributed energy dispatch based on IEEE 2030.5, battery swapping support, and standardized instant payment (credit/debit card terminals, dynamic QR codes, prepaid cards).
This version is still at the early pilot and technical verification stage, so we will not go deeper here.
| Item | OCPP 1.6J | OCPP 2.0.1 |
|---|---|---|
| Release status | Mature and stable (2015) | Current mainstream for new deployments (2019/2020) |
| Standard body | Open Charge Alliance | Open Charge Alliance |
| Communication | WebSocket / JSON | WebSocket / JSON |
| Protocol architecture | Single device model | EVSE / connector hierarchical model |
| Security | Optional TLS + basic authentication | TLS + X.509 certificate system |
| Smart charging | Basic charging control | Standardized charging profiles |
| Transaction model | Start/Stop + MeterValues | Event-driven TransactionEvent |
| Device model | Simple structure | Standardized component model |
| ISO 15118 | Not supported | Supports ISO 15118-2 (Plug & Charge) |
| V2G capability | Not supported | Limited support |
| Backward compatibility | — | Not compatible with 1.6 |
| CSMS support status | Legacy systems | Mainstream new deployments |
In OCPP 1.6, security measures are optional. You can enable TLS and authentication, but most OCPP deployments did not implement them. Chargers simply trusted all devices on the local network, because the main focus at the time was interoperability first — enabling EV chargers to quickly connect to backend systems.
OCPP 2.0.1 makes security mandatory. Every connection uses TLS encryption. Chargers and CSMS authenticate each other using X.509 certificates. Firmware must be signed — any modified code will not be executed by the charger.
This is the version that convinced regulators that OCPP can be used for public infrastructure.
For B2B buyers, this is essentially not a discussion point anymore. If a tender requires “IEC 63584 compliance”, OCPP 1.6 is already out of scope. The only question is whether the additional features of OCPP 2.1 are useful for your use case.
OCPP 1.6 is essentially a closed-loop authorization system. Fleet members or users subscribed to a platform can access charging via RFID cards or apps; others cannot.
Some vendor-specific solutions can implement Plug & Charge, but they cannot identify vehicles and handle payment in a standardized way.
OCPP 2.0.1 adds full Plug & Charge per ISO 15118-2, enabling automatic authentication and payment. This significantly improves user experience. However, it still requires a contractual relationship between the driver and the operator.
OCPP 1.6 and any 2.x versions are not compatible. Upgrading is very difficult. The device model and security architecture are completely different. A full upgrade may involve replacing the mainboard and rewriting firmware architecture.
There are also temporary gateway-based solutions to connect OCPP 1.6 devices into 2.0.1 systems, but these are not full upgrades
Is OCPP 2.0.1 backward compatible with OCPP 1.6?
No. OCPP 1.6 and all 2.x versions use completely different device models, security architectures, and message formats. Chargers or CSMS systems that support both are essentially running two independent protocol stacks at the same time.
Are you looking for EV charging hardware that supports OCPP 1.6 / 2.0.1 and IEC compliance certification?
We provide matching pre-certified solutions based on your target market. Contact us with your project requirements, and we will propose a suitable solution.
Xinya Dongfang Electricity Technology Co., Ltd.
