EV Basics

What Is OCPP? The Open Protocol Behind EV Charging Networks

Published on 2026-10-21

What Is OCPP and Why Does It Matter to CPOs?

OCPP is the open communication protocol linking a charging station with the CSMS (charging station management system) that operates it. Over this connection, an operator can boot and authorize chargers, start and stop sessions remotely, collect transaction data, apply smart charging limits, and receive status and alerts.
The specification is developed and maintained by the Open Charge Alliance, which publishes it openly so any manufacturer or software vendor can implement it. This lets a CPO choose chargers and the CSMS from different vendors, replace either side independently, and expand a network on mixed hardware under one platform.
The workload grows with the network: the IEA counted over 7 million public charging points worldwide in 2025, and average power per point rose from just above 40 kW to nearly 50 kW in a year, according to the Global EV Outlook 2026. More chargers and higher power mean more configuration, load management and monitoring work resting on the charger-to-platform link.
Three procurement questions drive the rest of this article: which OCPP versions does the equipment support, what does certification cover, and has the charger and CSMS combination been tested for your project’s functions?

How OCPP connects EV chargers to a CSMS

OCPP 1.6 vs. 2.0.1 vs. 2.1: What Has Changed?

OCPP 1.6
OCPP 2.0.1
OCPP 2.1
First released
2015
2020
January 2025
Standardization
Widely deployed industry standard
Within the IEC 63584 series
Edition 1 = IEC 63584-210:2025
Data model
Simpler, transaction-oriented
New Device Model, richer status and transactions
Extends the 2.0.1 model
Security
Basic in the core, extended by add-on specifications
Security profiles built in, including TLS
Extends 2.0.1 security
Smart Charging
Supported
Supported, richer profiles including stacking
More flexible model
V2G and DER
Not a design target
Limited, no native ISO 15118-20 bidirectional flow
Bidirectional via ISO 15118-20, DER control, battery swap
Compatibility
Installed-base baseline
Not compatible with 1.6
Compatible with 2.0.1, not with 1.6
Evolution and compatibility of OCPP versions 1.6, 2.0.1, and 2.1.

OCPP 1.6: The Installed Base

OCPP 1.6 has been on the market since 2015 and remains the most widely deployed version. Many networks, CSMS contracts and charger fleets still run on it, and replacing hardware or software that already works is rarely a decision made for the protocol alone.
One detail matters: OCPP 1.6 exists in more than one communication binding. Chargers communicate via SOAP or via JSON over WebSockets depending on the implementation, and vendors commonly call the JSON implementation OCPP 1.6J. The bindings are not interchangeable without a gateway, so confirm which binding a charger and a CSMS actually speak, not just the version numbers.

OCPP 2.0.1: Security and Device Management

Released in 2020, OCPP 2.0.1 is a new generation rather than an incremental update: a structured Device Model, richer transaction and status handling, and security built into the specification instead of add-ons. OCA certification mirrors this structure. Core certification covers booting, authorization, configuration, transactions, remote control and basic security, with separate optional profiles for Advanced Security (TLS with client authentication), Smart Charging and ISO 15118 support. For a CPO, it is the version against which current certification and most new platform integrations are built.

OCPP 2.1: New Capabilities and Upgrade Considerations

OCPP 2.1 was released by the OCA on 23 January 2025 and published as IEC 63584-210:2025. The confirmed new capabilities are mostly about energy flexibility: bidirectional charging via ISO 15118-20, DER control, a more flexible smart charging and transaction model, new payment options and battery swap support.
For planning, the compatibility boundary matters: 2.1 is backward compatible with 2.0.1 but not with 1.6. Existing 1.6 chargers cannot simply move to 2.1; they depend on vendor firmware or hardware paths, and some will stay on 1.6 for their service life.

Should CPOs Upgrade Now?

No single answer fits every network. Five questions frame the decision:
  1. Do the current chargers and CSMS meet today’s operational needs?
  2. Do you need a 2.1 capability, such as bidirectional charging or DER control, within your planning horizon?
  3. What do certification, integration testing and migration cost across your fleet?
  4. Do specific projects or regulations require particular versions or functions?
  5. Is a staged upgrade, for example new sites first, realistic for your operations?
For most operators the answer is a path, not a switch: keep 1.6 assets running where they work, deploy 2.0.1 as the certification baseline for new hardware, and evaluate 2.1 where its capabilities have a business case.

Does OCPP Compatibility Guarantee Interoperability?

Short answer: no. In vendor conversations, three claims get mixed up:
  • A vendor states that its charger supports OCPP.
  • A product has passed OCA certification for one or more profiles.
  • The charger and your target CSMS have completed project-level integration testing and acceptance.
OCPP compatibility, OCA certification, and project-level integration testing are separate evidence layers.
Each step adds evidence. None of them equals full interoperability on its own. Even with the same protocol version, devices can differ in optional profiles, security configuration and manufacturer-specific behavior, and CSMS products rarely implement identical feature sets.
Before deployment, verify these functions on the actual charger and platform combination:
  • Remote start and stop of sessions.
  • Status reporting and alert delivery.
  • Transaction records and their completeness.
  • Smart Charging behavior, including load management scenarios.
  • Security configuration and ISO 15118 related function scope.
