Table of Contents | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Status of the action | ||
---|---|---|
AE | Fixed length. 2 | Status of the action being performed on the terminal |
Processing on cash register side: | ||
Processing on terminal side: ‘01’ = Operation not performed | ||
Remarks: *When the terminal response must be immediate 01 : Operation not performed because of the network error, or POS is busy (with other process or app not in the front) for exemple PayXpress is busy. | ||
Example - The operation has not been performed | AE00201 |
...
Complementary info to the status of the action | ||
---|---|---|
AF | Variable length. 2-50 | Additional information to the status |
Processing on cash register side: | ||
Processing on terminal side: The terminal can provide additional information to the overall status of the action: ‘00’ - Unknown – If error we don’t know that is unkown by PayXpress. Could be a technical issue not a nominal scenario. | ||
Remarks: We send the response of the processing transaction | ||
Exemple : Canceled | AF00207 |
...
Ticket data | ||
---|---|---|
AK | Variable length. Max 900 | Generic data to include on ticket |
Processing on cash register side: Printing the ticket. | ||
Processing on terminal side: This Tag is included in the constructed Tag ZT. It is composed of the ticket data. | ||
Remarks: This Tag is a generic ticket data container. And may contain, depending on the case, merchant ticket data, cardholder ticket data, or another type of data. The format of the Tag CK that accompanies this Tag in the constructed Tag determines the type of data and its format. | ||
Example: See this exampleExample |
Anchor | ||||
---|---|---|---|---|
|
...