How to Reduce Chargebacks: A 30/60/90-Day Plan to Lower Your Chargeback Rate

Reducing chargebacks means bringing down two numbers at once: the count of disputes your store receives each month and your chargeback ratio, the share of transactions that end in a chargeback, measured against the thresholds Visa and Mastercard use to fine and eventually terminate merchants. Fees, lost goods, and monitoring-program penalties all scale with those two numbers, so every fix in this plan is ordered by how fast it moves them.

This is a 30/60/90-day playbook for merchants whose ratio is already too high or climbing. If you want the broader picture of what ecommerce chargebacks are, what they cost, and how the dispute process runs, read our ecommerce chargebacks guide first; this page assumes you know the basics and need the ratio down.

First, Know Your Number

Your chargeback rate is the number of chargebacks you receive divided by your total number of transactions in a given period. Card networks watch this number closely. If it climbs too high, you face penalties, fines, and potentially lose the ability to process payments altogether. Calculating your exact chargeback ratio each month makes it easier to catch a rising trend before it crosses a card network threshold.

The catch is that Visa and Mastercard do not calculate the ratio the same way, and both apply a minimum count before the ratio matters at all. A store doing 2,000 orders a month with 20 chargebacks has a 1% ratio but is nowhere near either program; a store doing 50,000 orders with 800 disputes is over the Visa line. Count matters as much as percent.

Visa consolidated its previous monitoring programs into a single program called VAMP, short for Visa Acquirer Monitoring Program. Because VAMP counts fraud reports as well as disputes, a chargeback you later win still counts, and so does a fraud report on a transaction that was never disputed. Mastercard runs the Excessive Chargeback Merchant program, or ECM, with its own dispute thresholds and fines that grow each month you stay above the limit, per published program guidance. The full breakdown of both programs, including acquirer-level triggers, is in our guide to chargeback thresholds.

Two more numbers to pin down before you start. Cardholders have 60 days from the statement date to raise a billing error under Regulation Z (12 CFR 1026.13), and issuers allow longer for card network disputes, so the chargebacks you see this month reflect sales from the last one to four months; your fixes take a full cycle to show up in the ratio. And the cost you are reducing is bigger than the order value: LexisNexis puts the total cost of fraud for US retail and ecommerce merchants at $5.13 for every $1 of direct loss, once fees, labor, and replacement goods are counted.

The Fastest Levers (Days 0 to 30)

These five moves change the count within one billing cycle. Do them in this order.

1. Enroll in chargeback alerts. Chargeback alerts give you a window to resolve disputes before they become chargebacks. Alert services from Visa's Verifi network and Mastercard's Ethoca network notify you the moment a customer initiates a dispute with their bank. When you receive an alert, you can issue a refund to the customer before the dispute officially becomes a chargeback. The refund resolves the issue, and the chargeback never counts against your ratio. Chargeflow Alerts aggregates alerts from Verifi, Ethoca, and the Chargeflow Network into one system, matches them to transactions, and processes refunds automatically, so the response time is minutes rather than days. This is the single fastest way to cut the count.
2. Fix your billing descriptor. This is the name that appears on your customer's credit card or bank statement next to the charge. If your billing descriptor does not match your brand name, customers will not recognize the charge. They assume it is fraud and call their bank to dispute it. Make sure your descriptor clearly shows your business name, and include a phone number or website URL so customers can reach you directly before filing a dispute. Descriptor confusion is a large slice of friendly fraud, which Visa puts at around 20% of all fraudulent disputes globally, and up to 30% for high-volume online merchants.
3. Refund proactively on "I do not recognize this charge" contacts. When a customer emails or calls saying they do not recognize a charge, treat it as a dispute in progress. A fast refund always costs less than a chargeback. Every chargeback comes with fees and ratio impact that a simple refund avoids entirely. Give support a standing authority to refund unrecognized-charge contacts under a set order value without escalation.
4. Tighten fraud rules on high-risk BINs and countries. Pull your fraud-coded chargebacks from the last 90 days and look for clusters: issuing BINs, shipping countries, mismatched billing and shipping, and repeated failed payment attempts before a success. Make sure your checkout uses AVS to confirm the billing address matches what the card issuer has on file, and require CVV verification on every transaction. Route the clusters you found to manual review or decline. Chargeflow Prevent screens orders after authorization and before you ship, using a global merchant network to catch the digital shoplifters that pre-checkout rules miss. For the wider control list, use the ecommerce fraud prevention guide.
5. Pause risky SKUs or channels. One product line, one affiliate, or one ad channel is usually responsible for a disproportionate share of disputes. Pausing it for 30 days costs you some revenue and buys you an immediate drop in the count while the structural fixes below take hold. Restart it once the ratio is back under control and the order source is cleaned up.

