EV charging integrations that hold up in production
i4B builds and maintains the connectors between charge points, CSMS platforms, roaming hubs and your back office. Native protocol implementations, delivered in production across Europe, and looked after by the same team once they go live.
Why charging integrations break after go-live
The connector passes its first tests. Then a partner moves to a new protocol version, a tariff changes, a CDR doesn't match the invoice, and nobody owns the code any more.
Every partner runs a different version
OCPI 2.1.1 on one side, 2.2.1 on the other, OICP for Hubject and ENAPI in the UK. Each one needs its own mapping, and each one keeps moving.
CDRs that don't reconcile
Sessions close on a partner network, tariffs are mapped differently and the numbers reach billing late or wrong. Revenue leaks quietly at the edges.
Every platform has its own API
CSMS, ERP, billing, fleet tools and driver apps all speak differently. Point-to-point scripts pile up until no one can change one without breaking another.
Nobody looks after the connector
Integrations are built as one-off projects and then left alone. When a hub changes its certificate or endpoint, the first to notice are your drivers.
Six integration types we deliver and maintain
Native OCPP, OCPI and OICP implementations, plus connectors to the platforms charging businesses actually run on.
Hubject OICP roaming
CPO and eMSP side. Publish your EVSEs to Hubject or give your drivers access to partner networks across Europe: token exchange, real-time status and CDR processing.
OCPI peer-to-peer roaming
Direct connections with roaming partners on OCPI 2.1.1, 2.2.1 and 2.3: locations, sessions, tariffs, tokens and CDRs, with version handling built in.
ENAPI for the UK
eMSP access to UK public CPO networks through the ENAPI roaming hub: remote start and stop, token forwarding and CDR processing for app users.
Private roaming hubs
CPO-to-CPO roaming inside one multi-tenant platform, without Hubject or GIREVE: token exchange, shared EVSE visibility and session data forwarding.
AMPECO CSMS integration
An integration layer between AMPECO's white-label CSMS and your back office, billing engine or customer app: REST API, webhooks and CDR sync.
OCPP gateways and platform connectors
Charger gateways for OCPP 2.1 and all earlier versions (2.0.1, 1.6), session control and firmware updates, plus connectors between CSMS, ERP, billing and fleet management systems.
Inside the platforms that charge Europe's EVs.
What stands out most is the combination of technical expertise and an understanding of the business context of the project. i4B did not approach the cooperation only as a set of IT tasks to complete but tried to understand why certain solutions were needed and what they meant from our perspective.
Integrations running in production today
A few of the EV charging integrations i4B has designed, built and still maintains for CPOs, eMSPs and charging platforms.
A SaaS platform's operators, published on Hubject
A multi-tenant CSMS wanted its CPO customers' stations visible to eMSPs across Europe. We built the OICP CPO interface: dynamic EVSE updates, real-time status, remote control and CDR reporting.
Roaming for a white-label driver app
An eMSP with its own app wanted roaming through Hubject. We built the OICP eMSP interface into its backend and app: remote control, session handling and CDRs across Hubject networks.
CPOs roaming with each other, no external hub
Several CPOs on one SaaS platform wanted access to each other's stations without Hubject or GIREVE. We built an internal roaming module that exchanges tokens, shares EVSE visibility and forwards session data.
UK public networks in an eMSP app
An eMSP wanted its customers to charge on UK public CPO networks. We integrated ENAPI for remote start and stop, token forwarding and CDR processing inside the mobile app.
AMPECO connected to ERP and invoicing
A B2B operator on AMPECO needed sessions, CDRs and tariffs in its existing back office. We built the REST and webhook integration, tariff sync with the ERP pricing engine and RFID authorisation tied to customer accounts.
A branded app on an AMPECO backend
An eMSP wanted its own app with live session control, driver authentication and usage history. We connected the customer account API to the app, with real-time start and stop, reports and multi-tenant support.
We also deliver the whole platform end to end: driver app, roaming, tariffs and billing.
An integration is not done at go-live
Scope
Partners, protocol versions, data flows and who owns which record. Written down before a line of code.
Build
Connector, data mapping and error handling, built by a dedicated team in 1-2 week sprints.
Test
Charging and roaming flows tested end to end against partner test environments before real drivers use them.
Go live
Staged rollout with monitoring on sessions, tokens and CDRs, so problems surface on a dashboard, not in support tickets.
Maintain
Protocol upgrades, new partners and hub changes handled by the team that built the connector.
One connector or a long-term integration team
Consulting and project discovery
We analyse your partners and systems, define the technical requirements and build a roadmap. Short engagement, billed hourly or per project.
Dedicated development team
Developers, testers and a PM working as an extension of your team. Long-term collaboration with a monthly fee based on team size.
Full project delivery
i4B runs the whole lifecycle, from design to support after go-live. Fixed price or time and materials.
Software vendors can also work with us as a technology, integration or alliance partner: we help bring your product into client environments and onboard it.
Built for the businesses that keep EV charging connected
Charge point operators
Opening your network to roaming partners or connecting your CSMS to billing and ERP.
E-mobility service providers
Giving your drivers access to more networks without rebuilding your app.
CSMS and SaaS platforms
Offering roaming and integrations to every operator on your platform at once.
Charger manufacturers
Making your hardware work reliably with the backends your customers choose.
Tell us what you need to connect
A 30-minute introductory call about your integration needs. We'll look at your setup together and suggest whether to build a connector, reuse what you have or keep it as it is.
Frequently asked questions
Which EV charging protocols do you integrate?
OCPP 2.1 and all earlier versions (2.0.1, 1.6) between chargers and the CSMS, OCPI 2.1.1, 2.2.1 and 2.3 for peer-to-peer roaming, OICP for Hubject and ENAPI for UK networks. i4B is a member of the Open Charge Alliance.
What is the difference between OCPP and OCPI?
OCPP connects a charger to its management system (CSMS). OCPI connects charging businesses with each other, for example a CPO with an eMSP, so drivers can charge on networks they don't have a contract with.
Do you integrate with Hubject on both the CPO and the eMSP side?
Yes. On the CPO side we publish EVSE data, status and CDRs to Hubject. On the eMSP side we connect your eMSP driver app and backend so customers can charge across Hubject partner networks.
Can CPOs roam with each other without Hubject or GIREVE?
Yes, when they run on the same platform. We have built private roaming hubs inside multi-tenant CSMS platforms that exchange tokens, share EVSE visibility and forward session data between operators.
Can you integrate AMPECO with our ERP or our own app?
Yes. We have connected AMPECO to back-office, ERP and invoicing systems through its REST API and webhooks, and built branded driver apps on an AMPECO backend.
Who maintains the integration after launch?
The same team that built it. Protocol upgrades, new roaming partners and hub changes are planned with you, not handled as emergency tickets.
How do you work with us commercially?
Three ways: consulting and project discovery, a dedicated development team, or full project delivery at a fixed price or on time and materials.