Error Scenarios

The scenarios defined below are not intended to be exhaustive, but are to highlight the interdependent nature of the holistic EV charging solution. Specifically, these scenarios ask integrators to consider the driver customer experience, and take actions that result in positive customer outcomes.

It is critical to either commit or cancel every sessionId in a timely fashion. Each sessionId represents cardholder funds that are reserved in their account and otherwise not available to spend. These sessionId’s should be finalised as soon as the driver has left the charge point.

Scenario	Summary	Charger Controller Action
Aborted Charge due to No Start	Payment has been authorized and `sessionId` is known Charge session not started Session considered aborted, either due to Driver confirmation or timeout	Confirm aborted status and then send Cancel to Payter terminal quoting `sessionId`. This is vital to ensure any authorized and reserved funds are returned to the cardholder.
Communication Loss with Charger	A charging session is underway The Charge Controller loses connection to the charger The Charge Controller decides to abort the charge	Confirm aborted status and then send Commit to Payter terminal quoting `sessionId`. This finalises the charge session for the last known total.
Payter Terminal Communication Loss	Terminal is unable to authorize payments	Authorize attempts will be declined. No charging sessions will start. Charge Controller can choose whether to free vend during this time.
	Terminal is unable to finalize amounts	Committed and Cancelled `sessionId`’s will still be confirmed. Commits will stored and automatically attempted when communication is restored.
	Terminal integration no longer available (Cloud Payment Service only)	Data from cards is not returned and no sessions can start. Charge Controller can choose whether to free vend during this time.