UI Stop

Description

The driver stops the charge process by selecting an on-screen option. Most commonly, this will include selecting a specific charger from a list, but it can also be used to select Start/Stop/Receipt. The UI can be either the Charge Controller, of if using the Apollo family, the Payter terminal.

Once the charge session is selected, Tap to Stop is typically used to authenticate the UI user is authorized to end the session.

Dependencies

The Charge Controller can display to, and collect feedback from, the driver before starting any processes. The Charge Controller provides instructions to the driver on what to do at each step.

Step by Step Process

1. The Charge Controller displays the interactive user interface

2. The driver selects their options, including confirming they are ready to stop the session

3. The Charge Controller sends the start command to the Payter terminal

4. Driver taps their card

5. Payter returns card data to the Charge Controller

6. The Charge Controller confirms the card data matches the selected session and finalizes the amount

7. A commit is sent in for the final amount.

UI Stop

The Unplug to Stop or Tap to Stop flow is recommended here as other Charge Controller users should not be able to stop a driver’s charging session from the Charge Controller without validation. Where a UI to Stop flow is used, then Tap to Stop is recommended as shown above.

Multiple Choice’s

Charge Controllers can use more than set of choices, to drive efficiency in a large charge station with multiple charge points. A choice of 4 different charge stations could be the first screen, followed by a second choice, to either; Start, Stop, Receipt.

In this approach the Charge Controller can leverage a single Terminal to be an Interface for multiple Connectors.