{{cta}}

Structural Fixes (Days 30 to 60)

With the count falling, fix the processes that generate disputes in the first place. These changes take a few weeks to implement and a full cycle to show in the ratio.

1. Add checkout friction only where it pays. Implement 3-D Secure authentication with risk-based rules so it steps up high-risk orders (new customer, high ticket, mismatched address, risky BIN) and leaves trusted repeat buyers alone. Blanket 3DS on every order costs conversion; targeted 3DS shifts fraud liability to the issuer exactly where you need it.
2. Capture delivery confirmation on every order. Ship with tracking from a carrier that records delivery scans, and store proof of delivery against the order. It is the first piece of evidence in any item-not-received dispute and a requirement for most processor protection programs.
3. Make refunds, returns, and cancellations easy. A clear, visible refund policy is one of your strongest chargeback prevention tools. When customers know exactly how to return a product and get their money back, they are far less likely to go straight to their bank. Display your return policy prominently on your website, in order confirmation emails, and on product pages. Remove any friction from the refund process so customers choose a refund over a dispute.
4. Set customer service SLAs. Most chargebacks happen because customers feel left in the dark after they buy. Answer every support contact within one business day, and every "where is my order" or "I want a refund" message within hours. If there is a delay, proactively notify the customer before they contact their bank. Send order confirmations immediately after purchase with clear merchant information, and provide tracking numbers and shipping updates so customers always know where their order is.
5. Send subscription reminders before every rebill. Recurring billing is a chargeback magnet when the charge surprises the customer. Email a reminder before each renewal, show the next billing date in the account, and make cancellation a one-click action. Card network rules for subscriptions require it, and the "did not authorize renewal" dispute drops sharply once you do.

Long-Term Fixes (Days 60 to 90 and Beyond)

The first two phases bring the ratio down. This phase keeps it down and recovers the revenue on the disputes you could not prevent.

1. Run root-cause analysis by reason code. Sort every chargeback by chargeback reason code: true fraud, friendly fraud, item not received, not as described, cancelled recurring, and processing errors. Each category points to a different owner (fraud rules, support, fulfillment, billing) and a different fix. Review the mix monthly and assign one owner per category.
2. Raise your win rate with representment. When prevention and alerts are not enough, chargeback representment lets you fight back by submitting evidence to the card issuer proving the transaction was legitimate. Strong evidence includes delivery confirmation, customer communication (emails, chat logs, or support tickets showing the customer received and used the product), signed terms and policies from checkout, and transaction data such as IP addresses, device fingerprints, and login activity linking the cardholder to the purchase. Visa Compelling Evidence 3.0 lets you submit historical transaction data from the same customer to prove a pattern of legitimate purchases on friendly fraud disputes. Chargeflow automated recovery assembles evidence from over a thousand data points and submits every dispute, so recovery runs without consuming your team's time. Know what compelling evidence needs to include before you invest here.
3. Feed dispute outcomes back into your fraud model. Every confirmed fraud chargeback should update your rules and your screening vendor's model: block the card, flag the device and email, and score the BIN and address pattern higher. Every won friendly-fraud dispute should feed a customer-level history you can reuse as evidence next time.
4. Decide whether coverage makes sense. Once the ratio is stable, compare what a processor protection program or chargeback insurance would cost against your remaining fraud-coded losses. Coverage pays after the loss and never lowers the ratio, so it belongs at the end of this plan, not the start.

Recovery does not change the ratio (a won dispute still counts), so keep the alerts and prevention layers running. A dispute, a refund, and a chargeback are distinct events with different ratio effects, which is why the definitions in what a chargeback is matter when you set targets.

Reducing Chargebacks by Platform

Shopify

Shopify Payments charges a $15 chargeback fee, and Shopify's dispute rate program auto-enrolls stores at around a 1% dispute rate, so the ratio bar is tighter than the network thresholds. Alerts and a clean descriptor matter most; Shopify Protect covers fraud-coded chargebacks on eligible Shop Pay orders but nothing else. The Shopify chargebacks guide walks through the dispute flow, fees, and the Chargeflow app setup.

