How to Prevent and Fight Chargebacks: Evidence, Reason Codes and Descriptor Fixes

A chargeback feels unfair the first time it happens. The customer got the product, you have the tracking number, and the money is still pulled from your account, plus a fee. Do nothing and you lose the sale, the product and the shipping cost. Let it happen often and your payment provider may hold funds or close your account.

The good news is that a large share of chargebacks are preventable, and many of the rest are winnable if you send the right evidence for the right reason code. This guide explains how the process works, what to collect for each type of dispute and the simple fixes, like a clearer statement descriptor, that stop “friendly fraud” before it starts.

What a chargeback is and how it works

A chargeback happens when a cardholder disputes a charge with their bank, and the bank reverses the payment. It’s different from a refund, which you choose to give. With a chargeback, the bank decides.

The typical lifecycle, as Stripe describes it:

1. The cardholder disputes the charge with their card issuer. Card networks typically allow disputes within 120 days of the payment, and longer in some cases, such as for future events where the clock starts on the event date.
2. Your provider debits the disputed amount plus a dispute fee from your balance. With Stripe, for example, the US fee is $15 per dispute received.
3. You decide whether to accept or respond. You usually have 7 to 21 days to respond, depending on the network.
4. The issuer reviews your evidence and decides, usually within 60 to 75 days.
5. The outcome is final. If you win, the funds return. The whole process can take 2 to 3 months.

Some networks, notably American Express and Discover, may first send an inquiry, a request for information before a formal chargeback. Stripe warns that ignoring an inquiry can lead to an unwinnable chargeback, so always answer.

The 3 types of chargebacks

Understanding why a customer disputed is the key to both prevention and response.

• True fraud: a criminal used a stolen card. The real cardholder never authorized the purchase.
• Merchant error or genuine problems: the item didn’t arrive, was damaged, didn’t match the description, or a refund wasn’t processed.
• Friendly fraud (first-party misuse): the cardholder made the purchase but disputes it anyway, because they don’t recognize the charge, forgot a subscription, a family member bought it, or they want to avoid a return.

Card networks have noticed how big friendly fraud has become. Mastercard launched its First-Party Trust program in the US in October 2023 to help merchants and issuers share data that proves genuine purchases, such as purchase history, device details and delivery information.

Know your reason codes

Every chargeback comes with a reason code. Each network has its own codes, but they group into similar categories. Stripe, for example, sorts them into categories such as fraudulent, product not received, product unacceptable, duplicate, credit not processed, subscription canceled and unrecognized.

Visa organizes its codes into 4 families: fraud (10.x), authorization (11.x), processing errors (12.x) and consumer disputes (13.x).

Key takeaway: Evidence only works if it answers the reason code. A tracking number won’t win a “not as described” claim, and a product photo won’t win a fraud claim. Read the code first, then build your response around it.

Evidence to collect on every order

You can’t create evidence after the fact. Set up your systems to record these details for every online order:

• Order details: order number, date, items, amount and the policies shown at checkout.
• Customer identity data: name, email, billing and shipping address, phone, account ID.
• Technical data: IP address and device ID or fingerprint at purchase.
• Authentication: whether 3D Secure was used and the result, plus address and security code check results.
• Fulfillment: carrier, tracking number, ship date, delivery confirmation and signature for high-value orders.
• Digital access: login and download logs with timestamps for digital products.
• Communication: all emails, chats and support tickets.
• Policy acceptance: proof the customer saw and accepted your refund, cancellation and subscription terms.

Visa Compelling Evidence 3.0 for friendly fraud

For Visa card-absent fraud disputes (reason code 10.4), Visa’s Compelling Evidence 3.0 rules let you show a history of legitimate purchases. According to Stripe’s documentation, you need at least 2 prior undisputed transactions on the same payment method, made 120 to 364 days before the disputed one. They must share matching data with the disputed transaction, either 2 main elements (customer IP address and device fingerprint or device ID) or 1 main element plus 1 secondary element (shipping address, email address or customer account ID). Qualifying evidence can increase the chance the issuer reverses the dispute. This is why recording IP and device data on every order matters.

