Quick Answer: Plug & Charge allows a compatible electric vehicle to authenticate itself at a compatible charging station after the cable is connected. Once the required account, charging contract and vehicle settings are configured, the driver can start eligible sessions without scanning a QR code, opening an app or tapping an RFID card. Support must exist across the vehicle, charger and service provider; a matching connector alone is not enough.
An EV charging stop can involve several steps: finding the right charger, opening an app, selecting a connector, confirming payment and waiting for the session to begin.
Plug & Charge aims to simplify that experience.
The driver connects the charging cable, and the systems handle identification and authorisation in the background. Billing follows the linked charging agreement.
For Indian EV owners and charging operators, the important questions are how this works, which equipment supports it and how it differs from other automatic charging services.
What Is Plug & Charge?
Plug & Charge is a charging feature associated with the ISO 15118 family of vehicle-to-charger communication standards.
It uses digital certificates to support authentication and authorisation. These certificates help the participating systems establish trust and associate the charging session with an eligible contract.
According to CharIN’s Plug & Charge guidance, the feature supports automatic communication and billing without requiring external identification at the charger, such as an RFID card or charging app.
However, “without an app” describes the experience of starting an eligible session. Drivers may still need an app, website or vehicle interface to activate the service, manage payments, view receipts or change account settings.
Plug & Charge also does not mean free charging. The session remains subject to the applicable tariff and service agreement.
How a Plug & Charge Session Works
The exact onboarding process varies by vehicle manufacturer and charging service. A typical journey looks like this:
| Stage | What happens |
|---|---|
| Initial setup | The driver activates a supported service and establishes the required account or charging contract |
| Cable connection | The vehicle is connected to a compatible charger |
| Communication | The vehicle and charger exchange the information needed to establish the session |
| Authentication and authorisation | Certificates and contract information are checked through the supported systems |
| Charging | Energy transfer begins once authorisation and the necessary charging checks succeed |
| Billing | Session information is used to bill the linked account under the applicable agreement |
The visible experience can be simple even though several organisations and systems operate behind it.
Hubject’s onboarding documentation describes an ecosystem involving vehicle manufacturers, mobility operators and charge point operators, supported by certificate services.
The driver should still confirm that charging has actually started before leaving the vehicle.
Plug & Charge and Autocharge Are Not the Same
Both features can offer a similar experience: connect the cable and charging begins automatically.
Their underlying identification methods differ.
| Feature | ISO 15118 Plug & Charge | Autocharge |
|---|---|---|
| Main identification approach | Certificate-based authentication | Recognition of a vehicle identifier linked to an account |
| Setup | Requires supported vehicle functionality and charging-contract provisioning | Usually involves registering a compatible vehicle with the charging network |
| Compatibility | Depends on the vehicle, charger, certificate services and participating providers | Depends on the vehicle identifier and the network’s implementation |
| Use across networks | Requires technical compatibility and accepted commercial arrangements | Depends on each network’s support and account setup |
| Driver experience | Eligible sessions can start after connection | Eligible sessions can start after connection |
ChargeNet’s explanation distinguishes identifier-based Autocharge from certificate-based ISO 15118 Plug & Charge.
An “automatic charging” label therefore does not, by itself, confirm that a service uses ISO 15118 certificates. Drivers and buyers should ask which technology is being offered.
What ISO 15118 and OCPP Each Do
Several communication standards may be involved in a charging installation, but they serve different purposes.
ISO 15118 concerns communication between the vehicle and charging equipment. Its scope includes messages used to support charging and related functions.
OCPP concerns communication between the charging station and its management system. That system can manage authorisation, transactions, equipment status and other operational information.
The Open Charge Alliance identifies native ISO 15118 support among the features of OCPP 2.0.1. It also publishes guidance on implementing Plug & Charge with OCPP 1.6 extensions.
This means an OCPP version label alone is not proof that a complete installation delivers Plug & Charge. The relevant features must be implemented, configured and tested across the system.
For background on charger-network communication, read our OCPP versus OCPI guide.
Why the Topic Matters for India
Interoperability—making different vehicles, chargers and software systems work together—is an active area of technical cooperation.
The March 2026 India–EU workshop on EV charging technologies covered charging communication, multi-brand interoperability and ISO 15118-related testing.
This is relevant progress, but it should not be interpreted as evidence that every Indian vehicle or public charging station already supports Plug & Charge.
Availability must be checked for the exact vehicle variant, software version, charging location and service provider.
Convenient payment features also need careful interpretation. For example, Hyundai India’s in-car payment service allows users to initiate charging payments through the vehicle’s infotainment interface. That workflow should not automatically be described as certificate-based Plug & Charge.
The customer experience may become simpler through several different technologies.
What Drivers Should Check Before Relying on It
Confirm Support for Your Exact Vehicle
Ask the manufacturer whether your vehicle supports ISO 15118 Plug & Charge in your market.
Check the model year, variant and software requirements. A feature advertised for the same model in another country may not be available under the same conditions in India.
Check the Specific Charging Location
Do not assume that every charger operated by a participating network has identical capabilities.
Confirm support for the location and connector you intend to use. Hardware, software and service availability may differ between sites.
Complete the Required Activation
Some services require an account, payment arrangement or in-vehicle activation before the first automatic session.
Finish that process before a time-sensitive journey. Follow the provider’s instructions rather than assuming that connecting the cable will complete enrolment automatically.
Review the Applicable Price
Automatic authorisation does not guarantee the lowest available tariff.
Check the linked contract’s energy price and any applicable session, parking or idle charges. Also confirm where receipts appear and how billing queries are handled.
Keep an Alternative Starting Method Available
If automatic authorisation fails, the site may offer an app, RFID card or another payment method.
Check the supported alternatives before travelling. A failure to start automatically does not necessarily mean the vehicle cannot charge at that location.
For other payment options, see our guide to paying for EV charging in India.
What Charging Operators Should Ask Equipment Suppliers
For a new installation, “Plug & Charge ready” should lead to specific procurement questions.
Ask the supplier to demonstrate:
- Which vehicle models and software versions have been tested.
- Which ISO 15118 features and versions are implemented.
- Whether the charger-management platform supports the required certificate workflows.
- Which charging-service providers and contracts are supported.
- How certificates are installed, renewed and revoked.
- How failed authorisation and interrupted sessions are handled.
- Which alternative activation methods remain available.
- What additional hardware, software licences or service fees are required.
The Open Charge Alliance’s certification information identifies ISO 15118 support as a distinct certification profile. Buyers should examine the actual certification scope rather than relying on a general protocol claim.
A useful acceptance test should include successful charging, failed authorisation, session termination and correct billing. Testing should use the intended vehicle and service combinations.
Security Depends on More Than Automatic Identification
Certificate-based authentication provides a structured way for systems to establish trust. It does not make the entire charging service immune to security problems.
Operators still need appropriate protection for accounts, software, certificate services and operational systems.
Practical questions include who manages certificates, how access is withdrawn, how updates are deployed and how unusual transactions are investigated.
Vehicle transfers also deserve attention. When a car is sold, returned or reassigned, the previous user should follow the provider’s process for removing linked charging arrangements.
For fleets, document which account pays for each vehicle and how authorisation changes when vehicles move between teams.
These are operational checks to include in deployment planning, alongside the broader measures discussed in our EV charging station cybersecurity guide.
Does Plug & Charge Make Charging Faster?
Plug & Charge can reduce the manual steps required to start a session. It does not increase the battery’s charging limit or the charger’s available power.
It is useful to distinguish:
- Session-start time: Time spent connecting, identifying and authorising.
- Energy-transfer time: Time spent adding the required energy to the battery.
A smoother start can improve convenience, but total charging time still depends on the vehicle, battery conditions, charging equipment and available power.
Compare these separately when assessing the customer experience.
A Practical Way to Introduce Plug & Charge
For an operator considering the feature, a controlled pilot is a sensible starting point.
Choose a small set of supported vehicles and chargers. Test account activation, repeat visits, billing accuracy and alternative activation when automatic authorisation is unavailable.
Record the proportion of eligible sessions that start successfully and the reasons for unsuccessful attempts. Include customer-support staff so they can explain the feature without confusing it with Autocharge or promising universal compatibility.
Expand the service after the intended vehicle and software combinations work reliably.
For drivers, the equivalent approach is simple: test the feature at a convenient location before relying on it during a long journey.
Conclusion
Plug & Charge can make public EV charging easier by allowing compatible vehicles and charging systems to handle authentication automatically after connection.
Its success depends on more than the charging cable. Vehicle support, charger software, digital certificates, service agreements and billing systems all need to work together.
For Indian EV owners, the next step is to verify support for their exact vehicle and intended charging location. For operators, the priority is demonstrated compatibility and reliable operation.
Explore EarthtronEV charging locations when planning a journey, and confirm the available activation and payment methods for your selected station.