OCPP software for hardware-agnostic EV charging
Connect any charger. Integrate everything else.
Flipturn connects to any OCPP-compliant charger, regardless of manufacturer. Renetwork existing chargers to Flipturn without hardware replacement, mix brands across sites, and extend functionality through Flipturn's REST API. No proprietary hardware required, no vendor lock-in.
OCPP 1.6J and OCPP 2.0.1 compliance
Flipturn's CSMS (Charge Station Management System) supports both OCPP 1.6J and OCPP 2.0.1, covering the vast majority of commercially deployed hardware today. OCPP 2.0.1 is the protocol required for NEVI-funded charging stations and mandated by several state funding programs.
OCPP 1.6.J
Full support for OCPP 1.6J including smart charging profiles, remote start/stop, firmware management, and meter values. Compatible with the majority of installed commercial charging hardware.
OCPP 2.0.1
Flipturn supports OCPP 2.0.1 with enhanced device management, improved security profiles, and advanced smart charging. OCPP 2.0.1 is the protocol standard required for NEVI-funded infrastructure and several state charging programs.
OCPP log and message inspection
Full OCPP message logs are available per charger in the Flipturn dashboard, filterable by port, time window, and message type. Useful for debugging integrations, verifying compliance, and supporting hardware vendor escalations. See charger monitoring features →
Hardware-agnostic EV charging
Flipturn's hardware-agnostic EV charging software connects to any charger communicating over OCPP 1.6J or OCPP 2.0.1, regardless of manufacturer. Operators can mix hardware from multiple vendors on the same site and dashboard, with no stranded assets if hardware changes and no dependency on a single manufacturer's roadmap.
50+ charger hardware models supported
Flipturn has tested and deployed with chargers from ABB, Autel, Siemens, Samsung, and others. Any OCPP-compliant charger not on this list can be evaluated for compatibility.
Mixed-hardware deployments
Multiple charger brands can operate simultaneously on the same Flipturn account, across the same or different sites. Mixed-brand configurations are managed from a single dashboard.
Renetworking existing chargers
Chargers can be renetworked to Flipturn without hardware replacement. The transition requires no new equipment and in most cases can be completed without site downtime.
OCPI 2.2.1 and network interoperability
OCPI 2.2.1 (Open Charge Point Interface) is the protocol that enables data exchange and roaming between different charging networks and eMobility service providers. Flipturn supports OCPI 2.2.1 for operators who need cross-network compatibility.
Network roaming
OCPI 2.2.1 support enables Flipturn-managed chargers to participate in cross-network roaming agreements, making chargers accessible to drivers from other networks without requiring a separate account or app.
Data exchange between operators
OCPI 2.2.1 enables standardized exchange of location data, tariff information, session records, and charge detail records between Flipturn and partner networks or eMSPs. This allows operators to share and receive charging data across network boundaries without custom integrations.
Driver authentication across networks
Flipturn uses OCPI 2.2.1 token validation to authorize drivers from partner networks at the charger level, so drivers can start sessions using their existing network credentials without a separate account or app.
More integrations
Flipturn connects with the tools your team already uses, from utility programs and telematics to payment terminals.
Utility program and DER integrations
Flipturn supports OpenADR 2.0b demand response, IEEE 2030.5/CSIP for utility control signals, Modbus submetering, and DER integration for solar and storage. Approved for SCE, SDG&E, and PG&E meter-data programs.
Telematics and fleet integrations
Flipturn connects with leading fleet telematics platforms including Geotab and Samsara, and with fleet routing and scheduling systems so departure times and route energy requirements can inform charging schedules automatically.
Payment terminal integrations
Flipturn integrates with Payter and Nayax payment terminals, enabling card-present transactions directly at the charger. Drivers can tap or insert a credit or debit card to start a session with no phone, app, or QR code required.
Frequently asked questions
Does Flipturn work with my existing chargers?
If your chargers communicate over OCPP 1.6J or OCPP 2.0.1, they are compatible with Flipturn. No hardware replacement is required.
Can I mix chargers from different manufacturers on the same account?
Yes. Flipturn is hardware-agnostic. Multiple brands can operate on the same account, on the same site, managed from the same dashboard.
What does it take to switch to Flipturn from another charging management system?
Switching to Flipturn does not require replacing hardware. If your chargers support OCPP 1.6J or OCPP 2.0.1, they can be re-provisioned to Flipturn without downtime in most cases. Flipturn's onboarding team handles configuration of sites, user groups, pricing, and schedules as part of the setup process.
Does Flipturn comply with NEVI requirements?
Flipturn supports OCPP 2.0.1, which is required for NEVI-funded infrastructure. For specific NEVI compliance documentation, contact us directly.
What is the difference between OCPP and OCPI?
OCPP governs communication between a charger and a management system; it is how Flipturn talks to hardware. OCPI governs communication between different charging networks; it is how Flipturn's network connects with external operators and eMSPs for roaming.
What can operators and developers do with Flipturn's API?
Flipturn's REST API gives operators and developers programmatic access to session data, charger commands, user management, and energy records. Common uses include pulling charging data into internal reporting tools, automating user provisioning, and building custom integrations with property management or fleet systems.
Does Flipturn integrate with telematics and fleet management platforms?
Yes. Flipturn connects with leading telematics platforms including Geotab and Samsara, enabling departure-time scheduling and charging decisions informed by vehicle state and location data. Integration is configured through the dashboard without custom development for supported platforms.