ChargeIndia Hub DocsWhen roaming via ChargeIndia Hub, partners maintain one credentials relationship with the Hub (IN / CIH, role HUB). Catalog and session data still belongs to the owning CPO. URL paths on async pushes identify the data owner, not the caller.
Summary
| Layer | Identity |
|---|---|
| Authorization token on inbound Hub calls | Hub token from credentials exchange |
{country_code}/{party_id} in URL path (locations, tariffs, sessions) | Owning CPO |
Credentials roles | Your own party + Hub (HUB), not every roaming CPO |
Do not reject Hub pushes because the path party is absent from your credentials roles.
Common migration mistake
In peer-to-peer mode, the authenticated party and the path party are usually the same counterparty. Via Hub, they are different: auth = Hub, path = CPO. This is expected OCPI Hub behavior.
Role-specific guides
| Role | What to implement |
|---|---|
| CPO | Push with your own {cc}/{pid}; set cdr_token on sessions |
| eMSP | Accept CPO path parties on receivers; validate via HubClientInfo + routing |