How to Prevent Chargebacks (and Win the Ones You Get)

You ship a tracked order, and two weeks later the buyer disputes the payment as unauthorized. Someone even signed for the parcel. Learning how to prevent chargebacks means checking suspicious payments before fulfillment, making purchases easy to recognize and cancel, and answering disputes with evidence that addresses the claim. A delivery signature helps establish delivery; it doesn't establish who authorized the payment.

Why do small sellers get so many chargebacks?

You cancel high-risk orders, check addresses, and still get a dispute on a low-risk payment. That can happen because the buyer is the real cardholder. A fraud score won't tell you whether they remember a renewal or recognize your business name on their statement.

Friendly fraud happens when a legitimate purchase becomes a fraud claim through confusion or deliberate misuse. The buyer might go straight to their bank because they can't find your support email. Or you put two orders in one box without explaining it, and they think the second order never arrived.

Match the fix to the cause: recognizable billing for forgotten purchases, clear shipment messages for delivery confusion, and an accessible refund route for complaints. Tightening stolen-card filters won't solve those problems.

Don't build your chargeback prevention plan around finding a shared buyer blacklist. Start with your processor's screening tools and your own order history, where you can check what happened before refusing another purchase.

What does one chargeback really cost?

For a US account on Stripe's standard pricing, manual disputes have these costs:

Say you sell a hypothetical $6 subscription. If you accept a dispute, the $6 payment is reversed and the $15 received fee stays charged: $21 debited, before original processing fees or your time. For a hypothetical $120 order, the same calculation is $135. The flat fee alone is larger than the subscription payment, which makes preventing small disputes especially valuable.

Country and contract terms differ. Your dispute rate also matters: winning doesn't erase a received chargeback from network statistics. Stripe says the process can take two to three months.

How to prevent chargebacks before you ship

A common tip is to decline every payment that fails address or security-code verification. Today, the available settings depend on your platform, and some checks are risk-based. Check what your rules actually block before relying on them.

In Shopify, go to Settings → Payments → Shopify Payments → Manage → Fraud prevention → Reduce credit and debit card fraud. To choose the filters yourself, disable Use automated settings, then activate Decline charges that fail AVS postal code verification and Decline charges that fail CVV verification. These are built-in settings. Unsupported issuer checks and saved-card flows can bypass verification; stricter AVS filtering can also reject legitimate customers.

Stripe's current default rules say CVC verification fails based on risk score and Postal code verification fails based on risk score. They can allow low-risk payments despite failed checks. Don't read these as blanket declines. Radar Lite is included with standard Payments pricing; custom rules and manual reviews require a paid Radar tier. Stripe is changing Radar pricing in early 2027; check Stripe's Radar pricing page for the current price.

Before shipping, review rush delivery combined with an unusually large order, changed delivery details, or repeated attempts across cards. Stripe documents these indicators; none proves theft. If several details look unusual, pause fulfillment and contact the buyer to confirm the order. This costs staff time, and a convincing answer isn't proof of card ownership. Address mismatches can be gifts.

For suspicious physical orders, consider a 24–48-hour shipping delay, within your promised delivery window. This may save the merchandise if fraud surfaces; it doesn't prevent a chargeback on an already captured payment.

Separate authorization and capture gives you time to review before collecting money. An uncaptured authorization reserves funds without completing payment, so it can't be disputed as a captured charge. Canceling before completion is free on Stripe.

Don't assume every hold lasts seven days. Stripe's current table lists seven days for typical online customer-initiated card payments, but Visa merchant-initiated authorizations have a shorter window, exactly four days and 18 hours. Check capture_before; an expired hold releases the funds. This workflow adds review work and integration changes where manual capture isn't already supported.

How to stop friendly fraud

Make your statement name recognizable from your storefront. Set your customer-facing business name in Stripe's Business details. The dedicated descriptor rules require 5–22 Latin characters, at least one letter, and a name reflecting your business. Some banks display it differently. Mention the expected name in receipts too.

Check receipt delivery instead of assuming it's enabled. Stripe creates receipts without necessarily emailing them. Enable Settings → Business → Customer emails → Successful payments, and supply a recipient email.

For subscriptions, enable Send emails about upcoming renewals. Stripe recommends about seven days before annual renewals and two to three before monthly renewals. Include the amount and cancellation route. Automatic renewal reminders apply to automatically charged subscriptions, not send_invoice subscriptions. These use existing Payments/Billing features; US pay-as-you-go Billing costs 0.7% of Billing volume, plus payment fees.

Show a clear refund policy before payment. Stripe recommends presenting the full policy at checkout or in a required popup, because a checkbox linking elsewhere can be weak evidence. Make support and cancellation easy to find among the trust signals on your checkout. Explain combined shipments in the confirmation email.

For valuable physical deliveries, consider signature confirmation. USPS charges a variable service fee and provides a signature record for eligible shipments. It supports delivery evidence, without guaranteeing a fraud-dispute win. Policies, emails, and support also cost setup and handling time; none removes the customer's dispute rights.

Should you fight or refund?

Contesting invalid claims fits high-value orders with strong evidence that's quick to assemble. Refunding small complaints before they escalate fits low-value products where preparing a response costs more than the payment. Use the amount and evidence to decide, even if you also plan to refuse future orders from an abusive customer.

Before a dispute opens, a refund can prevent escalation. After it opens, use Accept dispute or Counter dispute. Stripe doesn't permit a separate refund while it's open. Accept a valid complaint; don't pay to contest your own mistake.

For an invalid claim, a decision rule for a manual response is:

Expected benefit = chance of winning × recoverable amount − chance of losing × counter fee − staff cost.

