Disputes by Dispute Date Report
Monitor current chargeback and alert activity based on the date each dispute was filed, with card brand breakdowns and fee tracking.
The Disputes by Dispute Date Report shows you what dispute activity is happening right now. Disputes are grouped by the date they were filed, giving you a real-time view of chargeback and alert volume. Use this report to detect spikes in dispute activity as they happen and respond before card network thresholds are breached.
What This Report Includes
This report pulls successful sale and capture transactions alongside chargebacks and alerts that were processed during the selected date range. Charges and disputes in this view are not necessarily related — a chargeback filed today may be against a sale from months ago.
Transactions Included:
- Successful, non-declined sale and capture transactions
- Chargeback and alert transactions
- Only transactions with a charge amount greater than $0
- Test orders are excluded
- Date range is based on Transaction Completed Date (when the charge or dispute was processed)
Why This Matters: This view answers "What dispute activity happened during this period?" Charges provide the baseline denominator for rate calculations, but the disputes shown may originate from sales in earlier periods. This is the view to use for monitoring current dispute volume and identifying operational spikes.
Revenue calculations depend on your Company Profile settings for shipping and tax inclusion.
Prerequisites
For dispute fee tracking to be accurate, fee amounts must be configured on your merchant accounts. Learn how to set up fees here.
Report Metrics
Charges
The total count of successful charges processed during the selected period. This serves as the denominator for dispute rate calculations, but note that the disputes in this view may not be related to these specific charges.
Processed Revenue
The total revenue amount processed from all charges during the selected period, including tax and shipping.
Disputes
The total count of disputes filed during the selected period, combining chargebacks and alerts.
Dispute Revenue
The total revenue amount associated with disputes filed during the selected period.
Dispute Charge Rate
The percentage of disputes to charges. Calculated as Disputes divided by Charges. Because disputes may originate from charges in earlier periods, this is a volume ratio rather than a true cohort rate.
Dispute Revenue Rate
The percentage of dispute revenue to processed revenue. Calculated as Dispute Revenue divided by Processed Revenue.
Dispute Fees
The total fees incurred from all dispute activity during the selected period, combining chargeback fees and alert fees.
Chargebacks
The total count of chargebacks filed during the selected period.
Visa Chargebacks
The total count of Visa chargeback transactions filed during the selected period. Track separately to monitor your standing against Visa's Dispute Monitoring Program (VDMP).
Mastercard Chargebacks
The total count of Mastercard chargeback transactions filed during the selected period. Track separately to monitor your standing against Mastercard's Excessive Chargeback Program (ECP).
Other Card Chargebacks
The total count of chargeback transactions for card brands other than Visa and Mastercard (e.g., American Express, Discover).
Chargeback Revenue
The total revenue amount associated with chargebacks filed during the selected period.
Chargeback Charge Rate
The percentage of chargebacks to charges. Calculated as Chargebacks divided by Charges. Card network thresholds are typically 0.9% (Visa) and 1.0% (Mastercard).
Chargeback Revenue Rate
The percentage of chargeback revenue to processed revenue. Calculated as Chargeback Revenue divided by Processed Revenue.
Chargeback Fees
The total fees assessed for chargeback disputes during the selected period.
Refund to Chargeback
The total count of chargebacks that were filed on charges which had also received a refund.
Refund to Chargeback Rate
The percentage of chargebacks that also had refunds. Calculated as Refund to Chargeback divided by Chargebacks.
Alert to Chargeback
The total count of chargebacks that were filed on charges which had also received an alert.
Alert to Chargeback Rate
The percentage of chargebacks that also had alerts. Calculated as Alert to Chargeback divided by Chargebacks.
Alerts
The total count of alert transactions received during the selected period from services like Ethoca and Verifi.
Alert Revenue
The total revenue amount associated with alert transactions during the selected period.
Alert Charge Rate
The percentage of alerts to charges. Calculated as Alerts divided by Charges.
Alert Revenue Rate
The percentage of alert revenue to processed revenue. Calculated as Alert Revenue divided by Processed Revenue.
Alert Fees
The total fees charged by alert service providers during the selected period.
Available Dimensions
Use these dimensions to slice and filter your dispute data for deeper analysis.
| Dimension | Description |
|---|---|
| Transaction Date | The date the transaction was processed |
| Transaction Hour | Hour of day when the transaction was processed (0–23) |
| Transaction Day Of Week | Day of the week the transaction was processed |
| Transaction Week | ISO week number of the transaction |
| Transaction Month | Month and year of the transaction |
| Transaction Year | Year the transaction was processed |
| Customer ID | The customer's ID in the system |
| Customer Email | The customer's email address |
| Customer Name | The customer's full name |
| Customer Information | Combined customer details (name, email, phone) for searching |
| Connection | The connection (CRM instance) associated with the customer |
| Order ID | The unique order identifier |
| Transaction ID | The unique transaction identifier |
| Transaction Attempt | The attempt number for this charge |
| Transaction Cycle | The billing cycle of the transaction |
| Transaction Total | The total amount of the transaction |
| Transaction Type | The type of transaction (e.g., Sale, Capture, Chargeback, Alert) |
| Transaction Created User | The user or process that created the transaction |
| Transaction Descriptor | The billing descriptor shown on the customer's statement |
| Offer Status | The current status of the offer |
| Initial Offer | The offer on the initial charge |
| Initial Charge Offer | The offer tied to the initial charge transaction |
| Initial Charge Offer Code | Code of the offer on the initial charge |
| Initial Charge Offer Cycle | Billing cycle of the initial charge |
| Initial Charge Offer Attempt | Attempt number of the initial charge |
| Initial Charge Primary Offer Category | Primary category of the initial charge offer |
| Initial Charge Secondary Offer Category | Secondary category of the initial charge offer |
| Alert|Chargeback Code | Reason code for alerts or chargebacks |
| Days To Chargeback | Number of days between the transaction and the chargeback |
| Days To Refund | Number of days between the transaction and the refund |
| 3DS Verified Status | 3D Secure verification status |
| Has Gift | Whether the order was marked as a gift |
| Has Prepaid | Whether the order involved a prepaid offer |
| Has Discount Code | Whether a discount code was applied |
| Is Blacklist | Whether the customer is on the blacklist |
| Offers | The offers associated with the order |
| Offer Names | Display names of the offers on the order |
| Items | The items associated with the order |
| Item SKUs | The SKUs of items on the order |
| Campaign | The campaign associated with the order |
| Primary Campaign Category | Primary category assigned to the campaign |
| Secondary Campaign Category | Secondary category assigned to the campaign |
| Discount Codes | Discount or coupon codes applied to the order |
| Discount Name | Display name of the applied discount |
| Merchant | The merchant account used for processing |
| Merchant Group | The merchant group the merchant belongs to |
| Merchant Descriptor | The merchant's billing descriptor |
| Merchant MCC Code | The merchant category code |
| Primary Merchant Category | Primary category assigned to the merchant |
| Secondary Merchant Category | Secondary category assigned to the merchant |
| Processor | The payment processor used |
| Processor Response | The response message from the processor |
| Gateway | The payment gateway used |
| Gateway Transaction ID | The gateway's transaction identifier |
| Gateway AVS Code | Address Verification System response code |
| Gateway CVV Code | Card Verification Value response code |
| Gateway Response Code | The gateway's response code |
| Payment Method | The payment method used for the transaction |
| Payment Router | The payment router that directed the transaction |
| Card Bin Number | First six digits of the card number identifying the issuing bank |
| Card Bin Number + Card Last 4 | BIN and last 4 combined |
| Card Last 4 | Last 4 digits of the card number |
| Card Type | Card brand (e.g., Visa, Mastercard, Amex) |
| Card Issuer | The bank or institution that issued the card |
| Card Category | Category of the card (e.g., Consumer, Business) |
| Card Country | Country where the card was issued |
| Is Prepaid Card | Whether the card is a prepaid card |
| Currency | The transaction currency |
| Ship Country | Shipping destination country |
| Ship State | Shipping destination state or province |
| Tracking 1–20 | Custom tracking parameters on the order |
| Device | The device used to place the order |
| Device Type | The type of device (e.g., Desktop, Mobile, Tablet) |
| Referrer Domain | The full referring domain that drove the order |
| Referrer Base Domain | The base domain of the referrer |
Key Business Insights
-
Monitor your Chargeback Charge Rate against card network thresholds. Visa's standard monitoring threshold is 0.9% and Mastercard's is 1.0%. Approaching these limits should trigger immediate action — exceeding them leads to penalty programs with escalating fees and potential processing restrictions.
-
Track Visa and Mastercard chargebacks separately. Each network has its own monitoring program with different thresholds, timelines, and remediation requirements. A spike in one network may require a different response than the other.
-
Track Alert to Chargeback Rate as a prevention effectiveness metric. Your alert service is only valuable if resolving alerts actually prevents chargebacks. If alerts are escalating to chargebacks at a high rate, evaluate your alert response speed and process.
-
Use Refund to Chargeback data to improve your refund timing. If customers are filing chargebacks on already-refunded charges, your refund processing may be too slow, or customers may not recognize the refund on their statement.
-
Remember that charges and disputes in this view may not be directly related. A spike in dispute volume here doesn't necessarily mean this period's sales are problematic — use the By Charge Date report to identify which billing periods are generating disputes.
Optimization Strategies
Respond to alerts quickly
- Set up processes to respond to chargeback alerts within hours, not days
- The faster you resolve an alert (typically by issuing a refund), the higher your chance of preventing the formal chargeback
Set internal thresholds below card network limits
- Don't wait until you're at 0.9% to act
- Establish internal alert thresholds at 0.5–0.6% so your team has time to investigate and respond before you enter a monitoring program
Analyze dispute fee impact
- Track dispute fees as a standalone cost center
- Dispute fees, alert fees, and the operational cost of managing disputes add up significantly
- Quantifying these costs helps build the business case for investing in prevention tools
Pro Tips
-
Use this report for day-to-day dispute monitoring. This view shows you what's happening right now, making it ideal for operational dashboards and alerting.
-
Enable the card brand breakdown columns when approaching network thresholds. Managing each network separately gives you more precise control.
-
Compare with the Disputes by Charge Date Report to understand whether a spike in disputes here is coming from a specific billing period or is spread across many.
Frequently Asked Questions
Q: Why might my dispute rates here differ from the Disputes by Charge Date report? A: This report groups everything by the date the dispute was processed. A chargeback filed today against a sale from 3 months ago appears in today's data here, but in the original sale's period in the By Charge Date report. The two views will show different rates for the same date range.
Q: What's the difference between a chargeback and an alert? A: A chargeback is a formal dispute filed through the card network that reverses the charge and incurs fees. An alert is an early notification from services like Ethoca or Verifi that a customer intends to dispute a charge. Alerts give you a window to resolve the issue before it escalates to a formal chargeback.
Q: How is Chargeback Charge Rate calculated? A: Chargebacks divided by total charges, expressed as a percentage. Note that in this view, the chargebacks and charges are grouped by the same date range but may not be directly related — a chargeback filed this month may be against a sale from a prior month.
Updated 6 days ago