Plug & Charge (PnC) is an automated EV charging authentication and billing method defined by the ISO 15118 international standard. When a PnC-enabled vehicle is connected to a compatible charging station, the vehicle and station exchange encrypted digital certificates through the charging cable — authenticating the driver’s charging contract and authorizing the session to begin, entirely without RFID cards, smartphone apps, or any manual input beyond plugging in.
From the driver’s perspective, Plug & Charge reduces every charging session to a single physical action. From the CPO’s and fleet operator’s perspective, it eliminates authentication friction, enables contract-based billing, and is the technical prerequisite for advanced grid services including Vehicle-to-Grid (V2G) and dynamic smart charging. From a regulatory perspective, it is now mandated for all new publicly accessible AC charging stations in the EU from January 2026 under AFIR’s implementing framework.
This glossary covers the complete technical, commercial, and regulatory landscape of Plug & Charge — written for CPOs, fleet managers, EVSE procurement teams, and OEM integrators.
Related on this site: What Does ISO 15118 Mean? | Joint Tech ISO 15118 Certification | AFIR Glossary | MCS Glossary
Table of Contents
1. What Is Plug & Charge?
Plug & Charge is one of the two authentication methods defined in the ISO 15118 standard series — the other being External Identification Means (EIM), which covers RFID cards, apps, and contactless payment. The formal ISO 15118-1 definition describes PnC as an authentication mechanism where the vehicle automatically performs all steps necessary to start a charging session — identification, authorization, and negotiation of charging parameters — using contract credentials stored in the vehicle itself.
The critical distinction from simpler authentication methods is that PnC uses a cryptographic Public Key Infrastructure (PKI) — a hierarchy of digital certificates — to verify the identity of both the vehicle and the charging station before any energy transfer begins. This mutual authentication prevents unauthorized charging, protects billing integrity, and is the security foundation that makes cross-network roaming and V2G bidirectional services possible at scale.
PnC was introduced in ISO 15118-2 (published 2014) for DC fast charging, extended to AC charging and enhanced with V2G capabilities in ISO 15118-20 (published 2022). Joint Tech’s DC fast chargers support Plug & Charge via both DIN SPEC 70121 and ISO 15118, and Joint Tech has obtained ISO 15118 certification for its charging hardware.
2. How PnC Works: The Session Flow Step by Step
The PnC session flow is entirely automatic from the driver’s perspective but involves a precisely sequenced exchange of messages and certificates between the vehicle, the charging station, and backend systems — all completed within seconds of the cable being connected.
Pre-Condition: Contract Certificate Installation
Before a driver can use PnC at any charging station, a contract certificate must be installed in the vehicle’s secure storage. This certificate is issued by the driver’s eMobility Service Provider (eMSP) and represents the driver’s charging contract — their identity and billing authorization. This installation typically happens once, either:
- At the vehicle’s first charging session after the driver sets up a PnC-capable account with an eMSP
- Over-the-air (OTA) via the vehicle’s cellular connectivity, pushed by the OEM or eMSP
- At a service appointment or via the vehicle’s infotainment system connected to a mobile network
Step-by-Step Session Flow
| Step | What Happens | Who Is Involved |
|---|---|---|
| 1. Physical connection | Driver plugs the charging cable into the vehicle. Low-level pilot signal activates (IEC 61851 PWM). | Driver, vehicle, EVSE |
| 2. Protocol negotiation | Vehicle (EVCC) and charging station (SECC) communicate over the cable’s pilot line using Power Line Communication (PLC) or Ethernet (ISO 15118-20). They negotiate the highest mutually supported protocol version: DIN SPEC 70121 → ISO 15118-2 → ISO 15118-20. | EVCC, SECC |
| 3. TLS handshake | The station presents its EVSE certificate. The vehicle verifies it against the V2G Root CA certificate stored in the vehicle. A TLS encrypted session is established over the communication link — mandatory for PnC (optional for EIM in ISO 15118-2; mandatory mutual TLS in ISO 15118-20). | EVCC, SECC, V2G Root CA (pre-installed) |
| 4. PnC service discovery | Vehicle declares that it wants to use Plug & Charge (rather than EIM). Station confirms PnC is supported. | EVCC, SECC |
| 5. Contract certificate presentation | Vehicle sends its contract certificate (issued by eMSP) to the charging station. | EVCC → SECC |
| 6. Certificate verification | The charging station forwards the contract certificate to its backend CSMS. The CSMS verifies the certificate against the PKI — checking validity, expiry, and revocation status — via the eRoaming hub (e.g., Hubject). Authorization response returned to station. | SECC → CSMS → PKI/eRoaming hub |
| 7. Charging authorization | Station receives authorization. Session is approved. Contactors close, energy transfer begins. All within seconds of plug insertion — no driver action required. | SECC, EVCC |
| 8. Charging session | Vehicle and station exchange smart charging messages (SoC, power setpoints, pricing, grid signals) throughout the session via ISO 15118. | EVCC, SECC, CSMS |
| 9. Session end and billing | Driver unplugs. Session data (energy delivered, duration, cost) recorded by CSMS and forwarded to eMSP for billing against the driver’s contract. No payment terminal interaction required. | CSMS, eMSP |
The entire sequence from plug insertion to charging start typically completes in under 10 seconds on a well-implemented PnC system.
3. Governing Standards: ISO 15118-2, ISO 15118-20, and DIN SPEC 70121
Understanding the three-layer protocol hierarchy is essential for procurement and compliance decisions. Each standard represents a different capability level, and the vehicle and charger automatically negotiate the highest version both support.
| Standard | Published | PnC Support | AC/DC | TLS Security | V2G | Notes |
|---|---|---|---|---|---|---|
| DIN SPEC 70121 | 2012 (rev. 2014) | No | DC only | None | No | Baseline DC communication. No authentication beyond basic power negotiation. Still dominant in deployed DC infrastructure due to first-mover advantage. |
| ISO 15118-2 | 2014 | Yes (optional) | AC + DC | Optional one-way TLS | No | Introduced Plug & Charge and smart charging. TLS optional but mandatory for PnC sessions. Mandated for new EU public AC chargers from January 2026 (AFIR). |
| ISO 15118-20 | 2022 (MCS Annex K: 2024) | Yes (enhanced) | AC + DC + wireless | Mandatory mutual TLS (1.3) | Yes | Adds V2G, wireless charging, cryptographic agility, multiple contract support. Required for MCS communication. AFIR implementing acts mandate support by 2027 for V2G-capable stations. |
Protocol Negotiation Priority
When a vehicle connects to a charger, both sides declare which protocols they support. The session is conducted in the highest version both sides share. A vehicle that supports all three assigns priority: ISO 15118-20 > ISO 15118-2 > DIN SPEC 70121. If the charger only supports DIN SPEC 70121, PnC is not available — EIM (RFID/app) must be used instead. This negotiation is automatic and invisible to the driver.
What ISO 15118-2 and -20 Are Not
ISO 15118 is a communication standard, not a payment standard. It defines how authentication credentials are exchanged securely — the underlying billing and contract management is handled by eMSP backend systems and eRoaming platforms. This distinction matters for CPO system integration: implementing ISO 15118 on the charger hardware is necessary but not sufficient; PKI integration and eMSP roaming agreements must also be in place.
4. The PKI Architecture: Certificates, CAs, and Trust Chains
The security backbone of Plug & Charge is a hierarchical Public Key Infrastructure (PKI) — a system of digital certificates organized in a trust chain from a root authority down to individual vehicles and charging stations. This is structurally similar to the certificate authorities that secure HTTPS web traffic, but operated within the specific governance framework of the EV charging ecosystem.
Certificate Hierarchy
| Level | Certificate Type | Issued By | Installed In | Purpose |
|---|---|---|---|---|
| Root | V2G Root CA Certificate | V2G Root CA operator (e.g., Hubject) | Vehicle (from factory) and EVSE | Top-level trust anchor. Pre-installed in vehicles by OEM; used to verify all downstream certificates. |
| Intermediate | Sub-CA Certificates | V2G Root CA → OEM Sub-CA / CPO Sub-CA / MO Sub-CA | Vehicle, EVSE backend | Intermediate trust chain certificates for OEMs (vehicle identity), CPOs (EVSE identity), and Mobility Operators (contract issuance). |
| Leaf | Contract Certificate (EV Contract) | eMSP / Mobility Operator | Vehicle secure storage (HSM) | Represents the driver’s charging contract. Presented to the charging station during PnC authentication. |
| Leaf | EVSE Certificate | CPO Sub-CA | Charging station | Presented by the station to the vehicle during TLS handshake to prove the station’s identity. |
Certificate Lifecycle Management
All PnC certificates have defined validity periods and must be renewed, revoked, or replaced as they expire or as contracts change. Key lifecycle events:
- Initial installation: Contract certificate pushed to the vehicle at first PnC session setup — either OTA or at first charging event
- Renewal: Certificates are automatically refreshed before expiry, typically handled by the CSMS communicating with the PKI backend
- Revocation: If a contract is cancelled or a certificate is compromised, the certificate is added to a Certificate Revocation List (CRL) or invalidated via Online Certificate Status Protocol (OCSP). The PKI checks revocation status at each session
- Operator abstraction: In practice, a CPO’s CSMS handles most certificate lifecycle management automatically — the Hubject PKI, for example, automatically publishes new certificates, removes revoked ones, and cleans up expired entries via scheduled batch processes
Hardware Security Module (HSM)
The contract certificate and associated private key stored in the vehicle must be protected in a Hardware Security Module (HSM) — a tamper-resistant secure element in the vehicle’s charging communication controller. The private key never leaves the HSM; cryptographic operations are performed inside the secure element. This prevents certificate theft even if the vehicle’s software is compromised.
5. Ecosystem Actors: OEM, eMSP, CPO, V2G Root CA, and eRoaming Hub
PnC requires coordination among five distinct actor types, each with defined responsibilities within the PKI and billing ecosystem.
| Actor | Role in PnC | Key Responsibility |
|---|---|---|
| OEM (Vehicle Manufacturer) | Pre-installs V2G Root CA certificate and OEM Sub-CA certificates in the vehicle from the factory. Implements EVCC hardware (communication controller + HSM). | Ensures the vehicle has the hardware and root trust anchor to participate in PnC from day one. |
| eMSP / Mobility Operator (MO) | Issues the contract certificate that represents the driver’s charging contract. Manages contract lifecycle and invoices the driver. | The driver sets up a PnC account with an eMSP. The eMSP pushes a contract certificate to the vehicle (OTA or at first session). When a session is authorized via PnC, the eMSP receives billing records and invoices the driver. |
| CPO (Charge Point Operator) | Operates PnC-capable charging stations with SECC hardware, valid EVSE certificates, and a CSMS connected to the PKI. | Verifies contract certificates presented by vehicles, authorizes sessions, and reports energy delivery for billing. |
| V2G Root CA Operator | Operates the root trust anchor of the PKI — the V2G Root Certificate Authority whose certificate is pre-installed in vehicles. Manages sub-CA issuance and certificate verification infrastructure. | Hubject (founded by BMW, Bosch, EnBW, Enel X, E.ON, Mercedes-Benz, Siemens, and Volkswagen Group) is the primary V2G Root CA operator in Europe and is expanding globally. Other operators include Eonti in some markets. |
| eRoaming Hub | Enables cross-network PnC authorization — a driver with an eMSP account can use PnC at any CPO connected to the same eRoaming platform, even if the CPO and eMSP have no direct commercial agreement. | Hubject’s intercharge platform is the primary eRoaming hub for PnC in Europe, connecting 400,000+ charge points and 1,000+ B2B partners across 52 countries. CPOs and eMSPs connect via OCPI. |
6. PnC vs. RFID vs. Autocharge vs. QR Code
PnC is one of four common authentication methods in the EV charging market. Each has different security profiles, user experience characteristics, and infrastructure requirements.
| Method | How It Works | Security Level | Driver Experience | Infrastructure Requirement | Cross-Network Roaming |
|---|---|---|---|---|---|
| Plug & Charge (ISO 15118) | Certificate exchange via charging cable; automatic authorization | Highest — mutual PKI authentication, TLS encryption | Plug in and walk away — zero interaction | ISO 15118-capable EVSE + CSMS PKI integration + V2G Root CA contract | Yes — via eRoaming (Hubject/OCPI) |
| RFID Card | Driver taps a card on the reader; CSMS verifies card ID against whitelist or eRoaming platform | Medium — card UID can be cloned; no end-to-end encryption | Tap card, wait for authorization | RFID reader on EVSE; OCPP backend | Yes — via OCPI roaming |
| Autocharge | Station reads the vehicle’s MAC address from the PLC interface; matches to a stored account. Not standardized. | Low — MAC addresses can be spoofed; no cryptographic authentication | Plug in and walk away (when it works) | Proprietary implementation per network; no standard interoperability | No — network-specific |
| QR Code / App | Driver scans a QR code or opens an app to initiate session and pay | Medium-Low — QR codes can be fraudulently replaced (“quishing”) | Requires phone, app, or payment interaction | QR code display or app integration; AFIR requires uniquely generated QR per session (not static stickers) | Yes — via app account |
| Contactless Payment Terminal | Driver taps bank card or phone; anonymous payment processed | Medium — standard PCI-DSS payment security; anonymous (no billing fraud risk) | Tap and charge — familiar but requires physical interaction | Payment terminal hardware; mandatory for stations above 50 kW under AFIR | N/A — no account required |
Autocharge vs. PnC — a critical distinction: Autocharge is sometimes marketed as “plug and charge” but is technically different and inferior. It identifies a vehicle by its PLC MAC address — a value that is not cryptographically protected and can be spoofed. Autocharge has no standardized cross-network interoperability and will not satisfy ISO 15118 compliance requirements under AFIR. True Plug & Charge is defined exclusively by ISO 15118’s certificate-based PKI mechanism.
7. What CPOs Need to Implement PnC
Deploying Plug & Charge is a multi-layer integration project that spans hardware, firmware, backend, and commercial agreements. The following is the minimum implementation stack for a CPO:
Hardware Layer
- ISO 15118-capable EVSE: The charging station must include a communication controller supporting ISO 15118-2 (and ideally -20). This requires a PLC chip capable of HomePlug GreenPHY communication (for -2) or 10BASE-T1S Ethernet (for -20 / MCS), plus sufficient processor capacity to run TLS and certificate operations. Joint Tech’s commercial DC fast chargers support Plug & Charge via ISO 15118 — including the EVD003 (60–160 kW) which supports both DIN 70121 and ISO 15118.
- Secure element / HSM on EVSE: The station must store its EVSE certificate securely and perform TLS operations in a protected environment.
Firmware and Software Layer
- TLS 1.2 stack minimum (TLS 1.3 required for ISO 15118-20)
- ISO 15118 application layer implementation (SECC — Supply Equipment Communication Controller)
- Certificate signing request (CSR) generation and management
Backend Layer (CSMS)
- OCPP 2.0.1: Required for full ISO 15118 PnC integration with the CSMS — OCPP 2.0.1 carries the messages enabling Plug & Charge certificate management between charger and backend
- PKI integration: The CSMS must connect to a V2G Root CA (directly or via a managed service). At commissioning, the CSMS installs the V2G Root CA certificate on each charger and manages EVSE certificate issuance, renewal, and revocation
- Certificate pool access: The CSMS must be able to fetch contract certificates from the eRoaming hub’s certificate pool (Hubject intercharge or equivalent) to verify vehicle credentials at session time
Commercial Agreements
- V2G Root CA contract: The CPO must sign an agreement with a V2G Root CA operator (e.g., Hubject) to obtain CPO Sub-CA certificates, enabling the station to receive EVSE certificates
- eRoaming agreements: OCPI-based roaming agreements with eMSPs (or via an eRoaming hub) enable the CPO to authorize PnC sessions from vehicles whose contracts are held by any participating eMSP — not just those with direct CPO relationships
Realistic Timeline
A realistic PnC implementation project for a CPO deploying new hardware runs approximately 6–9 months from kickoff to live deployment — covering hardware procurement, firmware integration, CSMS backend configuration, Hubject PKI onboarding, interoperability testing, and field commissioning. Treating it as a simple firmware update significantly underestimates the integration scope.
8. Vehicle-Side Requirements: EVCC, HSM, and Certificate Storage
For a vehicle to use Plug & Charge, its charging communication system must satisfy several hardware and software requirements that are typically set at the OEM level during vehicle design.
EVCC (EV Communication Controller)
The vehicle-side counterpart of the SECC — the hardware module that manages ISO 15118 communication over the charging cable. Must support PLC (for ISO 15118-2) or Ethernet (for ISO 15118-20) and implement the full ISO 15118 application stack.
Hardware Security Module (HSM) / Secure Element
A tamper-resistant chip that stores the vehicle’s contract certificates and private keys. Cryptographic operations (signing, decryption) are performed inside the HSM — the private key never leaves it. Without an HSM, PnC cannot be implemented securely.
V2G Root CA Certificate (pre-installed)
The OEM installs the V2G Root CA certificate in the vehicle at the factory. This is the trust anchor that allows the vehicle to verify the identity of any charging station presenting a certificate signed by the same root CA.
Contract certificate storage
The vehicle must have secure memory for storing one or more contract certificates (ISO 15118-20 supports multiple simultaneous contracts from different eMSPs).
OTA update capability
Required for contract certificate renewal, revocation response, and firmware updates to the EVCC software stack. Vehicles without OTA capability require physical service visits for certificate management.
More than twenty vehicle brands globally have announced some level of Plug & Charge or ISO 15118 support, with real-world rollout varying by market, model, and software version. Volkswagen Group (Porsche Taycan, Audi e-tron, VW ID.4), Mercedes-Benz (EQS), and BMW were among the early EU adopters; North American network rollout has expanded significantly via Electrify America and EVgo.
9. Regulatory Drivers: AFIR, NEVI, and ISO 15118 Mandates
European Union — AFIR
The EU’s Alternative Fuels Infrastructure Regulation (AFIR) and its implementing acts have established Plug & Charge as a compliance requirement for new publicly accessible charging infrastructure in stages:
- From January 2026: All newly installed public AC chargers in the EU must support ISO 15118-2 (Plug & Charge) functionality. This applies to any charger commissioned from this date onward at any publicly accessible location.
- By 2027: AFIR implementing acts mandate ISO 15118-20 support for V2G-capable public charging stations — the more advanced standard covering bidirectional energy services and MCS communication.
The regulatory rationale is interoperability: AFIR requires that any EV driver can charge at any public station without network-specific apps or cards. PnC via ISO 15118 is the mechanism through which this is achieved in practice for the most seamless user experience.
United States — NEVI
The National Electric Vehicle Infrastructure (NEVI) program — part of the Bipartisan Infrastructure Law (2021) — requires all NEVI-funded charging stations to be OCPP 2.0.1-capable and to support ISO 15118 communication. While NEVI does not mandate that stations must implement PnC from day one, the hardware and protocol stack requirements ensure that all NEVI-funded infrastructure is PnC-ready as the ecosystem matures.
10. PnC for Fleet Operators: Contract Management and Billing
For fleet operators, Plug & Charge offers significant operational advantages over RFID-based authentication — but also requires upfront integration with a fleet eMSP or mobility operator that supports PnC contract management.
Fleet PnC Benefits
- No card management: Eliminates the operational burden of issuing, replacing, and deactivating RFID cards across a large vehicle fleet. The certificate is tied to the vehicle, not a physical card.
- Automated billing consolidation: All PnC sessions across any CPO network are billed to the fleet’s eMSP contract, with centralized reporting — simplifying reimbursement and cost-center allocation.
- Cross-network coverage: Via eRoaming (OCPI + Hubject), fleet vehicles can PnC-authenticate at any connected CPO network in the EU without the fleet operator needing separate accounts on each network.
- Audit trail integrity: Because PnC uses cryptographic authentication, each session is attributed to a specific vehicle and contract with non-repudiable records — useful for expense reporting, VAT reclaim, and compliance documentation.
Fleet-Specific Considerations
- Fleet vehicles must be enrolled in a fleet PnC contract with an eMSP that supports certificate-based billing
- Contract certificate renewal must be managed at scale — automated via OTA update or CSMS-triggered refresh
- Mixed fleets (PnC-capable and non-PnC vehicles) require CPO hardware that supports both ISO 15118 and EIM (RFID / contactless payment) simultaneously
For fleet depot charging equipment that supports both PnC and RFID, see Joint’s fleet and logistics charging solutions.
11. PnC and V2G: The Connection
Plug & Charge and Vehicle-to-Grid (V2G) are technically interdependent in the ISO 15118-20 framework. V2G — bidirectional energy flow from vehicle battery back to the grid — requires the vehicle and EVSE to maintain a secure, authenticated communication session throughout not just charging but also discharging. This requires:
- Mutual authentication: Both vehicle and station must prove their identity to each other before bidirectional energy transfer begins — preventing unauthorized grid draw from vehicle batteries. PnC’s PKI provides this.
- 0A mode persistence: ISO 15118-20 allows the communication session to remain active with zero current flow (contactors open or closed) — essential for V2G grid services where the vehicle is connected but may alternate between charging, standby, and discharging states based on grid signals.
- Smart charging messages: ISO 15118-20 carries the energy management messages (power setpoints, pricing, SoC targets, grid frequency signals) between vehicle and EVSE that make V2G operationally meaningful beyond simply reversing current direction.
In short: V2G at scale is not possible without the secure, interoperable authentication layer that ISO 15118 PnC provides. This is why AFIR’s V2G mandate (ISO 15118-20 support by 2027) and its PnC mandate (ISO 15118-2 by 2026) are sequential stepping stones in the same regulatory architecture.
12. Implementation Challenges and Adoption Status (2026)
Fragmented Certificate Management
The ISO 15118 PKI architecture is complex, and the standard deliberately leaves some aspects of certificate installation and management out of scope — resulting in non-uniform implementations that vary by vehicle OEM and eMSP. As of 2026, a charging session that works perfectly for one vehicle/eMSP combination may fail for another due to certificate provisioning differences. The industry is actively working to standardize this through bodies like CharIN and through eRoaming hub initiatives.
DIN SPEC 70121 Dominance
Despite ISO 15118-2’s 2014 publication date, DIN SPEC 70121 remains the dominant protocol in deployed DC fast chargers — primarily because of its earlier deployment and the absence of compelling commercial use cases for PnC until AFIR and NEVI created regulatory pressure. In practice, even vehicles and chargers that both support ISO 15118-2 frequently fall back to DIN SPEC 70121 during session negotiation if PnC is not properly configured end-to-end.
TLS Overhead
A full TLS handshake adds approximately 1.5–2 seconds to session startup time compared to unencrypted DIN SPEC 70121 communication. While modest in absolute terms, this overhead becomes perceptible at high-throughput commercial sites and must be factored into EVSE performance specifications.
Adoption Trajectory
With AFIR mandating ISO 15118-2 PnC for all new public AC chargers from January 2026, the adoption trajectory has accelerated sharply. Major EU networks and NEVI-funded US infrastructure are converging on OCPP 2.0.1 + ISO 15118 as the baseline specification. The remaining gap is on the vehicle side: not all vehicles in the current fleet support PnC, meaning CPOs must continue supporting RFID and contactless payment alongside PnC for the foreseeable future.
13. Frequently Asked Questions About Plug & Charge
What is Plug & Charge (PnC) and how is it different from regular EV charging?
Plug & Charge is an authentication method defined in the ISO 15118 standard where the vehicle and charging station exchange encrypted digital certificates through the charging cable to verify the driver’s identity and authorize billing — with no RFID card, app, or manual interaction required. Regular EV charging using RFID or a smartphone app requires the driver to authenticate separately before the session can begin. With PnC, plugging in the cable is the only action required — everything else is automated within seconds.
Is Plug & Charge mandatory in the EU?
Yes, under AFIR’s implementing framework. From January 2026, all newly installed publicly accessible AC charging stations in the EU must support ISO 15118-2 Plug & Charge functionality. For V2G-capable stations, ISO 15118-20 support is required by 2027. This means any EVSE commissioned for public use in the EU from 2026 onward must include the hardware, firmware, and backend integration required for PnC — not just the physical connector compatibility.
What is the difference between Plug & Charge and Autocharge?
Plug & Charge (ISO 15118) uses a cryptographic certificate-based PKI system — the vehicle and station mutually authenticate via TLS and exchange digital certificates that are cryptographically signed and verified in real time. Autocharge uses the vehicle’s PLC MAC address — an identifier that is not cryptographically protected, can be spoofed, and has no cross-network interoperability standard. ISO 15118 PnC is the only method that satisfies AFIR and NEVI regulatory requirements for secure, interoperable authentication.
What hardware does a charging station need to support PnC?
A PnC-capable charging station requires: (1) an ISO 15118-capable communication controller (SECC) with PLC hardware for ISO 15118-2, or 10BASE-T1S Ethernet for ISO 15118-20; (2) a secure element for EVSE certificate storage; (3) a TLS stack (v1.2 minimum for -2, TLS 1.3 for -20); (4) OCPP 2.0.1 connectivity to the CSMS backend; and (5) CSMS integration with a V2G Root CA (e.g., Hubject) for certificate issuance and session-time verification. Hardware that supports only DIN SPEC 70121 cannot implement PnC.
Does Plug & Charge work across different charging networks?
Yes — this is one of PnC’s key advantages over Autocharge. Via eRoaming hubs (primarily Hubject’s intercharge platform in Europe), a driver’s contract certificate issued by one eMSP can be verified at any CPO connected to the same eRoaming hub, even without a direct commercial agreement between the driver’s eMSP and that CPO. Cross-network PnC roaming requires both the CPO and the eMSP to be connected to the eRoaming hub via OCPI, with PKI relationships established through the hub.
Looking for ISO 15118-capable DC fast chargers for European commercial deployments? Joint Tech holds ISO 15118 certification and supplies CE-certified DC fast chargers from 30–400 kW supporting Plug & Charge via ISO 15118 and DIN SPEC 70121, with OCPP 1.6 and OCPP 2.0.1 backend connectivity. For North American projects, our CCS1 and NACS-compatible charger range is built to NEVI protocol requirements. For depot-scale fleet projects with energy management needs, explore our fleet and logistics charging solutions.
