Device Start

The Device Start flow initiates directly at the Nayax terminal, allowing consumers to begin a session by selecting a service or presenting their card. This enables interactive communication with the terminal, such as displaying tariffs or confirming service station availability, before the session officially begins on the machine.

The Device Start flow makes use of the following Spark methods:

• StartSession
• InfoQuery
• TransactionNotify
• Settlement
• CancelTransaction
• TimeoutCallback

📘

Pre-Authorization Only

Device Start currently only supports pre-authorization, for an option with Pre-Selection see Remote Start.

Pre-Authorization Flow

To understand the device start pre-authorization flow, see the diagram below:

Below is a breakdown of the diagram:

1. A consumer selects a service station (and/or presents a card) on the Nayax Device, which sends an InfoQuery request to the Nayax Server.
2. The Nayax Server sends a StartSession to the 3rd Party Server.
3. The 3rd Party Server responds to the Nayax Server with a StartSession Response.
4. The Nayax Server sends a InfoQuery to the 3rd Party Server.
5. The 3rd Party Server responds to the Nayax Server with a InfoQuery.
6. The Nayax Server sends an InfoQuery command back to the Nayax Device.
7. The consumer presents their card (if they haven't already done so). An AuthorizationRequest is sent from the Nayax Device to the Nayax Server.
8. The Nayax Server performs authorization with a Payment Provider and then sends a TransactionNotify to the 3rd Party Server.
9. The 3rd Party Server responds to the Nayax Server with a TransactionNotifyResponse.
10. The Nayax Server sends an AuthorizationResponse Back to the Nayax Device. At this point, the service can be provided on the Service Station, and the Nayax Device is back to idle.
11. The 3rd Party Server sends a Settlement command to the Nayax Server.
12. The Nayax Server performs the settlement with the Payment Provider and then sends a Settlement back to the 3rd Party Server.

See Also