A chargeback report is a detailed statement or dashboard from your payment provider that tracks when customers dispute a charge. These reports are how you track what’s being claimed, where each case stands, and why disputes are happening. In 2024, US cardholders disputed $9.8 billion in credit card charges, which resulted in $5.9 billion in chargebacks. The businesses that manage chargebacks well tend to read their reports closely enough to catch patterns before they become a card network problem.

Below, we’ll discuss what a chargeback report contains, how to use dispute data to separate true fraud from friendly fraud, and how to build an evidence strategy that actually wins cases.

Key takeaways

• Chargeback reports give you the dispute data you need to help protect revenue, maintain card network standing, and identify whether fraud or merchant error is driving your losses.

• Reading reason codes alongside your own order and customer data can reveal patterns that raw dispute logs alone won’t show.

• Creating templates of your evidence packages by reason code category is one of the most effective changes you can make to your dispute win rate.

What is a chargeback report?

A chargeback report is a structured log of every dispute filed against your account over a given period. It typically includes a standard set of fields, including the following:

• Transaction details: The original charge date, amount, currency, and card type

• Dispute reason code: The code assigned by the card network (e.g., Visa, Mastercard) that indicates the stated basis for the dispute

• Dispute status: Whether a dispute is open, won, lost, or withdrawn

• Evidence deadline: The date by which you must submit a rebuttal to the issuing bank

• Case ID: The reference number used to track the dispute across systems

• Outcome: Whether the dispute was resolved in your favour or the cardholder’s

Some reports also include customer identifiers, order metadata, and the specific product or service involved.

Why does chargeback reporting matter?

Chargebacks cost you twice: the initial cost is when the transaction amount is reversed and the second is a dispute fee per case. A less visible cost is a loss of good standing with the card networks. Visa and Mastercard both run dispute monitoring programmes with defined thresholds. Once these flag your business, it’s subject to fines, mandatory remediation plans, and—if the rate doesn’t come down—potential termination of your ability to accept cards.

Chargeback reports let you know where you’re at before the card networks do and let you measure whether your interventions are working. In terms of compliance, if you’re ever in a monitoring programme or facing an audit, you’ll need to show that you had systems in place to detect and respond to dispute trends. This requires a documented reporting history.

What chargeback metrics should you monitor?

Four metrics are the most important. If you track them consistently, you’ll likely have enough signals to catch problems early and take action.

Here’s what to monitor:

• Chargeback ratio: Calculated as chargebacks received in a month divided by transactions processed that month (Visa’s method) or the prior month (Mastercard’s method). This is the number card networks use for monitoring programmes. Track it at least monthly, but weekly if you’re operating at high volume.

• Win rate: The percentage of disputes you successfully rebut. Industry win rates vary by reason code and business type.

• Reason code mix: A summary of what cardholders are claiming, such as fraud, credit not processed, product not received, or product not as described. The mix helps you identify a chargeback’s root cause. For example, a report dominated by fraud codes in a low-fraud product category often suggests first-party fraud rather than true unauthorised use.

• Time to respond: How quickly your team submits evidence relative to deadlines. Issuers typically give you 14–45 days, depending on the card network and reason code. Missed deadlines are automatic losses because there’s no appeals process.

How do you read a chargeback report effectively?

Reason codes reflect what the cardholder told their bank, which isn’t always what actually happened. For example, a peak in Visa reason code 10.4 (Other Fraud—Card Absent Environment) might mean a true fraud problem, or it might mean your cancellation policy is confusing customers and causing them to dispute charges they don’t recognise. It’s useful to cross-reference reason codes against your own order and customer data.

Here’s how that works:

• Transaction clustering: Look at whether disputed transactions cluster around a specific product, stock-keeping unit (SKU), or service tier.

• Acquisition channel: Determine whether disputes come disproportionately from paid social, a marketplace, or an affiliate programme.

• Timing patterns: Disputes that arrive later in the allowable window tend to suggest friendly fraud. Those that arrive within days of the purchase tend to suggest true unauthorised fraud.

• Geographic and device signals: Find out whether there’s a Bank Identification Number (BIN) range, device type, or region that shows up repeatedly across disputed transactions.

