Transactions (Daily)
The daily transaction report is available by 9am PT.
This report contains settlement details about activity sent through the Transactions API, including reversals. Transactions originated before network cutoff times are included in this report.
Single vs Dual Message Cutoff Times May Impact ReportingSingle Message and Dual Message rails have varying cutoff times. If you use both, some daily reports generated at 9 AM PT may not reflect your expected total amounts. Remaining amounts will appear in the following day's report. For help, contact TabaPay Support, or email [email protected].
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 |
|---|---|---|
1 |
| 4-Digit ID assigned by TabaPay |
2 |
| Merchant ID (Identifies a specific program/merchant under the ISO) |
3 |
|
|
4 |
|
If Type = AVS, this is the avsID returned in the Query Card API response. |
5 |
| Corresponding TransactionID
|
6 |
| Network Approval Code |
7 |
| Date/Time (GMT) of the network response confirming that the transaction was processed |
8 |
| Date/Time (GMT) that TabaPay received the Transaction Request from the client |
9 |
| Transaction Type. Values include:
|
10 |
| For Purchases (pull): Network |
11 |
| For Purchases (pull): Settlement |
12 |
| Network Transaction Settled |
13 |
| Last 4 of beneficiary card (if the editor strips leading "0"s, left-pad “0s” to reach length 4) |
14 |
| Status of Transaction. Values include:
|
15 |
| |
16 |
| Transaction Amount. Passed in to Create Transaction API |
17 |
| Net Amount Settled
|
18 |
| TabaPay Fee for the Transaction |
19 |
| Network Fee for the Transaction |
20 |
| Interchange for the Transaction |
21 |
| Convenience Fee Merchant Charged |
22 |
| Cardholder First Name |
23 |
| Cardholder Last Name |
24 |
|
|
25 |
| Location Name passed in the Create Transaction API request. |
26 |
| Location Line 1 passed in the Create Transaction API request. |
27 |
| Location Line 2 passed in the Create Transaction API request. |
28 |
| Location City passed in the Create Transaction API request. |
29 |
| Location State Code passed in the Create Transaction API request. |
30 |
| Location Zip Code passed in the Create Transaction API request. |
31 |
| AVS Match Code received at the time of transaction. |
32 |
| CVV Match Code received at the time of transaction. |
33 |
| Transaction Network ID |
34 |
| Date Transaction Settled |
35 |
| Front of Card Brand |
36 |
| Card Type. Values include:
|
37 |
| Interchange Category |
38 |
| |
39 |
| First 6 of the Payment Card |
40 |
| Beneficiary amount in beneficiary currency, if disbursement sent in non-settlement currency |
41 |
| Beneficiary currency |
42 |
| FX Rate Applied, if disbursement sent in non-settlement currency. |
43 |
| Date OFAC was run (beneficiary) |
44 |
| OFAC results (beneficiary) |
45 |
| Issuing Name of Financial Institution |
46 |
| ISO 3166-1 Alpha-3 Code |
47 |
| Date OFAC was run (sender) |
48 |
| OFAC results (sender) |
49 |
| Sender First Name |
50 |
| Sender Last Name |
51 |
| Indicates how transaction was sent Valid values:
|
52 |
| Card network reference ID used for reconciliation and exceptions tracing Valid values: Asterisk followed by 23 characters Can be null |
53 |
| 22-character accountID returned in the Create Account API response Can be null |
54 |
| 29-character Payment Account Reference. Can be null |
55 |
| 2-character Merchant Advice Code (MAC). Relevant for MasterCard transactions only. Can be null |
Updated about 5 hours ago