How to reduce chargebacks: fix each dispute reason where it starts

To reduce chargebacks, find out why your buyers dispute and fix each cause where it starts: a billing descriptor they recognize, subscription terms stated before payment and reminders before renewals, shipping updates and fast refunds, fraud screening before you ship, and pre-dispute alerts that let you refund before a chargeback lands. Fight only the disputes your evidence can win.

Why do customers file chargebacks?

Card networks use hundreds of dispute reason codes. Stripe sorts them into eight categories: fraudulent, unrecognized, subscription canceled, product not received, product unacceptable, credit not processed, duplicate and general (Stripe's dispute categories). For a brand selling supplements through video ads, five causes do most of the damage:

• Fraud. A stolen card was used. Stripe calls this the most common dispute reason, and a difficult one to win.
• "I don't recognize this." The statement shows a name the buyer doesn't connect with your ad. Stripe treats an unrecognized dispute as effectively the same as a fraud claim.
• Subscription surprise. A renewal the buyer didn't know they had agreed to, or a cancellation that didn't stick.
• Not received. The parcel is late, lost or silent.
• Not as described. The product didn't match what the video promised.

Some of the "fraud" isn't fraud at all. Stripe calls it friendly fraud: a customer disputes a legitimate charge they believe is fraudulent (Stripe), sometimes because they don't recognize it on their statement. That is why the cheapest fraud fixes are a clear descriptor and a good receipt, not a fraud tool.

Your own mix is in your processor's dispute export, which carries a reason for every case. Count one quarter by reason before you change anything. In this example store, 27 of 48 disputes, more than half, come from three causes the store controls with words and operations:

Where one quarter's 48 disputes came from

Illustrative store, by Stripe's dispute categories

• Fraudulent1429%
• Unrecognized1021%
• Subscription canceled919%
• Product not received817%
• Product unacceptable510%
• Credit not processed, duplicate, general24%

How do you stop "I don't recognize this charge" disputes?

Weeks after the order, the statement line is all the buyer sees. If your ad and your page say one brand and the statement says your holding company, a careful customer calls the bank. Make the descriptor the brand name from the ad, add your website if it fits, and keep it the same for every charge. Then send a receipt that repeats it. Stripe's prevention advice for both fraud and unrecognized disputes is the same pair: a recognizable descriptor, and a receipt so customers can recall what they paid for (Stripe).

One case catches many funnels. If your checkout charges a one-click upsell as a separate transaction, the buyer sees two lines from you on the same day and may only remember the first purchase. Name the upsell on the upsell page, in the receipt and, where your processor allows it, in the descriptor's suffix. The upsell funnel guide covers the offer itself, and the billing descriptor guide covers character limits and examples.

How do you prevent subscription chargebacks?

Subscriptions produce the "subscription canceled" category, and preventing it comes down to clear terms and an easy exit. In the US, ROSCA already requires three things of an online subscription: clear disclosure of all material terms before you take billing information, the buyer's express informed consent before you charge, and a simple way to stop the charges (15 U.S.C. 8403). State laws add more, covered in the auto-renewal laws post. This is not legal advice.

Stripe's prevention list for canceled-subscription disputes reads like a checklist (Stripe):

• State the billing terms before you collect card details, and ask the buyer to click to confirm them.
• Send a reminder before a free or discounted trial ends.
• Send billing reminders before renewals. Stripe suggests about 7 days before a yearly renewal and 2 to 3 days before a monthly one.
• Offer a quick, easy way to cancel. Stripe calls an in-app cancel button often the best option.
• Be flexible with refunds: if someone cancels the day after being billed, offer a full or prorated refund.

Do the same in the video. A buyer who heard "a new bottle every 30 days for $49 until you cancel, and you can cancel online any time" in the offer section doesn't call the second charge a surprise. Say the terms aloud and print them next to the button, the way the VSL offer guide recommends for guarantees.

How do you prevent "item not received" disputes?

"Not received" disputes start with a delivery promise the operation can't keep. The FTC's Mail Order Rule sets the US baseline: you need a reasonable basis for any shipping time you state, you must ship within 30 days if you state none, and if you can't ship on time you must let the buyer choose between the delay and a cancellation with a prompt refund, which for card orders means within 7 working days (FTC). The Mail Order Rule post has the details.

The operations that prevent most of these disputes:

• Show realistic shipping times before checkout, in the page's FAQ as well as in the policy.
• Send the tracking number as soon as it exists, then a short note at every delay.
• Offer the refund before they ask when a delay passes your promise.
• Keep proof. Card issuers don't follow links, so save screenshots of tracking and delivery confirmations for any dispute (Stripe).

How do you prevent "not as described" disputes?

This category starts in the video. When a VSL promises a result the typical buyer won't see, the gap shows up first as refund requests and then as disputes. Keep claims inside what you can substantiate, make the video, the page, the label and the checkout describe the same product, price and terms, and handle complaints yourself. Stripe's prevention advice for this category is accurate, complete descriptions wherever you sell, and never sending the buyer to the manufacturer instead of resolving it (Stripe). VSL compliance covers the claim rules.

Then make the refund the easy road. A guarantee honored quickly, with no hoops the video didn't mention, gives an unhappy buyer a faster exit than their bank. The money-back guarantee post covers the terms.

Is it cheaper to refund or fight a chargeback?

When a buyer is set on getting their money back, a refund almost always costs less. Take an $89 order whose product and shipping cost you $22, processed on Stripe in the US. Stripe charges $15 when you receive a dispute and, for disputes opened after June 17, 2025, another $15 if you counter it, returned only if you win (Stripe):

What one unhappy $89 order costs you

Illustrative order with $22 of product and shipping already spent

Refund when the buyer asksproduct and shipping lost$22

Dispute acceptedplus the $15 dispute fee and one dispute in your ratio$37

Dispute fought and lostplus the $15 counter fee as well$52

Winning returns the $89 and the counter fee, but the first $15 stays spent and the dispute still counts in your ratio, because the monitoring programs ignore outcomes. A refund has one more advantage: a fully refunded payment can't be disputed. A partial refund doesn't protect you, since card rules let a partially refunded payment be disputed for the full amount (Stripe).

Fraud is the exception to "refund on request", because the real cardholder never contacted you. When an order looks like fraud, Stripe suggests refunding more aggressively if it hasn't shipped, if your dispute activity is already high, if you're in a monitoring program, or if your volume is small enough that one or two disputes move your ratio. Know what a refund can't do: issuers must report possible fraud on a captured payment even if you refund it, so Visa still counts the fraud report (Stripe).

How do you stop fraudulent orders before they ship?

Stolen-card orders are the ones a refund policy can't prevent. Screening works in layers, and each layer adds friction, so add them where fraud actually shows up (Stripe's fraud best practices):

