For charging networks
Put your chargers in front of more EV users
FillFast is an eMobility Service Provider (eMSP). Your chargers stay on your own system. Connect your Charge Point Operator (CPO) back office to us over OCPI, and customers can find, start and pay for charging on your stations. Roaming hubs and other eMSPs can connect the other way too.
On the network
Your chargers, in the FillFast app
Chargers keep reporting to your CSMS over OCPP. Your CSMS shares locations, status, sessions and CDRs with FillFast over OCPI, and customers see each change as it arrives.
Where FillFast fits
Your chargers stay on your system
In the most common setup, your chargers keep talking OCPP to your own CSMS, and FillFast connects to your CSMS over OCPI, the roaming protocol between operators (CPOs) and service providers (eMSPs).
OCPI · FillFast consumes
Your network in FillFast
You keep your CSMS. FillFast receives your locations, tariffs, sessions and CDRs, and FillFast customers charge on your stations.
OCPI · FillFast provides
FillFast's network for your users
For eMSPs and roaming hubs: receive the chargers FillFast manages or is authorised to share, so your customers can use them.
OCPP 1.6J / 2.0.1
FillFast as your CSMS
Where FillFast runs charger management for you, your chargers connect to FillFast directly. Arranged per project and tested with your hardware.
EV charger
Your hardware
OCPP 1.6 / 2.0.1Your CSMS
CPO back office
OCPI 2.2.1FillFast
eMSP
App & walletCustomer
FillFast app
OCPP
Charger ↔ CSMS. Stays between you and your hardware, unless FillFast runs your CSMS.
OCPI
CPO ↔ eMSP. How your network shares locations, prices and sessions with FillFast.
Roaming hub?
Already connected to a roaming hub over OCPI? We can reach you through the hub instead.
OCPI 2.2.1
Standard roaming, module by module
Each connection uses only the modules both sides support, agreed per direction and validated in a sandbox before go-live. A network with its own proprietary API may need extra integration work.
/ocpi/2.2.1/versions
Both waysVersions
Version and endpoint discovery, so each side knows exactly what the other supports.
/ocpi/2.2.1/credentials
Both waysCredentials
The credentials handshake that sets up the connection. Tokens can be rotated without downtime.
/ocpi/2.2.1/locations
CPO → eMSPLocations
Your stations, EVSEs and connectors, with status updates as they change.
/ocpi/2.2.1/tariffs
CPO → eMSPTariffs
Your pricing, shown to users with taxes before they start.
/ocpi/2.2.1/tokens
eMSP → CPOTokens
We share user tokens so your chargers can authorise FillFast customers.
/ocpi/2.2.1/commands
eMSP → CPOCommands
Remote start and stop from the FillFast app, where your network supports them.
/ocpi/2.2.1/sessions
CPO → eMSPSessions
Session updates: energy delivered and running cost.
/ocpi/2.2.1/cdrs
CPO → eMSPCDRs
Final charge records, the basis for billing, settlement and reconciliation.
Onboarding with clear gates
Saving a connection never switches it on. It goes live only after every check passes. Your team then gets a provider portal for connection health, sync status, sessions and CDRs, invoices and credential rotation.
- 01Share your OCPI versions endpoint and a credentials token. Secrets go straight to a secure store
- 02We run the credentials handshake and endpoint discovery, and map the modules both sides support in each direction
- 03Agree commercial terms: subscription, per-session, per-kWh, commission or tiered pricing
- 04Validate together in a sandbox: locations, tariffs, sessions, CDRs, and start/stop where supported
- 05Go live once every check passes. Health and sync are monitored from then on
Running a fleet or charging sites?
FillFast Fleet gives your drivers every partner network with spending policies and one invoice. FillFast Station gives site owners chargers, tariffs, sessions and settlement in one portal.
See the products- App access with per-driver limits
- Per-vehicle charging reports
- One invoice across networks