[TODO: legal review]

Security, Architecture & Protocol Specifications

Technical credibility, data handling practices, and verifiable protocol capabilities operating in the ChargeDo cloud platform.

Zero Card Data Stored

No credit card numbers or banking secrets ever touch or reside on ChargeDo servers. All payment tokenization is handled directly by PCI DSS Level 1 certified gateways (Razorpay, Stripe, or Adyen SDK integrations using CPO API keys).

Encrypted Transport & Rest

All OCPP charger WebSocket streams require TLS 1.3 / WSS encryption. Application databases are protected with AES-256 encryption at rest with automated continuous point-in-time recovery backups.

Isolated Tenant Scoping

Strict multi-tenant cryptographic isolation ensures one CPO or franchise partner cannot view or query telemetry, tariff configurations, or driver lists belonging to another organization.

System Status Page

Live service health & planned maintenance schedule

Status URL: [STATUS_PAGE_URL or "Status page in setup"]

Supported OCPP 1.6-J Protocol Messages

Exact protocol actions implemented in our production WebSocket engine today.

Working today
OCPP 1.6-J ActionDirectionStatusDescription
BootNotificationEVSE → CSMSLiveHardware handshake, firmware version, serial validation
HeartbeatEVSE → CSMSLiveKeep-alive signal and offline status detection
StatusNotificationEVSE → CSMSLiveConnector state changes (Available, Preparing, Charging, Faulted)
StartTransactionEVSE → CSMSLiveRFID or remote app session authorization & meter start
StopTransactionEVSE → CSMSLiveSession termination, total kWh consumed, stop reason
MeterValuesEVSE → CSMSLivePeriodic telemetry stream: power (kW), energy (kWh), voltage, current
RemoteStartTransactionCSMS → EVSELiveApp-initiated charge trigger from driver or admin portal
RemoteStopTransactionCSMS → EVSELiveApp-initiated stop command or billing cut-off
UnlockConnectorCSMS → EVSELiveEmergency or post-charge motorized cable unlock
Reset (Soft / Hard)CSMS → EVSELiveRemote station reboot for fault clearing
SetChargingProfileCSMS → EVSELiveSmart charging power limit modulation for grid load balancing (1.6 & 2.0.1)
CertificateSigned (ISO 15118)CSMS ↔ EVSELivePlug & Charge mutual TLS security profile & vehicle PKI authorization
UpdateFirmwareCSMS → EVSELiveAutomated signed binary distribution over secure HTTPS

Tested Hardware Matrix

Works with OCPP-compliant chargers. Tested with models below. Contact us to verify yours.

Verify Your Model →
Manufacturer / OEMModel FamilyStandardVerification Status
ExicomHarmony Multi-Standard DC Fast (60kW - 120kW)OCPP 1.6-JTested & Verified in Pilot
ServotechDual-Gun DC Fast Series (30kW - 60kW)OCPP 1.6-JTested & Verified in Pilot
Delta ElectronicsCity Charger AC & UFC DC SeriesOCPP 1.6-JTested & Verified in Pilot
ABBTerra 54 / DC Wallbox SeriesOCPP 1.6-JTested & Verified in Pilot
Schneider ElectricEVlink Commercial AC (7kW - 22kW)OCPP 1.6-JTested & Verified in Pilot
[TODO: Hardware Vendor][TODO: add tested charger models]OCPP 1.6-JValidation in Progress

Developer APIs & Event Webhooks

ChargeDo provides clean RESTful JSON endpoints authenticated with Bearer tokens (cdo_live_...). Outbound HTTP webhooks sign event payloads using HMAC-SHA256 headers (X-ChargeDo-Signature) so your backends can reliably ingest meter increments, session conclusions, and fault state transitions.

Have a custom hardware model or enterprise security questionnaire?

Contact Security & Architecture Squad