How to respond to a chargeback

1. Read the reason code and the cardholder’s claim. Decide what you need to prove.
2. Decide if it’s worth fighting. If the customer has a valid point, or the amount is smaller than your time and fees, accepting may be the better choice. Note that with Stripe, countering a dispute adds a $15 countered fee for disputes initiated after June 17, 2025, which is returned if you win.
3. Gather evidence that matches the code, using the table above.
4. Write a short, factual summary. Lead with the key fact: “The order was delivered to the cardholder’s address on March 3, confirmed by carrier tracking.” Then reference each attachment.
5. Keep it relevant and readable. Label documents clearly, highlight key details and leave out anything that doesn’t address the claim.
6. Submit before the deadline, and only once. Most providers allow a single submission.
7. Contact the customer, carefully. If they agree it was a mistake, ask them to withdraw the dispute with their bank. With Stripe, you still need to submit evidence for the dispute to close in your favor.

Our Stripe vs PayPal comparison explains how each provider handles disputes and their fees.

Prevention: stop chargebacks before they happen

Fix your statement descriptor

A surprising number of disputes happen simply because the customer doesn’t recognize the charge on their statement. Stripe’s documentation says clear and accurate statement descriptors can reduce chargebacks and disputes. On Stripe, a full descriptor must be 5 to 22 characters, reflect your doing-business-as name and use only Latin characters. You can also add a dynamic suffix with order details.

Practical fixes:

• Use the name customers know, such as your store or brand name, not your legal LLC name.
• Add a short website or phone number if space allows and your provider supports it.
• Use a dynamic suffix for multiple products or subscriptions, for example “BRAND* ANNUAL PLAN.”
• Match your email receipts to the descriptor so customers can connect them.

Other prevention steps

On early fraud warnings, Stripe’s analysis is useful. It reports that about 40% of Visa and Mastercard early fraud warnings become fraud disputes if not refunded, and suggests proactive refunds make most sense on charges roughly equal to or less than your dispute fee.

Payments built on secure foundations help too. For broader security basics, see our cybersecurity checklist for small business, and if you’re setting up checkout, start with how to accept payments on your website.

Why your dispute rate matters

Card networks and payment providers track your dispute rate, the share of transactions that turn into disputes. Visa and Mastercard both run monitoring programs that can penalize merchants and their acquirers when dispute or fraud levels run too high. High rates can lead to fees, reserves, holds or closure of your merchant account. Track your rate monthly, by product and by payment method, so a problem product or a fraud ring doesn’t catch you by surprise.

Where to start

1. Check your statement descriptor today and make it match your brand name.
2. Review your last 10 disputes and group them by reason code to find patterns.
3. Turn on fraud tools your provider offers, including 3D Secure for risky orders.
4. Make sure you record IP and device data for every order so you can use Visa CE 3.0.
5. Publish clear refund, shipping and cancellation policies, and show them at checkout.
6. Build response templates for your 3 most common reason codes.
7. Set a calendar alert for every dispute deadline.

Conclusion

Chargebacks are part of selling online, but they don’t have to be a constant drain. Prevention handles most of the problem: recognizable descriptors, clear policies, tracked shipping and responsive service. For the disputes that still arrive, match your evidence to the reason code, respond quickly and keep it factual. Do both consistently and you’ll lose fewer sales, pay fewer fees and keep your payment account in good standing. This is not legal advice.

Sources

• Stripe Docs: How disputes work — dispute lifecycle, 120-day window, response and decision times, inquiries and early fraud warnings
• Stripe Docs: Dispute reason code categories — Visa and Mastercard reason codes by category and evidence guidelines
• Stripe Docs: Visa Compelling Evidence 3.0 disputes — CE 3.0 qualifying criteria and matching data elements
• Stripe Docs: Statement descriptors — descriptor requirements and their role in reducing disputes
• Stripe Support: June 2025 dispute pricing updates — $15 dispute received and countered fees
• Mastercard: Mastercard targets friendly fraud — First-Party Trust program launch and data shared