Charging Journeys
Prove one outcome at a time against your real endpoint. We run the timed OCPI journey and grade the answers; you read the verdicts.
I'm testing
against
Build your own
Build a custom journey
Start from a real journey and open every knob: your cadence and jitter, your field combinations, PUT-only updates for long sessions and your disturbances. New to the shape? Download a sample to start from, or read the guide.
Charging Journeys runs timed, end-to-end OCPI journeys against your registered partner endpoint: find a charger, authorize, charge with live updates, stop, and reconcile the final bill. The tool plays the counterparty, drives configurable update cadences and real-world disturbances, and grades every answer against the vendored OCPI text with the clause cited. Runs are durable: a browser refresh, a lost stream, or our own runner restarting never invents a failure or loses evidence.
Verdicts stay separate: OCPI conformance, partner compatibility, business checks, and observations are graded independently, with run integrity reported first. Every verdict links to the exact request and response that proves it.
Every catalogue journey is also a starting point for a custom journey: your own cadence and jitter, PUT-only updates for long sessions, your field combinations and your disturbances. Write one that runs a 40 minute PUT-only session and delivers its CDR late, then save it and replay it from CI on the Integrate plan.
Common questions
What is a charging journey?
A charging journey is a timed, end-to-end OCPI story run against your endpoint: find, authorize, charge with live updates, stop, and bill, on a real or accelerated clock, with configurable disturbances such as dropped updates, a non-monotonic meter, or a late CDR.
How is a charging journey graded?
Every run is graded in four separate lanes: OCPI conformance against the vendored specification text, partner compatibility against named network profiles, business checks, and observations. A SHALL failure fails the lane, a SHOULD divergence warns, and simulator downtime is recorded as run-evidence integrity, never charged to the target platform.
Which OCPI versions can run a charging journey?
Charging journeys run against OCPI 2.1.1, 2.2.1, and 2.3.0 endpoints, for eMSP receiver and CPO sender roles, with a registered sandbox peer available so a journey can run without your own endpoint first.