Map charger data
Confirm status, meter values, transaction records, alarms and remote commands required by the operating platform.
OCPP 1.6J / 2.0.1 Charging Platform Integration
Connect compatible EV chargers to a local CSMS using OCPP 1.6J or OCPP 2.0.1, then coordinate remote operation, payment and project API requirements before deployment.
Application fit
Start from the site operation.
The charger, communication controller, CSMS, payment route and customer-facing application are one operating chain. Protocol version, message scope, security, network access and responsibility must be documented together.
- Charge point operators
- Public charging networks
- Commercial site owners
- Local platform integrations
Confirm before quotation
- OCPP version
- CSMS responsibility
- Payment provider
- API and data fields
Site planning
Three decisions before selecting the cabinet.
Connect the CSMS
Select OCPP 1.6J or 2.0.1, define network and security settings, and validate the required message set in a test environment.
Integrate local services
Coordinate HTTP or project API fields for web, app, QR or POS operation, then complete project-specific acceptance tests.
Platform architecture
From charger data to local operation and payment.
The final interface list is fixed during project review. Each connection point has an assigned owner, test environment and acceptance record.
Status · meter values · sessions · faults
OCPP 1.6J or 2.0.1 · remote commands · configuration
Web · app · QR · POS · operator reporting
Remote operation
Monitor charger availability, transactions and alarms; coordinate remote start, stop, configuration and approved update functions.
Local platform connection
Use the customer or CPO backend when documentation, test access, authentication and required messages are available.
Payment coordination
Define the QR or POS provider, settlement party, terminal requirements and data exchange before equipment configuration.
Recommended equipment
Compare all charging products →Compare charger ranges that fit this operating model.
Final sizing depends on the vehicle, connector, simultaneous demand and available site power.
Project configuration
Hardware, payment and platform are confirmed together.
Delivered branding, documentation, integration and warranty scope are matched to the final order.
- CCS1 · CCS2 · GB/T by model
- RFID · QR · POS options
- OCPP · API · 4G · RJ45 options
- Remote support and project-specific service
FAQ
Questions buyers ask before configuration.
Which OCPP versions can be coordinated?
Relevant configurations can support OCPP 1.6J or OCPP 2.0.1. The selected charger controller, backend feature set and acceptance procedure are confirmed before quotation.
Can MAINERAY connect chargers to a local CSMS?
MAINERAY can coordinate integration after the CSMS documentation, test endpoint, credentials process, required messages and system responsibilities are provided.
How long does payment or API integration take?
Timing depends on the local bank or payment provider, API documentation, sandbox access, terminal compliance and acceptance testing. The schedule is confirmed for each project rather than promised as a fixed lead time.