Skip to main content
Skip table of contents

Tap to Stop

Description

The Payter terminal is always scanning, waiting on a card to be presented. The trigger to a specific, existing charge session is when the card data that is read matches that for the existing session.

Dependencies

The Charge Controller must ensure the terminal is always scanning.
The Charge Controller must record the unique cardId to a given session and be able to reference that record.

Step by Step Process

  1. The Charge Controller sends the Start command to the terminal, typically immediately after the terminal has finished with the last activity and is otherwise idle

  2. Driver presents their EMV/RFID card to the Payter terminal

  3. The card data is read and returned to the Charge Controller

  4. The Charge Controller recognises the card data as belonging to an existing charge session and stops the existing charge session

  5. The Charge Controller calculates the final amount and sends the amount to the terminal

  6. The Payter terminal UI (optional) or charger UI displays the final session amount and provides a receipt.

image-20240712-155956.png

Tap to Stop Flow

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.