OCPP backend
OCPP 1.6 and 2.0.1 supported natively. Decisioned authorization callbacks with caching and idempotency. Realtime meter values via AMQP and WebSocket. Compatible with any charger that speaks the spec — we don't maintain a 'supported brands' list because the protocol is the contract.
OCPI 2.2 roaming
Connect to Hubject, Gireve, or any OCPI 2.2 hub. Outbound CDRs, inbound tokens, location push. Roaming partners are added via configuration, not engineering tickets.
Multi-tenant operator portal
RBAC-permissioned dashboard for stations, sessions, tariffs, exports, team access, fleets, reports, push campaigns, audit logs. Every team gets a scoped view; owners see across teams. Activity log per team for audit. The same portal our own operators use every day.
Driver app — yours or ours
Run Connect under your own brand on iOS + Android (white-label), or piggy-back on our existing driver app and user base. Phone OTP, Google, and Apple sign-in. Saved cards via secure binding. Live Activity on iOS, ongoing notification on Android.
Payments — global rails, locally tuned
Card networks (Visa, Mastercard, Amex, JCB, UnionPay, Mir) and digital wallets (Apple Pay, Google Pay) handled end-to-end: authorization holds, settlement, refunds, dispute records. On-site POS via Payter for chargers where drivers want to tap a card and walk away. Local payment rails — ArCa, Idram, Telcell, M-Pesa, Fawry, PIX, and country-specific schemes — pluggable per market. Tax line-items, fiscal receipts, refund/dispute trail configurable per country.
REST API + webhooks
Everything the operator portal does, exposed as REST with OpenAPI 3.1. Webhooks for session start/stop, payment events, and charger state changes. Token-scoped credentials. Integrate with your existing CRM, accounting, or fleet system without screen-scraping.