Exceptions (Daily)
The exceptions files can be used by treasury and accounting teams to reconcile funds movement associated with exception items. Chargebacks, returns, and adjustments are included in this file.
The Exceptions Report is generated daily. If there are no exceptions for the day, then an empty report is generated (header only).
Notification of Change (NOC) Appearing in the Exceptions File
Notification of Change (NOC) does not mean a failed ACH transaction. The related ACH transaction should still process as expected. It is only a notice to update customer’s records to avoid any issues with future payments. Learn more →
Report Names
If you are configured to receive reports at the ISO level, the file name format will be: ISO_YYYYMMDD_reportname (e.g. 1234_20251017_reportname.csv)
If you are configured to receive reports at the MID level, the file format name will be: ISO_MID_YYYYMMDD_reportname (e.g. e.g. 1234_321_20251017_reportname.csv)
Key Fields
| Position | Field | Description | Data Type | Data Format |
|---|---|---|---|---|
| 1 |
| 4-Digit ID assigned by TabaPay | Numeric | 4 digits |
| 2 |
| Merchant ID (Identifies a specific program/merchant under the ISO) | Numeric | 4+ digits |
| 3 |
| referenceID sent by the merchant in the Create Transaction API request | Alphanumeric | 1-15 characters |
| 4 |
| transactionID sent by TabaPay in the Create Transaction API response | Alphanumeric | 22 characters |
| 5 |
| Unique reference number generated by TabaPay for each exception. | Alphanumeric | ~15 characters |
| 6 |
|
| Alphanumeric | Text |
| 7 |
| Network-specific reason code | Alphanumeric | Text |
| 8 |
| Description of the Exception Code | Alphanumeric | Text |
| 9 |
| Date exception posted. Corresponds with the date of the report. | Date (MM/DD/YYYY) | MM/DD/YYYY |
| 10 |
| Indicates the status of the exception. | Alphanumeric | Text |
| 11 |
| Date of most recent change in Action Status. This is the date of the Exceptions report. | Date (MM/DD/YYYY) | MM/DD/YYYY |
| 12 |
| Days since last movement of funds. | Alphanumeric | 1+ digit |
| 13 |
| Acquirer Reference Number (ARN) | Alphanumeric | 9-24 characters |
| 14 |
| Date/Time (GMT) original Transaction Request was created | Date (MM/DD/YYYY) | MM/DD/YYYY |
| 15 |
| Date/Time (GMT) Transaction processed at the Network | Date (MM/DD/YYYY) | MM/DD/YYYY |
| 16 |
| Purchase Disbursement Adjustment - credit | Alphanumeric | Text |
| 17 |
| If "Exception type" = CHARGEBACK, exception source = Settlement If "Exception type" = REPRESENTMENT, exception source = the exception card network | Alphanumeric | Text |
| 18 |
| If "Exception type" = CHARGEBACK, exception destination = the exception network If "Exception type" = REPRESENTMENT, exception destination = Settlement | Alphanumeric | Text |
| 19 |
| Network card scheme or ACH | Alphanumeric | Text |
| 20 |
| Last 4 of beneficiary card (add “0s” in front of number if less than 4 digits) | Numeric | 4 digits |
| 21 |
| Original transaction amount | Decimal | 1+ digits |
| 22 |
| Original transaction amount | Decimal | 1+ digits |
| 23 |
| TabaPay fee for the exception | Decimal | 1+ digits |
| 24 |
| Network fee for the exception | Decimal | 1+ digits |
| 25 |
| Interchange for the exception | Decimal | 1+ digits |
| 26 |
| memo passed in the Create Transaction API request. | Alphanumeric | 1-32 characters |
| 27 |
| Case ID assigned by the card network. | Alphanumeric | Text |
| 28 |
| First Name | Alphanumeric | Text |
| 29 |
| Last Name | Alphanumeric | Text |
| 30 |
| Original transaction Network ID | Alphanumeric | Text |
| 31 | PAR | 29-character Payment Account Reference. Can be null. For more info, refer to Payment Account Reference (PAR). | Alphanumeric | 29 characters |
| 32 | MAC | 2-character Merchant Advice Code (MAC). Relevant for MasterCard transactions only. Can be null. For more info, refer to Merchant Advice Code. | Numeric | 2 characters |