This refers to the file interface specifications from an Acquiring System to Online Payments. The data is recorded in the Online Payments Application for the purpose of reconciling CNP and MasterPass transactions.

On a daily basis, the acquiring system sends a record of all transactions received (excluding online declines), at a detail level, and processed by their batch processing system. The acquirer mark-off files we receive from acquirers with these transactions are only for successful transactions.

If a merchant requests a mark-off file from Ecentric (for the purpose of e.g. reconciliation), Ecentric would be able to provide the merchant with a mark-off file which includes their transactions of the day.

Description

The file mark-off service provides the merchants with their very own mark-off file of all CNP and MasterPass transactions, which the merchant is able to access through SFTP with the aid of a public key. CNP and/or MasterPass transactions will be present in the mark-off file dependent on the merchant being configured for these payment methods. CNP and MasterPass transactions will be in separate mark-off files.

Method of Integration

The merchant has the option of accessing the mark-off 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, the merchant will be able to access their mark-off file. 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, across bank (acquirer) purchase/refund 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.

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 ().

Field Delimiters: This is a positional formatted file.

Padding: Field’s may be left padded with zero.

Record Details

Header Record

FIELD NO.	FIELD NAME	DEFINITION	DESCRIPTION
1	Record type	Record type	Will always be the character ‘H’
3	Date	PIC 9(06)	YYMMDD
4	File number	PIC 9(10)	A batch number for the file, this should be sequential and unique

Detail Record

FIELD NO.	FIELD NAME	DEFINITION	DESCRIPTION
1	Record Type	PIC X(01)	Will always be the character ‘D’
2	Merchant Number	PIC 9(12)	The merchant number of the store where the transaction took place
3	Transaction Account Number (PAN)	PIC X(23)	Numeric value. The masked bank card number.
4	Transaction Type	PIC 9(02)	See transaction Type list below
5	Reject Reason Code	PIC 9(03)	Supplied rejection code from Acquirer
6	Transaction Date	PIC 9(06)	YYMMDD
7	Transaction Time	PIC 9(06)	HHHMMS
8	Settlement Date	PIC 9(06)	The date the bank (acquirer) will settle the transaction
9	Transaction Amount	PIC 9(13)V99	Numeric value (no decimal point) in cents
10	Cashback	PIC 9(13)V99	Numeric value (no decimal point) in cents
11	Transaction Authorisation Code	PIC X(10)	The authorization code returned by the bank
12	Card Type	PIC X(02)	See card type list below
13	POS Entry Mode	PIC X(03)	POS Entry mode
14	Cashier Number	PIC X(06)	Cashier number
15	Retrieval Reference Number	PIC X(12)	For Card Not Present (CNP) transactions: The first 12 characters of the merchant reference/order number field will be sent to the acquirer/bank as the Retrieval Reference Number (RRN). Only a maximum of 12 characters are sent due an acquirer/bank limitation to support more characters for this field. The first 12 characters should to be unique as duplicate RRN’s may cause a transaction to fail acquirer/bank validation. Merchants need to ensure that they do not resend the same merchant reference through to Ecentric if the user initiates the payment (after adding items to a shopping cart), cancels, and then goes to pay again. Settlement rules taken into account more fields than only the RRN and hence transactions with merchant references longer than 12 characters may still be settled. The bank mark-off file showing settled transactions will show the 12 character RRN and not the merchant reference. Hence if required, other fields need to be used to reconcile the RRN to the merchant reference. For MasterPass transactions: The bank mark-off file showing settled transactions will show the RRN generated from MasterPass. Hence if required, other fields need to be used to reconcile the RRN to the merchant reference.
16	System Trace Audit Number (STAN)	PIC 9(6)	The ISO Stan (ABSA does not provide this field)
17	GUID	PIC 9(36)	Unique Identifier assigned to Merchant (not displayed)
18	Terminal ID	PIC X(08)	POS Terminal ID (This is hard coded per merchant)

Trailer Record

FIELD NO	FIELD NAME	DEFINITION	DESCRIPTION
1	Record Type	PIC X(01)	Will always be the character ‘T’
2	Total records	PIC 9(9)	Numeric value
3	Total of transaction amount	PIC 9(15V99)	Tallied on transaction amount

Card Types

The card type according to the acquirer. Below is a sample list:

CARD TYPE	CODE
Debit	00
Credit	01
Hybrid	02

Transaction Types

At least the following transaction types should be supplied:

TRANSACTION TYPE	CODE (FROM POSTILION
Purchase	00
Refund	200