Introduction
Each different request or notification type received by the Retail Module is represented by a unique class, with associated data extracted from the received Nexo message. A distinction is made between Events, which do not have an associated response, and Requests, which require a response.
TOC
| Table of Contents |
|---|
Login
A LoginRequest was accepted by the Retail Module
...
In general, it is suggested to manage aborts through the PollingProvider, providing aborts up to card detection.
| Info |
|---|
If this request is received outside of a valid service exchange, or received too late, the Application should signal that the message was completed, using |
DisplayRequest
A DisplayRequest was received while the System was available
...