Hubject OICP Testing
Validate how your CPMS exchanges OICP 2.3 messages with Hubject — EVSE data and status pushes, RFID and remote authorization, and Charge Detail Records — without onboarding to the live intercharge hub first.
What is Hubject OICP testing?
Hubject runs the intercharge roaming network on the Open InterCharge Protocol (OICP), currently OICP 2.3. CPOs and eMSPs connect to Hubject's QA environment for integration and its PROD environment for live traffic. Hubject OICP testing validates how your CPMS speaks OICP against a simulated hub: publishing charge points with eRoamingPushEvseData and eRoamingPushEvseStatus, handling eRoamingAuthorizeStart and eRoamingAuthorizeRemoteStart, and submitting an eRoamingChargeDetailRecord for billing — so you reach QA onboarding already working.
Why this matters
- OICP authorization bugs — a malformed eRoamingAuthorizeStart or a dropped SessionID — strand drivers at the charger and are hard to debug once live partner traffic is flowing.
- Getting eRoamingPushEvseData and eRoamingPushEvseStatus right before QA onboarding means your charge points show up in partner apps on the first try.
- A simulated hub lets you exercise the full CPO-to-eMSP exchange, including eRoamingChargeDetailRecord for settlement, before you depend on Hubject's QA or PROD environment.
What to validate
- Partner-readiness checks for hub-oriented roaming flows and operational exchange patterns.
- Session, authorization, tariff, and settlement-path validation at the integration boundary.
- Failure handling across delayed responses, invalid payloads, and asynchronous operational callbacks.
- Cross-checks between your roaming implementation and the underlying CPMS or settlement systems behind it.
Example Hubject OICP roaming validation flow
A practical Hubject readiness test verifies that your backend can exchange the right operational data with a hub-facing integration boundary before any live partner traffic arrives.
CPO -> Hub (QA): eRoamingPushEvseData (publish EVSE static data, EvseID DE*ABC*E1234567)
CPO -> Hub (QA): eRoamingPushEvseStatus (status: Available)
Hub -> CPO: Acknowledgement (Result: true)
# Driver taps a partner RFID at the charger
CPO -> Hub: eRoamingAuthorizeStart (EvseID, Identification: RFID UID)
Hub -> eMSP: forward AuthorizeStart
eMSP -> Hub: Authorized + SessionID
Hub -> CPO: AuthorizationStatus = Authorized
# App-initiated remote start from the eMSP
eMSP -> Hub: eRoamingAuthorizeRemoteStart (EvseID, EvcoID, SessionID)
Hub -> CPO: AuthorizeRemoteStart
CPO -> Hub: Acknowledgement (Result: true)
# Session ends
eMSP -> Hub: eRoamingAuthorizeRemoteStop (SessionID)
CPO -> Hub: eRoamingChargeDetailRecord (SessionID, kWh, start/stop time)
Hub -> eMSP: forward CDR for billingHubject readiness proof points
Hubject-facing validation is usually about proving that the backend can survive hub-mediated partner workflows before live onboarding and operational rollout.
| Area | Coverage | Typical validation |
|---|---|---|
| EVSE data publication | eRoamingPushEvseData and eRoamingPushEvseStatus | Confirm your charge points and live status reach the hub so partner apps can show them. |
| Authorization | eRoamingAuthorizeStart, eRoamingAuthorizeStop, and remote start/stop | Exercise both RFID and app-initiated sessions, including SessionID handling. |
| Charge Detail Records | eRoamingChargeDetailRecord exchange | Validate CDR fields and timing so settlement with the eMSP reconciles. |
Common scenarios
Before Hubject QA onboarding
Get eRoamingPushEvseData, authorization, and eRoamingChargeDetailRecord working against a simulated hub so your first cycle in Hubject's QA environment is not spent fixing avoidable OICP errors.
OICP regression after a CPMS change
Re-run the full eRoamingAuthorizeStart-to-eRoamingChargeDetailRecord flow whenever you change authorization, session, or CDR logic in your CPMS.
Running OICP alongside OCPI
Check that your backend keeps OICP roaming with Hubject consistent when it also speaks OCPI to other partners.
Related resources
Test your OICP 2.3 flows before Hubject onboarding
Simulate the CPO-to-hub-to-eMSP exchange — EVSE pushes, authorization, and Charge Detail Records — so you reach the Hubject QA environment already passing.