Connect charging to the
rest of your business.

Bring payments, roaming partners and your own software into the same charging operation. With connected services and the EOSVOLT Public API, charging data and actions can work across the systems your business relies on.

Payment providers, card terminals, reporting tools, fleet software, roaming hubs, direct partners, national access points and your own applications connected to EOSVOLT
Connected services

Give customers
familiar ways to pay.

Bring payment providers and card terminals into your charging service, with the methods that fit how customers pay in your markets.

Payment providers

Connect payment gateways for card payments, checkout and prepaid wallets. Build your payment setup around local preferences, currencies and the way you bill customers.

Logos of payment providers the platform connects to, including Stripe, Adyen and Mercado Pago

Payments at the charger

Accept card payments directly at the charger through integrations with Payter, Nayax and Vourity terminals. Give drivers a way to pay without creating an app account.

Payter, Nayax and Vourity, the supported payment terminal brands
Logos of payment providers the platform connects to, including Stripe, Adyen and Mercado Pago
Payter, Nayax and Vourity, the supported payment terminal brands
Roaming

Reach drivers beyond
your own network.

Use OCPI 2.2.1 to connect with roaming partners. Make your chargers available through other services, give your app users access to partner networks and share charger data with national access points.

Roaming as a CPO

Let drivers from partner services find and charge at your locations. Connect through roaming hubs such as ENAPI and Gireve, or establish direct OCPI relationships with other providers, while managing your own charging network and commercial terms.

Roaming as an eMSP

Give your app users access to charging locations beyond your own network. Bring partner chargers into your branded app through roaming hubs or direct connections, so customers can charge across participating networks.

National access points

Share charger data with national access points using OCPI where your market requires it. Manage these data connections alongside your roaming hubs and direct partners.

Roaming as a CPO

Roaming as an eMSP

National access points

One operator’s charger shown in three partner apps
Chargers from several networks on the map of one app
EOSVOLT connected to direct OCPI partners, roaming hubs and a national access point
Public API

Put charging data to work
beyond the dashboard.

Connect EOSVOLT with the reporting, fleet and customer systems you already use. Our Public API gives your applications access to charging resources and documented actions.

Charging data and resources

Work with chargers, connectors, sessions, bookings and home charging resources through documented endpoints. Authentication and account permissions keep access tied to the right users and systems.

Your business systems

Bring charging sessions, energy, costs, vehicles and charge-key data into your reporting or fleet software. Use API workflows to start and stop charging or create bookings from your own applications.

Custom integrations

Build around the workflows your business needs. Start with the available endpoints, test your integration in staging and work with us to evaluate any additional development.

Charging data and resources

Your business systems

Custom integrations

Chargers, connectors, sessions, bookings and home charging connected to the Public API
The Public API connected to reporting software, fleet software and your own applications
The production and staging environments of the Public API and its versioned routes
For developers

Start building with
the Public API.

Give your development team a clear starting point, with API authentication, endpoints, request parameters and example responses documented in one reference. Test your integration in staging before connecting it to production.

The token request of the Public API reference: client credentials in exchange for an access token
Customer story

Charging connected
to a wider
fleet ecosystem.

WHA Logistics Mobilix uses EOSVOLT for its commercial fleet charging service. Through Voltality VoltNet, its chargers connect with roaming and API services that support WHA’s branded app and access to live charging data.

Frequently asked questions

Can we connect our own payment provider?

We can review your payment provider and the payment methods your business needs. EOSVOLT can work with multiple connected gateways in a deployment, with a default provider selected for the account. Additional integrations can be considered as development work.

Does roaming give us access to every charging network?

Roaming gives you access to networks connected through your OCPI partners. The networks, services and data available depend on the roaming hubs or direct agreements you establish.

Can we keep our existing customer app?

We can review your application’s requirements against the EOSVOLT Public API and available integrations, and help you plan an approach that supports the customer journey you want to offer.

Are all integrations included by default?

Your integration setup depends on the services your business uses, the modules selected for your account and any necessary agreements with third-party providers.

Can our developers test before going live?

Yes. The Public API has separate staging and production environments, with documented versioned routes to help you develop and test integrations.

Who connects the payment terminal to EOSVOLT?

The EOSVOLT team adds and links the payment terminal to your account. Share the terminal and the charging locations or chargers where it will be used, and we’ll handle the platform setup.

What would you
like to connect?

Tell us about your payment providers, roaming partners and business systems. We’ll help you plan how they can work with EOSVOLT.