Perform real-time remote charging authorization with Hubject OICP eRoamingAuthorizeStart / eRoamingAuthorizeStop

Steps

1. When a CPO's own backend doesn't recognize a driver's presented identification (RFID UID or EvcoID), send eRoamingAuthorizeStart to Hubject with the OperatorID, the identification data, and optionally the EvseID where the session is starting.
2. Hubject validates the identification against the roaming eMSP's contract data, generates and returns a SessionID, and persists that SessionID alongside the EvseID and identification data for the duration of the session.
3. CPO backend uses the returned authorization result to allow or deny the physical charging session to begin at the charge point.
4. When the driver ends the session, send eRoamingAuthorizeStop referencing the same SessionID Hubject issued at start; Hubject derives the authorizing eMSP from that SessionID rather than requiring the identification data again.
5. Hubject can typically authorize the stop directly using persisted session data, or forward the stop request to the eMSP when its rules require an explicit check — design the CPO side to handle either a synchronous or slightly delayed authorization result.