NEW IN EVBOOST

Many networks.
One balance.

Find EVBOOST Connect stations, top up your balance and start charging right on the site or in the app.

Find a charger How EVBOOST Connect works →
EVBOOST
Get EVBOOST Pro Sign in
EVBOOST
Sign in Download the app

One integration. More channels. More charging sessions.

Connect once — and your network becomes visible to drivers on EVBOOST, other eMSPs, banks, fleets and OEMs - without losing control over your stations, tariffs and operating model.

Get a proposal View the architecture
OCPI / API Session routing CDR and reconciliation Partner channels
Hub online OCPI / API
EVBOOST Roaming Hub
CPO Charging networkstations, tariffs, statuses
APP eMSPusers and session start
BNK Banksco-branding and loyalty
FLT Fleetsaccess and reporting
OEM Carmakersin-car charging
API Partnerswhite-label and API
Live data locations, statuses, tariffs
Remote start session start and stop
Settlement CDR, reconciliation, fees
Why the market is fragmented

No new integration should start from scratch.

One CPO.
Dozens of potential demand channels.
01

Every partner asks for its own API flow

Separate formats for authorisation, statuses, session start, errors, tariffs and reporting drive up the cost of every new partnership.

02

Roaming often comes down to a mere technical connection

The stations are connected, but there is no clear channel for driver acquisition, conversion to sessions or joint growth scenarios.

03

A failed session passes through several teams

Without end-to-end traceability, it's hard to quickly see where the error occurred: in the app, the roaming layer, the CPO backend or at the station.

04

Reconciliation turns into manual operational work

CDRs, tariffs, refunds, fees and discrepancies pile up in different systems and slow down partnership scale-up.

Partnership architecture

EVBOOST becomes a controlled layer between your network and distribution channels.

We don't replace the operator's backend. We standardise connections, route sessions and create a single model for working with different partners.

Supply layer Your network
Locations and EVSEs

Network structure, connectors, power and availability.

Tariffs and rules

You set pricing, restrictions and commercial terms.

CSMS / backend

Stations and operational control stay in your system.

Roaming layer EVBOOST Hub
Single integration

OCPI or an agreed API adapter to your backend.

Session management

Authorisation, remote start/stop, statuses, errors and CDRs.

Monetisation rules

Fees, partner models, reconciliation and financial reports.

Demand layer New channels
EVBOOST

Map, routes, app and our own driver audience.

Enterprise partners

Banks, fleets, leasing, insurers and loyalty programmes.

API / white-label

Embedded charging flows in third-party products.

The CPO stays in control

We open your network to partners, but we don't take it away from you.

Roles are fixed before launch: who sets the tariff, who takes the payment, who supports the user and who is responsible for the technical side of the session.

Stays with the CPO

Control of the charging network

  • Ownership and management of charging stations
  • Tariffs, availability and usage rules
  • CSMS, technical logs and equipment operation
  • Merchant/payment logic - according to the agreed model
  • The final say on which partner channels are available
Handled by EVBOOST

Roaming and distribution layer

  • A single connection flow for partner products
  • Routing of remote start/stop and session statuses
  • User interface and start context
  • CDR reconciliation, fees and partner reporting
  • Conversion analytics and joint growth campaigns
Demand ecosystem

Connecting to EVBOOST can open more than one B2C channel.

The same technical foundation lets you roll out new distribution models step by step, without a separate integration for each partner.

Core channel

EVBOOST takes the driver from station search to a completed session.

Map, route demand, station card, charging start and session history work as one measurable funnel for the operator.

Map and search Trip Planner Roaming start Session analytics
Enterprise distribution

Banks, fleets and loyalty programmes

Co-branded tariffs, corporate access, bonus mechanics and charging as part of a broader customer product.

Embedded charging

OEM, logistics and mobility platforms

API or white-label scenarios where charging is built into the car, a fleet dashboard or a partner app.

Commercial model

The format depends on who takes the payment and what role EVBOOST plays.

At the discovery stage we agree on the flow of funds, responsibility for refunds, support, fraud, logs and SLA - and only then fix the final model.

The principle: transparent economics for every session.

There should be no “black box” in the operator model. The CPO sees where a session came from, how it was calculated and which fee was applied.

01
Single session ID and CDRTechnical and financial traceability of every transaction.
02
Agreed reporting periodRegular reconciliation with no manual hunting for sessions across systems.
03
A model that scalesA new partner channel doesn't change the CPO's core integration.
Model A Fee per session

EVBOOST receives an agreed service or transaction fee for each successful roaming session.

Model B Platform fee

A fixed fee for roaming infrastructure, support, reconciliation, SLA and an agreed scope of integrations.

Model C Hybrid

A base platform fee plus a variable part for sessions, partner channels or additional B2B modules.

Optional Growth modules

Location promotion, route demand, analytics, pricing and joint campaigns can be added separately.

Launch plan

From the first technical call to a controlled commercial pilot.

We start with a small scope, test the full cycle on real stations and scale only once operation is stable.

01

Discovery and role map

We define the backend, protocol, payment flow, support model, refunds, logs, SLA and commercial expectations.

Result Architecture and agreed scope
02

Integration and test environment

We connect locations, tariffs, statuses, remote start/stop, sessions and CDRs in a sandbox or restricted environment.

Result A completed end-to-end flow
03

Pilot on selected stations

We open 5–10 stations, or an agreed number, and monitor starts, errors, support and reconciliation.

Result Real sessions and a reliability report
04

Scale-up and new channels

We extend the integration across the network and add partner products, analytics and joint campaigns.

Result A full roaming partnership
EVBOOST Roaming for CPO

We'll design a connection scheme built for your network.

Describe your backend, number of stations, current integrations and preferred payment flow. We'll prepare a proposal covering the architecture, pilot and commercial model.

✉️ info@evboost.com.ua 🔒 NDA before any technical or commercial information is shared ⚡ OCPI, custom API and non-OCPI discovery