status update flows - AEVI-AppFlow/pos-android-sdk GitHub Wiki
In addition to the standard flows that are defined to perform a certain action, like a purchase, or generating a token, AppFlow also enables applications to provide status updates via flows. These status updates can be of any nature that involves passing some data to one or multiple applications.
Unlike the normal generic flows (such as tokenisation) where a single application handles the request and passes back a response with an outcome, these flows allow multiple applications to be called in sequence for the purpose of reading input data. The application can choose to not send any data back, or to pass back a set of references. FPS will collate all references from the applications and pass back in the final Response back to the client.
These flows are processed via a request queue in the background, separately from the standard flows. Applications in these flows may not launch any user interface - they must handle the update in the service only. Responses to status updates come in via the BaseResponseListenerService.notifyStatusUpdateResponse() callback method. If the client application is not interested in the responses, this method can be left empty.