How to Handle a Chargeback on Stripe

A chargeback notice lands in your Stripe dashboard: a customer claims they never received the product, or does not recognize the charge, and their bank has pulled the money back — plus Stripe hits you with a $15 dispute fee. Chargebacks feel like theft, and sometimes they are (so-called “friendly fraud” is rampant). But win or lose, how you respond in the first 48 hours determines the outcome. Stripe gives you a structured dispute process with real win rates for merchants who submit strong evidence. Here is exactly how to handle it.

Understand What Kind of Chargeback You Are Facing

Chargebacks fall into reason categories, and your evidence must match the category. Common ones: “product not received” (prove delivery), “product not as described” (prove it matched the listing), “fraudulent” (prove the legitimate cardholder made the purchase), “duplicate processing” (prove one charge was refunded or legitimate), and “subscription canceled” (prove the cancellation policy and continued use). Read the reason code in your Stripe dashboard first — submitting delivery proof for a “not as described” claim wastes your one shot. Each category has a different evidence standard, and card networks decide based on how precisely you rebut the specific claim.

Act Within the Deadline — Evidence Has an Expiry

Stripe typically gives you 7 to 21 days to submit evidence depending on the card network, and the clock starts at notification, not when you notice it. Turn on email and dashboard alerts for disputes so nothing sits unread. Your first decision: fight or accept. Fight when the claim is false and the order value justifies the effort — generally orders over $50-$75, since building evidence takes 30-60 minutes. Accept (and refund if you have not) when the claim is legitimate, the amount is small, or your evidence is thin; a lost dispute costs the amount plus the fee anyway. Decide within 48 hours so evidence gathering never becomes a deadline panic.

Build Compelling Evidence for Stripe

Strong evidence is specific, timestamped, and directly rebuts the reason code. Include: the order receipt with item descriptions matching your listing, shipping confirmation with tracking showing delivery (signature confirmation for high-value orders), customer communications showing satisfaction or acknowledging receipt, your refund and return policy as displayed at checkout, and for digital goods, access logs with IP addresses and timestamps proving usage. For “fraudulent” claims, add AVS/CVC match results, device fingerprints, and any prior purchase history from the same customer. Write a concise cover summary connecting each piece of evidence to the dispute reason — reviewers decide in minutes, so make their job easy. Stripe’s dispute documentation guide lists exactly what each network wants to see.

Prevent the Next Chargeback

Winning disputes is good; not getting them is better. Use clear billing descriptors so customers recognize the charge — cryptic LLC names are a top cause of “unrecognized” disputes. Send order confirmation and shipping emails with tracking links; customers who can track a package rarely claim non-receipt. For subscriptions, email before each renewal and make cancellation genuinely easy — forced-continuity complaints are chargeback magnets. Enable Stripe Radar fraud rules to block obviously risky transactions before they become disputes. And resolve complaints fast: a customer who gets a quick refund never files a chargeback. Keep your overall dispute rate under 0.75% — above 1%, card networks can place you in monitoring programs with fines.

Know the Costs and When to Write It Off

Every lost dispute costs the transaction amount plus Stripe’s $15 dispute fee (waived if you use certain Radar protections and win). Factor this into your fraud budget: most healthy businesses accept a small dispute rate as a cost of selling online. Do not spend an hour fighting a $20 chargeback you will probably lose — but absolutely fight a $500 fraudulent claim with delivery proof. Track your win rate over time; if it is under 30%, your evidence process needs work, not more effort per case. The Consumer Financial Protection Bureau’s chargeback explainer describes the process from the cardholder side, which helps you understand what you are up against.

When Chargebacks Signal a Bigger Problem

A sudden spike in chargebacks is a diagnostic signal. Ten “product not received” disputes in a week means your fulfillment or shipping notifications are broken. A run of “not as described” claims means your product photos or copy oversell reality. Repeated “fraudulent” claims from similar patterns means your fraud screening has a hole. Treat clusters as operations problems, not just finance problems — fix the root cause and the disputes stop. If disputes exceed 1% of transactions, act urgently: card network monitoring programs bring monthly fines and can ultimately cost you the ability to process cards.

Setting Up Stripe Radar to Stop Disputes Before They Start

The cheapest chargeback is the one that never happens, and Stripe Radar is your first line of defense. Start with the free Radar rules: block payments where the CVC or postal code fails verification, flag transactions with mismatched billing country and IP location, and set velocity limits that catch card-testing attacks (many small charges in rapid succession). Review the Radar dashboard weekly at first — false positives cost you legitimate sales, so tune rules based on what you see. As volume grows, consider Radar for Fraud Teams ($0.05 per screened transaction), which adds machine-learning risk scoring and, importantly, can cover the dispute fee on fraudulent payments it approves. Pair Radar with 3D Secure (now called SCA) for high-risk transactions: it shifts fraud liability to the card issuer. No fraud setup is perfect, but merchants who actively manage Radar typically cut dispute rates by half or more within a quarter.

Handle a Stripe chargeback by reading the reason code first, deciding within 48 hours whether to fight or accept, and submitting timestamped evidence that directly rebuts that specific claim. Then prevent repeats: clear billing descriptors, tracking emails, easy cancellations, and a dispute rate kept under 0.75%.

Conclusion

Chargebacks are a cost of doing business online, but they are not random — they follow patterns you can fight with evidence and prevent with better operations. Respond fast, match your evidence to the reason code, and treat every dispute as feedback on your checkout, fulfillment, or communication. Keep your dispute rate low and your documentation sharp. For more on protecting your revenue, browse our business guides, learn about us, or contact us.

Frequently Asked Questions