Define test cases, an integration workflow and acceptance criteria before deployment, and treat the results as procurement documentation.
For planning, OCPP compatibility is the foundation for assessing interoperability, but it does not by itself guarantee that every device will work with every platform. Compatibility problems are not everywhere, but verify the functions your project needs.

OCPP Certification: What Does It Prove?

OCA runs an independent certification program for OCPP implementations, tested by independent laboratories; for OCPP 2.0.1 it opened in 2023.
Certification is structured in profiles. Core is mandatory, covering basic charging station functionality: booting, authorization (including cache), configuration, transactions, remote control and basic security. Optional profiles cover Advanced Security (TLS with client authentication), Smart Charging (including stacking) and ISO 15118 support (smart charging and Plug and Charge authorization). Certificates are issued separately for charging stations and for CSMS, with hardware certified in AC and DC categories.
OCA publishes maximum fees for one full test run on its certification page, applicable as of 1 April 2025:
Category
AC Charging Station
DC Charging Station
CSMS
OCA participant, Core
EUR 5,700
EUR 7,100
EUR 3,700
OCA participant, Core + all optional profiles
EUR 10,300
EUR 13,000
EUR 5,600
Non-participant, Core
EUR 9,200
EUR 10,600
EUR 7,200
Non-participant, Core + all optional profiles
EUR 13,800
EUR 16,500
EUR 9,100
Laboratories may reduce fees for partial profile testing, and OCA participants pay less. Confirm current fees before budgeting.
Verification is straightforward: check the certificate in the OCA directory of certified products, confirming the product model, OCPP version, certificate number and certification scope. OCA numbers follow the format OCA.xxxx.xxxx.CS or OCA.xxxx.xxxx.CSMS; for certificates issued since mid-2024, signature validation is also available.
Certification also has limits. It proves that a specific product, in a tested scope, conforms to the tested profiles. It does not guarantee compatibility with every CSMS, and it says nothing about the operational quality of a running network. Certification is strong evidence in vendor evaluation, but a CPO should still verify the specific certificate scope and run integration testing against the target platform.

OCPP vs. OCPI vs. ISO 15118

The terms are often confused; they operate at different layers:
Charger ↔ OCPP ↔ CSMS ↔ OCPI ↔ eMSP / Roaming Hub
  • OCPP connects charging equipment with the CSMS that operates it.
  • OCPI connects platforms with each other, linking eMobility Service Providers (eMSPs) and CPOs directly or via roaming hubs; it is maintained free to use by the EVRoaming Foundation.
  • ISO 15118 is the vehicle-to-charger standard family, covering Plug and Charge, smart charging and, in its second generation (ISO 15118-20), bidirectional use cases.
OCPP
OCPI
ISO 15118
Maintained by
Open Charge Alliance
EVRoaming Foundation
ISO
Connects
Charger with CSMS
CPO platform with eMSP / roaming hub
Vehicle with charger
Primary use
Remote management, transactions, smart charging
Roaming, tariffs, session and charging data
Plug and Charge, smart charging, bidirectional communication
Notes
Versions 1.6, 2.0.1 and 2.1 in the field
Current version 2.3.0; OCPI 3.0 in draft, target around mid 2027; select per deployment needs
Referenced in EU requirements for recharging points in scope
Plug and Charge is a chain rather than a single-protocol feature: automatic authentication and authorization involves the vehicle, charger, certificate infrastructure and backends on both sides, with OCPP, ISO 15118 and the CSMS each handling part of the flow. In OCA certification, ISO 15118 support is its own optional profile, so check it explicitly rather than assuming it.

AFIR and ISO 15118: What European CPOs Need to Check

The EU Alternative Fuels Infrastructure Regulation (AFIR, Regulation (EU) 2023/1804) was amended by Commission Delegated Regulation (EU) 2025/656, signed on 2 April 2025, published in the Official Journal on 18 June 2025 and applicable from 8 January 2026.
The amended Annex II sets ISO 15118 requirements as follows:
  • Publicly accessible AC and DC recharging points installed or renovated from 8 January 2026 must comply at least with EN ISO 15118-1:2019, -2:2016, -3:2016, -4:2019 and -5:2019 (point 2.1.1).
  • Publicly accessible recharging points installed or renovated from 1 January 2027 must comply with EN ISO 15118-20:2022; where they offer automatic authentication and authorization services such as plug and charge, they must comply with both EN ISO 15118-2:2016 and EN ISO 15118-20:2022 (point 2.1.2).
  • Private recharging points installed or renovated from 1 January 2027 must comply with EN IEC 61851-1:2019 for Mode 2 charging, and EN ISO 15118-20:2022 for Mode 3 or Mode 4 charging (point 2.1.3).
