Registration is the record, not the connection
The operator registers a station, charger and its connectors in the platform. A serial number helps identify the physical device, but entering it into a dashboard does not remotely discover or connect that device.
Configure the charger
An authorised installer or operator configures the charger with the CSMS endpoint, a unique charge-point identity and the required credentials or certificates. The hardware must have usable internet access. The charger initiates the connection to the backend; the website does not directly control the electrical hardware.
OCPP is the shared language
The Open Charge Point Protocol defines communication between charging equipment and a management system. It covers functions such as status reporting, transaction records and remote commands. Wouri initially targets OCPP 1.6J over a secure WebSocket. Other OCPP versions are not automatically interchangeable.
Identity is not authentication
A charger ID names the device. A secret key or certificate demonstrates that the connecting device is authorised to use that identity. Without authentication, another device could try to impersonate a registered charger. Credentials must be unique, protected and never published in a website or repository.
Test the full loop
Before opening to drivers, validate connection, status, pricing, payment confirmation, remote start and stop, meter readings, final cost and interrupted-session handling. OCPP support on a product sheet is useful, but is not proof of interoperability with every management system.
Wouri is in development. Pilot locations, payment providers and launch timing will be announced after validation.