Chargers, Telematics and Payments On One Platform
💡 EV Fleet System Integration: Key Highlights
- Integrate in one fixed order — chargers, telematics, payments, then data rules. Each layer consumes identifiers the previous one creates, so teams that start with payments rebuild them.
- OCPP 1.6J still runs most Indian depot hardware, while OCPP 2.0.1 (an IEC standard since 2024) and OCPP 2.1 (2025) add security and smart-charging depth. Build your adapter for both.
- Public charging is a separate integration. India has over 52,700 operational public charging points; reaching them means OCPI 2.2.1 CDRs, not OCPP.
- AIS-140 already fits a GPS + NavIC unit to every new Indian commercial vehicle at roughly ₹6,000–₹11,000 — integrate that feed rather than buying a second tracker.
- Payments carry hard deadlines: GST e-invoicing applies above ₹5 crore turnover, with a 30-day IRN reporting window above ₹10 crore.
- Data ownership is a go-live gate, not paperwork. Driver location is personal data, and full DPDP data-fiduciary obligations bite by 14 May 2027.
Most fleet software projects do not fail on features. They fail on sequence. EV fleet system integration — wiring chargers, vehicle telematics and payment rails into one platform — is a dependency chain, and teams that attack it in the wrong order end up rebuilding the same connector twice. This guide is written for the technical PM or IT lead running that project inside a commercial fleet: a 60-van last-mile operation in Delhi, a 100-cab urban taxi fleet in Bengaluru, or a 40-EV corporate employee-transport fleet in Pune. The stages below are the same for all three; only the volumes and the exception tolerance change. If you are still deciding whether to build on an open stack at all, read the strategy companion to this piece first: why vendor-agnostic EV operating systems win. This one assumes that decision is made and takes you to go-live.
What EV Fleet System Integration Actually Involves
Here is how to think about the scope. An electric fleet generates four streams of machine data a diesel fleet never had: charger telemetry, vehicle battery state, energy cost per session, and driver-to-vehicle-to-session attribution. EV fleet system integration is the work of joining those streams on shared keys, so that one charging event, one vehicle, one driver and one invoice line all resolve to the same trip. The order below is not a preference — each layer produces the identifiers the next one needs, and skipping ahead is how these projects double in length.
| Stage | Layer | Key it creates | Blocked until it exists |
|---|---|---|---|
| 1 | Chargers (depot + public) | Session ID, connector ID, meter values | Everything downstream |
| 2 | Telematics | Vehicle ID, SOC, odometer, location | Cost per km, charge-aware dispatch |
| 3 | Payments & invoicing | Payer ID, tariff, tax document | Reimbursement, CPO reconciliation |
| 4 | Data ownership rules | Access scopes, retention, export rights | Audit, vendor exit, DPDP compliance |
The four integration layers and their dependencies. Stage 3 cannot be reconciled without the session IDs from Stage 1 and the vehicle IDs from Stage 2.
Stage 1: Connect the Chargers, Depot and Public
Depot chargers and public chargers are two different integrations. Treating them as one is the most common scoping error in these projects.
Depot chargers speak OCPP — support two versions, not one
Your depot hardware connects to your platform over the Open Charge Point Protocol. Indian depot fleets run a mix: OCPP 1.6J remains the workhorse on installed hardware, OCPP 2.0.1 — ratified as IEC 63584 in 2024 — adds proper device management and security profiles, and OCPP 2.1, released in 2025, extends into bidirectional charging and distributed energy resources. Specify an adapter that handles 1.6J and 2.0.1 from day one: a fleet that buys 12 new DC units this year and inherits 20 older AC units will run both for years.
The checks that matter here are unglamorous. Confirm the charger emits MeterValues at a usable interval (60 seconds or better, not once per session), that StartTransaction carries an idTag you can map to a driver or vehicle, and that the unit reconnects cleanly after a WebSocket drop. Depot connectivity in Indian industrial estates is not reliable, and a charger that loses its session on every reconnect will corrupt your energy accounting. Your charging management module depends entirely on this layer.
Public charging needs OCPI, a different protocol entirely
India now has more than 52,700 operational public charging points, including over 16,500 DC fast chargers. None of them will speak OCPP to you, because you do not own them. Reaching a third-party charge point operator (CPO) means the Open Charge Point Interface — OCPI 2.2.1 — which is a backend-to-backend protocol with six modules worth knowing: Locations, Sessions, Tariffs, Tokens, CDRs and Commands. Your platform authorises a driver with a Token, watches the Session live, and receives a Charge Detail Record (CDR) that becomes the billable line item. Getting CDR ingestion right here is what makes unified invoicing across multiple CPOs possible later.
Stage 2: Ingest Telematics Data From Vehicles
Indian fleets have a structural advantage here that most global integration guides miss. Under Ministry of Road Transport and Highways notification GSR 979(E), the AIS-140 standard already requires a certified vehicle tracking unit — GPS plus NavIC, panic button, tamper alerts, battery backup — on new commercial vehicles. At roughly ₹6,000 to ₹11,000 per unit, that device is already fitted and already transmitting. Integrating its feed is almost always cheaper than procuring a parallel tracker.
Run two feeds, and reconcile them
AIS-140 gives you location, speed and trip data. It does not give you battery state of charge, cell temperature or DC fast-charge acceptance — those come from the OEM telematics API. So teams run both feeds: AIS-140 for compliance-grade location, the OEM API for battery health. Your integration then has one genuinely hard job — reconciling them onto a single vehicle record keyed on the VIN, with a clear rule for which source wins when odometer readings disagree. Define that precedence rule in writing before you build the connector, not after your first month-end variance.
Set polling intervals by segment, not by default
Poll frequency is a cost decision, not a technical one. A 100-cab taxi fleet in Bengaluru dispatching against live SOC needs 30-second granularity at peak, because a 12-minute-stale battery reading routes a cab to an airport run it cannot finish. A 40-EV corporate shuttle fleet running fixed loops out of a Pune tech park gains nothing from that rate — five-minute polling is sufficient and cuts data volume by roughly 90%. A 60-van last-mile fleet in Delhi sits between the two: tight during the shift, relaxed overnight on depot chargers. Make the interval a per-segment configuration parameter, because you will change it. Everything downstream, including EV vehicle tracking and charge-aware dispatch, inherits what you set here.
Stage 3: Wire the Payment and Invoicing Layer
Payments are where an Indian EV fleet integration diverges most sharply from a global template: three separate money flows have to land in the same ledger.
Three flows, three mechanisms
Depot energy arrives as a DISCOM bill against a connection, and your job is allocating it to sessions using Stage 1 meter values. Public charging arrives as CPO invoices that must reconcile line-by-line against ingested OCPI CDRs. Driver home charging arrives as a reimbursement claim — the messiest of the three; the driver home-charging reimbursement playbook covers structuring the rate. The first is a utility integration, the second a reconciliation engine, the third a payout rail.
Build to the compliance deadlines, not around them
Two Indian rules constrain the design directly. First, GST e-invoicing applies to businesses above ₹5 crore aggregate turnover, and operators above ₹10 crore must report invoices to the Invoice Registration Portal within 30 days of the invoice date — a batch reconciliation job that runs monthly will miss that window on late CPO statements. Second, the Reserve Bank of India consolidated recurring-payment rules into a single e-mandate framework in April 2026: pre-authorised debits up to ₹15,000 clear without a fresh OTP, higher caps apply to specific categories, and a pre-transaction notification is required at least 24 hours before each debit. If your driver reimbursements or corporate charging subscriptions run on auto-debit, that 24-hour notice is a scheduling requirement inside your platform, not a bank problem.
Design this layer so tariff logic sits in one place. Fleets that scatter pricing across a charger config, a spreadsheet and a billing tool cannot answer “what did this trip cost” without a manual join. A consolidated payment management layer prevents exactly that; the broader commercial logic sits in our EV fleet payments strategy piece.
Stage 4: Define Data Ownership Rules Before Go-Live
This is the stage teams postpone and then cannot retrofit. Once three vendors are writing into your stack, renegotiating who owns what costs leverage you no longer have.
⚠️ The clause that decides your exit cost
Ask every vendor one question in writing before signature: “On termination, in what format and within how many days do we receive the full historical session, telematics and transaction data?” A vendor that answers “CSV export on request” is describing a manual favour, not a right. The answer you want is a documented API with no volume cap and a stated retention period — and it belongs in the contract, not the sales deck.
Driver data is personal data under the DPDP Rules
India’s Digital Personal Data Protection Rules, 2025 were notified in November 2025 under the DPDP Act, 2023, phased in through consent-manager registration from November 2026 to the full data-fiduciary regime by 14 May 2027. Continuous driver location, shift patterns and home-charging addresses are personal data under that framework, which makes the fleet operator a data fiduciary. That means three concrete things in your integration: consent capture that is specific and revocable inside the driver app, role-based access so a depot supervisor sees their depot and not the whole network, and a retention period after which granular location rows are aggregated away. Build them as configuration now, not as a compliance scramble in 2027.
Write the access matrix before the first API key
A workable matrix has four rows — charger vendor, telematics provider, payment processor, platform — and three columns: what each may read, what each may write, and what each may never see. In practice, teams usually discover the charger vendor has been reading driver identity it has no operational need for, purely because the idTag mapping was convenient. Fix that at design time; it costs nothing then and is a breach notification later.
The EV Fleet System Integration Checklist: A 90-Day Sequence
Here is the sequence that works for a fleet of 40 to 150 vehicles. Larger networks stretch the timeline; they do not reorder it.
Days 1–25
Chargers online
Inventory every connector and its OCPP version. Stand up the OCPP 1.6J and 2.0.1 adapter, verify MeterValues intervals and reconnect behaviour, then sign the OCPI 2.2.1 credentials handshake with your first CPO. Gate: one clean CDR received end-to-end.
Days 20–45
Telematics ingested
Connect the AIS-140 feed and the OEM battery API. Reconcile both onto the VIN, publish the source-precedence rule, and set polling intervals per segment. Gate: SOC and odometer agree within tolerance across a full week.
Days 40–70
Payments reconciled
Map DISCOM bills to depot sessions, CPO invoices to OCPI CDRs, and driver claims to a payout rail. Wire GST e-invoicing inside the 30-day IRN window and add the 24-hour pre-debit notice. Gate: one month-end closes without a manual join.
Days 60–90
Data rules enforced
Publish the access matrix, turn on role-based scopes, capture driver consent in the app, set retention and aggregation, and test the contractual data export for real. Gate: a full historical export lands and parses.
Notice the overlaps. Stages start before the previous one finishes, but no stage’s gate is cleared out of order — that is the discipline the sequence protects. The most expensive failure mode is a fleet that goes live on payments in week six with charger identifiers still unstable, then spends a quarter explaining variances to finance.
None of this requires building four integrations from scratch. That is the case for consolidating on a fleet operating system like YoMobility, which ships the charger, telematics and payment connectors as configuration rather than bespoke engineering — and, more importantly, keeps the joins between them in one schema, so a session, a vehicle and an invoice line resolve to the same trip on day one. If your EV fleet system integration is starting now, model your actual charger mix and telematics sources against the 90-day sequence above before you commit budget.
Frequently Asked Questions
You need both if your vehicles charge anywhere other than your own depot. OCPP connects chargers you control to your platform; OCPI connects your platform to charge point operators you do not control, and delivers the Charge Detail Records you bill against. A pure depot-charging fleet can start with OCPP alone, but most last-mile and taxi fleets hit public charging within the first year.
Yes, for location, speed and trip data — that is what the AIS-140 unit is certified to provide, and it is already fitted on new Indian commercial vehicles. It will not report battery state of charge or cell temperature, so pair it with the OEM telematics API rather than replacing it. A second GPS tracker duplicates a device you already pay a subscription for.
For a 40 to 150 vehicle fleet on a platform with existing connectors, about 90 days across four overlapping stages. The variable is rarely the software — it is how many distinct charger models and OEM APIs you run. Each extra charger firmware version adds roughly a week of testing, which is why the connector inventory belongs in week one.
Whatever your contract says — which is why the export clause matters more than the marketing claim. Insist on a documented API export of full historical session, telematics and transaction data, with no volume cap and a stated turnaround on termination. Separately, driver location and home-charging addresses are personal data under India’s DPDP framework, so your fleet carries data-fiduciary obligations regardless of which vendor stores the rows.
You build a billing layer against identifiers that are still changing. Reconciliation depends on stable session IDs from the charger layer and stable vehicle IDs from telematics; if either is renumbered mid-project, every mapping is rewritten and historical invoices stop tying back. Teams that take this shortcut typically lose a quarter to variance investigation at month-end close.
Sources: Open Charge Alliance — OCPP protocol versions | Ministry of Road Transport & Highways — AIS-140 vehicle tracking mandate | GST e-Invoice Portal — e-invoicing thresholds and IRN rules | Reserve Bank of India — Digital Payments E-mandate Framework | Press Information Bureau — DPDP Rules, 2025 notified
Manage Your Fleet’s Charger, Telematics and Payment Integrations Today
Bring us your charger mix, your telematics sources and your CPO list. We will map them against the 90-day sequence and show you exactly where your integration risk sits before you commit a rupee of budget.
Book a Free Demo