Configure your charge point's Central System URL and Charge Point Identity separately.

1. Open your charge point's config interface (local UI or manufacturer app).
2. Set Central System URL to the endpoint above.
3. Set OCPP Protocol to ocpp1.6.
4. Enter the password from Step 3 in the security / Basic Auth field.
5. Save and reboot — the CP should appear in Step 4 within seconds.

Each charge point requires a password to authenticate with the WebSocket endpoint. Email us with your CP ID and we will set it up for you.

Every RFID card or app token must have a matching User record with an id_tag field. Unknown tags are rejected.

1. Log in to the admin dashboard → Users → Add User.
2. Set ID Tag to the exact string the charge point sends (e.g. 04A3F12B for a Mifare card UID).
3. Save — takes effect immediately, no restart needed.

The driver app is a mobile-friendly web page — no installation required. Drivers scan a QR code posted at the charger to open it.

Peer with another charging network so their stations appear in our EV driver app's roaming list — and, if they run their own eMSP, ours appear in theirs. This is the OCPI 2.2.1 Credentials handshake, not a custom integration.

1. Exchange party info: Party ID, country code, business name, and role (CPO, eMSP, or both).
2. Send us your OCPI Versions URL and a Token A over a secure channel (see email below) — never post credentials in a support ticket or chat.
3. We run the Credentials handshake from our side — it registers both directions in a single call.
4. Once registered, we sync your published Locations. Your stations typically appear under "Roaming stations near you" within a few minutes.
5. If you also run an eMSP, your Tokens are pushed to us the same way — your drivers can then charge at our stations too.

A lightweight mobile dashboard for whoever physically hosts the charger — no admin account, no separate login. It logs in with the exact same CP ID and password from Step 3, since that's the same credential already proving they control the charger.