Transaction Detail (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.
File name: YYYYMMDD_txndetail.csv
Note: Transaction Details Report differs from the Transactions (Daily) 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].
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
May be null |
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: Network For Disbursements: Settlement |
11 |
| For Purchases: Settlement For Disbursements: Network |
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 request. |
26 |
| Location Line 1 passed in the Create Transaction request. |
27 |
| Location Line 2 passed in the Create Transaction request. |
28 |
| Location City passed in theCreate Transaction request. |
29 |
| Location State Code passed in the Create Transaction request. |
30 |
| Location Zip Code passed in the Create Transaction request. |
31 |
| AVS Match Code received at the time of transaction. |
32 |
| CVV Match Code received at the time of transaction. |
33 |
| Network Transaction 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 (Present if |
41 |
| Beneficiary Currency Code (ISO 4217 Alpha 3, Present if |
42 |
| FX Rate Applied (Present if |
43 |
| OFAC Screening Date of Cardholder |
44 |
| Cardholder's OFAC Results |
45 |
| Issuing Name of Financial Institution |
46 |
| ISO 3166-1 Alpha-3 Code |
47 |
| OFAC Screening Date of Corresponding Entity If |
48 |
| OFAC Results of Corresponding Entity If |
49 |
| Corresponding Entity First Name If |
50 |
| Corresponding Entity Last Name If |
51 |
| Indicates how transaction was sent Valid values:
|
52 |
| Acquirer Reference Number. Used for reconciliation and exceptions tracing Format: Asterisk (*) followed by 23 characters Can be null |
53 |
| 22-character TabaPay Can be null |
54 |
| 29-character Payment Account Reference. See here for more information about PAR. Can be null |
55 |
| 2-character Merchant Advice Code (MAC). Relevant for MasterCard transactions only. See here for more information about MAC Can be null |
Updated 11 days ago