Disputes & Chargebacks

A dispute is not just a lost sale. It is a signal to Stripe that your business might be a liability. Every dispute — regardless of whether you win, lose, or the customer withdraws it — gets counted. It increases your dispute rate, contributes to your risk profile, and moves you closer to the thresholds that trigger account reviews.

Stripe evaluates disputes as a percentage of total transactions over a rolling window. If you process a high volume of small transactions, a handful of disputes might barely register. But if you are doing 200 transactions a month and two customers file chargebacks, you are at 1% — already past Stripe's 0.75% threshold. The lower your transaction count, the more each individual dispute hurts.

Beyond the rate calculation, disputes also carry direct financial costs (fees), indirect costs (time spent gathering evidence), and reputational costs with Stripe's risk systems. A merchant with a dispute history, even if every dispute was won, looks different to Stripe than a merchant with zero disputes. The cleanest accounts are the safest accounts.

This is the single most misunderstood fact about Stripe disputes. Most merchants assume that winning a dispute clears the record. It does not. Stripe's own documentation confirms: all disputes — won, lost, or withdrawn — count toward your dispute rate.

This changes the calculus entirely. If you are fighting every dispute on principle, you might be winning the battles while losing the war. Each dispute you fight takes time, costs fees, and still counts against your rate regardless of outcome. The question is not "can I win this?" — it is "is fighting this dispute the best use of my account health?"

For merchants near the 0.75% threshold, every dispute that gets filed is damage — win or lose. Prevention is the only strategy that actually protects your account.

Every dispute is a math problem. The variables are: the transaction amount, the dispute fees ($15 filing + $15 counter if you fight), your current dispute rate, how close you are to the 0.75% threshold, and the probability of winning (industry average: 8.1%).

The refund path: You lose the sale amount. Your dispute rate stays the same (refunds before a dispute is filed do not count as disputes). Your account health is preserved.

The fight path: You pay $15 immediately. If you lose (91.9% likely), you also lose the sale + another $15. If you win (8.1% likely), you get the $15 counter fee back and keep the sale — but the dispute still counts against your rate.

For a $20 product: fighting costs an expected $43.67 (weighted by win probability). Refunding costs $20. The refund is cheaper by $23.67 and does not touch your dispute rate. For a $500 product: fighting costs an expected $52.30, while refunding costs $500. Fighting makes sense — if your dispute rate can absorb the hit.

A proactive refund is a refund you issue before the customer files a dispute. This is the single most effective tool for dispute rate management because a refund does not count as a dispute. The customer gets their money back, your dispute rate stays clean, and you avoid the $15-30 in fees.

The triggers for proactive refunds should be systematic, not emotional. Watch for: customers who have contacted support multiple times about the same order, transactions flagged as elevated risk by Radar, repeat complainers who have disputed charges with you before, and any customer who explicitly threatens a chargeback.

The hardest part is psychological. It feels like giving in. It feels like rewarding bad behaviour. But the math does not care about feelings. A $30 proactive refund that prevents a dispute saves you $30 in fees, protects your rate, and keeps you further from a freeze that could cost you thousands in held payouts and lost revenue.

The caveat: do not refund everything. A high refund rate is its own risk signal. Be selective. Refund the ones where the dispute risk is real and the transaction value does not justify a fight.

Stripe charges a $15 dispute fee when a chargeback is filed. If you contest the dispute, there is an additional $15 counter fee — refunded only if you win. These are the visible costs. The invisible costs are what kill businesses.

A lost dispute on a $10 product costs you: the $10 product + $30 in fees = $40 total loss on a $10 sale. That is a 300%+ loss. Merchants win only 8.1% of disputes on average. The expected value of fighting a $10 dispute is deeply negative.

But the dispute rate cost is the one that compounds. Each dispute pushes you closer to the threshold where Stripe takes action. One dispute might not matter. Five in a month on a low-volume account could trigger a freeze that holds $50K+ in payouts for weeks. The true cost of a dispute is not $30 — it is the downstream risk it creates.

When you do fight a dispute — because the amount justifies it and your rate has headroom — the quality of your evidence submission is everything. Submitting a receipt and a screenshot of your refund policy is not enough. Card issuers see hundreds of dispute responses. Yours needs to tell a clear, evidence-backed story.

The signals that carry the most weight with card issuers: CVC match (the customer entered the correct security code), AVS match (billing address matched), 3D Secure authentication (the customer completed additional verification), Stripe Radar risk score for the transaction, device fingerprint consistency (same device used for purchase and account creation), and prior successful transactions with the same customer.

The strongest dispute responses combine multiple signals into a narrative. Not just "here is the receipt" — but "this customer has made 4 previous purchases with this card, CVC and AVS matched, Radar scored the transaction at 12 (low risk), and the customer logged in from the same device they used to create their account. The chargeback was filed 47 days after delivery confirmation."

PayCanary's Transaction Vault stores these signals automatically for every transaction, so when you do need to fight a dispute, you have the evidence ready without scrambling through logs.

Card testing is when bad actors use your checkout to validate stolen credit card numbers. They run small transactions — usually under $5 — to test whether the card is active. If the charge succeeds, the card is confirmed stolen and gets used for larger fraud elsewhere. The small charges on your end eventually lead to chargebacks that count against your dispute rate.

The pattern is distinctive: a sudden spike of low-value transactions, often with different card numbers but similar metadata (same IP, same device fingerprint, rapid-fire timing). If you are seeing dozens of $1-5 charges from unfamiliar customers in a short window, you are likely under a card testing attack.

Immediate defences: Enable 3D Secure for transactions under a threshold amount via Radar rules. Set a minimum transaction amount (even $1 helps). Block prepaid cards if they are not part of your normal customer base. If the attack is active, rotate your API keys immediately — attackers may have your publishable key.

Long-term defences: Use Stripe Radar rules to block by velocity (e.g., more than 3 failed charges from the same IP in 10 minutes). Require customer accounts for checkout. Add CAPTCHA to your payment flow. These measures add friction for legitimate customers, so apply them selectively.

PayCanary detects card testing patterns — the sudden spike of low-value failed charges — and alerts you with an immediate response playbook before the chargebacks start rolling in.

Every dispute that comes in creates a decision: fight or fold? Most merchants make this decision on gut feeling — "I know I delivered the product, I am going to fight this." That instinct costs money more often than it saves it.

PayCanary's Fight-or-Fold Advisor calculates the expected value of contesting each dispute. It factors in: the transaction amount, your current dispute rate, your proximity to the 0.75% threshold, the evidence signals available for this transaction (CVC match, AVS, Radar score, 3DS authentication), and the base win rate for the dispute reason code.

The output is a recommendation with numbers attached. "Fight — expected value +$187 with strong evidence signals" or "Fold — expected value -$23, and contesting would push your dispute rate to 0.68%." You can override the recommendation, but now you are making an informed decision instead of an emotional one.

The Fight-or-Fold Advisor is included in the Protect and Shield plans. For merchants on the Monitor plan, the free Stripe health check gives you your current dispute rate and risk score — the starting point for making better dispute decisions.