First of all, in V2, there is only one supported communication method which is USB/RS232. In this version, all the data are structured following a specific order. The structure is different between the query of the cash register and the reply of the POS.
The following tables will detail the structure of data <message> including STX, ETX and LRC.
| Note |
|---|
There is no field for tickets, it is up to the cash register to build it on its own. |
Data structure of the cash register query
Field | Length | Description |
|---|---|---|
STX | 1 | Start of the frame |
ECR# | 2 | Cash register number |
MNT | 8 | amount |
IND | 1 | Response field indicator (0 = NO REP, 1 = REP but only PAN, 2 = TLV) |
EMETTEUR | 1 | Payment method |
TYPE | 1 | Transaction type |
DEV | 3 | Currency |
PRIV | 10 | Private data (if none, it is blank, so 10 |
DELAI | 1 | POS response delay |
AUTO | 1 | Authorization request |
ETX | 1 | End of the frame |
LRC | 1 | Checksum (computed using bytes from ECR# to AUTO + ETX) |
Data structure of the POS reply
Field | Length | Description |
|---|---|---|
STX | 1 | Start of the frame |
ECR# | 2 | Cash register number |
STAT | 1 | Transaction status |
MNT | 8 | amount |
IND | 1 | Response field indicator (0 = NO REP, 1 = REP but only PAN, 2 = TLV) |
EMETTEUR | 1 | Payment method |
TYPE | 1 | Transaction type |
DEV | 3 | Currency |
PRIV | 10 | Private data (if none, it is blank, so 10 |
DELAI | 1 | POS response delay |
AUTO | 1 | Authorization request |
ETX | 1 | End of the frame |
LRC | 1 | Checksum (computed using bytes from ECR# to AUTO + ETX) |
| Info |
|---|
A POS message could look like this (STX + <message> + ETX + lrc):  |