OCPP 1.6 vs OCPP 2.0.1: Which Version Suits You?

May 29,2026 Blog
a man using XYDF OCPP EV CHARGER

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.

Short Answer

  • OCPP 1.6 is a practical choice for cost-sensitive projects with no immediate upgrade needs.
  • OCPP 2.0.1 is better suited for large-scale public charging projects that require stronger security, smart charging, and future expansion.
  • Always confirm the final protocol version with your EV charger supplier and CMS provider.

About OCPP Protocol

OCPP is a communication protocol that connects EV charger with a Charging Station Management System(CSMS) . It helps you better manage your EV chargers. Read the OCPP Protocol Guide.

What’s the Different between OCPP 1.6 and OCPP 2.0.1?

OCPP 1.6 is still widely used in many EV charging projects and is usually enough for basic charging, monitoring, and payment functions. OCPP 2.0.1 is a newer version designed for more advanced charging networks, with better security, improved device management, smarter charging control, and stronger support for ISO 15118. OCPP 2.0.1 usually costs more to implement than OCPP 1.6 from a manufacturer’s perspective, mainly because it requires more complex firmware development, stronger security design, and more compatibility testing. For cost-sensitive projects with basic charging needs, OCPP 1.6 may still be enough.

ItemOCPP 1.6JOCPP 2.0.1
Release statusMature and stable (2015)Current mainstream for new deployments (2019/2020)
Standard bodyOpen Charge AllianceOpen Charge Alliance
CommunicationWebSocket / JSONWebSocket / JSON
Protocol architectureSingle device modelEVSE / connector hierarchical model
SecurityOptional TLS + basic authenticationTLS + X.509 certificate system
Smart chargingBasic charging controlStandardized charging profiles
Transaction modelStart/Stop + MeterValuesEvent-driven TransactionEvent
Device modelSimple structureStandardized component model
ISO 15118Not supportedSupports ISO 15118-2 (Plug & Charge)
V2G capabilityNot supportedLimited support
Backward compatibilityNot compatible with 1.6
CSMS support statusLegacy systemsMainstream new deployments

Security architecture of OCPP

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.

Who can plug and charge?

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.

Key tips

  • The OCPP version of EV charger must match the protocol supported by the CSMS. For example, OCPP 1.6 chargers cannot connect to a CSMS that only supports 2.0.1.
  • If a system requires IEC 63584 compliance, it means OCPP 2.0.1 is required.
  • Confirm with your EV charger supplier or CMS provider is a good idea.

FAQ

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.

Can existing OCPP 1.6 chargers be upgraded to OCPP 2.0.1?

OCPP 1.6 and any 2.x versions are not compatible, so OCPP 1.6 EV chargers are not always directly upgradeable to OCPP 2.0.1. In many cases, the upgrade depends on the charger hardware, firmware, and CSMS compatibility.

Final recommendation

  • If it is for personal use and you only need charging, OCPP is not necessary.
  • If you are cost-sensitive and working with existing projects, OCPP 1.6 is acceptable.
  • If you are building public charging stations or commercial charging projects with subsidies, OCPP 2.0.1 is recommended. If hardware supports upgrade to OCPP 2.1, it is a plus.

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.

+86 133 3697 0557
service@xinya-ee.com