Disputes & Fraud

The Disputes & Fraud page in Corgi Intelligence gives you a complete view of dispute activity, fraud patterns, and their financial impact on your business. Use it to track trends over time, identify where disputes are coming from, and take action to reduce chargebacks.

Dispute, Fraud, and Chargeback Rate & Count

At the top of the page, you will see two headline numbers:

• Dispute, Fraud, and Chargeback Rate: The percentage of your transactions that resulted in a dispute, a fraud claim, or a chargeback during the selected period.

• Count: The total number of dispute, fraud, and chargeback cases in that same period.

Both numbers include a trend comparison against the previous period, so you can see at a glance whether your dispute activity is rising or falling.

How to read them: Use the rate to understand proportional impact (are disputes growing relative to your total volume?) and the count to see absolute volume (how many cases are you actually handling?). A falling rate with a rising count often means you are growing fast but dispute prevention is not keeping pace. A rising rate with a flat count means disputes are eating into existing volume.

Dispute Win Rate

The Dispute Win Rate shows the percentage of disputes you have won.

A low win rate is a signal. It may mean your evidence is thin, your response practices are inconsistent, or the disputes you are receiving are difficult to win. Review your evidence practices: make sure you include delivery confirmation, customer communication logs, and transaction details in every response.

Estimated Loss Analytics

This section shows the estimated financial damage from disputes and fraud. It is calculated as three times the total disputed amount.

The 3x multiplier captures more than just the refunded transaction value. It includes operational costs (time spent responding), network fees, and the lost value of goods or services already delivered. This gives you a realistic picture of what disputes are actually costing your business.

Use this metric to prioritize investment. If your estimated loss is rising, it may be time to tighten your fraud model, review fulfillment processes, or shift payment methods.

Fraud Breakdowns

Dispute Reason Breakdown

A stacked bar chart shows how many disputes fall into each reason category over time:

• Fraud (unauthorized use of a card)

• Product Not Received

• Product Unacceptable

• Duplicated Charge

• All Other Reasons

This view answers a critical question: are your disputes driven by fraud, or are they operational problems you can fix?

If fraud dominates your chart, focus on detection and prevention: review your authorization rules, check for card-testing attacks, and make sure your fraud model is tuned to your transaction patterns. If Product Not Received or Product Unacceptable lead the pack, look at your fulfillment and customer service workflows. Duplicated Charge disputes often point to a UI bug or a retry loop in your checkout flow.

Payment Method Distribution

This section breaks down disputes and fraud by payment method (for example, Visa, Mastercard, American Express, JCB). It highlights three specific lenses:

• Highest Fraud Rate by method: Which card brand carries the most fraud risk for your business?

• Most Disputes by method: Which brand generates the highest absolute volume of disputes?

• Safest Payment Method: Which brand has the lowest dispute and fraud rate for you?

A bar chart compares Fraud vs. Other Disputes for each payment method, so you can see not just which methods are problematic, but what kind of problem they create.

Why payment method matters

Different card networks have different dispute rules, liability protections, and fee structures. Understanding these patterns helps you decide whether to adjust your acceptance rules by network.

Payment Method Details Table

Below the chart, a detailed table gives you precise numbers for each payment method:

Use the table when you need exact figures for reporting or for targeting a specific payment method. Use the chart when you are looking for broad patterns.

Country Breakdown

Switch to the Countries tab to see fraud and dispute patterns by geography. This view helps you identify high-risk regions, spot sudden spikes in specific countries, and adjust geographic risk rules in your fraud model.

If you see a fraud surge from a single country, investigate whether it coincides with a recent campaign, a new sales channel, or a known card-testing pattern. If a previously safe country suddenly shows disputes, check for a change in your shipping policy or targeting.

Rate Basis Setting

You can toggle how rates are calculated using the Rate Basis setting:

• Dispute date: Rates are calculated based on when the dispute was filed. Use this to understand your current dispute workload and recent trends.

• Transaction date: Rates are calculated based on when the original transaction occurred. Use this when you need to link a fraud spike to a specific event, like a product launch, a promotional campaign, or a system change.

Why the two views differ: A dispute filed today may be tied to a transaction from weeks ago. If you had a flash sale three weeks ago and your fraud rate spikes this week under Dispute date, the cause is not a new attack. It is the delayed appearance of fraudulent transactions from that sale. Flip to Transaction date to confirm the timing.

Putting it together

Use the Disputes & Fraud page in a regular review cycle:

1. Check your headline rate and count to spot trends.

2. Review your win rate to judge whether your dispute response process is effective.

3. Look at Estimated Loss to quantify the business impact.

4. Use the Fraud Breakdowns to find the root cause: payment method, geography, or dispute reason category.

5. Adjust your Rate Basis to confirm whether a spike is recent or delayed from an earlier event.

If fraud is the dominant driver, review your Corgi Model rules or explore tightening your authorization settings. If operational issues lead your dispute reasons, focus on fulfillment and customer communication workflows.