The OCPI testing tool that catches roaming bugs before your partners do

The tool is hosted and talks to your system server to server, so the endpoint has to be reachable from the internet. If it lives on localhost or inside a VPC, a tunnel takes minutes to set up. There is also a connector you download and run next to your service, which removes even that step and never exposes it. CORS does not matter here: that is a browser policy, and these calls never come from a browser.

No, and that is deliberate. A SHALL violation fails the run. A SHOULD divergence is reported but never fatal, because a partner who ignores a SHOULD is still compliant, and failing them for it sends your team off to fix code that was never broken. Every check names the rule it encodes and carries the exchange that proves it, so a finding is always something you can act on.

Yes. A charging journey can drop status updates, send a meter that goes backwards, deliver a CDR late, or lose the connection mid-session, on a real or accelerated clock. You watch how your platform recovers, which is the part a clean conformance pass never shows you.

Yes. There is an OCPI 2.3.0 Payments conformance suite, and the tool now runs a full Direct Payment terminal journey: it plays the CPO and takes a payment terminal end to end, terminal registration, the tariff and pre-authorization, the charge, and the Financial Advice Confirmation with its full, partial, and failed capture outcomes, reconciling the captured amount against the CDR. It runs on OCPI 2.3.0 and on the 2.2.1 Direct Payment working document, with the payment verdict kept separate from the charging one. Against our sandbox peer it is free; against your own endpoint it is on the Automate plan.

Yes, on OCPI 2.3.0, which is the version that adds them. The 2.3.0 Locations and Booking suites validate payloads carrying the MCS connector, the truck vehicle types, and the refrigeration outlet for reefer trailers, against your endpoint or our sandbox peer. Earlier OCPI versions do not define these fields, so a heavy-duty charging deadline is a 2.3.0 conversation.

Yes. Register each client endpoint as its own target and run the same suites and journeys against it, with a report per endpoint you can hand over. If you are testing on behalf of several clients, talk to us about which plan fits.

Yes. A run can be shared as a read-only report link that carries the plan hash, the rule behind each check, and sanitized evidence, with no login required to read it. A sandbox run stays shareable on every tier, marked as one. Running the suite against your own endpoint takes a plan, and so does the link: a link to a report about your own endpoint stops opening when the plan ends, while a shared sandbox report keeps working. Deleting your account revokes every report link you created, even where your organisation keeps the report itself.

Yes. The same plan the browser runs can be compiled and started from a pipeline with an API key, and retries are idempotent, so a flaky network never double-starts a run. CI automation belongs to the paid plans.