EMSP providers

EMP Backend

E-Mobility Provider portal: roaming partners, driver tokens, CDRs, tariff publishing.

Pipelet EMP Backend — OCPI Roaming Hub EMP Backend verbindet Driver- und Fleet-Tokens mit Roaming-Partnern wie Hubject, direkten CPOs und dem Pipelet CPMS über OCPI 2.2 und 2.3. Driver & Fleet Tokens · Contracts Magic-Link · REST PIPELET · EMP BACKEND OCPI Roaming Hub OCPI 2.2 · 2.3 Tokens SENDER Sessions RECEIVER CDRs RECEIVER Tariffs SENDER OCPI 2.2 · 2.3 ROAMING-PARTNER Hubject Intercharge Direct CPOs Peer-to-peer Pipelet CPMS api.pipelet.com

The EMP Backend is a fully-fledged EMSP portal with a built-in OCPI 2.2 server. You onboard CPO partners via a three-step credentials handshake (tokens A/B/C), automatically receive locations and CDRs, roll up monthly per driver and per partner, and publish your own tariffs to roaming partners.

Multi-tenant from day one — multiple EMSP providers in a single instance, each with their own party_id, drivers, and tokens.

For charging providers who want to act as EMSP in addition to CPO operations, or for pure EMSPs without their own infrastructure.

What to expect

OCPI 2.2 server

Full OCPI 2.2 server with credentials, tokens, sessions, CDRs and tariffs modules. Partners onboard via the three-step handshake.

Driver & token management

RFID, app, and ad-hoc tokens per driver. Whitelist mode, contract_id management, real-time token validation to partners.

CDR ingest & monthly roll-up

Incoming CDRs are denormalized and rolled up per driver × partner × month. Export for billing or BI.

Tariff publishing

Maintain your own EMSP tariffs and publish them automatically to all connected CPO partners. Versioning built in.

How EMP Backend fits into the suite

Frequently asked questions

Is Pipelet available as source code?
Yes. Every module is available as a source-access package — complete with Docker Compose, documentation and an SLA support channel. You can audit, customize and self-host.
Which OCPP versions are supported?
Full OCPP 1.6 and 2.0.1 including Security Profiles, Smart Charging, and ISO 15118 Plug & Charge.
Can I use individual modules only?
Yes. Every module is standalone — you can deploy e.g. just the OCPP Broker as infrastructure and build your own CPMS on top.
What does onboarding look like?
We start with a 30-minute call to scope requirements. After that you get a concrete proposal with modules, timeline and price. Pilot typically live in 4–8 weeks.

Sounds like a fit?

Let's talk. 30 minutes is enough for an honest assessment of whether EMP Backend helps you.

You might also like

All products