EV Charging Regulations in 2026: What CPOs Need to Implement, Not Just Know
There is no shortage of articles listing EV charging regulations. Most cover what each regulation says. Few cover what each regulation requires you to build. That distinction matters, because every major regulation now active or imminent in the US, EU, and UK ultimately translates into a protocol implementation requirement. Knowing that AFIR mandates data transparency is useful. Knowing that AFIR data transparency requires OCPP 2.0.1 or later for the granularity of pricing, availability, and connector status data the regulation demands — that is actionable. This article maps the EV charging regulations landscape across three jurisdictions and connects each regulation to the specific protocol work your platform needs.
The Regulatory Acceleration: Three Jurisdictions, Three Compliance Clocks
If you operate charging infrastructure in more than one market — or plan to — you are now managing three simultaneous compliance timelines. The US, EU, and UK each have distinct regulatory frameworks, each with different deadlines, and each requiring different protocol capabilities.
| Jurisdiction | Regulation | Key Deadline | What It Requires |
|---|---|---|---|
| US (Federal) | NEVI (23 CFR 680) | Ongoing (budget reduced — $879M clawed back FY2026) | 4+ DCFC ports per station, 150 kW minimum, CCS Type 1, uptime reporting, payment interoperability |
| US (Federal) | FERC Order 2222 | State-by-state (2024-2027) | DER aggregation participation in wholesale markets; requires grid-facing protocol (OpenADR or IEEE 2030.5) |
| US (California) | Rule 21 | Active now | IEEE 2030.5/CSIP mandatory for DER grid interconnection, including V2G-capable chargers |
| EU | AFIR (2023/1804) | 2025-2027 (phased) | Real-time data transparency (pricing, availability, connector status via open API); ISO 15118 for V2G from 2026; payment card readers by 2027 |
| EU | NC Demand Response | National enforcement ~2027 | Harmonized DR participation for connected assets including EV chargers; requires OpenADR or EEBUS interface |
| UK | SCPR 2021 (+ amendments) | Annual reporting from Jan 2026 | Smart charging, default off-peak, 99% reliability (rapid chargers), OCPI data sharing, 24/7 helpline |
The timelines overlap in ways that compound the engineering burden. A CPO deploying across the US and EU in 2026 must simultaneously satisfy NEVI’s interoperability and uptime requirements, AFIR’s data transparency mandates, and — if participating in grid services — FERC 2222’s DER participation rules. Each regulation adds a protocol layer. Together, they create a multi-protocol compliance challenge that cannot be addressed one regulation at a time.
US Regulations: From NEVI to FERC 2222
The US regulatory landscape combines federal baseline standards with an increasingly complex state-level patchwork.
NEVI (National Electric Vehicle Infrastructure) sets the federal floor. Originally authorized at $5 billion but materially reduced by congressional cuts — $879 million clawed back in FY2026 alone — the program requires charging stations along designated Alternative Fuel Corridors to meet minimum standards: at least four network-connected DC fast charging (DCFC) ports, each capable of 150 kW continuous power delivery, CCS Type 1 connectors, and uptime reporting. NEVI’s interoperability requirements effectively mandate OCPP connectivity — without it, the uptime reporting and network management capabilities the program requires are impractical to deliver.
FERC Order 2222 opens a different dimension entirely. By allowing DER aggregations (including EV fleets with bidirectional capability) to participate in wholesale energy markets, it creates a revenue opportunity — but one that requires grid-facing protocol compliance. Participation through ISO/RTO markets like PJM, CAISO, and NYISO means implementing OpenADR or IEEE 2030.5 for demand response signaling and DER coordination.
California Rule 21 goes further still, mandating IEEE 2030.5 with the Common Smart Inverter Profile (CSIP) for any DER seeking grid interconnection — including V2G-capable chargers. Hawaii’s Rule 14H and Utah’s interconnection standards follow the same pattern. For CPOs with multi-state operations, the challenge is not just knowing which regulation applies where, but having a protocol stack flexible enough to satisfy all of them.
EU Regulations: AFIR Data Transparency and the Network Code
In the EU, AFIR (Alternative Fuels Infrastructure Regulation, 2023/1804) is the anchor regulation. Its Article 5 data transparency requirements mandate that charging operators provide real-time data on pricing, availability, connector status, and energy delivered — accessible through an open API. The data granularity AFIR demands effectively requires OCPP 2.0.1 or later; the richer transaction model, metering capabilities, and real-time status reporting of 2.0.1 are what make AFIR compliance technically feasible without building custom data collection layers on top of a protocol that was not designed for it.
AFIR also mandates ISO 15118 support for V2G-capable public charging infrastructure from 2026, with full Plug & Charge compliance for newly deployed public points by 2027. Payment card readers on all fast chargers (50 kW and above) are required by 2027.
Beyond AFIR, the EU Network Code on Demand Response — proposed by ACER to the European Commission in March 2025 — will require harmonized demand response participation for connected assets, including EV chargers. National enforcement is expected by 2027. For CPOs, this means adding a grid-facing DR interface: OpenADR or EEBUS, depending on the member state. The regulation has not yet been finalized, but the protocol direction is clear.
National implementation variations add complexity. Germany, France, the Netherlands, and the Nordic countries are each at different stages of AFIR transposition, creating a patchwork of compliance deadlines within the EU itself. A CPO operating across multiple member states must track not one AFIR timeline but several.
UK Regulations: Smart Charge Point and Grid Flexibility
The UK’s Smart Charge Point Regulations (SCPR), enacted in 2021 and amended through 2025, mandate capabilities that most pre-2021 chargers were not designed for: default off-peak charging, demand-side response capability, and interoperability with smart energy tariffs.
Annual reporting requirements took effect in January 2026, requiring CPOs to report total charge points, network reliability, and per-point operational status. Rapid charging networks (above 50 kW) must maintain 99% reliability. Data sharing must be supported via the Open Charge Point Interface (OCPI) protocol.
The grid flexibility dimension is growing. The UK government’s framework for smart and flexible energy systems positions EV chargers as grid assets — participants in flexibility markets, not just electricity consumers. That participation requires OCPP for charger management, OSCP or OpenADR for grid-facing DR signaling, and increasingly, IEEE 2030.5 for DER coordination as the UK’s interconnection standards evolve.
For CPOs already operating in the UK, the interoperability mandate is not optional — it is a license to operate. The compliance window for 2025-2026 amendments is narrow, and the protocol requirements are specific.
Mapping Regulations to Protocol Implementations
When you strip away the legal language, every regulation in the table above reduces to one or more protocol implementation requirements. “Data transparency” means OCPP 2.0.1 transaction data. “Grid flexibility” means OpenADR or IEEE 2030.5 signaling. “Interoperability” means OCPI roaming and OCPP charger connectivity. “V2G-readiness” means ISO 15118-20 plus IEEE 2030.5/CSIP.
| Regulation | Required Protocol(s) | Implementation Scope |
|---|---|---|
| NEVI | OCPP 1.6+ (effectively required for network management and uptime reporting) | Charger-to-backend connectivity, session metering, uptime monitoring, payment system integration |
| AFIR | OCPP 2.0.1+ (data granularity); ISO 15118 (V2G from 2026, Plug & Charge by 2027) | Real-time data API, transaction-level pricing/metering, vehicle-to-charger authentication |
| FERC 2222 | OpenADR or IEEE 2030.5 (grid-facing DR signaling) | DER aggregation interface, demand response participation, wholesale market bidding |
| Rule 21 | IEEE 2030.5/CSIP (mandatory for DER interconnection) | Grid interconnection approval, real-time DER monitoring and control, V2G dispatch |
| UK SCPR | OCPP (charger management); OCPI (data sharing); OSCP/OpenADR (grid flexibility) | Smart charging control, reliability reporting, DR readiness, cross-network data interoperability |
| EU NC DR | OpenADR or EEBUS (varies by member state) | Demand response interface, flexibility market participation, load curtailment signaling |
The compounding effect is the critical insight. No single regulation requires the full protocol stack. But a CPO operating across the US, EU, and UK — or even across multiple US states — faces a cumulative set of requirements that spans OCPP, OpenADR, IEEE 2030.5, OCPI, and ISO 15118. Each new regulation does not replace the previous ones; it adds another protocol layer to the stack.
This is why treating regulatory compliance as a checklist fails at scale. A checklist approach implements each regulation’s protocol requirements as a standalone project. A platform architecture approach implements them as modules on a shared foundation — so that the next regulation does not trigger another standalone project but plugs into the existing infrastructure.
Implementation, Not Just Awareness, Separates Leaders from Laggards
The regulatory landscape for EV charging is no longer a watch-list. It is a build-list. Every regulation discussed here — NEVI, AFIR, UK SCPR, FERC 2222, Rule 21, EU NC DR — has moved past the consultation stage and into enforcement or active implementation. The gap between CPOs that lead and those that scramble is not knowledge of these regulations. It is the protocol architecture that translates awareness into compliance.
The CPOs that are best positioned today are the ones that made the architecture decision early: a modular, multi-protocol platform where OCPP, OpenADR, IEEE 2030.5, and OCPI coexist on shared infrastructure. For everyone else, the time to make that decision is now — not when the next compliance deadline arrives.