• Collect the CVC and the full billing address. The card issuer verifies them, and a failed check is a reason to stop and look.
• Ship to an address that passed the postal code and street checks. When you ship elsewhere, you can't prove the parcel went to the real cardholder.
• Review risky orders before fulfillment: billing and shipping addresses that differ, rush shipping on a big order, several cards from one IP address, products with high resale value.
• Separate authorization from capture when you need time to review. Cardholders can't dispute an authorization you never capture, and issuers don't have to report fraud on an authorization you reverse before capture.
• Hold shipments 24 to 48 hours on orders you're unsure about, so the real cardholder has time to spot the charge.
• Use 3D Secure where fraud concentrates. It adds a check with the cardholder's bank, and authenticated payments might be protected from most fraud disputes by liability shift. Note the "might": liability shift covers fraud claims only, it isn't guaranteed, and you'll still receive early fraud warnings, which count toward the card networks' monitoring programs.

If fraud shows up as a burst of small payment attempts rather than single orders, it's probably card testing, which has its own signs and defenses.

What are chargeback alerts and pre-dispute tools?

Between the buyer's call to the bank and a formal chargeback there is often a window, and three services work inside it:

• Verifi Order Insight, a Visa service, connects merchants to issuers so a customer asking about a charge sees the purchase details in real time (Visa).
• Verifi Rapid Dispute Resolution (RDR) refunds pre-disputes automatically, based on rules you set.
• Ethoca and Verifi alerts work with participating issuers to warn you when a chargeback is about to be filed, so you can refund first (Stripe).

