If a merchant requests a Reconciliation (Recon) file from Ecentric (for the purpose of e.g. reconciliation), Ecentric would be able to provide the merchant with a Recon file which includes their transactions that have completed on the previous day.

Description

The Payment Gateway Recon file contains details of transactions that have completed since the last recon file was processed.

📘
NOTE: The Recon file typically includes all transactions that completed on the previous day. However, it may also include completed transactions that have not been included in a previous Recon file.

A single file will be created per day and include both successful and failed transactions.

Fields are delimited by the pipe symbol (vertical bar, |). Records are terminated by carriage return line feed (CR-LF). The file layout consists of a header, detail and trailer sections. The file will contain just a header and trailer sections if there are no detail records. The receiver will therefor always receive a file even if it contains no actual data records to know whether the communication channel is working or not.

Method of Integration

The merchant has the option of accessing the Recon file via SFTP (Secure File Transfer Protocol). From Ecentric’s side, a file will be set up for the merchant and by means of a public key. Please refer to the SFTP Account Setup section for more information.

File Structure

A file may contain only 1 batch.

Each batch includes:

A header record
Many detail records
A trailer record

Records are defined as detailed level transactions.

File Name

The file name must contain the date of the file, to ensure uniqueness, and to avoid overwriting existing files.

File Level Rules

A file contains all mark-off entries at the time of processing of transactions.
The total records in the trailer must equal the total count of all detail records in the file.
The amount in the trailer must be the sum of the transaction amount on all detail records.

File Versions

There are currently 2 versions of the Recon File:

Version 2
Version 4 - uses the same format as Version 2 with additional fields at the end of each record

Record Formatting

The file data is encoded using standard ASCII character set.

Record Delimiters: Each record in the file is delimited by the carriage return line feed, ASCII characters: 0D0A (<CR><LF>).

Field Delimiters: Fields are delimited by the pipe symbol (vertical bar, |).

Record Details

The file layout consists of a header, detail and trailer sections.

The file will contain just a header and trailer sections if there are no detail records. The receiver will therefore always receive a file even if it contains no actual data records to know whether the communication channel is working or not.

Blanks are allowed for all fields excluding RecordType field in the Header and Detail sections.

📘
IMPORTANT NOTE: placeholder fields have been allocated at the end of each record for future enhancements. Please note that further additional fields may be added at the end of each record in the future.