Return File 4.0
- Goals
- Definitions
- File Structure
- Record format
- Record 0 – Header
- Record 1 - Sale Details
- Record 10 - Credit Details
- Record 2 – Adjustments
- Record 100 – Anticipation Batch
- Record 200 – Anticipated transactions
- Record 9 – Trailer
- Remark
- Limitations
- template for saving to database
- Code table
- Version Changes
1. Goals
- The detailed return file generated on disk is intended to allow the custommer's back-end system to download the outstanding bills.
Target Audience: Any and all customers that need to save data to disk.
The consolidated generated file is used to check the values recorded in the map of
store cash against the value recorded by SiTef, for payment transactions with
credit, debit and benefit cards.
- The detailed return file has its origin in the electronic statement file, sent by the authorizers, organizing them in a single model. The return file also includes information on transactions that pass through SiTef, for records reconciled with those transactions.
2. Definições
The generation of the file is done through the "SiTefWeb Conciliation Reports" interface, requiring only the “Start Date”, “End Date” and version information.
-
The files will be generated in CSV format, that is, the fields are separated by semicolon (";").
-
Only the fields available according to each network are present.
-
In case there is no content for the field, there will be a separator (“;”), making the number of fields of each “Fixed” record independent of the network.
-
In the case of Non-TEF transactions, the NSU Sitef field will contain the Receipt Number.
-
If the user selects the date type as "Sale Date", only the Record data
Sale details (in addition to Header and Trailer) will be filled. This change has occurred so
that the created file is immutable regardless of the present date. -
In the case of "Credit Date", the other fields will be filled, they are: Credit Details,
Anticipation Batch, Advance Transactions and Adjustments, in addition to the Header and Trailer; -
The ordering, all ascending, of the records for the Sale Details field will be:
- Sale Date
- Idt Rede
- Codlojasitef
- TipoProduto
- NSU SiTef
- Installment Number
-
The ordering, all ascending, of the records for the Credit Details field will be:
- Credit Date
- Idt Rede
- Codlojasitef
- TipoProduto
- NSU SiTef
- Installment Number
-
The ordering, all ascending, of the records for the Adjustments field will be:
- Adjustment Date
- Idt Rede
- Codlojasitef
-The ordering, all ascending, of the records for the Anticipation Batch field will be:
- Anticipation Credit Date
- Idt Rede
- Codlojasitef
- Summary number
- Installment
-
The ordering, all ascending, of the records for the Anticipated Transactions field will be:
- Sale Date
- Idt Rede
- Codlojasitef
- TipoProduto
- NSU SiTef
-
The default filename format for saving to disk will be:
-
Detailed file: “Det<Nome_Rede><Data_Atual>.csv”
-
Where:
- <Nome_Rede> Network Name, or “miscellaneous” when two or more authorizers are selected.
- <Data_Atual> in the format YYMMDD.
-
The output to database requires the creation of a table for each type of Detail Record.
3. File Structure
Filter by Sale Date:
0 – Header
1 – Sale Details*
8 - Rejected Details
9 - Trailer
Filter by Credit Date:
0 – Header
10 – Credit Detail*
.
.
2 – Adjustments
.
.
100 – Anticipation Batch
.
.
200 – Anticipated Transactions
.
.
9 – Trailer
> \* For transactions in installments, one (1) record of this type will be generated per installment.
## 4. Record format
### **Record 0 – Header**
| Field Name | Minimum size |Maximum size | Informations |
| :--------------------------------------------- | -----------: | -----------: | :--------------------------------------------------------------------- |
| H01 - Record type | 1 | 1 | ‘0’ |
| H02 - File creation date | 8 | 8 | YYYYMMDD |
| H03 - File creation time | 6 | 6 | HHMMSS |
| H04 - Period - Start Date | 8 | 8 | YYYYMMDD |
| H05 - Period - End Date | 8 | 8 | YYYYMMDD |
| H06 - Layout Version | 5 | 5 | ‘V3.2’ |
| H07 - network identifier code | 1 | 3 | ‘00’ – More than one selected Network [See Table I](code-table) |
| H08 - File sequential number | 14 | 14 | |
| H09 - Sequential number of record in file | 6 | 6 | |
### **Registro 1 – Detalhes Venda**
| Field Name | Minimum size |Maximum size | Informations |
| :---------------------------------- | -----------: | -----------: | :--------------------------------------------------------------------- |
| V01 - Record Type | 1 | 1 | ‘1’ |
| V02 - Transaction Identifier | 1 | 30 | Custommer Code |
| V03 - Company Code | 1 | 15 | ‘’ |
| V04 - Sale Date | 8 | 8 | YYYYMMDD |
| V05 - Summary Number | 1 | 16 | ‘’ |
| V06 - receipt Number | 1 | 12 | ‘’ |
| V07 - SiTef's NSU | 1 | 12 | \* |
| V08 - Credit Card Number | 1 | 19 | ‘’ |
| V09 - Gross Value | 3 | 16 | No cent separator Gross Value of the installment, if divided into installments |
| V10 - Total Installments | 2 | 2 | For cash transactions = “00” |
| V11 - Net value | 1 | 16 | No cent separator Value of the installment, if divided into installments |
| V12 - Credit Date | 8 | 8 | AAAAMMDD |
| V13 - Installment Number | 2 | 2 | Installment Number | |
| V14 - Product Type | 1 | 1 | ‘C’ - credit ‘D’ – debit ‘V’ – voucher ‘S’ – withdraw ‘A’ – payment ‘F’ – Flex Car ‘T’ – debit with change
| V15 - Capture | 1 | 1 | ‘0’, ‘2’, ‘3’ – SiTef ‘1’, ‘4’ , ‘5’ – Others |
| V16 - Network identity code | 1 | 3 | [See table I](code- table) |
| V17 - Bank Number | 1 | 9 | ‘’ |
| V18 - bank branch number | 1 | 6 | ‘’ |
| V19 - checking account number | 1 | 20 | ‘’ |
| V20 - commission amount | 3 | 16 | No cent separator |
| V21 - Service Fee Amount | 3 | 5 | No cent separator Eg: 199 = 1,99 % |
| V22 - CodLojaSiTef | 8 | 8 | |
| V23 - Authorization Code | 0 | 12 | \*\* |
| V24 - Invoice | 0 | 20 | Invoice. Tax information transferred from the network to Sitef. If non existent, ``will be displayed.
| V25 - Credit Card Company Code | 4 | 4 | [See Table II](code-table) |
| V26 – Sale Date Sitef | 0 | 8 | \*\*\* YYYYMMDD date of sale registered on Sitef. If non existent, ‘’ will be displayed. |
| V27 – Sale Time Sitef | 0 | 6 | HHMMSS time of sale registered on Sitef. If non existent, ‘’ will be displayed. |
| V28 – POS | 0 | 9 | POS number. If not informed by the Authorizer, only the POS number of Reconciled transactions will be informed. If non existent, ‘’ will be displayed.
| V29 – Unique Summary Number | 0 | 22 | \*\*\* Exclusive to Cielo2 to find payment record, for other networks ´´ will be displayed
| V30 – Recovery file indication | 1 | 1 | \*\*\*\* Exclusive to Cielo2, for other networks ´will be displayed. 0 – Normal record 1 – Record from recovery file.
| V31 – Sale Time | 0 | 6 | When informed, Authorizer Sale Time. If not, ‘’ will be displayed.
| V32 – means of capture | 1 | 1 | |
| V33 – Tax Date | 8 | 8 | YYYYMMDD, This is the Sale Date of the transaction, subject to “fiscal time”. It may or may not be changed depending on the time the transaction was executed. Suitable for companies that consider the same date, even if the sale is made the next day until 02:00. |
| V34 – NSU_HOST_SITEF | 1 | 21 | For Reconciled transactions, the nsu_host information from the cash front will be displayed.If not, ‘’ Type: Alphanumeric´´ will be displayed.
| V35 - record sequence in the file | 6 | 6 | |
> \* For NON-TEF transactions, this field is filled with the receipt Number information (V06).
>
> \*\* In the case of Redecard Debit, Goodcard and Tecban, this data is not available in electronic statements.
>
> \*\*\* Exclusive field for Cielo2, this field is equivalent to the Unique Identification Number of the Operations Summary
formatted as follows:
>
> First Part - 15 fixed positions: identifies the summary while maintaining its history at Cielo.
>
> Second Part - 07 variable positions: for use by Cielo. Identifies the changes made to the Operations Summary
.
### **Registro 10 – Detalhes Crédito**
| Field Name | Minimum size |Maximum size | Informations |
| :---------------------------------- | -----------: | -----------: | :--------------------------------------------------------------------- |
| C01 - Record Type | 2 | 2 | ‘10’ |
| C02 - Transaction Identifier | 1 | 30 | Client Code |
| C03 - Company Code | 1 | 15 | ‘’ |
| C04 - Sale Date | 8 | 8 | YYYYMMDD |
| C05 - Summary Number | 1 | 16 | ‘’ |
| C06 - receipt Number | 1 | 12 | ‘’ |
| C07 - SiTef's NSU | 1 | 12 | \* |
| C08 - Credit Card Number | 1 | 19 | ‘’ |
| C09 - Gross Value | 3 | 16 | No cent separator Gross Value of the installment, if divided into installments |
| C10 - Total Installments | 2 | 2 | For cash transactions = ‘00’ |
| C11 - Net value | 1 | 16 | No cent separator Value of the installment, if divided into installments. If the value is lower than the value in the column "C12 - Original Net Value", it means that some event has changed the value to be paid. Value=“0”, means total cancellation of the amount to be paid. |
| C12 - Original Net Value | 0 | 16 |No cent separator Original Net Value, if divided into installments. Mainly used to indicate a cancellation by Redecard. empty if there is no unscheduling. |
| C13 - Credit Date | 8 | 8 | YYYYMMD |
| C14 - Original Credit Date | 0 | 8 | YYYYMMDD Mainly used to indicate an acceleration of Visa. empty in case there is no acceleration.
| C15 - Installment Number | 2 | 2 | Installment Number |
| C16 - Tipo Produto | 1 | 1 |‘C’ - credit ‘D’ – debit ‘V’ – voucher ‘S’ – withdraw ‘A’ - payment ‘F’ – flex ‘T’ – debit with change
| C17 – Capture | 1 | 1 | ‘0’, ‘2’, ‘3’ – SiTef ‘1’, ‘4’, ‘5’ – Others |
| C18 - Network identity code | 1 | 3 | [See Table I](code-table)
| C19 - Bank Number | 0 | 9 | It is not padded with leading zeros. If non existent, ´´ will be displayed.
| C20 - bank branch Number | 0 | 6 |It is not padded with leading zeros. If non existent, ´´ will be displayed.
| C21 - checking account number | 0 | 20 |It is not padded with leading zeros. If non existent, ´´ will be displayed.
| C22 - commission amount | 3 | 16 | No cent separator |
| C23 - Service Fee Value | 3 | 5 | No cent separator Eg: 199 = 1,99 % |
| C24 - CodLojaSiTef | 8 | 8 | |
| C25 - Authorization Code | 0 | 12 | \*\* |
| C26 - Invoice | 0 | 20 | Invoice Tax information transferred from the network to Sitef. If non existent, ``will be displayed
| C27 - Credit Card Company Code | 4 | 4 | [See table II](code-table
| C28 – Sale Date Sitef | 1 | 8 | YYYYMMDD, date of sale registered on Sitef, if non existent, ´´ will be displayed.
| C29 – Sale Time Sitef | 1 | 6 | HHMMSS date of sale registered on Sitef, if non existent, ´´ will be displayed.
| C30 – POS | 0 | 9 | POS Number. If not informed by the Authorizer, only the POS number of Reconciled transactions will be informed. If non existent, ´´ will be displayed. |
| C31 – Unified Summary Number | 0 | 22 | \*\*\* Exclusive to Cielo2 to find payment record, for other networks, ´´will be displayed.
| C32 – Recovery file indication | 1 | 1 | \*\*\*\* Exclusive to Cielo2, for other networks ´will be displayed. 0 – Normal record 1 – Record from recovery file.
| C33 – Sale Time | 0 | 6 | When informed, Authorizer Sale Time. If not, ‘’ will be displayed.
| C34 – means of capture | 1 | 1 | |
| C35 – Release Type | 1 | 2 | 0=Forecast, 1=Normal Settlement |
| C36 – Tax Date | 8 | 8 | YYYYMMDD, This is the Sale Date of the transaction, subject to “fiscal time”. It may or may not be changed depending on the time the transaction was executed. Suitable for companies that consider the same date, even if the sale is made the next day until 02:00. ||
| C37 – NSU_HOST_SITEF | 1 | 21 | For Reconciled transactions, the nsu_host information from the cash front will be displayed.If not, ‘’ Type: Alphanumeric´´ will be displayed
| C38 - Seq. do Registro no Arquivo | | | |
> \* For NON-TEF transactions, this field is filled with the receipt Number information (C06).
>
> \*\* In the case of Redecard Debit, Goodcard and Tecban, this data is not available in electronic statements.
>
> \*\*\* Exclusive field for Cielo2, this field is equivalent to the Unique Identification Number of the Operations Summary
formatted as follows:
>
> First Part - 15 fixed positions: identifies the summary while maintaining its history at Cielo.
>
> Second Part - 07 variable positions: for use by Cielo. Identifies the changes made to the Operations Summary
.
### **Registro 2 – Ajustes**
### **Registro 2 – Adjustments**
| Field Name | Minimum size |Maximum size | Informations |
| :-------------------------------- | -----------: | -----------: | :------------------------------------------------------------------------------------------ |
| A01 - Record Type | 1 | 1 | ‘2’ |
| A02 - Company Code | 1 | 15 | ‘’ |
| A03 - Adjustment Date | 8 | 8 | YYYYMMDD |
| A04 - Adjustment Value | 3 | 16 | No cent separator |
| A05 - Net Adjustment Value | 3 | 16 | No cent separator |
| A06 - Summary Number | 1 | 16 | ‘’ |
| A07 - Credit Card Number | 1 | 19 | ‘’ |
| A08 - Receipt Number | 1 | 12 | ‘’ |
| A09 - Sale Date | 8 | 8 | YYYYMMDD |
| A10 - Adjustment Reason Code | 1 | 15 | ‘’ |
| A11 - Description of Reason for Adjustment | 1 | 64 | ‘’ |
| A12 - Reference number | 1 | 15 | Exclusive Redecard (POS) |
| A13 - Original Summary Number | 1 | 10 | Exclusive Redecard |
| A14 - Reference Month | 6 | 6 | Exclusive Redecard (POS) |
| A15 - network identifier code | 1 | 3 | [See table I](code table) |
| A16 - Bank Number | 0 | 6 | It is not padded with leading zeros. If non existent, ´´ will be displayed. |
| A17 - bank branch Number | 0 | 6 | It is not padded with leading zeros. If non existent, ´´ will be displayed. |
| A18 - checking account number | 0 | 20 | It is not padded with leading zeros. If non existent, ´´ will be displayed. |
| A19 - commission amount | 3 | 16 | No cent separator |
| A20 - Service Fee Value | 3 | 16 | No cent separator |
| A21 - Codlojasitef | 8 | 8 | |
| A22 – Unified Summary Number | 0 | 22 | \*\*\* Exclusive to Cielo2 to find payment record, for other networks, ´´ will be displayed. |
| A23 - Record sequence in the file | 6 | 6 | |
> \*\*\* Exclusive field for Cielo2, this field is equivalent to the Unique Identification Number of the Operations Summary
formatted as follows:
>
> First Part - 15 fixed positions: identifies the summary while maintaining its history at Cielo.
>
> Second Part - 07 variable positions: for use by Cielo. Identifies the changes made to the Operations Summary
.
### **Record 100 – Anticipation Batch**
| Field Name | Minimum size |Maximum size | Informations |
| :-------------------------------- | -----------: | -----------: | :------------------------------------------------------------------------------------------ |
| L01 - Record Type | 3 | 3 | ‘100’ |
| L02 - Company Code | 1 | 15 | ‘’ |
| L03 - CodLojaSiTef | 8 | 8 | |
| L04 - Summary Number | 1 | 16 | ‘’ |
| L05 - Anticipated Credit Date | 8 | 8 | YYYYMMDD |
| L06 - Amount paid | 3 | 16 | Sem separador de centavos. Valor líquido pago. |
| L07 - network identifier code | 1 | 3 | [See Table I](code-table) |
| L08 - Installment | 2 | 2 | For batch with cash transactions = ‘00’ |
| L09 - Original Credit Date | 8 | 8 | YYYYMMDD
L10 - Original Net Value | 3 | 16 | No cent separator. Net value before anticipation. |
| L11 – Gross Value | 3 | 16 | No cent separator. Gross Value of the Anticipation. |
L12 - Bank Number | 1 | 9 | ‘’ |
| L13 - bank branch Number | 1 | 6 | ‘’ |
| L14 - checking account number | 1 | 20 | ‘’ |
| L15 – Unified Summary Number | 0 | 22 | \*\*\* Exclusive to Cielo2 to find payment record, for other networks, ´´will be displayed. |
| L16 - Record sequence in the file | 6 | 6 | |
> \*\*\* Exclusive field for Cielo2, this field is equivalent to the Unique Identification Number of the Operations Summary
formatted as follows:
>
> First Part - 15 fixed positions: identifies the summary while maintaining its history at Cielo.
>
> Second Part - 07 variable positions: for use by Cielo. Identifies the changes made to the Operations Summary
.
### **Registro 200 – Anticipated Transactions**
| Field Name | Minimum size |Maximum size | Informations |
| :--------------------------------- | -----------: | -----------: | :--------------------------------------------------------------------------------------------------------- |
| TA01 - Record Type | 3 | 3 | ‘200’ |
| TA02 - Transaction Identifier | 1 | 30 | Custommer Code |
| TA03 - Company Code | 1 | 15 | ‘’ |
| TA04 - Sale Date | 8 | 8 | YYYYMMDD |
| TA05 - Summary Number | 1 | 16 | ‘’ |
| TA06 - Receipt Number | 1 | 12 | ‘’ |
| TA07 - SiTef's NSU | 1 | 12 | \* |
| TA08 - Credit Card Number | 1 | 19 | ‘’ |
| TA09 - Gross Value | 3 | 16 | No cent separator Gross Value of the transaction |
| TA10 - total installments | 2 | 2 | For cash transactions = “00” |
| TA11 - Product Type | 1 | 1 | ‘C’ - credit ‘D’ – debit ‘V’ – voucher ‘S’ – withdraw |
| TA12 - Capture | 1 | 1 | ‘0’, ‘2’, ‘3’ – SiTef ‘1’, ‘4’ , ‘5’ – Others |
| TA13 - network identifier code | 1 | 3 | [See table I](code table) |
| TA14 - CodLojaSiTef | 8 | 8 | |
| TA15 - Authorization Code | 0 | 12 | \*\* |
| TA16 - Invoice | 0 | 20 | Invoice Tax information transferred from the network to Sitef. If non existent, ``will be displayed
| TA17 - Credit Card Company Code | 4 | 4 |[See table II](code-table) |
|| TA18 - Sale Date Sitef | 1 | 8 | YYYYMMDD if non existent ´´ wil be displayed
| TA19 - Hora Venda Sitef | 1 | 6 | HHMMSS if non existent ´´ wil be displayed
| TA20 – POS | 0 | 9 | POS Number |
| TA21 – Unified Summary Number | 0 | 22 | \*\*\* Exclusive to Cielo2 to find payment record, for other networks, ´´will be displayed.
| C32 – Recovery file indication | 1 | 1 | \*\*\*\* Exclusive to Cielo2, for other networks ´will be displayed. 0 – Normal record 1 – Record from recovery file.
| TA23 – Sale Time | 0 | 6 | When informed, Authorizer Sale Time. If not, ‘’ will be displayed. |
| TA24 – means of capture | 1 | 1 | |
| TA25 – Anticipated Installment | 2 | 2 | Anticipated Installment. For cash transactions=0
| TA26 - Seq. do Registro no Arquivo | 6 | 6 | |
> \* For NON-TEF transactions, this field is filled with the information on the Receipt Number (TA06).
>
> \*\* In the case of Redecard Débito, Goodcard and Tecban, this data is not available in electronic statements.
>
> \*\*\* Exclusive field for Cielo2, this field is equivalent to the Unique Identification Number of the Operations Summary
formatted as follows:
>
> First Part - 15 fixed positions: identifies the summary while maintaining its history at Cielo.
>
> Second Part - 07 variable positions: for use by Cielo. Identifies the changes made to the Operations Summary
.
**ATTENTION!**
**As of 12/09/2013, the Anticipated Transactions record will be sent for each installment of the anticipated transaction, unlike its initial behavior, where only 1 record was sent per transaction, with 1 or more anticipated installments**
### **Registro 9 – Trailer**
| Nome Campo | Tamanho Mín. | Tamanho Máx. | Informações |
| :--------------------------------------------- | -----------: | -----------: | :---------- |
| T01 - Record Type | 1 | 1 | ‘9’ |
| T02 - Sequential number of record in file | 6 | 6 | |
## 5. Observação
1. Limitações
1. Limitations
- Due to limitations of the data sent by the administrators, the Amex, Visa and Redecard have projected installments.
2. Suggestion of process for downloading the title and respective keys
- Use record 10 (normal settlement) and records 100 and 200 (anticipated settlement)
for the write-off of bills;
- In the Anticipations record, the relationship between each Batch(L) (Record 100) and its
details(TA)(Registration 200), for possible result of a new Record(LTA), are
respectively the fields:
L02 = TA03 (Company Code)
L03 = TA14 (CodLojaSiTef)
L04 = TA05 (Summary Number)
L07 = TA13 (Network identity code)
L08 = TA25 (Installment)
- The relation of settlement records (10, 100 and 200) with sales (record 1)
they are:
V03 = C03 = LTA02(result of merging records 100 and 200) Company Code
V04 = C04 = LTA04(result of merging records 100 and 200) Sale Date
V07 = C07 = LTA07(result of merging records 100 and 200) SiTef's NSU
V13 = C15 = LTA08(result of merging records 100 and 200) Installment Number
V16 = C18 = LTA07(result of merging records 100 and 200)Network identity code
- The fields to be updated upon write-off are: Amount Paid and Credit Date, being
represented in Record 10:
C11 Net Value
C13 Credit Date
- The fields to be updated upon write-off are: Amount Paid and Credit Date, being
represented in Record 100 :
L06 Value Paid in Advance
L05 Anticipated Credit Date
As it is a suggestion, we recommend the customer to validate whether these columns are sufficient.
## 6. Code Table
[Code Table](code-table)
## 7. Version Changes
- Version V3.6 on 06/07/2016 – Responsible.: Thiago Leite
- Inclusion of product type "T" = Debit with changeo.
- Version V3.6 on 04/15/2016 – Responsible.: Adriano
- Change in product description 0010, from table II from Visa Vale to Alelo.
- Version V4.0 on 02/11/2016 – Responsible.: Thiago Leite
- Version 4.0 was included, exclusive to SiTefGW Conciliação / SiTef Integradores, which maintains the same layout as V3.6 of SiTef Conciliação, but with all fields present without the need for previous configuration.
The “Authorization Code” field is now filled in for Redecard Debito, on reconciled transactions only.
- Version V3.6.1 on 11/26/ 2015 – Responsible.: Thiago Leite
- Added note about version V3.6.1, exclusive to SiTefGW Conciliação / SiTef Integradores, in Registry 200.
- Version V3.6 on 11/25/2015 – Responsible.: Adriano
- Inclusion of product type "F" = Flex Card.
- Inclusion of “idt_rede” codes
- Version V3.6 on 08/19/ 2015 – Responsible.: Adriano
- Inclusion of item 5.2: Suggestion of process to write off title and respective keys.
- Version V3.6 on 05/18/2015 – Responsible.: Adriano
- Inclusion of Credit Card Company Code 0023 - Avista.
- Version V3.6 on 10/03/2014 – Responsible.: Sérgio
- Inclusion of the Tax Date column in Record 10.
- Version V3.6 on 10/01/2014 – Responsible.: Adriano
- Inclusion of the Tax Date column in Record 1.
- Inclusion of nsu_host_Sitef column in Records 1 and 10.
- Version V3.6 on 05/24/2014 – Responsible.: Adriano
- Inclusion of the Credit Card Company Code Table II - "0022" - Hyper Debit
- Version V3.6 on 05/13/2014 – Responsible.: Adriano
- Inclusion of new Credit Card Company Codes Table II
- Version V3.6 on 03/18/2014 – Responsible.: Sergio
- Inclusion of the description of Means of Capture field in Record 1
- Version V3.6 on 02/21/2014 – Responsible.: Thiago Leite.
- Included paragraph about the origin of the return file in the Objective item.
- Changed the description of the Invoice Number field.
- Version V3.6 on 02/18/2014 – Responsible.: Artur.
- Inclusion of POS and Means of Capture fields in Record 200.
- Inclusion of two Credit Card Company Codes (0016, 0017) in Annex I - Table II
- Version V3. 6 on 12/23/2013 – Responsible. : Jefferson.
- Inclusion of a new column "Type of Entry" (configurable) in Record 10.
- Version V3.6 on 02/09/2013 – Responsible. : MKK.
- Changed behavior of record 200 (Anticipated Transactionss)
- Version V3.6 on 11/26/2013 – Responsible. : MKK.
- Added SisCred, Sorocred, CredSystem and CUP products to the Rede authorizer
- Version V3. 6 on 04/25/2013 – Responsible. : Adriano.
- Inclusion of a new Sale Time column (configurable).
- The bank fields: Bank Code, bank branch and Checking Account, now have their configurable sizes with zeros on the left.
- Version V3.6 on 03/28/2013 – Responsible. : Adriano.
- Inclusion of new POS column (configurable).
- Added field "Indication File Recovery" in records 1, 10 and 200.
- Version V3.5 on 11/09/2012 – Responsible. : Adriano.
- Inclusion of the brand code: 0010 - Visa Vale.
- Version V3.5 on 09/13/2012 – Responsible. : Junior.
- Modification of the column "Summary Number" field modified from 10 to 15
positions.
- Version V3.4 on 07/08/2012 – Responsible. : Adriano.
- Inclusion of the column "Unique Operations Summary Number" field with 22 positions exclusively for use
of Cielo2. Payment record identification
- Version V3.2 on 05/24/2012 – Responsible. : Adriano.
- Inclusion of the "Gross Value" column in record 100
- Version V3.1 on 05/16/2012 – Responsible. : Adriano.
- Inclusion of comment in Record 10 column C11 - Net Value
- Inclusion of new network codes
- Version V3.1 on 12/08/2011 – Responsible. : MKK.
- Inclusion of Anticipation Batch and Anticipated Transaction records
- Version V3.0 on 27/09/2011 – Responsible. : Adriano.
- Inclusão das colunas Data Venda SITEF e Hora Venda SITEF nos registros 1 e 10
- Version V3.0 on 27/05/2011 – Responsible. : Adriano.
- Correção nos tamanhos máximos dos campos V07 Registro 1 e C07 Registro 10 de 9 para 12 caracteres
- Version V3.0 on 03/10/2011 – Responsible. : Adriano.
- Inclusion of a new column: Credit Card Company Code, in Type 1 and 10 Records
- Version V2.0 on 03/04/2011 – Responsible. : Adriano.
- Inclusion of new Network codes
- Version V2.0 on 04/09/2010 – Responsible. : Adriano.
- Inclusion of Capture =5 as Non-TEF
- Version V2.0 on 01/27/2010 – Responsible. : Adriano.
- Inclusion of the comment in columns V07 and C
- Version V2.0 on 09/01/2009 – Responsible. : MKK.
- Inclusion of the product type = "S"(Withdraw)
- Version V2.0 on 21/01/2009 – Responsible. : MKK.
- Creation of the Credit Date and Sale Date record
- Negative Values record elimination
- Inclusion of the withdraw product type ('S') for Redecard and Visanet
- Version V1.9 on 11/06/2008 – Responsible. : MKK. ( return file version: 1.6.3 - 11/06/2008)
- Modification in the Redecard Installment form
- Version V1.8 on 11/06/2008 – Responsible. : Adriano. ( return file version:1.6.1-06/11/2008)
- Inclusion of the Invoice Code
- Version V1.7 on 10/09/2008 – Responsible. : MKK.
- Inclusion of the Authorization Code
- Version V1.6 on 01/31/2008 – Responsible. : Adriano Galati.
- Changing the Network Identifier Code column with new codes
- Version V1.5 on 04/20/2007 – Responsible. : Adriano Galati.
- Inclusion of product type "V" - voucher
- Inclusion of captures "2", "3" - TEF and "4" NON-TEF on 06/08/2007 – Adriano
- Changing the delimiter to “;” (RMISERVER v. 1.5.3 06/11/2007)
- Version V1.4 on 08/01/2006 – Responsible. : Adriano Galati.
- Inclusion of the identRede column in the Header;
- Inclusion of a new type of record 3 - Negative sales;
- Inclusion of Bank, bank branch, Checking Account Number , Codlojasitef columns in the Detailing and Adjustments;;
- Version V1.3 on 07/05/2005 – Responsible. : Adriano Galati.
- Version V1.2 on 05/04/2004 – Responsible. : Marcus Adolfo Lucio
- Version para V1.1;
- Inclusion of record type '2' - Adjustment record;
- Version V1 on 01/05/2003 - Responsible: Alexandro Alves Moreira
Updated 15 days ago