OCPP and charging platforms FAQ

Charging platforms are relevant when a charger needs remote monitoring, access control, billing, reimbursement, public roaming or fleet reporting. For homes a simple setup is often enough; for businesses, hospitality and multi-site projects the platform choice should be clarified before installation, because it affects connectivity, RFID provisioning and ongoing operating cost.

Key questions

What is OCPP?

OCPP (Open Charge Point Protocol) is the standard communication protocol between an EV charger and a charging platform (operator backend). It allows a charger and a backend from different vendors to exchange status, authorisation, sessions and remote commands without proprietary lock-in. Veton chargers support OCPP and connect to the platform of the customer’s choice — there is no Veton-only cloud.

Which OCPP platforms can a Veton charger be connected to?

The Veton website maintains an overview of platforms used in real Veton installations on the EV charging platforms page. The list covers residential, business, hospitality, fleet and mobility-service-provider platforms. Choosing the platform before installation fixes the connectivity (Ethernet, optional 4G/2G), the RFID provisioning model and the operator that will handle invoicing, reporting and remote support.

When do I need a charging platform?

• Paid or public charging — invoicing, tariffs, settlement.
• Reimbursement at scale — company cars, fleet, multi-tenant residential.
• Multi-site reporting and remote support.
• RFID-based access control with rotating user lists.
• Roaming with eMSPs (so visitors can charge with their own card).

For a single household with a fixed user list, the Veton mobile app already provides session tracking with CSV export, and no cloud platform is strictly required.

What if my OCPP platform or the internet goes down?

Charging itself, load balancing and EMS logic run locally on the Veton charger and (where present) the local energy management system. The OCPP platform is used for authorisation, billing and reporting, but the site continues to charge when the cloud is unavailable. This local-first design is one of the reasons Veton sites stay usable during connectivity outages — the dependency on a single vendor cloud is intentionally minimised.

What should project teams decide upfront?

• Private, semi-public or public use.
• OCPP platform and operator — see EV charging platforms.
• User authentication and access control (open, RFID, app, roaming).
• Billing or reimbursement needs.
• Reporting and support responsibilities.
• Connectivity (Ethernet, optional 4G/2G) and the position of the Veton component box.

See also EV charging platforms, billing and reimbursement FAQ, local OCPP, EMS and cloud management FAQ and energy management & EMS integration FAQ.