ISO 15118 Plug and Charge Complete Guide: Authentication, Certificates and Commercial Deployment

What Is ISO 15118?

ISO 15118 is a communication standard for the interaction between electric vehicles and charging equipment. In the EV charging industry, it is often discussed as a high-level protocol, but the easiest way to understand its value is through the user experience it enables: Plug & Charge.Plug & Charge allows an EV driver to connect the charging cable and start charging without repeatedly scanning a QR code, tapping an RFID card, opening a mobile app, or manually authorizing the session. The vehicle and the charging station exchange the information needed to identify the EV, authenticate the charging contract, authorize the session, and support a more automated charging experience.In simple terms, ISO 15118 helps the charging ecosystem move from manual charging access to vehicle-based digital authentication.For drivers, this means less friction. For charging operators, it means a more premium user experience, a stronger foundation for secure authorization, and better preparation for future smart charging and bidirectional charging scenarios.Authoritative industry organizations such as CharIN describe Plug & Charge as a way to enable automated communication and billing processes between the electric vehicle and the charging station without relying on external identification methods such as RFID cards, payment cards, or charging apps. This makes ISO 15118 especially important for operators that want to build a more seamless and future-ready charging experience.

ISO 15118 Is Not a Replacement for OCPP

One of the most common misunderstandings in EV charging software is treating ISO 15118 as a replacement for OCPP. It is not.ISO 15118 and OCPP work at different layers of the EV charging stack. ISO 15118 focuses on communication between the electric vehicle and the charging equipment. OCPP focuses on communication between the charging station and the central management system or backend platform.A mature EV charging software architecture may use ISO 15118 for vehicle-to-charger communication, OCPP for charger-to-backend communication, OCPI for network-to-network roaming, billing software for pricing and invoicing, payment systems for transaction processing, and CPMS software for operational management.This is why operators should not treat Plug & Charge as an isolated feature. It must be understood as part of a broader software and payment architecture. If you are evaluating the backend layer behind charger operations, TrendPower’s guide to EV charging backend software explains how OCPP, billing, payments and multi-site operations work together inside a charging platform.

How Plug & Charge Works

Plug & Charge sounds simple from the driver’s perspective, but the backend process is more complex.When a compatible EV is connected to a compatible charging station, the EV and charger exchange digital credentials. These credentials help confirm that the vehicle has a valid charging contract and is allowed to start a charging session.A simplified Plug & Charge process usually works like this:

1. The driver plugs the charging cable into the EV.
2. The vehicle and charger establish a communication session.
3. The EV presents contract or certificate information.
4. The charger or backend validates the certificate chain.
5. The charging session is authorized.
6. Charging starts automatically.
7. Session data is recorded.
8. Billing and settlement are handled by the relevant software systems.

The value is clear: the driver does not need to manually choose a charger in an app, scan a QR code, tap a card, or enter payment information at the station.However, this convenience depends on several systems working together correctly. The EV, charging station, backend system, certificate infrastructure, payment workflow and operator business rules all need to align. For operators, this means Plug & Charge should be planned together with CPMS software, payment tools, billing systems and operational dashboards.

Why Certificates Matter in Plug & Charge

Certificates are at the heart of ISO 15118 Plug & Charge.In a normal app-based charging flow, a user may log in with an account, scan a QR code, select a connector and pay through a mobile wallet or card. In a Plug & Charge flow, the vehicle itself becomes the identity carrier.To make this secure, Plug & Charge relies on digital certificates and a public key infrastructure, often referred to as V2G PKI. The certificate system helps answer several key questions: Is this vehicle allowed to charge? Is the charging contract valid? Can the charger trust the certificate? Can the backend trust the charging request? Which customer account should be billed?This is why Plug & Charge is not simply a “connect and start” feature. It is a secure authentication and authorization framework.CharIN has published detailed materials around Plug & Charge, PKI governance and interoperability, including the role of multi-PKI environments and the need for harmonized implementation across the global charging ecosystem. Operators who want to understand the standards background can refer to CharIN’s ISO 15118 communication standard resources.

ISO 15118 in the Larger EV Charging Software Stack

To understand ISO 15118 commercially, it is helpful to place it in the complete EV charging software stack.A practical EV charging architecture may include the vehicle communication layer, charger firmware, OCPP communication, CPMS or charging backend, user account system, payment gateway, billing engine, certificate management, driver app, operator dashboard and roaming or partner integrations.ISO 15118 operates closest to the vehicle and charger interaction. But Plug & Charge cannot create commercial value unless it connects with the backend, payment and billing layers.For example, when a vehicle is authenticated through Plug & Charge, the backend still needs to know which customer account is responsible for the session, which tariff should be applied, whether the session belongs to a private user, fleet, subscription plan or roaming partner, how the transaction should be billed, how revenue should be reported, and whether the session should be visible in the operator dashboard.This is why Plug & Charge should be planned together with EV charging payment solutions, EV charging billing software and backend reporting tools.

The Relationship Between ISO 15118 and OCPP 2.1