Stripe

Stripe reports your dispute rate in the Dashboard and charges a dispute fee whether you win or lose. Use Radar rules to block the BIN and country clusters you found in the first 30 days, enable 3DS step-up through Radar, and connect alerts so Verifi and Ethoca notifications resolve before the dispute posts. The Stripe chargebacks guide covers Radar, Stripe Chargeback Protection, and how to contest the disputes it excludes.

PayPal

PayPal disputes run through PayPal's own resolution center before they become card chargebacks, which gives you a response window card networks do not. Answer every PayPal dispute inside that window, ship to the address on the Transaction Details page with tracked delivery to keep Seller Protection, and read the PayPal chargeback protection guide for the eligibility rules that decide whether PayPal absorbs the loss.

WooCommerce and other platforms

On WooCommerce, Magento, BigCommerce, or a custom stack, the ratio is governed by your payment service provider rather than the platform. Confirm AVS, CVV, and 3DS are enforced at the gateway, make sure the descriptor is set at the acquirer level, and route alerts and recovery through the processor integration. The 30/60/90 plan above applies unchanged.

What Not to Do

• Do not block all international cards. It removes real revenue and leaves domestic friendly fraud, usually your largest category, untouched. Block the specific BIN and country clusters your data points to.
• Do not refund every dispute reflexively. Refund on alerts and on unrecognized-charge contacts, where the refund stops a chargeback from posting. Once a chargeback has posted, a refund does not remove it from the ratio; represent it instead.
• Do not ignore inquiries and retrieval requests. An unanswered inquiry becomes a chargeback you cannot win. Treat inquiries as the earliest alert you have.
• Do not measure by percent alone. A rising count with flat percent still moves you toward the 100 and 1,500 minimums, and a falling transaction volume can push the percent over the line with no change in disputes.
• Do not stop the fixes when the ratio dips. Disputes lag sales by one to four months, so a good month reflects work you did last quarter. Keep the alerts, rules, and SLAs in place permanently.

How to Track Progress

Put these metrics on one dashboard and review them on the cadence shown. The targets are for a store that wants a comfortable margin under both network programs; tighten them if your acquirer or platform sets a lower bar.

Turning these numbers into a repeatable workflow, backed by an ongoing chargeback prevention review, is what keeps the rate down for good. The industry win-rate and net-recovery benchmarks above come from a 2026 industry chargeback field report; the fee range reflects published processor pricing.

Reduce Chargebacks FAQ

How quickly can a merchant reduce chargebacks?

A merchant can reduce the chargeback count within the first billing cycle by enrolling in chargeback alerts, fixing the billing descriptor, and refunding unrecognized-charge contacts, because those actions stop disputes that are already in motion. The chargeback ratio lags by one to four months, since disputes reflect earlier sales, so expect the ratio to show the full effect in 60 to 90 days.

What chargeback rate is too high, and what counts as healthy?

A chargeback rate above 1.5% is too high for any merchant: Visa's VAMP flags merchants at 1.5% with 1,500 or more monthly fraud reports and disputes, and Mastercard's ECM starts at 1.5% with 100 or more chargebacks. A healthy chargeback rate is below 0.9%, and many platforms and acquirers act well before the network thresholds, with Shopify enrolling stores at around 1%.

Do chargeback alerts reduce the chargeback ratio?

Yes. Chargeback alerts from Verifi and Ethoca notify a merchant when a cardholder has started a dispute, and a refund issued in response resolves the dispute before it is filed as a chargeback, so it never enters the count or the ratio. Alerts are the only protection model that lowers the ratio directly; insurance, guarantees, and representment do not.

Does refunding a customer count as a chargeback?

No. A refund issued by the merchant is not a chargeback and does not count toward the chargeback ratio, which is why refunding on alerts and on unrecognized-charge contacts reduces chargebacks. A refund issued after a chargeback has already posted does not remove that chargeback from the ratio; the merchant has then lost both the funds and the count.

Can a high chargeback rate get a merchant account terminated?

Yes. A merchant that stays above Visa VAMP or Mastercard ECM thresholds faces escalating monthly fines and, if the rate does not come down, the acquirer can close the merchant account and place the business on the MATCH list, which makes it difficult to open a new account with another acquirer. Acquirers often terminate or add reserves before the network programs formally act.