| Table of Contents | ||
|---|---|---|
|
...
Version | Date | Changes | Author |
|---|---|---|---|
1.0 | 11 April 2024 | Initial Documentation for V4 | Anne-Claire Femia |
1.1 | 14 Oct 2024 | Added Json Ticket Example | David Guignard |
1.2 | 28 Oct 2024 | Added Process Flow | Tim MacGowan |
Introduction
This document lists all the PayXpress V4 features available from an Android Intent callin order to make a Inter-application (‘app-to-app’) integration between mobile apps installed on the same mobile device.
The following features are available:
...
The diagram bellow outlines the relationship and process flow between the systems involved in the Intent communication.
...
The steps of the above process flow are explained below:
The Merchant Mobile App initiates a transaction by sending a payment request to PayXpress Payment App.
PayXpress Payment App will display screen to Customer in order to present card / inser card.
Once the end customer completes the transaction and the POS operation concludes, the POS displays the transaction outcome (Payment accepted or refused).
Optional: PayXpress can offer the posibility to the customer to either retrieve his ticket via QR, or sent it by Email.
In this case a screen is displayed requesting for this information.
If no ticket is required in a electronic format (QR, Email), then process to finalize the transaction is realized by PayXpress.
Upon the finalization of the transaction, PayXpress Payment app will export in the Android Intent Reponse the transactions details including the client and merchant ticket.
Calling PayXpress from another Android Mobile application
To call PayXpress, you should use an Intent with a Component.
...