Unified Bharat eCharge Fixed Payments. Uptime Is Next.
Unified Bharat eCharge lets EV drivers pay at participating chargers via BHIM UPI and puts every operator’s reliability on one map. What CPOs should fix first.
For most Indian EV drivers, crossing from one charging network to another has meant one more app, one more login and one more prepaid wallet. That is starting to change. Unified Bharat eCharge (UBC), a government-backed network unveiled in August 2026, now lets drivers in five pilot states find a participating charger, scan a QR code and pay over UPI from the BHIM app.
That is real progress for the front door of EV charging. But it leaves the hardest part untouched: what happens when the driver arrives and the charger does not work. This post explains what UBC changes, what it cannot change, and why uptime is quickly becoming the number that matters most for charge point operators (CPOs).
Key Takeaways
Unified Bharat eCharge, run by the Ministry of Heavy Industries with BHEL and NPCI BHIM Services, puts discovery and UPI payment for many charging networks in one place. It is still a pilot in five states.
Interoperability makes reliability public. When every network shows up on one map, a dead charger is a bad experience for the whole system, not just one operator.
IEEFA’s September 2026 briefing recommends linking public financial support for chargers to verified uptime and performance.
CPOs should prepare now: trustworthy live status, high session-success rates, fast fault resolution and a backend that can speak more than one protocol.
What is Unified Bharat eCharge?
Unified Bharat eCharge is a national interoperability layer for public EV charging. The Ministry of Heavy Industries (MHI) sponsors it, Bharat Heavy Electricals Limited (BHEL) is the project implementation agency, and NPCI BHIM Services is building the platform. That structure is set out in Energetica India’s report on the launch (17 August 2026). It is built as digital public infrastructure on the open Beckn protocol, so any participating app can discover and pay at any participating charger.
For a driver, the flow is short. Open the BHIM app, find a UBC-enabled charger, scan its QR code and pay straight from a bank account over UPI. There is no separate account and no operator-specific wallet to top up.
The rollout is still early. On 3 September 2026, MHI announced that the pilot phase had begun across Maharashtra, Karnataka, Delhi-NCR, Haryana and Rajasthan. Early participants include Mahindra, which said its 180 kW Charge_iN stations are reachable through UBC in the pilot states. One certified technology enabler also reported connecting more than 10,000 chargers from over 100 CPO partners (Energetica India, August 2026).
Before UBC | With UBC (pilot states) |
|---|---|
One app per charging network | One entry point in BHIM, with participating networks listed together |
Separate accounts and prepaid wallets | Pay per session over UPI from a bank account |
Discovery limited to each operator’s own map | Shared discovery across participating networks |
A failed session reflects on one brand | A failed session reflects on the shared network, and on EV charging as a whole |
If this sounds familiar, it is the same idea behind roaming, which we covered in why EV roaming is becoming a growing need. UBC simply brings it to India’s payment rail of choice.
What UBC solves, and what it does not
UBC removes the friction before the plug goes in: finding a charger, signing up and paying. It does not, and cannot, make the charger itself work.
UBC handles the first half of the journey. The second half still depends on each operator.
A discovery network can only show what operators feed into it, which typically means where a charger is, which connector it has, what it costs and whether it is free right now. If that last field is stale, the network does something worse than showing nothing. It sends a driver to a dead charger with confidence.
There is a second gap. UPI makes paying easy, but a successful payment is not a successful charge. Every session that is paid for and then fails becomes a refund, a support call and possibly a payment dispute. The easier payment gets, the more these failures stand out.
India’s real charging problem is reliability
India has added public chargers far faster than it has made them dependable. The Institute for Energy Economics and Financial Analysis (IEEFA) counts 52,718 public charging stations as of July 2026, up from 5,151 in 2022, roughly a tenfold increase in four years. Over a longer window, annual EV sales rose from about 50,000 in 2016 to about 2.5 million in FY2025-26 (IEEFA briefing, via EMobility+, September 2026).
Source: IEEFA, “Improving the EV charging experience in India: Beyond charger deployment” (September 2026), via EMobility+. Counts from other datasets differ (see note below).
Reliability has not kept pace. In a 2024 study of public chargers across South, Central, West and East Delhi, IEEFA found that about 84% of the chargers it examined were not functional. The main causes were theft of connectors and copper cables, and poor maintenance that left units without power or with blank screens (IEEFA feedback on the draft Delhi EV Policy 2026, 8 May 2026). That was a sample in one city, not a national figure, but drivers across the country will recognize the pattern.
IEEFA attributes this to low historical demand and a lack of incentives for operations and maintenance, which left chargers installed and then neglected (IEEFA). Support went into installing hardware; very little rewarded keeping it running.
A note on numbers: national station counts vary by source and definition. The government told the Rajya Sabha in April 2026 that India had 27,737 public charging stations, while IEEFA’s July 2026 figure is 52,718. We use IEEFA’s series in the chart because it gives both years from a single source.
Uptime is becoming a funding metric
The policy conversation is moving from how many chargers India installs to how many actually work. IEEFA’s September 2026 briefing, Improving the EV charging experience in India: Beyond charger deployment, recommends linking public financial support for EV chargers to verified uptime and performance. It also calls for a unified payment system across networks and a cut in GST on public charging from 18% to 5% (EMobility+).
There is clear international precedent. As IEEFA points out in its Delhi policy feedback, the UK requires rapid charger networks to be reliable 99% of the time on average each year, with a free 24/7 helpline at every public site and penalties for non-compliance (Public Charge Point Regulations 2023). UK operators must also publish availability data free of charge so third-party apps stay accurate. California requires 97% uptime for public chargers and real-time availability data from operators (IEEFA).
India already has a lever. PM E-DRIVE’s guidelines cover about 72,300 public charging stations with a ₹2,000 crore outlay and BHEL as the implementation agency, and subsidy is paid in two instalments linked to compliance and performance milestones (Business Standard, September 2025). Uptime-linked support is a recommendation today, not a rule. But with UBC putting many networks onto one map, it is easy to see where policy goes next: when reliability becomes visible, it becomes measurable, and what is measurable gets funded or penalized.
What this means for CPOs, eMSPs and fleets
The shift affects three groups: CPOs, e-mobility service providers (eMSPs, the apps drivers use to find and pay for charging) and fleets. Interoperability turns reliability from an internal operations metric into a public, comparable one. Three things change for operators.
Live status becomes public-facing. Whatever availability data you publish into UBC or a roaming hub is what drivers will see and act on. Inaccurate status is no longer an internal reporting issue. It is a customer-facing promise you are breaking.
Payment success is not session success. UPI removes payment friction, but it also removes the buffer of a prepaid wallet. Every failed session after payment needs fast, automatic reconciliation and refunds, or it turns into a dispute.
Multi-protocol is the new normal. UBC uses Beckn. Roaming partners and aggregators commonly use OCPI, chargers talk OCPP, and automakers are bringing Plug & Charge, which we wrote about in bringing Plug & Charge to drivers across networks. Operators will rarely get to pick just one. The safer design is one source of truth in the backend, exposed to every channel. Our earlier piece on why EV standardization is key to the future covers why this matters.
For fleets, shared networks are only useful if status data is reliable. Route planning that depends on public charging falls apart when chargers marked “available” on a corridor turn out not to be. See how EV fleets are transforming charging operations for more on that shift.
What CPOs should do now
These steps are ordered by urgency. None of them depends on whether or when you join UBC.
This week: measure honestly. Baseline uptime and session-success rate per charger, not per site. Identify the bottom 10% of chargers and start there.
This month: make status data trustworthy. Use OCPP heartbeats and status notifications to drive your availability feed, and mark faulted units unavailable automatically instead of waiting for a field report.
This quarter: shorten time to repair. Add remote diagnostics and resets, set fault-resolution targets, and build field playbooks for the common failures. Where theft is a problem, budget for tamper-resistant cables and connectors.
Before you onboard to any shared network: close the payment loop. Reconcile payment and session states in real time, and refund failed sessions automatically.
Ongoing: stay protocol-agnostic. Keep your backend able to serve Beckn, OCPI and OEM integrations from the same data.
What not to do: do not treat UBC as fully national yet, since it is still a pilot. Do not tear out existing apps or customer relationships. And do not publish availability data you cannot keep accurate. A charger marked “available” that fails does more damage than one marked “offline”.
Frequently asked questions
How does Unified Bharat eCharge work?
Unified Bharat eCharge (UBC) is a government-backed interoperable EV charging network from the Ministry of Heavy Industries, BHEL and NPCI BHIM Services. Built on the open Beckn protocol, it lets drivers find participating chargers and pay over UPI through the BHIM app. Its pilot, announced in September 2026, covers Maharashtra, Karnataka, Delhi-NCR, Haryana and Rajasthan.
Do drivers need a separate app to use UBC?
No. During the pilot, drivers use the BHIM app to find a UBC-enabled charger, scan its QR code and pay from their bank account over UPI, without creating an account with each charging operator.
Why do so many public EV chargers in India not work?
IEEFA’s 2024 Delhi study found about 84% of sampled chargers were not functional, mostly because of theft of connectors and cables and poor maintenance. Low early usage and a lack of incentives for operations and maintenance meant many chargers were installed but not looked after.
Will EV charging subsidies be linked to uptime?
Not yet. IEEFA recommended in September 2026 that public financial support for chargers be linked to verified uptime and performance, similar to the UK’s 99% uptime rule for rapid chargers. It is a policy recommendation, not current regulation.
The bottom line
Unified Bharat eCharge is a genuine step forward. It does for EV charging access what UPI did for payments: one rail, many providers. But it shifts the weak point from the app to the charger itself, and from private dashboards to a shared public map. The operators who fix status data, repair times and payment reconciliation now will be ready for whichever shared network, and whichever uptime rule, comes next.
Numocity’s charging platform supports CPOs, eMSPs and fleets across 26+ countries. If you are working out how to raise uptime and session success across your network, talk to our team.
Cover image: “Power cables plugged into an electric vehicle charging station” by Ivan Radic, CC BY 2.0, via Flickr. Cropped.
