Chargeback Metrics
On this page
Before tracking chargeback metrics, understand:
- Chargeback lifecycle and terminology
- Network monitoring programs (VAMP, ECM)
- Fraud metrics for overlap context
- Reason codes for segmentation
- Ratio targets: Chargeback ratio under 0.9% (processor danger zone), under 1.5% (Mastercard ECM)
- Operational targets: Win rate over 40%, response rate 100%, response time under 7 days
- Financial tracking: Net CB loss = Gross - Recovered; CB fees $15-100 each
- Segment by: reason code, channel (CNP vs. CP), product type, customer segment, BIN/issuer
- See Network Programs for threshold details
Your chargeback ratio is the single most important number in payment risk. Go above the network thresholds and you face monthly fines, mandatory remediation, and potential account termination. These metrics tell you where you stand, whether you're trending in the right direction, and where to focus your efforts.
| Zone | Visa Threshold | What Happens |
|---|---|---|
| Safe | Under 0.65% | No action, monitor monthly |
| Warning | 0.65-0.9% | Internal alert, investigate causes |
| Processor concern | 0.9%+ | Processor may contact you, increase reserve |
| VAMP Merchant Excessive | 2.2%+ (tightening to 1.5% April 2026) | Enrolled in monitoring, fines begin |
| Termination | Persistent violation | Account closed, added to MATCH |
Visa VAMP (effective April 2025) replaced the old VDMP/VFMP programs and changed how ratios are calculated. The VAMP ratio includes both TC40 fraud reports and TC15 chargebacks. See Network Programs for current thresholds.
Ratio Metrics
| Metric | Calculation | Network Threshold |
|---|---|---|
| Chargeback Ratio | Chargebacks / Transactions | Under 0.9% (Visa) |
| Dispute Ratio | Disputes / Transactions | Under 1.5% (MC ECM) |
| Fraud Ratio | Fraud chargebacks / Volume | Under 0.9% (Visa) |
How to Calculate Your Chargeback Ratio
The card networks calculate chargeback ratio differently than you might expect:
Visa's method:
Chargeback Ratio = Chargebacks received this month / Transactions processed this month
Example:
45 chargebacks in January / 8,000 transactions in January = 0.56%
The catch: Visa counts chargebacks in the month they're received, not the month the original transaction happened. A December sale that gets disputed in February counts against your February ratio. This means a bad month of transactions creates a delayed spike in your ratio 30-90 days later.
Mastercard's method:
Dispute Ratio = Disputes filed this month / Transactions processed previous month
Example:
60 disputes in February / 7,500 transactions in January = 0.80%
Mastercard uses the previous month's transaction count as the denominator, which means the ratio can swing more with seasonal volume changes.
If your transaction volume drops (seasonal slowdown, marketing pause, site issue) but chargebacks keep arriving from prior months, your ratio spikes even though your fraud didn't get worse. Watch your ratio during low-volume months. A business doing 10,000 transactions/month with 50 chargebacks (0.5%) that drops to 5,000 transactions/month with the same 50 chargebacks is suddenly at 1.0% and in monitoring territory.
Ratio vs. Count: Both Matter
Network monitoring programs require both a ratio and a count threshold. Visa's VAMP merchant excessive threshold is currently 2.2% (tightening to 1.5% in April 2026) with 1,500+ disputes. Mastercard's ECM triggers at 1.5% with 100+ chargebacks. Most processors start flagging you well before these levels - typically around 0.9% - which is why 0.9% remains the practical "danger zone" even though the network-level thresholds are higher. If you have a 2.0% ratio but only 15 chargebacks (because you process low volume), you won't be enrolled in a network program. But your processor may still have concerns.
Conversely, 200 chargebacks on 100,000 transactions is only a 0.2% ratio, which is safe from network programs, but 200 chargebacks is still costing you $5,000-$20,000 in fees and staff time.
Operational Metrics
| Metric | Definition | Target |
|---|---|---|
| Win Rate | Won representments / Total represented | >40% |
| Response Rate | Responded / Total received | 100% |
| Response Time | Days to respond | Under 7 days |
| Recovery Rate | Recovered $ / Total CB $ | >30% |
Win Rate: What's Realistic
The average chargeback win rate across the industry is 20-30%. If you're above 40%, you're doing well. If you're above 60%, you have strong evidence collection.
Win rate varies dramatically by reason code:
| Reason Code Category | Typical Win Rate | Why |
|---|---|---|
| "Not received" (with tracking) | 60-80% | Delivery proof is strong evidence |
| Fraud (with 3DS/CE 3.0) | 50-70% | Authentication data is compelling |
| Fraud (without 3DS) | 10-25% | Hard to prove without authentication |
| "Not as described" | 15-30% | Subjective, hard to disprove |
| "Cancelled recurring" | 20-40% | Depends on cancellation proof |
| "Unrecognized" | 5-15% | Descriptor issue, hard to fight |
What to do with this data: Don't fight every chargeback equally. Invest your time in categories where you can win. An "unrecognized" chargeback for $30 with a 10% win rate isn't worth 45 minutes of staff time. A $300 "not received" with tracking data and a 70% win rate is. For what evidence actually wins by reason code, see Winning Evidence.
Response Rate: Always 100%
Respond to every chargeback, even ones you expect to lose. Why:
- Some issuers auto-resolve in your favor if you submit any evidence
- An uncontested chargeback is a guaranteed loss
- Your processor tracks your response rate; low rates suggest you're not managing disputes
The only exception: if your chargeback vendor or alert service (Verifi, Ethoca) already resolved the dispute before it became a chargeback, there's nothing to respond to.
Recovery Rate: The Financial Bottom Line
Recovery Rate = Dollars recovered through representment / Total chargeback dollars
Example:
$12,000 in chargebacks this month
Fought 10 out of 12 (the two under $25 weren't worth fighting)
Won 5 of 10 = $7,500 recovered
Recovery rate = $7,500 / $12,000 = 62.5%
A 30%+ recovery rate means your representment process is working. Under 20% means your evidence collection needs improvement or you're fighting the wrong chargebacks.
Financial Impact
| Metric | Definition | Notes |
|---|---|---|
| Gross CB Loss | Total chargeback volume | Before recoveries |
| Net CB Loss | Gross - Recovered | True P&L impact |
| CB Fee Cost | Fees per chargeback | $15-100 each |
| Program Fee Risk | Monthly monitoring fees | $10K-25K/month if in program |
The Real Cost of a Chargeback
A single chargeback costs more than the transaction amount:
True Chargeback Cost = Transaction amount (if lost)
+ Chargeback fee ($15-100)
+ Cost of goods (if already shipped/delivered)
+ Staff time to respond (~$20-50 per case)
+ Ratio damage (harder to quantify, very real)
Example ($200 physical goods order, chargeback lost):
$200 transaction
+ $25 chargeback fee
+ $80 cost of goods (already shipped, not returned)
+ $30 staff time
= $335 total loss on a $200 sale
For a business with 20% margins, you need to sell $1,675 in additional product to make up for one $200 lost chargeback.
Program Fee Risk
If your ratio crosses the threshold and you enter a network monitoring program, the fees escalate fast:
| Month in Program | Visa VAMP Fee |
|---|---|
| Month 1-3 | $8 per CNP dispute (passed through by acquirer) |
| Month 4-6 | $8 per dispute + remediation required |
| Month 7-9 | $8 per dispute + enhanced monitoring |
| Month 10+ | Risk of account termination |
At 200 chargebacks/month over threshold, program fees add $1,600/month on top of your regular chargeback costs. See Network Programs for current fee schedules.
Segmentation
Track metrics by:
- Reason code category (fraud vs. non-fraud)
- Transaction channel (CNP vs. CP)
- Product type (digital goods have higher dispute rates)
- Customer segment (new vs. returning)
- BIN/Issuer (some issuers file more disputes)
Segmentation That Actually Helps
The most useful segmentation for most merchants:
By reason code: Tells you whether your problem is fraud, fulfillment, billing confusion, or policy. If 60% of your chargebacks are "unrecognized," fix your billing descriptor. If 60% are "not received," fix your shipping confirmation.
By new vs. returning customers: High dispute rates from new customers suggest fraud. High dispute rates from returning customers suggest product or service issues.
By product/SKU: One problem product can drive your entire chargeback ratio. A single high-return item attracting disputes is cheaper to pull from your catalog than to fight.
Test to Run (30 Days)
Chargeback source audit:
- Export your last 30 days of chargebacks.
- Categorize each by reason code (fraud, not received, not as described, billing, other).
- For each category, note: could this have been prevented with a refund, an alert, a descriptor fix, or better evidence?
- Calculate your win rate per reason code category.
- Identify the single category that accounts for the most chargebacks. That's your highest-leverage fix.
Success criteria: You can name your top chargeback reason code and have a specific action to reduce it. If "unrecognized" is your top category, fix your billing descriptor this week. If "not received" is top, audit your shipping confirmation process.
Scale Callout
| Volume | What to Track | How |
|---|---|---|
| Under $50K/month | Chargeback count, ratio (monthly) | Check processor dashboard weekly. A single chargeback can swing your ratio at low volume, so trend over 90 days. |
| $50K-$250K/month | Add: win rate, response time, reason code breakdown | Monthly spreadsheet. Respond to every chargeback within 5 business days. |
| $250K-$1M/month | Add: recovery rate, cost per chargeback, segmentation by product | Weekly reporting. Set internal alert at 0.65% ratio. |
| Over $1M/month | All metrics, segmented by BIN/issuer, product, geography | Automated dashboards. Dedicated dispute owner. Real-time ratio monitoring. |
Where This Breaks
- Low volume ratio swings. Under 2,000 transactions/month, a single bad week can push your ratio above thresholds even if your fraud rate is normal. Don't panic over one month. Trend over 90 days.
- Mixing CP and CNP chargebacks. Card-present transactions rarely generate disputes. If you combine them with CNP, your ratio looks better than it is. Segment.
- Counting alerts as chargebacks. If you use Verifi or Ethoca alerts and refund pre-dispute, those are not chargebacks. Don't count them in your ratio. Your processor doesn't.
- Ignoring the denominator. A chargeback ratio can spike because chargebacks went up OR because transaction volume went down. Check both numbers before reacting.
- Treating all chargebacks equally. A $20 chargeback and a $2,000 chargeback count the same toward your ratio, but the response strategy should be very different.
What to Do When...
Ratio crosses 0.75%:
- This is your early warning. You have weeks, not months, before you hit 0.9%.
- Set up chargeback alerts (Verifi/Ethoca) immediately if you haven't already. These deflect disputes before they become chargebacks.
- Review your top 5 reason codes. The fix is different for each.
- See Reduce Chargebacks Fast for the full emergency playbook.
Ratio crosses 0.9%:
- You're in program territory. See Zero Point Nine Panic for the emergency response.
- Contact your processor proactively. They'll find out anyway. Being proactive shows you're taking it seriously.
- Implement every quick win: alerts, descriptor fix, refund policy liberalization.
Win rate drops below 30%:
- Check if your evidence quality has degraded. Are you still submitting complete evidence packs?
- Segment by reason code. A new fraud pattern may be generating chargebacks you can't win.
- Review Compelling Evidence for what wins by reason code.
- Consider whether you're fighting chargebacks you shouldn't be. Under $50, refunding is usually cheaper than fighting and losing.
Chargebacks spike suddenly:
- Check for a pattern: same product, same BIN range, same geography, same day.
- If it's fraud: tighten rules immediately, check for a card testing attack or compromised credentials.
- If it's fulfillment: check for a shipping delay, product issue, or service outage that affected a batch of customers.
- If it's billing: check if a subscription renewal batch just went out, or if a pricing change confused customers.
Next Steps
Setting up tracking?
- Understand the lifecycle - Know what you're measuring
- Review network thresholds - Set internal targets below limits
- Build your dashboard - Combine with compliance metrics
Ratio too high?
- Check Zero Point Nine Panic - Emergency response
- Set up alerts - Deflect before they hit
- Follow the playbook - Step-by-step guide
Optimizing win rate?
- Study compelling evidence - Know what wins
- Improve representment process - Systematic approach
- Segment by reason code - Focus on winnable disputes
Tracking chargebacks is just one piece. See also: Payments Metrics · Fraud Metrics · Compliance Metrics · Operations Metrics
Related Topics
- Chargeback Lifecycle - Understanding dispute flow
- Network Programs - VAMP, ECM thresholds
- Fraud Metrics - Related fraud measurement
- Representment - Fighting disputes
- Compelling Evidence - Winning representment
- Chargeback Prevention - Reducing disputes
- Chargeback Alerts - Pre-dispute resolution
- Monitoring Thresholds - Network limits
- Dispute Monitoring - Compliance requirements
- Zero Point Nine Panic - Emergency response
- Friendly Fraud - First-party abuse
- Refund Policy - When to refund vs fight
- Refund Strategy - Operational refund decisions
- Running Fraud Operations - Operational cadence