Communication messaging layout
This section will present the formats that the messages generated by the requesting Terminal must have. TEF and the formats of the return messages generated by the SiTef Client with the confirmation or not of each transaction.
Messages will be transferred through a multi-line text file, where each line contains a type of information. The lines have a standard format and variable size. The generic format is:
AAA-BBBC=CDDDDDDD......DDDDDEF
Where:#
| Format | Description |
|---|---|
| A | Identification of the type of information or field. |
| B | Sequence number complementary to the type of information or field.. |
| C | Position containing space or white. |
| D | Information (always aligned to the left, without filling in zeros or spaces). |
| E | Carriage Return (CR) = 13 (according to the ASCII table). |
| F | Line Feed (LF) = 10 according to the ASCII table). |
The types of possible operations are:#
| Header | Description of Operations |
|---|---|
| ADM | Allows the Customer to be activated to perform administrative functions. |
| CRT | Authorization request for transaction by card (credit or debit) |
| CHQ | Authorization request for transaction by check |
| CNC | Cancellation of sales made using any payment method |
| CNF | Sales confirmation and coupon printing |
| NCN | No confirmation of sale and/or printing. |
| PRE | Credit card pre-authorization |
| PGV | VisaNet bill payment |
| PGB | Payment of Banrisul charges. |
| PCB | Bill payment via banking correspondent. |
| EPH | Transactions for E-Pharma Pharmacy. |
| INF | Transactions for Pharmacy InfoCard. |
| VIL | Transactions for VidaLink Pharmacy |
| EMS | EMS Transactions. |
| PPB | Prepaid Card and Bonus Card |
| CEL | Cell phone recharge. |
| SHL | Shell Card Transactions |
| TCN | TrnCentre Transactions |
| PVS | PrevSaúde Transactions |
| ACSP | ACSP Transactions |
| CSR10 | CSR10 Transactions |
| TRCP (Obsolete) Use the PROPRIET | Transaction for Reading the Proprietary Card Trail |
| JGV | JGV Transactions |
| CONSCRED | Pre-Approved Credit Consultation Transaction (DMCARD) |
| CONSPGEN | Invoice Payment Consultation |
| CRTFIEDL | Fidelity Transactions |
| FTC | FTC Network Fidelity Transactions |
| PROPRIET | Transaction for Validation and Capture of Owner Card Data, and can also capture the password for the owner card. |
| WAYUP | WAYUP Transactions |
| PICPAY | Picpay network transactions |
| GETNETLA | GetNetLAC network transactions |
It is worth mentioning here that sales cancellation can be done in two ways: through an ADM operation, or then through a CNC operation, with the TEF requesting Terminal being responsible for how the cancellation will be accessed.
In the next sections, the types of information (or fields) that may be present in the files sent and received by the TEF requesting Terminal. The information (or fields) varies depending with the type of operation, and all fields present in the file are optional, as the SiTef Client is able to collect all the data necessary for the transactions it carries out. However, the fields present in the received file by the SiTef Client will be preserved in the return file and the SiTef Client will only include in this file the fields pertinent to the response of the operation performed and not the data collected by the program to carry out the transaction.
Note that the automation application must be prepared to receive and ignore the types of records it don't know. This feature is important to maintain compatibility with future versions.
When there is a discrepancy between the content of the field sent by the TEF requesting Terminal and that received by the SiTef Client will be worth that of the SiTef Client.