eMSP Certification

Use this checklist after completing Onboarding and the eMSP Integration Guide. It confirms end-to-end readiness for production traffic.

Coordinate UAT sessions against Sandbox (https://sandbox-hub.chargeindia.com) with your ChargeIndia account team. See Coordinated testing and Environments in Getting Started.

Shared verification

[ ] Credentials exchange complete (POST + PUT /ocpi/2.2.1/credentials)
[ ] Hub token stored securely; Authentication implemented on all outbound calls
[ ] GET /ocpi/versions and GET /ocpi/2.2.1 succeed with Hub token
[ ] Party appears as CONNECTED in GET /ocpi/2.2.1/hubclientinfo
[ ] Receiver URLs registered with account team
[ ] Routing rules enabled for target partner networks
[ ] Logging captures X-Request-ID and X-Correlation-ID for support

Outbound calls to Hub

[ ] Token authorization to routed CPOs via Hub
[ ] START_SESSION / STOP_SESSION commands with valid response_url
[ ] GET locations and tariffs return routing-filtered results
[ ] Pagination handled for large catalogs

Async receivers

[ ] Locations/tariffs receiver accepts Hub pushes with CPO path party (not Hub CIH)
[ ] Sessions receiver accepts async PUT with CPO {country_code}/{party_id} in path
[ ] CDRs receiver accepts async POST
[ ] Receivers are idempotent (safe on Hub retries)

Hub receiver identity

[ ] Inbound pushes authenticated with Hub token
[ ] Path party validated via HubClientInfo + routing, not credentials roles alone
[ ] No HTTP 400 from P2P-style party mismatch - see Hub Receiver Identity (eMSP)

End-to-end session (with account team)

[ ] Authorize → start → active session → stop → CDR received on your receivers
[ ] Command async result delivered to your response_url

See Session Lifecycle for the full flow.

Sign-off

When all items pass, request production cutover from your account team. Keep this checklist updated for regression testing after platform changes.