The received fee and already-spent fulfillment costs are sunk either way. Hypothetically, a $120 claim, 50% win estimate, $15 counter fee, and $10 of work gives $60 − $7.50 − $10 = $42.50. Fighting has positive expected value. With a $6 claim and the same assumptions, it's $3 − $7.50 − $10 = −$14.50. These are illustrative calculations. Estimate your chances from the evidence and your own past results, and use actual preparation time.

For an Early Fraud Warning, Stripe reports that about 40% of unrefunded Visa/Mastercard warnings become fraud disputes. Its analysis favors refunds around or below the dispute fee, with account risk justifying a more aggressive approach. Refunding sacrifices the revenue, and original processing fees aren't returned. It also doesn't erase an existing fraud report. Check whether a dispute already exists before acting.

How to win a chargeback

Read the issuer's claim before assembling files. If you decide to fight, submit your response on time: missing Stripe's deadline means an automatic loss. The usual response window is 7–21 days; use the deadline shown for your case.

Match your response to the dispute category:

A shipment screenshot doesn't answer every claim. Keep the explanation factual and brief. Stripe accepts PDF, JPEG, or PNG, totaling no more than 4.5 MB and fewer than 50 pages. Stricter limits apply: its response guide specifies a 19-page Mastercard maximum. Follow the case's displayed limit. Issuers don't follow tracking links, and you can't amend a submitted response.

Visa Compelling Evidence 3.0 helps with eligible Visa 10.4 card-absent fraud claims. Visa requires two prior undisputed transactions on the same card, normally 120–365 days before dispute processing. At least two qualifying fields must match across those purchases and the disputed purchase: account ID, delivery address, device ID/fingerprint, or IP address. One must be IP or device data. Include the item description.

Stripe flags eligible cases and pre-populates available history. Review missing fields and submit the response; ordinary countering fees still apply. A new customer's first purchase can't supply that history. Paid pre-dispute CE 3.0 blocking is a separate service.

How do you keep your dispute rate low?

Two disputes among 100 payments is 2% in a simple same-period calculation. That's illustrative arithmetic, not a network-program formula. Low volume makes each complaint consequential, even below formal enrollment thresholds.

As checked November 5, 2026:

Visa's fact sheet dates the AP/Canada/EU/US reduction to April 1, 2026. It leaves Brazil, Chile, and India to separate announcements; confirm local implementation. VAMP combines fraud reports and disputes over same-month settled Visa transactions, subject to exclusions. Mastercard uses current-month chargebacks over prior-month Mastercard transactions; Shopify documents both ECP levels.

These excessive thresholds aren't safe operating targets. Stripe also lists a VAMP non-compliant level of five reports and 0.5%; processors can act below excessive-program floors. Received disputes count regardless of outcome. Review processor metrics and notifications regularly; refunds after capture don't necessarily remove network fraud reports. Ask your processor which regional rules apply.

What should you do in the next 30 minutes?

1. First five minutes: Open pending disputes and record each deadline. Read the claim, then accept valid complaints or assess the recoverable amount before spending time on evidence.
2. Next ten: Review your descriptor, receipt emails, renewal reminders, and cancellation route. Check these from the customer's side of your Stripe checkout page.
3. Next ten: Inspect verification rules and suspicious unfulfilled orders. Confirm supported checks and hold-expiry times before changing capture or fulfillment.
4. Last five: Save relevant policy and delivery screenshots, locate digital access records, and check recent fraud warnings. Record the cause of each dispute so the next change addresses what actually happened.

FAQ

Can a customer dispute a refunded order?

A fully completed refund normally prevents a new dispute; partial refunds don't, even for the full original amount. A pending refund isn't completed. Stripe documents rare issuer errors on already-refunded payments, so keep the refund reference and check any notification rather than paying twice.

Does 3D Secure stop all chargebacks?

No. A common tip is to turn on 3D Secure and treat every payment as protected. Today, 3D Secure liability shift generally protects eligible fraud claims after successful authentication, without guaranteeing coverage. Non-delivery claims still follow the normal process. Answer inquiries or risk losing the protection.

Broader authentication can fit a business facing costly stolen-card fraud. A targeted approach can fit a checkout where extra challenges lose legitimate purchases. Modern 3DS can be frictionless, but issuers choose the flow; indiscriminate use can reduce conversion. Match additional authentication to risk while meeting mandatory requirements. US standard Stripe Payments includes 3DS.

Off-session renewals can use exemptions after setup authentication and customer consent. That doesn't guarantee every later renewal is protected.

Do you get the Stripe dispute fee back if you win?

On standard US pricing, the received fee stays charged; the manual counter fee comes back. Exceptions depend on country and contract. Advice that winning returns every fee is outdated for these US accounts.

Should you send lost chargebacks to collections?

A common tip is to send every lost dispute to collections. Don't assume losing a chargeback establishes an enforceable debt. Before considering collection, get jurisdiction-specific advice and compare likely recovery with agency and legal costs. FTC guidance explains debt-verification rights and collection restrictions; it doesn't establish your right to recover a particular chargeback. For a small balance, those checks can cost more than the amount at stake.

Do chargeback alert services pay off for small stores?

Sometimes. Visa RDR and Mastercard Ethoca Alerts can resolve eligible cases before chargebacks count, by returning funds. Stripe's US prices at the time of writing (November 2026) are $15 per Visa resolution and $29 per Mastercard resolution, plus the returned payment. Rules apply after enrollment; RDR doesn't support partial disputes or already-refunded transactions. Compare those costs with likely escalation losses and account risk.

Guaranteed-fraud protection instead reimburses covered losses, with eligibility and fulfillment conditions. Current platform documentation shows paid-per-protected-order and free restricted models. Coverage can exclude digital goods and subsequent subscription orders, and non-delivery or quality claims. Check the actual contract and cost per protected order before buying coverage.