Separate declines, refunds and disputes
A declined payment never completes successfully. A refund returns a successful payment through the merchant’s refund flow. A dispute follows a cardholder challenge through the issuing bank and card network process. Treating all three as “failed payments” makes both product decisions and cost estimates harder. Each event can have its own timing and fee treatment.
The chargeback & dispute cost calculator starts with successful transactions and a dispute-rate assumption. It estimates expected lost revenue and dispute fees. It is not a retry tool and does not infer card-network monitoring thresholds. For operational context, read the refunds and chargebacks guide.
A five-dispute monthly example
Assume 1,000 successful monthly transactions at an average of 50, a 0.5% dispute rate, a 40% win rate and a 15 fee per dispute. Expected disputes are five; expected wins are two and losses are three. Lost sales are 150. If fees remain even after a win, five fees add 75, producing an expected monthly cost of 225.
| Example component | Calculation | Cost |
|---|---|---|
| Lost sales | 3 lost cases × 50 | 150.00 |
| Dispute fees retained | 5 cases × 15 | 75.00 |
| Total expected cost | 150 + 75 | 225.00 |
If the same illustrative fee is fully returned on a win, net fees fall to 45 and total cost to 195. Change the selector only when the actual agreement supports that treatment. Winning the underlying payment does not automatically establish that every related charge is returned.
A won dispute can still affect cash flow
Dispute processes have multiple stages. Stripe’s documentation describes how a challenged payment is handled and how evidence and outcomes affect the balance. A final loss and a temporary debit are different exposures: one affects expected cost, while the other can make money unavailable before the outcome is known.
Source: Stripe: how disputes work · reviewed 17 October 2026.
The cost tool excludes temporary holds and staff time. Use the payout and reserve tool for a separate liquidity stress scenario, and use your dispute reports to budget the timing of actual debits and recoveries. Do not combine a recovered principal amount with lost revenue a second time.
Measure your own cohort
Use a consistent denominator: the example expresses disputes as a share of successful transaction count. The average disputed amount is assumed equal to the entered average sale amount. If unusually large orders are more likely to be challenged, a simple average can understate losses. Run a separate high-value scenario instead of relying on one blended ticket.
A fractional expected case is normal when modeling averages across months; it is not a forecast that part of a dispute will occur. Small businesses can see substantial month-to-month variation. Keep the estimated expected cost alongside a stress case in which several disputes arrive together, particularly for annual plans and preorders.
Use the result to compare responsibilities
Compare Stripe and other payment providers on evidence workflows, refund policies, support and fee terms as well as the cost line. An MoR’s dispute responsibilities depend on its agreement. A bundle description does not establish that every loss, fee or product category is covered.
Start with the provider fee calculator for ordinary transaction costs, then add a separately documented dispute scenario. Preserve your quote and assumptions. The goal is to see the economic effect of disputes and decide which controls and support you need, rather than assign an unsupported reliability score to a provider.
Compare current provider profiles, country coverage and fees in the directory.
Explore providers