The payoff shows up in your ratio: Visa leaves disputes resolved through pre-dispute services out of its VAMP count. Ask your processor which of these it supports, what each alert or resolved case costs, and how quickly you must act. Treat alerts like customer emails: someone should act on them the same day.

Put together, every dispute passes five points where it can be stopped:

Five places to stop a chargeback

1. 1Before paymentHonest claims, subscription terms and shipping times stated up front
2. 2At checkoutCVC and address checks, 3D Secure where fraud shows up
3. 3After paymentA receipt naming the descriptor, tracking, delay notices
4. 4Before a chargebackFast refunds, alerts and pre-dispute services
5. 5After a chargebackAccept what you can't win; fight the rest with evidence

When should you fight a chargeback?

Fight when your evidence answers the reason code directly, and accept when it doesn't:

• Not received: carrier tracking that shows delivery to the address the buyer gave, as screenshots.
• Subscription canceled: the terms the buyer saw, their confirmation click, the reminders you sent and your cancellation records.
• Not as described: the claims on the page and in the video, the label, your refund policy and your messages with the buyer. Stripe warns that issuers can reject a checkbox that only links to your policies, so show the full policy before purchase.
• Fraud on a Visa card: Compelling Evidence 3.0.

Compelling Evidence 3.0 covers Visa's card-absent fraud disputes (condition 10.4) for pre-arbitration attempts processed on or after April 15, 2023. You show two earlier undisputed transactions on the same card, processed between about 120 days and a year before the disputed transaction (Visa's October 2026 merchant guide), where at least two data points match the disputed order: account or login ID, delivery address, device ID or fingerprint, and IP address. At least one of the matches must be the device or the IP address. Qualifying evidence moves liability to the issuer (Visa's CE 3.0 FAQ), and a fraud report that qualifies drops out of Visa's VAMP count. From October 24, 2026, Visa widens CE 3.0 to accept evidence from transactions at more than one merchant (Visa's April 2026 rules). To use it at all, your checkout has to record the data it matches on, such as the IP address and device ID, plus the shipping address and a description of what was sold, with every order.

Every fight costs time and, on Stripe, a second fee. The ratio doesn't care whether you win, so put your effort into prevention first and fight the cases your evidence wins. When you do fight, chargeback representment walks through the deadlines, the evidence and the rebuttal letter step by step.

How do you know your chargeback prevention is working?

Measure each cause against its own history, not the total:

• Count disputes by reason every week. A descriptor fix should move "unrecognized", not "not received".
• Group disputes by order date. A fix shows up first in the orders it touches. The monthly ratio catches up later, because disputes keep arriving for months after an order.
• Trace disputes to the traffic that sold them. In RevvyScales, each sale your checkout reports back is tied to the CTA click behind it, and the rvs URL parameter carries that click's campaign, ad set and ad (conversion tracking), so a disputed order can be traced to the campaign that sold it. If one ad angle produces most of the "not as described" disputes, that is a claims problem, not a payments problem.

The outcome to watch is your ratio with each network, counted the way each network counts it:

A checklist to reduce chargebacks this week

Work through it once, then again whenever you change the offer, the checkout or the shipping partner:

Chargeback prevention checklist

• The descriptor uses the brand name from the ad, and the receipt says how the charge will appear
• Upsells charged separately are named on the upsell page and in the receipt
• Subscription price, frequency and how to cancel are said in the video and printed next to the button
• The buyer clicks to confirm the subscription terms before paying
• Reminders go out before trials end and before renewals
• Canceling takes one step online and is confirmed by email
• Shipping times shown before checkout match what the warehouse achieves
• Tracking goes out the day it exists, and every delay gets an email with a refund option
• Refund requests are answered within one business day
• CVC and full billing address are collected, and risky orders are reviewed before shipping
• Alerts or pre-dispute services are connected through your processor, with an owner
• Disputes are reviewed every week by reason and by campaign

0 of 12 done