Frequently Asked Questions
The three major regulatory frameworks are: NEVI (US) — federal minimum standards for EV charging infrastructure including interoperability, uptime, and payment requirements; AFIR (EU, Regulation 2023/1804) — data transparency, payment accessibility, ISO 15118 support, and infrastructure deployment mandates across EU member states; and UK SCPR (Smart Charge Point Regulations) — smart charging capabilities, demand-side response readiness, 99% reliability for rapid chargers, and OCPI data sharing. Additionally, FERC Order 2222 (US) enables EV participation in wholesale energy markets as DERs, and California Rule 21 mandates IEEE 2030.5/CSIP for grid interconnection.
NEVI compliance means meeting the minimum standards set by the US National Electric Vehicle Infrastructure program (23 CFR Part 680) for federally funded charging stations. Key requirements include: at least four networked DCFC ports per station, 150 kW minimum continuous power per port, CCS Type 1 connectors, uptime reporting, payment interoperability (contactless payment without subscription), and network connectivity for remote monitoring and management. In practice, NEVI compliance requires OCPP-connected chargers capable of reporting the operational and metering data the program mandates.
AFIR and NEVI share a goal — expanding reliable, interoperable EV charging infrastructure — but differ in scope and specifics. NEVI is a US federal funding program focused on corridor charging, with requirements around minimum power (150 kW), port count, and payment interoperability. AFIR is an EU regulation that covers all public charging infrastructure, with broader mandates including real-time data transparency (pricing, availability, connector status via open API), ISO 15118 support for V2G-capable chargers, and payment card readers on all fast chargers by 2027. AFIR also mandates infrastructure deployment targets along the TEN-T network. The protocol implications differ: NEVI effectively requires OCPP for network management; AFIR additionally requires OCPP 2.0.1+ for data granularity and ISO 15118 for V2G readiness.