Stop Session
Once the controller has a sessionId there are only two possible outcomes:
The ‘Vend’ of charge has not started or otherwise needs to be cancelled without payment.
The ‘Vend’ is complete and a finalised amount needs to be committed to the original
sessionIdand card.
End Session
Use case scenarios | Description |
|---|---|
The Payter terminal is always scanning, and when a tapped card is recognised as belonging to an existing charge session, this is the trigger to stop the charge process. | |
Tap to Start and Tap to Stop are often used together as the logic is similar. | |
When the charge controller detects the vehicle has been disconnected, the current charge session is finalised. | |
Plug In to Start & Unplug to Stop are often used together as the logic is similar. The Unplug to Stop flow is the same as any other unexpected stop e.g. emergency shutoff. | |
Either the Payter terminal User Interface, or the charge controller interface (if it exists) recognises the presence of a driver through on-screen prompts. | |
This flow can optionally be used to identify the charge station to be used, where a single charge controller and Payter terminal are used to manage multiple charge points. Once Stop is requested, Tap to Stop is used. | |