variable, max 64

PAN

fixed, 4

Expiration date

variable, max 10

Authorization number

fixed, 2

Status of the action

variable, 2-50

Complementary value to the Status of the action

variable, max 32

Application ID (AID) of the card

variable, max 900

Ticket data

fixed, 1

Type of PAN

fixed, 13

Date of the operation

variable 2-20

serial number of the pos

fixed, 1

Response delay

fixed, 20

Shopper’s phone number from cash register

fixed, 256

Shopper’s email from cash register

fixed, 2

Cash register number

variable, 2-12

Amount

fixed, 1

Type of action

fixed, 3

Currency code

variable, 1-99

This field is reserved for private use

variable, 1-99

This field is reserved for private use

fixed, 1

How card was read

fixed, 12

Cash Register Protocol identifier

fixed, 3

'Print ticket?' selection

fixed, 4

Protocol Version used

variable, max 999

Constructed Tag for the ticket

variable, max 999

PayXpert Transaction Id

variable, max 999

PayXpert Transaction Id

PAN (primary account number) of the card

Processing on terminal side:
PayXpresss always send the partial PAN for security reasons.
This tag is always with the tag AL with the value at “1” (partial PAN)

Remarks:

Transmission is not secure.
For EMV applications, the PAN cannot be returned complete. The terminal returns a partial PAN or a token.

Example - PAN is 123456XXXXXX1234

Expiration date of the card

Processing on terminal side:

An application can return the expiration date of the card being used in the transaction (YYMM format).

Remarks:

Example - Expiration date is 03/16

Authorization number

Processing on terminal side:

PayXpress can return your bank’s identifier of the given authorization transaction.

Example - Authorization nº is A00395

Status of the action being performed on the terminal

Processing on terminal side:

‘01’ = Operation not performed
‘10’ = Operation performed

Remarks:

01: Operation not performed because of a network error, or PayXpress is busy. PayXpress can be busy if there is another process which is running / another transaction ongoing. This answer could also be given if the app is not in the foreground (but rather, it has been pushed to the background).

10: The request successfully reached the terminal and the terminal can handle it.

Example - The operation has not been performed

Additional information to the status

Processing on terminal side:

The terminal can provide additional information to the overall status of the action:

‘00’ - Unknown – If error is unknown by PayXpress. Could be a technical issue. Not a nominal scenario.
‘01’ - Transaction authorized - Transaction has been accepted by the bank.
‘04’ - Refused - Transaction declined by the bank for example
‘06’ - Abandoned - If Cardholder cancelled the transaction during the payment process.
‘07’ - Not completed - This is a additional information from the TAG AE 01 (Operation not performed).
‘08’ - Timeout from PayXpress* - If PayXpress detects a timeout during the transaction then the transaction will be closed automatically.
‘09’ - Operation not performed because of message format error - If we detect an error with the parameters.
‘10’ - Error selection
‘11’ - Error during Operation abort
‘12’ - Error - unknown action
‘13’ - Currency not supported
‘14’ - Incorrect amount
‘15’ - incorrect Transaction id
‘16’ - transaction already completely refund
‘17’ - refund amount exceeds the remaining amount in the transaction
‘18’ - Error refund forbidden
‘19’ - Network failure
‘20’ - Refund pending
‘21’ - Merchant disabled
‘22’ - Terminal unknown
‘23’ - Unable to perform refund

Remarks:

We send the response after processing the transaction.
*A transaction can time out depending on the specific timeout values of the specific screen on which the cardholder is situated.

Example - Cancelled

Application ID of the card

Processing on terminal side:

An application can send the AID of the card that performed the transaction.

Example - An example AID

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 example

Gives us the type of PAN returned by reading the card

Processing on terminal side:

Returned PAN type is always '1' = a Partial PAN.

Remarks:

This Tag is optional.

Example - An example response:

Give the date and time in which the operation was realized

Processing on terminal side:

Returned Date & time in which the operation was realized.

Remarks:

This Tag is optional.
This Tag AP is ruturned in the response only when the transaction is sucessfull.
Format is a timestamp. Applies for Debit, Annulation and Credit

Example - An example response:
Timestamp 1738069356000
GMT +2 → Tuesday 28 January 2025 13:02:36

Give the serial number of the pos

Processing on terminal side:

Returned the serial number of the pos

Remarks:
This Tag AP is returned in the response only on the identification request.

Example - An example response:

Response delay

Processing on cash register side:

By default, set this field to 0 (response at the end of the transaction).

Processing on terminal side:

List of terminal response times:

• ‘0’ = Response at the end of the transaction

• ‘1’ = Immediate response (without valid status)

Remarks:

If this field is omitted, the default value is taken into account (Response at the end of the transaction).
If an immediate response is requested, the status of the transaction is unknown at the time of the response: the status simply indicates that the request is taken into account.

Example - The cash register needs an immediate response

Shopper’s mobile phone number

Processing on cash register side:

Mobile number with the possibility of transmitting an extension for international numbers.

Processing on terminal side:
This can be used later to send the dematerialized ticket to the shopper’s phone in text (SMS) format via a web service.

Remarks:

Example

Shopper’s email address

Processing on cash register side:

The email address of the shopper as input or appearing on the cash register (x@x.xx).