Test your OCPI payment terminal integration before a CPO connects.
ChargerDojo plays the CPO against your payment terminal platform.
OCPI 2.2.1 Direct Payment extension and 2.3.0 Payments.Free on our sandbox, no login. Your own system needs Automate.Covers your OCPI interface, not terminals, settlement or AFIR compliance.
- payment terminal provider to CPO.POST
/terminalsReply:201 - payment terminal provider to CPO.GET
/locations/{location_id}Reply:200 - payment terminal provider to CPO.GET
/tariffs/{tariff_id}Reply:200 - payment terminal provider to CPO.POST
START_SESSIONReply:200 - payment terminal provider to CPO.POST
/financial-advice-confirmationsReply:201
We send the other eight: activation, assignment and its read-back, the START_SESSION result to your response_url, two Session updates, the CDR and deactivation.
All thirteen calls
- CPO to payment terminal provider.POST
/terminals/activateReply:200 - payment terminal provider to CPO.POST
/terminalsReply:201 - CPO to payment terminal provider.PUT
/terminals/{terminal_id}Reply:200 - CPO to payment terminal provider.GET
/terminals/{terminal_id}Reply:200 - payment terminal provider to CPO.GET
/locations/{location_id}Reply:200 - payment terminal provider to CPO.GET
/tariffs/{tariff_id}Reply:200 - payment terminal provider to CPO.POST
START_SESSIONReply:200 - CPO to payment terminal provider.POST
{response_url} - CPO to payment terminal provider.PUT
/sessionsReply:201 - CPO to payment terminal provider.PUT
/sessionsReply:200 - CPO to payment terminal provider.POST
/cdrsReply:201 - payment terminal provider to CPO.POST
/financial-advice-confirmationsReply:201 - CPO to payment terminal provider.POST
/terminals/{terminal_id}/deactivateReply:200
Your system sends five of thirteen calls in the sample.
Your system is the payment terminal provider (PTP). ChargerDojo plays the CPO and waits up to 5 minutes for each request your system needs to send.
On OCPI 2.3.0, ChargerDojo activates the terminal, sends the Session and the CDR, then deactivates it. OCPI 2.2.1 runs without terminal activation and deactivation. Read the setup guide
The report compares each capture with its CDR.
When the CPO invoices, the report compares the total in the capture confirmation with the CDR and warns on a mismatch, and fails a successful capture that does not record total, currency and EFT data.
On the sandbox, a partial or failed capture stays a payment failure even when the CDR is valid.
When the PTP invoices, your system sends no confirmation, so none of these capture checks run.
The report shows recorded requests and responses, with applicable rules.
- Session
D07START_SESSION carries an authorization reference (required on 2.2.1, a warning on 2.3.0) and, when the CPO invoices, the confirmation repeats it.- Capture
D10The confirmation records total, currency and EFT data.D12The captured total is compared with the CDR total. A mismatch is a warning, because OCPI does not require them to match.- Reported, not failed
D04Whether your system pulls the tariff it shows on the terminal.
These results come from our sandbox run. The report names what it could not grade, such as the processor's preauthorization release.
Two versions, two contracts.
OCPI 2.3.0 moves Payments into the core specification: the preauthorization amount moves from max_price to preauthorize_amount, terminals gain activate and deactivate, and prices use before_taxes and taxes.
| What changes | OCPI 2.2.1 Direct Payment | OCPI 2.3.0 Payments |
|---|---|---|
| Defined in | EVRoaming Foundation working document, March 2024 | Core specification chapter |
| Preauthorization amount | max_price on the Tariff | preauthorize_amount on the Tariff |
| Terminal activation | Not in the document | activate and deactivate on the PTP interface |
| Price shape | excl_vat, incl_vat | before_taxes, taxes |
What a verdict covers.
It covers
Your payment terminal platform's OCPI interface.
Recorded requests and responses, with applicable rules.
A report you can share with a CPO.
It does not cover
Physical terminals.
Settlement with your payment processor.
AFIR compliance.
AFIR puts the card payment duty on charge point operators, not payment terminal providers. From 1 January 2027 it applies to existing points of 50 kW or more on the TEN-T network. Regulation (EU) 2023/1804, Article 5
Sandbox-tested. These checks have run against our own sandbox terminal system, not yet against a payment terminal provider's own system.
Before you connect.
Do I need a physical terminal?
No. ChargerDojo talks to your payment terminal platform over OCPI.
More detail
Your system still has to start the session and, when the CPO invoices, send the confirmation, so use a test terminal or a script of your own.
Our system connects as an eMSP. Does this apply?
The journey needs a Payments Sender interface.
More detail
If you connect through eMSP modules without Payments, test your system as an eMSP endpoint instead. If you can choose, connect over OCPI 2.3.0 Payments, where the module is part of the standard.
We are a CPO connecting a payment terminal provider. What can we test?
Run the Payments suite against your Receiver interface, on Automate, $499 a month.
More detail
No journey plays the PTP against a CPO today.
Does this cover AFIR ad hoc payment?
It tests the OCPI link a payment terminal provider uses with a CPO and excludes terminal hardware, settlement and AFIR compliance.
Is a report a certification?
No. ChargerDojo is an independent testing tool.
More detail
A report records the checks that ran against your endpoint.
What does it cost?
Running it against our sandbox is free, with no login.
More detail
Testing your own payment terminal platform needs Automate, $499 a month.
Which OCPI versions does it test?
The OCPI 2.2.1 Direct Payment extension and OCPI 2.3.0 Payments, the two versions that define terminal payments.
Run it before your first CPO connects.
Free on our sandbox, no login. Testing your own system needs Automate, $499 a month.