The short version.
This page is the authoritative list of which messages, features, and security profiles our backend supports.
Standards we implement
Reliable Charge's charging management system supports the following open standards.
Supported messages & features
The table below summarises which OCPP operations and 2.0.1 features are supported on our central system.
Hardware brands on the network
These are the charger manufacturers currently visible in the Reliable Charge dashboard. Availability varies by site and connector model.
Security & transport
All production connections must use TLS 1.2 or higher. New installations require OCPP Security Profile 3 unless a restricted roaming protocol applies.
- Heartbeat interval: 30 seconds.
- Maximum message size: 32 KB.
- Reconnect backoff: exponential, 5s to 5min, with jitter.
Roaming & OCPI
Reliable Charge operates as both a Charge Point Operator and an e-Mobility Service Provider under OCPI 2.2.1. Roaming connections are established via Hubject and IndianGrid, plus bilateral OCPI peering with major Indian CPOs.
Reporting an interoperability issue
If you observe an OCPP message that is rejected, mis-billed, or behaves contrary to the specification, report it with full session traces. We acknowledge within one working day and provide RCA within ten working days.
- Acknowledge within one working day.
- Provide root-cause analysis within ten working days.
- Publish a public post-mortem if the issue affected interoperability for any partner.
