Description of parameters
| Parameter | FieldType | Type | Description |
|---|---|---|---|
| Hexadecimal code of bearer data | 2967 | Entry, by value | Hexadecimal code of the message that will be displayed on the PIN pad during data collection. Check the following table. The data may contain optional leading zeros. See observation described below (1). |
| Minimum size | 2968 | Entry, by value | Minimum data size. See observation described below (2). |
| Maximum size | 2969 | Entry, by value | Maximum data size. See observation described below (2). |
| Maximum idle waiting time | 2970 | Entry, by value | Maximum inactivity waiting time until the function aborts. Value 0 = infinity. |
| Hexadecimal code of bearer data | Message displayed |
|---|---|
| 1 | TYPE THE DDD |
| 2 | REDIT THE DDD |
| 3 | ENTER PHONE |
| 4 | RE-ENTER PHONE |
| 5 | TYPE DDD+PHONE |
| 6 | REDIT DDD+PHONE |
| 7 | ENTER CPF |
| 8 | REDIT YOUR CPF |
| 9 | ENTER ID |
| A | REDIT YOUR ID |
| B | ENTER THE LAST 4 DIGITS |
| C | ENTER SECURITY CODE |
| D | TYPE CNPJ |
| E | REDIT YOUR CNPJ |
| F | ENTER THE DATE (DDMMYYY) |
| 10 | ENTER THE DATE (DDMMYY) |
| 11 | ENTER THE DATE (DDMM) |
| 12 | ENTER THE DAY (DD) |
| 13 | ENTER THE MONTH (MM) |
| 14 | ENTER THE YEAR (YY) |
| 15 | ENTER THE YEAR (YYYY) |
| 16 | DATE OF BIRTH (DDMMYYY) |
| 17 | DATE OF BIRTH (DDMMYY) |
| 18 | DATE OF BIRTH (DDMM) |
| 19 | BIRTHDAY (DD) |
| 1A | BIRTH MONTH (MM) |
| 1B | YEAR OF BIRTH (YY) |
| 1C | YEAR OF BIRTH (YYYY) |
| 1D | ENTER ID |
| 1E | LOYALTY CODE |
| 1F | TABLE NUMBER |
| 20 | NUMBER OF PEOPLE |
| 21 | ENTER QUANTITY |
| 22 | PUMP NUMBER |
| 23 | VACANCY NUMBER |
| 24 | WINDOW/CASH NUMBER |
| 25 | SELLER CODE |
| 26 | WAITER CODE |
| 27 | SERVICE NOTE |
| 28 | TAX INVOICE NUMBER |
| 29 | COMMAND NUMBER |
| 2A | VEHICLE PLATE PLATE |
| 2B | ENTER MILEAGE |
| 2C | INITIAL MILEAGE |
| 2D | FINAL MILEAGE |
| 2E | ENTER PERCENTAGE |
| 2F | SATISFACTION SURVEY (0 to 10) |
| 30 | EVALUATE SERVICE (0 to 10) |
| 31 | ENTER TOKEN |
| 33 | NUMBER OF INSTALLMENTS |
| 34 | PLAN CODE |
| 35 | PRODUCT CODE |
OBSERVATION:
1) If a PIN pad is used in the Abecs protocol in version 2.03 or higher, collections of codes 1 to C will be carried out in the open (no asterisks are displayed) and without confirmation of the data. If a PIN pad is used in the Abecs protocol in version 2.10 or higher, collections of codes D to 35 will be carried out in the open (no asterisks are displayed) and without confirmation of the data. If a PIN pad is used in the Shared Library protocol, all collections are carried out closed (asterisks are displayed) and with data confirmation, displaying what was captured. When a collection is carried out in a closed form, the PIN pad used must have the Software Express DES key and SiTef must have the GerPDV module in version 6.2.3.56 / 6.2.4.19 or higher, which provides keys (access and secret) for this functionality in a transparent way.
2) When a collection is carried out indoors, the minimum and maximum sizes will only be accepted if they are between 4 and 12, with exceptions described below for Security Code (C) and CNPJ (D) collections. When an open collection is carried out, the minimum and maximum sizes will only be accepted if they are between 1 and 32.
Bearer data with codes D or higher such as CNPJ, date and token can only be captured in the open using the Abecs 2.10 protocol. If a transactional flow uses a mix of captures such as CPF + CNPJ, the CPF capture will be done open and without confirmation, while the CNPJ capture will be done encrypted and with confirmation.