# E-Gridium · ChargeBridge

> E-Gridium operates ChargeBridge, the OCPI roaming and clearing hub where charge point operators and e-mobility service providers connect once, decide scope explicitly and settle per period.

Electroop and E-Gridium are separate companies operating under common ownership. ChargeBridge is an E-Gridium product.

Status: Technical connectivity is live for onboarding partners: handshake, data flow and settlement statements. Settlement runs in dry-run until the financial go-live gate closes (data processing agreements with every partner, regulatory registrations, e-invoicing). No partner names or counts are published on this site; connected parties are visible to each other through the hub directory.

## Pages (English; Turkish at /tr)
- [How the hub works](https://egridium.com/en/how-the-hub-works) · TR: https://egridium.com/tr/hub-nasil-calisir
- [OCPI modules](https://egridium.com/en/ocpi-modules) · TR: https://egridium.com/tr/ocpi-modulleri
- [Settlement and clearing](https://egridium.com/en/settlement-and-clearing) · TR: https://egridium.com/tr/uzlastirma-ve-takas
- [For CPOs](https://egridium.com/en/for-cpos) · TR: https://egridium.com/tr/sarj-agi-isletmecileri-icin
- [For eMSPs](https://egridium.com/en/for-emsps) · TR: https://egridium.com/tr/mobilite-hizmet-saglayicilari-icin
- [Onboarding and sandbox](https://egridium.com/en/onboarding-and-sandbox) · TR: https://egridium.com/tr/katilim-ve-sandbox
- [Trust](https://egridium.com/en/trust) · TR: https://egridium.com/tr/guven
- [Türkiye](https://egridium.com/en/turkiye) · TR: https://egridium.com/tr/turkiye
- [About](https://egridium.com/en/about) · TR: https://egridium.com/tr/hakkimizda
- [Evidence records](https://egridium.com/en/evidence) · TR: https://egridium.com/tr/kanit
- [Developers and MCP](https://egridium.com/en/developers) · TR: https://egridium.com/tr/gelistiriciler
- [Agreements](https://egridium.com/en/agreements) · TR: https://egridium.com/tr/sozlesmeler
- [Apply to connect](https://egridium.com/en/contact) · TR: https://egridium.com/tr/iletisim

## OCPI modules (offer status in brackets)
- credentials (OCPI 2.2.1; CPO both, eMSP both) [offered]: Registration handshake and token lifecycle between a partner and the hub.
- locations (OCPI 2.2.1; CPO sender, eMSP receiver) [offered]: Locations, EVSEs and connectors with live status.
- sessions (OCPI 2.2.1; CPO sender, eMSP receiver) [offered]: Charging sessions in progress, from start to end.
- cdrs (OCPI 2.2.1; CPO sender, eMSP receiver) [offered]: Charge detail records: the billable record of a session.
- tariffs (OCPI 2.2.1; CPO sender, eMSP receiver) [offered]: Tariff definitions with price components and restrictions.
- tokens (OCPI 2.2.1; CPO receiver, eMSP sender) [offered]: Driver tokens (RFID, app) and real-time authorization.
- commands (OCPI 2.2.1; CPO receiver, eMSP sender) [offered]: Remote start, stop, reserve and unlock, relayed through the hub.
- chargingprofiles (OCPI 2.2.1; CPO receiver, eMSP sender) [offered]: Smart-charging profiles set and read through the hub.
- hubclientinfo (OCPI 2.2.1; CPO receiver, eMSP receiver) [offered]: The hub tells each partner which other parties are connected and in which role.
- bookings (OCPI 2.3.0; CPO receiver, eMSP sender) [offered]: Reservation of a charger for a time window, create and cancel.
- parking (OCPI 2.3.0; CPO sender, eMSP receiver) [offered]: Parking-bay information attached to locations.
- payment (OCPI 2.3.0; CPO sender, eMSP receiver) [offered]: Payment-session objects for ad-hoc (card) charging as defined in OCPI 2.3.0.
- tokens (groups) (OCPI 2.3.0; CPO receiver, eMSP sender) [offered]: Grouping of tokens for fleet and shared-account scenarios.
- tr-cdr-additionals (OCPI tr-extension; CPO sender, eMSP receiver) [offered]: Türkiye profile: the CDR fields local regulation and tax rules need, carried as an OCPI extension.

## Not offered (stated explicitly)
- OICP bridge: A bridge exists in the codebase but is not installed in any environment. Partners who need OICP must connect to that network directly.
- webhooks: Partners receive events through the OCPI modules above; a separate webhook delivery channel is not part of the service.

## Roles
- For charge point operators: Publish your locations and tariffs once; decide per partner which eMSP sees which site; receive sessions, CDRs and settlement statements from one place.
- For e-mobility service providers: Receive locations, live status and tariffs from every CPO you have a relationship with; push your tokens once; start, stop and reserve through a single command channel.
- For navigation and data providers: Receive locations, status and tariffs that CPOs choose to publish to you; no sessions, CDRs or settlement, because you neither operate chargers nor sell to drivers.

## Trust (programmes, not certifications)
- ISO/IEC 27001:2022: in-progress, target 2026-12-31
- SOC 2 Type II: planning
- PCI DSS SAQ-A: self-assessment
- No numeric service level is published; service levels are defined in the participation agreement. No fee rates are published.

## Evidence
- [Evidence records](https://egridium.com/en/evidence): every claim links to a dated record stating what it supports and what it does not show. Machine access: https://egridium.com/api/public/v1/evidence

## Machine access
- Public API: https://egridium.com/api/public/v1/modules, /roles, /trust, /evidence (locale=en|tr)
- MCP (read-only, streamable HTTP, stateless): https://egridium.com/mcp
- OpenAPI: https://egridium.com/api-specs/ocpi-adapter.openapi.json, clearing-platform.openapi.json, identity-service.openapi.json
- Full text: https://egridium.com/llms-full.txt

## Related
- Electroop (separate company, common ownership): https://electroop.io