Exceptions (Daily)
The Exceptions Report is generated daily. If there are no exceptions for the day, then an empty report is generated (header only). Chargebacks, returns, and adjustments are included in this file. The exception transaction is posted to the file the day TabaPay receives notification of the exception.
| Position | Field | Description |
|---|---|---|
| 1 | ISO | |
| 2 | MID | |
| 3 | Merchant Reference ID | referenceID sent by the merchant in the Create Transaction API request |
| 4 | Original Transaction ID | transactionID sent by TabaPay in the Create Transaction API response |
| 5 | Exception ID | Unique reference number generated by TabaPay for each exception. |
| 6 | Exception type | |
| 7 | Exception Code | Network-specific reason code |
| 8 | Exception Description | |
| 9 | Exception Date | Date exception posted. Corresponds with the date of the report. |
| 10 | Action-Status | |
| 11 | Status Date | |
| 12 | Days Open | |
| 13 | Network Transaction ID | |
| 14 | Original Creation Date | |
| 15 | Original Processed Date | |
| 16 | Original Transaction Type | |
| 17 | Exception Source | |
| 18 | Exception Destination | |
| 19 | Exception Network | |
| 20 | Last 4 | Last 4 of beneficiary card (add “0s” in front of number if less than 4 digits) |
| 21 | Original Settled Amount | |
| 22 | Exception Settled Amount | |
| 23 | TabaPay Fee | |
| 24 | Network Fee | |
| 25 | Interchange | |
| 26 | Memo | |
| 27 | CB ID | |
| 28 | Firstname | |
| 29 | Lastname | |
| 30 | Network ID |
The Exceptions reports contain information about all exception items that do not pass through the API. The Exceptions reports contain chargeback records whenever there is a movement of funds. A chargeback case may appear on the Exceptions report multiple times throughout its lifecycle.
Updated about 2 months ago