OCPP remains essential for charger-to-backend communication. As the EV charging industry evolves, the relationship between OCPP and ISO 15118 becomes more important.The Open Charge Alliance explains that OCPP 2.0.1 supports ISO 15118, while OCPP 2.1 adds further capabilities such as ISO 15118-20 support, bidirectional power transfer, DER control, improved smart charging, local cost calculation, ad hoc payment options and secure dynamic QR codes.For operators, this means the question is not only “Do we support Plug & Charge?” The better question is: Can our charging platform support the full vehicle-to-charger-to-backend workflow required for modern authentication, smart charging, cost calculation and future bidirectional charging?This is where OCPP version strategy becomes important. If your network is still mainly based on OCPP 1.6, you may be able to manage many charging operations, but advanced ISO 15118-related capabilities may require a more modern protocol roadmap.For a deeper comparison, review TrendPower’s article on OCPP 1.6 vs OCPP 2.0.1 vs OCPP 2.1.

Commercial Benefits of Plug & Charge

Plug & Charge is not only a technical improvement. It has direct commercial value for charging operators, site owners, fleets and e-mobility service providers.

Better Driver Experience

The first benefit is better driver experience. Drivers do not want to download a new app for every charging network, scan unreliable QR codes, wait for payment pages to load or search for RFID cards. Plug & Charge reduces the number of user actions needed to start a charging session. This can be especially valuable at premium public charging stations, highway corridors, commercial parking sites and fleet depots.

Higher Charging Conversion

In public charging, friction directly affects conversion. If a driver arrives at a charger but cannot easily authorize or pay, the session may never start. Plug & Charge can reduce failed starts caused by app confusion, payment friction or unfamiliar user interfaces.

Stronger Fleet Charging Experience

Fleet operators care about speed, predictability and control. Drivers should not waste time figuring out how to authorize charging. Vehicles should be recognized automatically, and charging sessions should be linked to the correct fleet account.

Foundation for Bidirectional Charging

ISO 15118 is closely connected with more advanced EV-grid interaction. As vehicle-to-grid, vehicle-to-home and vehicle-to-building scenarios become more important, secure vehicle communication and richer authorization flows will matter even more.

Premium Brand Positioning

For charging operators, supporting Plug & Charge can become a premium signal. It tells customers, partners and fleet buyers that the platform is ready for modern EV charging use cases. This can help differentiate a charging network from basic app-only or QR-only charging experiences.Operators that want to improve utilization and payment conversion can also review TrendPower’s guide to EV charging payment systems, because Plug & Charge still needs a strong financial workflow behind the driver experience.

Implementation Challenges of ISO 15118 Plug & Charge

A strong article about Plug & Charge should not only describe benefits. It should also explain implementation challenges. This makes the content more credible for technical readers and more useful for buyers.

Certificate Management Is Complex

Certificate management is one of the biggest challenges. The certificate chain behind Plug & Charge is not simple. Operators need to understand how certificates are issued, installed, validated, renewed and revoked. The challenge becomes greater when multiple vehicle brands, charging networks, eMSPs, certificate authorities and regional requirements are involved.

PKI Governance Requires Industry Coordination

PKI governance is another challenge. Public key infrastructure is not only a technical issue. It is also a governance issue. Different markets may have different trust models, certificate policies, operating entities and compliance requirements. This is why Plug & Charge deployment often requires collaboration across OEMs, CPOs, eMSPs, backend providers, PKI providers and standards organizations.

Vehicle Compatibility Is Not Universal

Vehicle compatibility is not universal. Not every EV supports Plug & Charge in the same way. Some vehicles support ISO 15118 features, while others may require software updates, hardware support or specific charging network compatibility. Operators should avoid assuming that “Plug & Charge support” automatically works with every EV model.

Charger Hardware and Firmware Must Be Ready

Charger hardware and firmware must also be ready. A backend platform alone cannot deliver the full experience if the charger does not support the required communication and security features. Operators planning ISO 15118 deployment should evaluate charger compatibility early.

Backend and Payment Systems Must Be Integrated

Backend and payment systems must be integrated. A Plug & Charge session still needs billing and financial processing. Authentication is only one part of the charging journey. The backend must connect vehicle identity, customer contract, pricing rules, charging records and payment settlement.

Security Must Be Treated Seriously

Security must also be treated seriously. Plug & Charge uses certificates and secure communication, but that does not mean implementation risk disappears. Recent academic research on streamlining Plug-and-Charge authorization with OAuth2 and OIDC highlights that credential installation can be complex and not always user-friendly. Another research paper on security aspects of ISO 15118 Plug and Charge payment discusses security limitations and the importance of improving implementation approaches.For operators, the practical lesson is clear: Plug & Charge is valuable, but it is not a simple switch that can be turned on without architecture, security and operational planning.

ISO 15118 for CPOs: What to Evaluate