Segmenting this way turns a report full of individual cases into an actionable pattern. Build a dispute log that captures this metadata for every case, even if your payment provider’s report doesn’t include it by default. Over 90 days, you’ll have enough data to distinguish what’s structural.

How do you use chargeback reports to spot fraud trends?

The hard part of fraud analysis is separating the fraud types because they require different responses. Here’s how the different types compare.

True fraud

A cardholder’s credentials were stolen and used without their knowledge. These disputes typically cluster in tight windows of time, involve cards with mismatched billing addresses, and appear in unauthorised transaction reason codes. To fight true fraud, tighten authentication, add velocity checks, and improve card verification.

Friendly fraud

A cardholder disputes a legitimate charge, either intentionally or because they didn’t recognise it. These disputes often arrive later in the transaction lifecycle, correlate with single-purchase customers, and appear in reason codes such as “product not received” on transactions where you have clear fulfilment records. When businesses submit evidence, they tend to win these types of cases because the underlying transaction was real.

Merchant error

These are disputes that stem from your own gaps in operations, such as refunds that aren’t processed in time, billing descriptors that don’t match what customers recognise, and trial conversions that weren’t clearly communicated. These show up as credit-related and cancellation reason codes.

How do you use chargeback reports to win disputes?

Winning a dispute requires submitting evidence that directly addresses the reason code. What compelling evidence looks like varies by dispute type.

Here’s what to provide for the different types of disputes:

• Unauthorised transaction claims: Proof the cardholder authorised the charge, such as signed receipts, address verification service (AVS) and card verification value (CVV) match data, 3D Secure authentication records, or device fingerprinting tied to the cardholder’s known devices. If the cardholder has a purchase history with you, that transaction history is relevant.

• Product not received: Delivery confirmation with a delivered status, a signature if the order required one, or access logs if it’s a digital product.

• Product not as described: Detailed product descriptions from the time of purchase, photos or specifications, and any customer communications that prove they received what was advertised.

• Credit not processed: The refund record, including the date initiated, amount, and transaction ID. If there’s a delay between return and refund, include the policy that governs it.

Create templates of your evidence packages by reason code category. The fields in your chargeback report, such as reason code, dispute date, and original transaction details, map directly to what you need to pull.

What tools simplify chargeback reporting?

The Stripe Dashboard gives you a real-time view of every dispute on your account, including the status, reason code, evidence deadline, and outcome—without the need for a separate tracking system. You can filter disputes by date, status, and reason code and export the full dataset for deeper analysis.

Stripe automates parts of the evidence submission process for certain dispute types; it pulls transaction data, customer records, and shipping information and submits them before the deadline.

Stripe Radar, the fraud detection layer, connects upstream to your dispute data. You can also review Radar’s logs for any disputed transaction to see exactly what signals it evaluated at authorisation time, which helps you understand why a fraudulent charge got through.

Stripe’s application programming interface (API) exposes full dispute data in a structured format for businesses with high dispute volumes or monitoring programme requirements. That means you’re not limited to the views the Dashboard shows by default. You can build the segmentation and trend analysis that fits your operation, with unified workflows from prevention to representment.

How Stripe Radar can help

Stripe Radar uses AI models to detect and prevent fraud, trained on data from Stripe's global network. It continuously updates these models based on the latest fraud trends, protecting your business as fraud evolves.

Stripe also offers Radar for Fraud Teams, which allows users to add custom rules addressing fraud scenarios specific to their businesses and access advanced fraud insight.

Radar can help your business:

• Prevent fraud losses: Stripe processes over $1 trillion in payments annually. This scale uniquely enables Radar to accurately detect and prevent fraud, saving you money.

• Increase revenue: Radar's AI models are trained on actual dispute data, customer information, browsing data and more. This enables Radar to identify risky transactions and reduce false positives, boosting your revenue.

• Save time: Radar is built into Stripe and requires zero lines of code to set up. You can also monitor your fraud performance, write rules and more in a single platform, increasing efficiency.

Learn more about Stripe Radar or get started today.