Two boundaries matter. First, the requirements apply to equipment installed or renovated from those dates; existing chargers do not become non-compliant overnight, and transitional provisions cover some equipment. Second, they cover ISO 15118, not OCPP: the applicable objects, standard versions and timing are defined in the regulation text itself. OCPP remains an industry-adopted standard for charger-to-platform communication, not an EU legal requirement.
CharIN publishes implementation guidance on ISO 15118 readiness and certificate management. When planning new sites or renewals in Europe, check both the ISO 15118 capabilities the rules require and the OCPP capabilities your operations depend on. Heavy-duty corridors carry separate AFIR requirements. For the standards around connectors and protocols, see our global EV charging standards guide and our CCS1 vs CCS2 comparison.

How to Choose an OCPP-Ready Charging Partner

Use this checklist in vendor conversations; every item is something you can ask for or test:
  1. Which OCPP versions does the equipment support in shipped firmware, not only on datasheets?
  2. Is there an OCA certificate, and what exactly does its scope cover?
  3. Has the charger been integrated with your target CSMS, or can a joint test be scheduled?
  4. How are security features configured, and how are certificates managed over the product lifetime?
  5. What ISO 15118 capabilities are supported, and at which level?
  6. How are Smart Charging and dynamic load management implemented across multiple chargers? See how dynamic load balancing works in practice.
  7. Which remote operations, alerts and diagnostics are available for daily operations?
  8. What integration test and acceptance process is proposed for the project?
  9. What are the costs of expansion, maintenance and future version upgrades?
  10. Who is responsible for support, and where does vendor responsibility end?
We apply the same logic ourselves: Wattecho networked EV charging products support OCPP 1.6J, and our commercial solutions support OCPP 1.6J and 2.0.1 together with ISO 15118, with the exact scope defined per solution. Protocol capability and OCA certification status are separate topics: any certification claim, including ours, should be verified in the OCA directory using the method above. If you are evaluating a platform integration, our team can run a joint test against your target CSMS.
Planning platform integration, a charger fleet or a new site? Request partner pricing from our team. See also our fleet charging solution and DC fast charging portfolio.

Frequently Asked Questions

More general charging questions are answered in our FAQ. The answers below focus on OCPP:
1. What is OCPP in simple terms?
An open protocol that lets an EV charger communicate with the management platform (CSMS) operating it, so chargers and software can come from different vendors.
2. Is OCPP mandatory in the EU?
No. AFIR, as amended by Delegated Regulation (EU) 2025/656, sets ISO 15118 requirements for chargers in scope. OCPP is a widely adopted industry standard, not an EU legal requirement.
3. Is OCPP 2.1 backward compatible?
With OCPP 2.0.1, yes. With OCPP 1.6, no.
4. OCPP 2.0.1 vs. 2.1: do I need to upgrade now?
Only if you need 2.1 capabilities such as bidirectional charging via ISO 15118-20 or DER control, or a project requires them; otherwise 2.0.1 remains the certification baseline for new hardware.
5. What is the difference between OCPP and OCPI?
OCPP connects chargers with a CSMS. OCPI connects platforms with each other for roaming between CPOs and eMSPs. They complement each other.
6. What is Plug and Charge?
Automatic authentication and authorization based on ISO 15118, using certificates across the vehicle, charger, certificate infrastructure and backends. For EU timing, see the AFIR section above.
7. How do I verify OCPP certification?
Look up the product in the OCA certified products directory, then check the model, OCPP version, certificate number (format OCA.xxxx.xxxx.CS or OCA.xxxx.xxxx.CSMS) and certification scope.
8. Does Wattecho support OCPP?
Wattecho networked EV charging products support OCPP 1.6J, and commercial solutions support OCPP 1.6J and 2.0.1 together with ISO 15118, per solution scope. Contact the team for integration details.

Sources

All external sources accessed 20 October 2026.
  1. IEA, Global EV Outlook 2026 (20 May 2026), iea.org/reports/global-ev-outlook-2026/
  2. Open Charge Alliance, Certification OCPP 2.0.1, openchargealliance.org/certificationocpp/certification-ocpp-2-0-1/
  3. Open Charge Alliance, OCPP 2.1 is now available, openchargealliance.org/ocpp-2-1-is-now-available/
  4. EUR-Lex, Commission Delegated Regulation (EU) 2025/656, eur-lex.europa.eu/eli/reg_del/2025/656/oj/eng
  5. Open Charge Alliance, Certified products (dynamic directory), openchargealliance.org/certified-companies/
  6. Open Charge Alliance, Verification of certificates, openchargealliance.org/verification-of-certificates/
  7. EVRoaming Foundation, OCPI and OCPI Downloads, evroaming.org/ocpi/ and evroaming.org/ocpi-downloads/
  8. CharIN, Clarifying ISO 15118 implementation under AFIR, Position Paper V2 (3 August 2026), charin.global/technology/knowledge-base/
Last updated: 20 October 2026.

Inquiry Us

Contact Us

*We respect your privacy. When you submit your contact information, we agree to only contact you in accordance with our Privacy Policy.
Table of contents

We value your privacy

We use cookies to enhance your browsing experience, serve personalised ads or content, and analyse our traffic. By clicking "Accept All", you consent to our use of cookies.