If you are a Charge Point Operator, ISO 15118 should be evaluated from both a technical and commercial perspective.CPOs should ask whether their chargers support ISO 15118 communication, whether their backend supports OCPP versions that can work with ISO 15118-related workflows, whether the platform can manage certificate-related data, whether vehicle authentication can be connected to customer accounts, whether the billing engine can apply the correct tariff automatically, and whether the payment solution can handle Plug & Charge sessions.CPOs should also consider whether Plug & Charge is a near-term requirement or a roadmap capability. For early-stage operators, basic QR, RFID, app and card payment may still be enough. For premium charging networks, highway charging, enterprise fleets and future V2G use cases, ISO 15118 becomes more strategic.If the business goal is large-scale public operation, Plug & Charge should be considered alongside EV charging management software, backend monitoring, automated billing and payment settlement.

ISO 15118 for eMSPs and Platform Providers

For eMSPs and charging platform providers, Plug & Charge creates a stronger customer experience but also introduces new responsibilities.The eMSP may need to manage contracts, user accounts, certificate provisioning workflows, billing relationships and customer support logic. If the user expects charging to start automatically, the platform must make sure account status, payment method, tariff and authorization data are all ready before the driver arrives at the charger.This is especially important for white-label charging platforms, fleet charging solutions, subscription-based eMSP services, OEM charging services, corporate charging accounts and premium public charging networks.If Plug & Charge is not properly integrated with the customer account and payment system, the user experience may look seamless at the charger but become confusing when invoices, receipts or support cases appear later.

Where Plug & Charge Fits in the Payment Journey

Plug & Charge changes the front-end authorization experience, but it does not remove the need for payment infrastructure.A complete payment journey still needs to answer several commercial questions. Who is the customer? Which contract applies? Which tariff applies? Which payment method should be used? What happens if the account balance is insufficient? How are refunds handled? How is tax invoicing managed? How are fleet or corporate accounts billed? How are settlement and revenue reports generated?This is why Plug & Charge should be connected with a charging-specific payment and billing platform, not treated as a standalone authentication feature. TrendPower’s EV Charging Payment Solution guide explains how operators can manage payment gateways, wallets, RFID or IC card payments, settlement, revenue sharing and financial reporting.

Practical Deployment Roadmap

Operators planning ISO 15118 and Plug & Charge should use a staged implementation roadmap.

Step 1: Confirm Business Need

Start by confirming the business need. Do you need Plug & Charge for public users, highway charging, fleet depots, OEM partnerships or future V2G services? If there is no clear business case, implementation may become an expensive technical project without measurable return.

Step 2: Audit Hardware Compatibility

Next, audit hardware compatibility. Check whether your charging stations support ISO 15118 and whether firmware upgrades are required.

Step 3: Review OCPP Version Strategy

Then review your OCPP version strategy. Advanced ISO 15118 workflows are easier to support when the charger-to-backend communication layer is modern. Operators using older systems may need to evaluate their OCPP roadmap before launching Plug & Charge commercially.

Step 4: Define Certificate and PKI Strategy

After that, define the certificate and PKI strategy. Decide how certificates will be issued, installed, updated, revoked and validated. Identify which partners or ecosystems are required.

Step 5: Connect Backend, Billing and Payment

The next step is to connect backend, billing and payment systems. Vehicle authentication must be linked to user accounts, charging contracts, tariffs, CDRs, payment methods and invoices.

Step 6: Test with Real Vehicles and Chargers

Finally, test with real vehicles and chargers. Lab testing is not enough. Real-world testing should include different EV models, charger types, network conditions and edge cases. After deployment, operators should monitor Plug & Charge success rate, failed authorization attempts, payment exceptions, user support cases and charger compatibility issues.

Common Mistakes to Avoid

One common mistake is treating Plug & Charge as a marketing label. Some platforms say they support Plug & Charge but only provide partial technical readiness. Buyers should ask what level of ISO 15118 support is available, how certificates are handled and how billing connects to the authentication process.Another mistake is ignoring payment and billing. Plug & Charge makes authorization easier, but it does not replace billing, payment or settlement. These systems must still work correctly.Fleet use cases should not be forgotten. Fleet charging is one of the strongest commercial scenarios for Plug & Charge. Operators should design account structures, vehicle identity mapping and fleet reporting from the beginning.Security should never be treated as an afterthought. Certificate management, PKI governance and secure authorization workflows require careful implementation.Interoperability testing is also essential. Even if all components claim standards support, real-world interoperability still needs testing across vehicles, chargers, backend platforms and payment flows.

Conclusion

ISO 15118 and Plug & Charge represent an important step toward a more automated, secure and user-friendly EV charging experience.For drivers, the benefit is simple: plug in the vehicle and start charging without manual identification. For operators, the value is broader: higher conversion, better fleet workflows, premium user experience, future readiness for bidirectional charging and stronger integration between vehicle identity, backend systems, billing and payment.However, Plug & Charge is not a one-click feature. It requires compatible vehicles, compatible chargers, certificate management, backend integration, OCPP readiness, payment logic and operational testing.For charging businesses, the best approach is to treat ISO 15118 as part of a complete commercial software stack. A strong internal reading path is OCPP Version Comparison → EV Charging Backend Software → EV Charging Payment Solution → EV Charging Billing Software.If your goal is to build a charging platform that supports advanced authentication, future-ready smart charging and scalable commercial operations, ISO 15118 and Plug & Charge should be part of your long-term roadmap.