How to Prevent Chargebacks: 10 Steps for Online Sellers
Key Takeaways
- •On Stripe in the US, a dispute costs a $15 fee that is never returned, plus another $15 to respond that comes back only if you win, as of November 2026.
- •Stripe says the card industry treats dispute activity above 0.75% as excessive, and every dispute counts toward it whether you win or lose.
- •Most chargebacks are preventable with a recognizable statement descriptor, clear product descriptions, a full refund policy shown before checkout, fast support and fast refunds.
- •Early fraud warnings matter: Stripe says about 40% of Visa and Mastercard warnings become fraud disputes if you do not refund.
- •Affiliateo is not chargeback software, but buyers can refund themselves within 30 days, disputes hold the seller's share and the affiliate's commission, and new sales pause at a 0.75% dispute rate.
What a chargeback really costs
A chargeback happens when a customer asks their bank to reverse a payment instead of asking you. The bank pulls the money back, and you pay a fee whether or not you were in the wrong.
Here is how it works with Stripe in the US, from Stripe's own pricing and docs as of November 2026:
- Dispute fee: $15 when a dispute arrives. Stripe does not give it back, even if you win.
- Answering the dispute: another $15 if you respond yourself. You get this one back if you win.
- Smart Disputes: if Stripe answers for you automatically, it charges 30% of the disputed amount, only on disputes it wins.
- Timing: card networks usually let cardholders dispute within 120 days of the payment. Once a chargeback opens, you usually have 7 to 21 days to respond. The bank then takes 60 to 75 days to decide. The whole process can take 2 to 3 months.
The fee is only part of the cost. You also lose the product or time you delivered, the hours spent gathering proof, and some standing with your payment processor.
That last part matters most. Stripe says the card industry treats dispute activity above 0.75% as excessive. Every dispute counts toward that rate, won or lost. Go over it for long enough and you can face fines from the card networks, or lose the ability to take cards at all.
So chargeback prevention is not about winning disputes. It is about never getting them.
Why customers file chargebacks
Most chargebacks fall into a few groups:
- "I don't recognize this charge." The name on their statement means nothing to them.
- "I never got it." They could not find the download, the login, or the course.
- "I didn't buy this." Real fraud with a stolen card, or a family member who used the card.
- "I want my money back." They are unhappy, could not reach you, or did not know you offer refunds.
Each group has its own fix. The ten steps below cover all of them.
10 steps to prevent chargebacks
1. Use a statement descriptor people recognize
The statement descriptor is the name on your customer's card statement. Stripe recommends your website domain or business name, so people can identify the purchase. On Stripe it must be 5 to 22 characters.
If your brand and your company name are different, use the one customers know. "ACME LLC" means nothing to someone who bought "Pixel Course".
2. Say exactly what they are buying
Vague sales pages create "not as described" disputes. Before checkout, state what is included, the format (video, PDF, live calls), how long access lasts, and when it starts. If it is a subscription, say how often it renews and the price of each renewal.
3. Show your full refund policy before they pay
Stripe's guidance is specific here. Put your refund and cancellation policy in your terms, make customers agree before they buy, and show the full policy, not just a link. Stripe notes that a checkbox with only a link may be rejected by the card issuer as proof that the customer saw your policy.
Not sure what to write? Use the refund policy template further down.
4. Make support easy to reach, and answer fast
A customer who can reach you is far less likely to go to their bank. Put a support email or chat on every page and in every receipt. Answer within one business day. A quick "sorry, here is your refund" costs you less than any dispute.
5. Refund instead of fighting
If a customer is unhappy, refund them. A refund is almost always cheaper than a dispute, and it does not count against your dispute rate.
One detail: customers cannot dispute a fully refunded payment, but they can still dispute a partially refunded one, and card network rules allow the dispute to be for the full amount. When in doubt, refund in full.
6. Remind subscribers before you charge them
Forgotten subscriptions are a major source of "I didn't authorize this" claims. Email people before a free trial turns into a paid plan, and before a yearly renewal. Make cancelling easy. A customer who cancels is a lost sale. A customer who files a chargeback is a lost sale plus a fee.
7. Turn on fraud checks and 3D Secure
Fraud prevention stops the "I didn't buy this" group. Stripe's Radar screens payments for fraud and can block or flag risky ones. 3D Secure adds a verification step with the card issuer. Payments authenticated with 3D Secure can be protected from most fraud disputes through a liability shift, though Stripe notes the fraud warnings still count toward card network monitoring.
For a deeper look at fraud patterns, see our guide to ecommerce fraud prevention.
8. Act on early fraud warnings
Card issuers on Visa, Mastercard and JCB send early fraud warnings when they suspect a payment was fraud. Stripe says that if you don't refund, about 40% of Visa and Mastercard warnings become fraud disputes.
Stripe's analysis suggests refunding warned payments that are about the size of your dispute fee or smaller. For a $15 product with a fraud warning, refund it. For a $500 product, look closer before you decide.
9. Keep proof of delivery and use
When a dispute does come, proof wins it. For digital products, that means records that the customer got access and used it: login times, lessons completed, files downloaded, and your messages with them.
If you sell a course on Affiliateo, its course analytics show each student's completion and last activity, which is exactly this kind of proof. Banks don't follow links, so save screenshots, not URLs.
10. Check your dispute rate every month
Look at disputes divided by sales, every month. One or two disputes can push a small store's rate high fast. Stripe notes that for a new or small business, with fewer than 100 payments a month, one or two fraud disputes can have an outsized effect. Spot a rise early and you can fix the cause before it becomes a problem with your processor.
How to respond when a dispute arrives
Even with good prevention, some disputes will come. Good dispute management is mostly speed and organization. When one arrives:
- Read the reason code. "Fraud" and "product not received" need different proof.
- Decide fast whether to fight. If the customer has a point, accepting the dispute closes it sooner.
- Gather your evidence: the receipt, proof of access or use, your refund policy as shown at checkout, and any messages with the customer.
- Write a short, factual summary. Banks read many cases. Make yours easy.
- Submit before the deadline. Late evidence is the same as no evidence.
What about Stripe chargeback protection?
People often search for Stripe chargeback protection hoping for a switch that makes disputes go away. As of November 2026, Stripe's Radar page describes dispute tools in two parts: prevention tools powered by Verifi and Ethoca, and Smart Disputes, which manages and submits evidence on your behalf. That is what chargeback management usually means: software that gathers your evidence and answers disputes for you. Stripe's pricing page lists Smart Disputes at 30% of the disputes you win. Radar itself is sold as a subscription with four tiers: Lite, Standard, Plus and Pro.
These tools help. None of them replace the basics above. A clear descriptor and a fast refund prevent more chargebacks than any software.
A refund policy template you can copy
Many sellers look for a refund policy generator. A good refund policy is short enough to write yourself. Copy this and fill in the brackets:
Refund policy for [BUSINESS NAME]
- Who can get a refund: anyone who bought from us in the last [30] days.
- What you get back: the full amount you paid, to your original payment method. It usually appears in [5 to 10] business days.
- How to ask: [click Request refund on your order page / email support@yourdomain.com with your order number]. You don't need to give a reason.
- What happens to access: when a refund is issued, access to the product ends and any subscription is cancelled.
- Subscriptions: you can cancel anytime from [where]. You keep access until the end of the period you paid for.
- Questions: email [support email]. We reply within [1 business day].
Show this policy in full on your sales page and checkout, and link it in every receipt.
How chargebacks and refunds work on Affiliateo
Affiliateo is not chargeback software, and it does not promise to stop disputes. But if you sell through Affiliateo's checkout, its rules for refunds and disputes shape your prevention plan, so here is what its docs say.
Refunds. Every purchase on Affiliateo can be refunded within 30 days of payment. Only full refunds are supported. Buyers can request a refund themselves from their order in Settings, or with the Refund button on the payment page. Sellers can refund from the Payments tab. When a refund goes through, the money returns to the buyer's original payment method (usually 5 to 10 business days), memberships are revoked, subscriptions are cancelled, and an affiliate commission still in the hold period is reversed automatically. Details are in refunds.
That self-serve refund is useful for prevention. A buyer who can get their money back in two clicks has little reason to call their bank. So your refund policy on Affiliateo should match the platform: 30 days, full refund.
Disputes. When a customer files a dispute on an Affiliateo sale:
- Stripe charges a $15 dispute fee, passed on to the seller at cost. It is not refunded if you win.
- The buyer is banned from the platform automatically, and you get a notification.
- Your share of the disputed amount is held until the bank decides.
- If an affiliate referred the sale, their commission is held too.
If you win, the held funds go back to your balance and the affiliate gets their commission back. If you lose, the held amount is not returned. You respond from the Payments tab with the Respond button. You can add a PDF or up to 10 pictures per box, and you can send your response only once. Answering yourself costs $15 if you lose and nothing if you win. If you don't answer, Stripe may answer for you automatically, which costs 30% of the disputed amount and only if it wins. The full process is in disputes.
Dispute rate limit. Affiliateo measures your disputes, won or lost, against your sales over the last 90 days. At 0.5% you get a warning. At 0.75%, once you have at least 3 disputes in that time, new sales pause automatically. Existing customers keep their access, and nothing is deleted.
Early resolution. Affiliateo's fees page also lists dispute resolution: when a customer's bank reports a purchase as fraud, Stripe refunds it automatically before it becomes a chargeback, so the $15 dispute fee does not apply. That resolution is listed at $15 for Visa and $29 for Mastercard. See the fees page.
Payout hold. Incoming funds are held for 7 days before you can withdraw them, which the docs say protects against fraud, chargebacks and refund abuse.
If you run affiliates, these rules matter for them too. A sale that is refunded or disputed should not earn a commission, and good affiliate terms say so. Our affiliate fraud prevention guide covers the affiliate side.
The short version
Most chargebacks are preventable. Use a name customers recognize. Say what they get. Show your refund policy in full. Answer quickly. Refund when someone is unhappy. Remind subscribers before you charge them. Keep proof. Watch your rate. Do those eight things well, and the fraud tools only have to handle the rest.
Written by Jamal Brooks
Jamal is a product engineer at Affiliateo who writes about payments, integrations, and technical best practices.


