Reporting
preconfigured reports help you manage business operations and reconcile account activity. Use the table below to identify the most suitable report for your specific task.
| TASK | SUGGESTED REPORT |
|---|---|
| Payments |
| Merchant Fees |
| Payout Summary, Payout Details |
| Disputes |
| Processing Summary |
| Interchange Details |
Generate a Report
To download a preconfigured report via the Dashboard:
- Navigate to the Reports page
- Locate the report you wish to download and click the Generate Report button
- Apply report filters and click the Generate Report button
- Click the Download icon once the report has completed downloading
Report customization
Reports can be filtered by account, timezone, and date range. Column selection options are also available for certain reports.
Account filter
Reports can be downloaded for a single account or across your entire portfolio.
Timezone selection
Reports are downloaded in your local timezone, determined by your computer’s settings. You can adjust the timezone to Pacific, Mountain, Central, or Eastern time when downloading a report.
Updating the timezone can be helpful when reconciling reports generated in different timezones.
Date range filter
Reports can be filtered on predefined date ranges or a custom date selection. The selected dates are inclusive. For example, selecting a date range of January 1, 2025 – January 31, 2025 will include data from 12:00 a.m. on January 1 through 11:59 p.m. on January 31 in the respective time zone.
Custom columns
Users can customize the columns in the Payments and Payout Details reports. Available options include default columns, all columns, or custom columns.
Report Details
Payments report
The Payments report is useful for tracking payment activity and analyzing payment failures. If generating via the Create a Report RunAPI endpoint, set type = payments_summary_2.
Default columns
| FIELD | DETAILS |
|---|---|
merchant_account_id | Unique merchant account id |
merchant | Merchant name |
transaction_date | Date transaction was processed |
transaction_type | Type of transaction, such as a charge or refund |
payment_method | Payment method used for the transaction |
transaction_id | Unique charge or refund id |
transaction_status | Status of the charge or refund |
failure_code | Failure code, if payment failed |
failure_description | Failure description, if payment failed |
authorized | Amount authorized |
captured | Amount captured |
fees | Total amount of associated fees |
net | Net amount of the payment; net = captured minus fees plus tips* |
related_charge_id | Related charge id, if transaction_type = refund |
Payout Summary report
The Payout Summary report is useful for tracking payout activity and reconciling bank deposits. If generating via the Create a Report RunAPI endpoint, set type = payouts_summary_3.
Available columns
| FIELD | DESCRIPTION |
|---|---|
merchant_account_id | Unique merchant account id |
merchant | Merchant name |
payout_date | Date payout was initiated |
payout_id | Unique payout id |
total_activity_amount | Sum of all transactions associated with the payout, include charges, refunds, disputes, and adjustments |
fee_amount | Total fees withdrawn from the payout |
payout_amount | Payout amount deposited or withdrawn from the merchant's bank account; net = gross minus fees |
Payout Details report
The Payout Details report is useful for reconciling individual transactions within a payout. If generating via the Create a Report RunAPI endpoint, set type = payouts_detail_1.
Default columns
| FIELD | DESCRIPTION |
|---|---|
merchant_account_id | Unique merchant account id |
merchant | Merchant name |
payout_date | Date payout was initiated |
payout_id | Unique payout id |
transaction_date | Date transaction was processed |
payment_method | Payment method associated with the transaction |
source_id | Unique source id |
transaction_type | Type of transaction, such as a charge, refund, dispute, or adjustment |
description | Detailed description of the transaction |
gross | Gross amount of the transaction |
fees | Total fees withdrawn from the payout that are associated with the transaction |
net | Net amount of the transaction; net = gross minus fees |
Merchant Fees report
The Merchant Fees report is useful for tracking posted fees, analyzing total processing costs, and understanding the amount due in the merchant’s next billing cycle. If generating via the Create a Report RunAPI endpoint, set type = fees_summary_1.
Available columns
| FIELD | DESCRIPTION |
|---|---|
merchant_name | Merchant name |
account_id | Unique merchant account id |
balance_transaction_id | Unique balance transaction id |
balance_transaction_created_at | Date the fee was created |
source_id | Unique id of fee source, such as the charge or refund id |
source_type | Source of balance transaction, such as the charge or refund |
payout_id | Unique payout id |
amount | Amount of the fee |
description | Fee description |
fee_type | Fee type, such as discount, transaction, or pass-through |
fee_subtype | Fee subtype, such as the pass-through fee type |
payment_method_type | Payment method used for the transaction |
card_brand | Card brand, if applicable |
payment_intent_id | Unique id of the payment intent |
charge_amount_captured | Amount captured |
Interchange Details report
The Interchange Details report is useful for analyzing interchange costs and identifying factors that impact interchange qualification. If generating via the Create a Report RunAPI endpoint, set type = interchange_detail_2.
Factors impacting interchange costs
- Payment method: Online payments generally have higher interchange costs than in-person payments.
- Funding type: Credit cards typically cost more to process than debit cards.
- Card type: Consumer and international cards often incur higher rates than business or commercial cards.
- Settlement time: Transactions settled more than two days after authorization may result in higher costs.
- Level 2/3 data: Payments missing level 2/3 data qualify only for level 1 rates.
- AVS/CVV data: Incorrect or missing avs/cvv data can lead to higher interchange fees.
- Merchant category code: Certain MCCs are subject to higher interchange rates.
Available columns
| FIELD | DESCRIPTION |
|---|---|
software_platform | Software platform name |
merchant | Merchant name |
merchant_account_id | Unique merchant account id |
processor | Processor through which payment was routed |
transaction_id | Unique charge or refund id |
transaction_type | Type of transaction |
payment_method | Payment method type, such as online or in-person |
transaction_date | Date transaction was processed |
settlement_date | Date transaction settled |
funding_type | Card funding type, such as debit or credit |
card_brand | Card brand |
card_bin | Card BIN |
interchange_program | Interchange program |
avs_address | Results of the AVS address check |
avs_zip_code | Results of the AVS zip code check |
cvv | Results of the CVV/CVC check |
level_2_3 | Indicates whether level 2/3 data was provided |
interchange_discount_rate | Interchange discount rate; the rate does not include any markups |
interchange_transaction_fee | Interchange transaction fee; the amount does not include any markups |
transaction_amount | Amount of the charge or refund |
transaction_count | Number of transactions that qualified for the interchange program |
total_interchange_cost | Total interchange cost = (transaction_amount*interchange_discount_rate) + (transaction_count*interchange_transaction_fee) |
Processing Summary report
The Processing Summary report is useful for comparing processing activity across merchants. If generating via the Create a Report RunAPI endpoint, set type = processing_summary_1.
Available columns
| FIELD | DETAILS |
|---|---|
merchant_name | Merchant name |
account_id | Unique merchant account ID |
start_at | Start date of the selected time period |
end_at | End date of the selected time period |
succeeded_charge_volume | Volume of successful charges |
succeeded_charge_count | Number of successful charges |
failed_charge_volume | Volume of failed charges |
failed_charge_count | Number of failed charges |
succeeded_refund_volume | Volume of successful refunds |
succeeded_refund_count | Number of successful refunds |
won_dispute_volume | Volume of disputes, where dispute was ruled in favor of the merchant |
won_dispute_count | Number of disputes, where dispute was ruled in favor of the merchant |
lost_dispute_volume | Volume of disputes, where dispute was ruled in favor of the cardholder |
lost_dispute_count | Number of disputes, where dispute was ruled in favor of the cardholder |
total_dispute_volume | Total volume of disputes |
total_dispute_count | Total number of disputes |
charge_fee_volume | Volume of charge-related fees |
refund_fee_volume | Volume of refund-related fees |
dispute_fee_volume | Volume of dispute-related fees |
administrative_fee_volume | Volume of administrative-related fees |
Disputes report
The Disputes report is useful for analyzing dispute activity, including dispute reasons. If generating via the Create a Report RunAPI endpoint, set type = disputes_summary_1.
Available columns
| FIELD | DETAILS |
|---|---|
account_id | Unique merchant account id |
merchant_name | Merchant name |
dispute_id | Unique dispute id |
created_at | Date dispute was created |
currency | Currency of the original payment |
dispute_amount | Amount being disputed by the cardholder |
reason_description | Reason for the dispute, as provided by the cardholder |
status | Status of the dispute when the report is generated |
closing_at | Deadline to submit evidence in response to the dispute |
reversed_at | Date dispute was reversed, if applicable |
charge_id | Unique id of the original payment |
charge_amount_captured | Amount of the original payment |
charge_refunded | Whether the payment was refunded |
amount_refunded | Amount of the refund, if payment was refunded |