OCPI Tariff Dimensions: ENERGY, TIME, FLAT & PARKING_TIME
The four OCPI tariff dimensions in depth: ENERGY, TIME, FLAT and PARKING_TIME, how step_size rounding works, and how restrictions gate each one.
25 articles in this category
The four OCPI tariff dimensions in depth: ENERGY, TIME, FLAT and PARKING_TIME, how step_size rounding works, and how restrictions gate each one.
How money actually flows in OCPI roaming: the fees, the settlements, and how to think about the economics of cross-network charging.
How to test an OCPI implementation properly: mocks, schema validation, partner-style fixtures, and the operational tests that catch real bugs.
Run a complete OCPI 2.2.1 flow in a sandbox: credentials handshake, Locations, Sessions, Commands and CDRs, with no roaming partner needed.
Copy-paste OCPI 2.2.1 request examples: real Locations, Sessions, and CDR JSON payloads, with the HTTP method, endpoint path, and headers for each.
A step-by-step OCPI integration test workflow: handshake, versions, module smoke tests, and error handling, so nothing surprises you on go-live day.
Common OCPI integration mistakes and pitfalls (pagination, idempotency, timestamps, status codes) and the concrete fix for each, from real builds.
How OCPI security and authentication really work: bearer tokens, TLS, mTLS, the threat model, and a checklist to keep tokens from leaking.
What OCPI 3.0 is positioned to change: bidirectional sessions, CDRs, tariffs, and grid services, plus how to prepare while running 2.2.1 today.
The features OCPI 2.3.0 adds: the Payments module, AFIR-ready pricing, the Parking object, North American tax support, and who should upgrade.
OCPI 2.2 vs 2.2.1 differences explained: the exact fields and enums 2.2.1 changed, what stayed the same, and whether you need to migrate.
How the OCPI HubClientInfo module lets a hub publish its connected parties, with worked PUT/GET examples, the four status values, and the gotchas that bite.
OCPI 2.1.1 to 2.2 migration in the order to actually do it: what changed, the Credentials handshake to fix first, and how to upgrade without breaking partners.
How OCPI ChargingProfiles lets an eMSP shape power on a live session: the fields, a full worked round trip, and the gotchas that quietly break it.
When to roam through a hub, when to build direct peer-to-peer integrations, and what the tradeoffs cost you in practice.
Before any data can flow between an eMSP and a CPO via OCPI, they have to negotiate. The Credentials and Versions modules are the handshake.
How eMSPs trigger start/stop/reserve actions on CPO stations via OCPI. The Commands module is what makes "Start Session" buttons in apps work.
How the OCPI Tariffs module models EV charging prices: per-kWh, per-minute, time-of-use and idle fees, with annotated JSON and step_size gotchas.
The OCPI Locations module explained: the Location/EVSE/Connector data model, push updates, evse_id format, and the gotchas that get objects rejected.
How eMSPs grant customers access to CPO stations via tokens, and how CPOs validate those tokens without ever seeing the underlying customer.
CDRs (Charge Detail Records) are the final, immutable billing records exchanged via OCPI after a session completes. Here is how they work.
How CPOs stream live session data to eMSPs over OCPI: when a session starts, how much energy has flowed, and how status changes get pushed.
CPOs operate the charging stations. eMSPs own the customer relationship. The split is the foundation of how the EV charging industry actually works.
Every OCPI release from 2.1.1 through 2.3.0, plus the 3.0 preview: what each version changed, and which one a new integration should target.
OCPI (Open Charge Point Interface) is the protocol that lets one charging network accept another network's customers. What it is and how it works.