Interface Specification
Reconciliation Interface Specification
TJ Generic Reconciliation file format. This specification defines the interface for daily transactional reconciliation between participants.
Overview
Transaction Junction performs a daily audit to ensure the merchant's sales records match the bank's records. To do this, we ingest two datasets: the Client File (the store's record of sales) from the merchant point of sale system and the Provider File (the bank or authorising entity's record of approvals). TJ cross-references these files at the line-item level to identify “ghost” transactions or missing funds, supporting both individual store files or a consolidated estate-wide file.
Filename, Format & Content Guidance
The Client file follows a strict data input specification. Please follow the below specifications regarding file name, header record, detail record and trailer record. The overall file is formatted as ASCII (Basic Characters Only) with comma-separated fields.
Example Client File
Amazon_Consolidated_RECON_110226_073000.txtClick a section in the file to see its documentation
Before submitting your file, please validate it. The most common integration issues we see — missing comma delimiters for blank fields, amounts sent in rands instead of cents, omitted mandatory fields, and incorrect field ordering — are all caught instantly by our free validation tool. Test your file now →
Detail Record Fields — Requirements by Product Type
The file should contain all approved and unreversed transactions for the day. Each record should be populated per the grid below.
| Field Name | EFT | AIR | QR | LOY | eCom | Vouch | Example | Notes |
|---|---|---|---|---|---|---|---|---|
| Batch number | Opt | Opt | Opt | Opt | Opt | Opt | N/A | — |
| Terminal ID | Req | Req | Opt | Req | Opt | Opt | 18160001 | — |
| Merchant ID | Req | Req | Req | Req | Req | Req | 000000001732742 | Card Acceptor ID for QR |
| STAN | Req | Req | Req | Req | Opt | Opt | 097118 | — |
| Transaction Reference Number | Req | Req | Req | Req | Opt | Opt | 097118020678 | — |
| System Reference Number | Opt | Opt | Opt | Opt | Opt | Opt | 097118020678 | — |
| Local date and time | Req | Req | Req | Req | Req | Req | 20201130175549 | — |
| Business date | Opt | Opt | Opt | Opt | Opt | Opt | 20201130 | — |
| Transaction Type | Req | Req | Req | Req | Req | Req | 00 | ECOM/REDEMPTION: 00 = purchase, 20 = refund |
| Masked PAN/account number | Req | Req | Opt | Req | Req | N/R | 410588******4110 | AIR: 000000******0000 |
| Product ID | Req | Req | Req | Req | Opt | Req | EFT / AIR / QR / LOY / ECOM / REDEMPTION | — |
| Amount | Req | Req | Req | Req | Req | Req | 5000 | Minor denomination (cents) |
| Authoriser | Opt | Opt | Opt | Opt | Opt | Opt | N/A | — |
| Product name | Opt | Opt | Opt | Opt | Opt | Req | N/A | REDEMPTION: set to voucher number |
| Message type | Opt | Opt | Opt | Opt | Opt | Opt | N/A | — |
| Response code | Req | Req | Req | Req | Req | Req | 00 | 00 = Approved, 05 = Declined |
| Extended transaction type | Opt | Opt | Opt | Opt | Opt | Opt | N/A | — |
| Products list | Opt | Opt | Opt | Opt | Opt | Opt | diesel02;50.00;20.00;2.50 | — |
| Unique Transaction Identifier | Req | Req | Req | Req | Req | Req | f81d4fae-7dec-11d0-a765-00a0c91e6bf6 | — |
| Account Type | Opt | Opt | Opt | Opt | Opt | N/R | 20 | — |
Field Definitions
The table below defines every field in the reconciliation interface. Use the search box to filter by field name, format, or description.
| Field Name | Format | Description |
|---|---|---|
| Name | ANS..50 | Set to <Name>. When providing a file per store: Name = MerchantID. When providing a consolidated file: Name = Customer or POS provider. |
| Version | N..3 | Version, indicating the version of the file format. The version for this format is 2.5. |
| Business Date | yyyymmdd | The business date on which the transactions were performed. |
| Batch number | Int | The transaction batch ID (e.g. the batch from a POS processing session). |
| Terminal ID | ANS..8 | The PosID of the terminal used to perform the transaction. Can be supplied by the acquirer or Transaction Junction. |
| Merchant ID | ANS..15 | The store ID or provider merchant ID. |
| STAN | N6 | The auto incremented system trace audit number on the terminal being used. |
| Transaction Reference Number | ANS12 | The retrieval reference number of the transaction. |
| System Reference Number | ANS..32 | Optional reference number. |
| Local date and time | yyyymmddhhmmss | The date and time on which the transaction was performed. (24 hr format) |
| Business date | yyyymmdd | The date on which the transaction was performed. |
| Transaction Type | N2 | Map the TranType value as follows: PUR = 00, PCB = 09, CWD = 01, RET = 20, LOY = 21. |
| Masked PAN/Card number | ANS..30 | Set to PAN when transaction is associated to a card. Set to loyalty card number for loyalty transactions. Set to 000000******0000 for airtime. Do not set where not required. |
| Product ID | ANS..50 | Possible values: EFT (Card present), AIR (Airtime), QR (QR transactions), LOY (Loyalty), CASH (Cash), ECOM (eCommerce / Card Not Present), REDEMPTION (Voucher redemption). |
| Amount | N..12 | The full transaction payment amount in minor denomination (cents, not rands). For example, R50.00 = 5000. |
| Authoriser | Varchar(50) | The name of the payment authoriser. |
| Product name | Varchar(50) | The name of the product / Voucher number. |
| Message type | Char(4) | ISO 8583 message type. |
| Response code | AN2 | Indicates the final outcome of the transaction. Use the code received in the online message response if available, otherwise "00" to indicate approval and "05" to indicate decline. |
| Extended transaction type | Char(6) | Extended transaction type qualifier code. |
| Products list | ANS..255 | A list of products purchased. Each product separated by "|". Every product contains SKU, total amount, unit price and quantity. Values should have 2 decimals. Format: <SKU>;<TotalAmount>;<UnitPrice>;<Quantity>|<SKU>;<TotalAmount>;<UnitPrice>;<Quantity> |
| Unique Transaction Identifier | ANS 36 | The UTI should reflect the UTI used in the online message. Must conform to UUID format as per RFC 4122, populated with hyphens intact. Example: f81d4fae-7dec-11d0-a765-00a0c91e6bf6. |
| Account Type | N.2 | Indicates if the transaction was debit or credit. 00 = Default/unspecified (debit), 10 = Savings, 20 = Cheque, 30 = Credit, 40 = Universal. |
Chat with James from signal-studios.dev, the builders of this site, .