OCPP certification
How the Open Charge Alliance certifies chargers and backends: the certification profiles of OCPP 1.6 and 2.0.1, the OCTT test tool, the test labs, OCPP 2.1 as IEC 63584-210, what a certificate says and what it does not, and how the analyzer reads OCPP logs.
The programme
The Open Charge Alliance (OCA), owner of OCPP, runs an independent certification programme. Its OCPP 1.6 programme has run since 2019, and a programme for OCPP 2.0.1 followed. In 2025 OCA launched renewed programmes for both versions, which it says reduce the effort of certification and make a certificate easier to verify. A product is certified per profile: the Core profile is mandatory and the others are optional.
| Version | Profiles |
|---|---|
| OCPP 1.6 | Core (which now includes Firmware Management and Security Profile 2), with optional profiles such as Smart Charging, Reservation, Local Authorization List Management, Remote Trigger and Security |
| OCPP 2.0.1 | Core and Advanced Security (available since June 2023); Local Authorization List Management, Smart Charging, Advanced Device Management, Reservation, Advanced User Interface and ISO 15118 Support (full certification available since April 2025) |
The OCTT test tool
- OCTT (OCPP Compliance Test Tool) plays the other side of the system under test: a backend for a charger, or a charger for a backend, and runs the test cases of the specification against it.
- It is a cloud service hosted by OCA, sold by subscription for internal use; the current generation launched in October 2022 and holds the test cases of OCPP 1.6 and 2.0.1.
- OCA releases a new OCTT version about every two months and validates each release against several systems under test. It is adding APIs for running test cases from CI pipelines, and coverage for OCPP 2.1.
How in house OCTT runs count toward a certificate under the renewed 2025 programme, and what the lab does itself, was not confirmed for this page. Read the current OCA certification procedure.
Test labs
OCA lists its certification test laboratories on its site. At the time of research these included DEKRA (Arnhem in the Netherlands and sites in Virginia and California in the US), DNV (Arnhem), the Korea Smart Grid Association, the Korea Testing Certification Institute and the Korea Testing Laboratory.
The list of OCA labs changes; check the testing laboratories page of OCA before planning a certification.
OCPP 2.1 and IEC 63584
- OCPP 2.1 was released in January 2025. It adds support for ISO 15118-20, a functional block for bidirectional charging, a functional block for DER control, battery swapping and new authorization options.
- It extends OCPP 2.0.1: its JSON schemas are those of 2.0.1 with added optional fields, so a 2.0.1 implementation remains the base.
- IEC accepted OCPP 2.0.1 edition 3 as IEC 63584 in late 2024, and published OCPP 2.1 edition 1 as IEC 63584-210:2025.
A certification programme for OCPP 2.1 was not confirmed in the sources read (September 2026). Check the OCA certification page.
What a certificate says, and what it does not
- It says that the product passed the test cases of the listed profiles, for the listed OCPP version, at a certification lab. A buyer should read the profiles, not only the version: "OCPP 2.0.1 certified" with Core alone says nothing about smart charging.
- It is about the messages between charger and backend. Electrical safety, the charger to car link (ISO 15118 or DIN 70121 conformance), billing metrology and field reliability are tested elsewhere: Safety and type approval of chargers and cars, Conformance testing: ISO 15118-4, -5 and Testivals, Billing and measurement testing, Reliability of public charging: what field data says.
- It does not pair the product with every backend or charger in the market. That is what plugfests are for (Interoperability test events).
In this tool
An OCPP-J log from the charger (a timestamped frame per line, or JSON Lines) of OCPP 1.6 or 2.0.1 is recognised by its content and placed in the session it belongs to. The OCPP tab shows the connector status, the transactions with their metered energy, backend errors and the slowest answer, and the backend view against the cable, for example the transaction start after PowerDeliveryRes. OCPP never changes a check or the verdict: it explains what the backend saw. The demo ocpp-rejected shows a backend that answers an authorization with Invalid while the charger keeps the car waiting; see Worked example: the backend rejects the card, OCPP: the charger's link to its backend and OCPP 2.0.1 and ISO 15118: the backend behind the cable.
Sources
- Open Charge Alliance: OCPP certification programme
- Open Charge Alliance: Certification OCPP 2.0.1
- Open Charge Alliance: OCPP 2.0.1 full certification is now available
- Open Charge Alliance: New certification program OCPP 1.6
- Open Charge Alliance: Renewed OCPP certification program launched
- Open Charge Alliance: Annual Report 2025
- Open Charge Alliance: Certification procedure
- Open Charge Alliance: Test tool (OCTT)
- Open Charge Alliance: Testing laboratories
- DEKRA: OCPP certification
- Open Charge Alliance: OCPP 2.1 accepted by IEC as IEC 63584-210
- Open Charge Alliance: OCPP 2.1 edition 1 published by IEC as IEC 63584-210:2025
- IEC 63584-210:2025, SCC catalogue entry
- SPEC.md of this tool, FR-TOOL-06, the OCPP tab