What it means
A cardholder can dispute a card charge with the issuing bank, and the payment processor informs the merchant and may debit the disputed amount while the claim is reviewed. The merchant may submit evidence within a deadline, and the final outcome can differ from the initial debit.
A basic business metric divides dispute count by captured card payments for a defined period, so 30 disputes against 5,000 payments give a simple rate of 0.6%. State the time window, denominator and whether inquiries and duplicate reports are included, otherwise two rates may not be comparable.
Stripe's guidance says Visa and Mastercard monitoring programs count months differently, with Visa comparing relevant reports with payments in the same calendar month and Mastercard comparing with the prior month's payments in the described program. Do not assume the dashboard's convenient rate is the network's official measure.
Card-network monitoring can count more than final chargebacks, as Stripe explains that network programs generally do not wait for dispute outcomes and that Visa's VAMP combines some dispute and fraud reports. It also warns of differences between processor-visible data and network figures, so verify the applicable network and region before quoting a threshold.
A high rate can mean several things: fraudsters may use stolen cards, customers may not recognise the billing descriptor, or delivery promises may not match reality. A product with long delivery times may draw disputes before customers receive tracking updates, so investigate causes rather than simply contesting every case.
Classify disputes by reason code, product, channel, geography and date of sale, because a burst of unauthorised-use reports needs a different response from customers complaining about subscription cancellation. Check whether one campaign, new payment page or supplier change coincided with the rise, and remember that small samples can swing a rate sharply.
The first control is prevention: use appropriate authentication and fraud screening without making legitimate checkout impossible, show a merchant name customers will recognise on statements, and send clear confirmation, delivery information and a real support route so people can ask before contacting their bank. For recurring billing, state price, renewal timing and cancellation method before signup and save evidence of consent and service delivery.
If a customer cancels, stop future charges under the applicable terms and send confirmation, since a refund may still be cheaper than a dispute when the merchant has made an error. If a dispute arrives, preserve the processor's notice, response deadline and eligible evidence, because a delivery receipt, order history or agreed terms may be relevant but the issuer and network decide the result.
Do not fabricate logs or send unrelated customer information, and remember that a win does not erase the fact that a dispute occurred in every monitoring calculation. Track dispute amounts as well as counts, since thirty small disputes can create a high count rate while one large dispute can threaten cash even when the count rate is low, and include fees and temporary debits in a cash forecast because a chargeback is not identical to a voluntary refund or a failed payment.
In practice
Real-world examples.
Example
Thirty disputes appear against 5,000 captured payments in a defined month. The simple dispute-count rate is 0.6%, before network-specific rules.
Example
Customers do not recognise a processor descriptor; the merchant changes it and adds the billing name to receipts, then tracks later disputes.
Example
A merchant sees a dispute from a June order in September and separates the September network event rate from the June sales-cohort rate.
Formula
Calculation
Illustrative dispute-count rate = eligible disputes in the defined period / eligible captured card payments for the matching denominator x 100.
Worked example: 30 disputes against 5,000 captured payments gives 30 / 5,000 x 100 = 0.6%. By value, if the average payment is $100, sales are 5,000 x $100 = $500,000. If the 30 disputes are 29 of $100 and one of $5,000, the disputed value is $2,900 + $5,000 = $7,900, a value rate of $7,900 / $500,000 x 100 = 1.58% even though the count rate is still 0.6%. Card-network monitoring may use a different month, include fraud reports or apply other rules, so label the metric.Case study
Seen in the real world.
This illustrative and entirely fictional case follows Rivercart, an invented online retailer. It saw 30 disputes in a month with 5,000 captured payments, a simple 0.6% count rate. The analyst grouped reports and found many customers did not recognise the statement descriptor; another group concerned delayed shipping.
Rivercart changed the descriptor, put its billing name on receipts and added proactive delivery updates. It kept evidence for genuine disputes and refunded clear errors. The company checked processor and network measures separately over later months; the case does not promise any particular monitoring outcome.
Watch out
Common mistakes.
- Calling every initial disputed debit a final merchant loss or equating refunds with chargebacks.
- Comparing rates with different denominators or ignoring the network's reporting-month rules.
- Fighting each dispute while leaving an unclear descriptor, weak cancellation flow or delivery problem unchanged.
Questions
People also ask.
What is chargeback rate?
A simple version is dispute count divided by card-payment count for a clearly defined period. Network programs can use different timing and included events.
Why does it matter?
A high rate can signal fraud, billing or service problems, can draw processor or network monitoring, and ties up cash while disputes are pending. A single dispute is not always a final loss, because it may be reversed after evidence is reviewed, though it can still affect monitoring metrics.
How can it be reduced?
Fix the causes: use a recognisable descriptor, send clear confirmations and delivery updates, make cancellation easy, use sensible fraud screening and refund clear errors early. Processors and card networks set current, region-specific monitoring rules, so check the applicable program rather than relying on one remembered universal percentage.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%