A chargeback is a forced reversal of a card payment: the cardholder disputes a charge with their bank, and the bank pulls the money back from the merchant while it investigates. To reduce chargebacks, you need to stop fraud before it's captured, make every charge easy to recognize, and remove the service failures that push genuine customers to call their bank instead of you.
This guide explains how the dispute process works, what it costs, which card-network rules matter, and the practical steps that lower your dispute rate.
How a chargeback works
When a cardholder files a dispute, the card network debits the disputed amount from the merchant's account and holds it for the entire duration of the case. According to Stripe's documentation on the dispute lifecycle, the typical timeline looks like this:
- Filing window: card networks typically allow cardholders to dispute within 120 days of the original payment, with longer windows in some situations. For pre-paid future services such as travel or event tickets, the clock usually starts on the event date, not the payment date.
- Your response window: once a chargeback is created, you usually have 7 to 21 days to respond, depending on the network.
- Issuer decision: after you submit evidence, the issuer typically has 60 to 75 days to decide. The whole cycle can take two to three months.
The final decision rests with the cardholder's bank, not with your payment provider. If you win, the funds come back. If you lose, they stay with the cardholder.
What a chargeback really costs
A lost dispute costs more than the order value. You usually lose:
- The revenue, which is debited as soon as the dispute opens.
- The goods, if they have already shipped and aren't returned.
- A dispute fee. On Stripe, for example, the fee for receiving a dispute is non-refundable for businesses outside Mexico, and a separate fee applies if you counter the dispute; that second fee is returned only if you win.
- Time spent gathering evidence, and, if your rate climbs, your standing with the card networks.
That last point is the one that can threaten the whole business, so it is worth understanding in detail.
Card-network monitoring programs
Visa and Mastercard track each merchant's disputes and fraud every month. Exceed their thresholds and you can be placed in a monitoring program with fines, and persistent non-compliance can end with the network refusing further payments. The figures below are summarized from Stripe's guide to card monitoring programs; always check the networks' own documentation for the current rules.
Visa: VAMP
The Visa Acquirer Monitoring Program (VAMP) combines disputes and fraud into a single measure. In 2025, Visa said it was adjusting the formula to include all disputes, both fraudulent and non-fraud. The VAMP ratio counts disputes plus fraud reports (TC40 early fraud warnings) against captured payments, and a transaction that appears in both reports counts twice.
| VAMP criterion | Non-compliant | Excessive |
|---|---|---|
| Count of disputes and fraud | 5 | 1,500 (150 in CEMEA) |
| Ratio to captured payments | 0.5% | 1.5% (2.2% in CEMEA) |
Mastercard: ECM, HECM and EFM
Mastercard's Excessive Chargeback Program has two levels. A merchant with 100 to 299 chargebacks and a chargeback rate of 1.5% to 2.99% in a month is an Excessive Chargeback Merchant; 300 or more chargebacks at a 3% rate or higher is the High Excessive level. Fines start in the second month and escalate the longer you stay in. Mastercard counts a chargeback regardless of its outcome, whether it was refunded, and whether liability shifted. A separate Excessive Fraud Merchant program targets merchants with high fraud chargebacks and low 3-D Secure usage.
The practical lesson: winning disputes doesn't lower your rate. Monitoring programs count disputes when they are filed, so prevention is the only lever that keeps you safe.
The three main causes
- True fraud: a stolen card is used to buy from you, and the real cardholder disputes the charge.
- Friendly fraud: a real customer disputes a legitimate charge, often because they don't recognize it, forgot about it, or a family member made the purchase.
- Service problems: the order arrived late, didn't arrive, wasn't as described, or the customer couldn't find an easy way to return it.
Practical steps to reduce chargebacks
1. Authenticate risky payments with 3-D Secure
3-D Secure (3DS) asks the card issuer to verify the shopper, often invisibly in a frictionless flow and sometimes with a one-time code or app approval. Its main benefit for merchants is the liability shift: when a payment is successfully authenticated and later disputed as fraud, liability typically moves from you to the issuer. As Stripe's 3DS documentation stresses, this is typical, not guaranteed. It applies to fraud disputes only; a "product not received" dispute still follows the standard process, and liability generally doesn't shift if the card doesn't support 3DS or authentication fails. In Europe, Strong Customer Authentication rules already require 3DS for many payments; elsewhere, many merchants apply it selectively to higher-risk orders.
2. Make your billing descriptor recognizable
A large share of friendly fraud starts with a customer who doesn't recognize a line on their statement. Stripe notes that clear and accurate statement descriptors can reduce chargebacks and disputes. Descriptors are short (5 to 22 characters on Stripe) and should reflect the name customers know you by, not a legal entity name they've never seen. If you sell several product lines, a dynamic suffix can add order-specific detail.
3. Stop fraud before you capture
Issuers must report possible fraud on a captured payment even if you later refund it, but not on an authorization you reverse before capture. Separating authorization and capture, and reviewing flagged orders in between, keeps suspicious orders out of your fraud count entirely. When you receive an early fraud warning on a small order, a proactive refund can head off a dispute; Stripe's analysis suggests this pays off mainly on charges at or below your dispute fee.
4. Remove service-related disputes
- State shipping times before checkout, and tell customers quickly about delays, offering a refund if they don't want to wait.
- Send a tracking number as soon as an order ships; for high-value goods, consider signature on delivery.
- Describe products accurately with real photos, and show the full price including taxes before payment.
- Publish a clear return policy and make returns easy to start. A customer who can get a refund from you in two clicks has little reason to call their bank.
- Make it easy to reach you. Visible contact options and fast replies resolve problems before they become disputes.
5. Answer every inquiry and every dispute
Some networks send an inquiry before a formal chargeback. Ignoring it can escalate the case into a chargeback that is likely unwinnable, and on a 3DS-authenticated payment an unanswered inquiry can lead to a "no-reply" chargeback that undoes the liability shift. When you do contest a dispute, send evidence that matches the claim: proof of delivery for "not received," the product page and your policies for "not as described."
6. Use Visa Compelling Evidence 3.0 against friendly fraud
For Visa card-absent fraud disputes (reason code 10.4), Compelling Evidence 3.0 lets you point to two earlier, undisputed transactions with the same cardholder, processed between 120 and 365 days before the disputed one, that share identifying data such as the customer email, delivery address, device ID or IP address. Keeping clean order records makes this evidence available when you need it, and Stripe notes that fraud reports qualifying for CE3.0 are excluded from the VAMP count.
Track the right numbers
Watch your dispute rate per card network every month, using each network's own formula: Visa compares disputes to payments in the same month, while Mastercard compares this month's chargebacks to last month's payments. Break disputes down by reason code. A spike in "not received" points at shipping; a spike in "unrecognized" or "general" points at your descriptor or receipts; a spike in fraud points at your checkout controls.
How CIQRA fits in
CIQRA stores connect to Stripe, PayPal, iyzico, PayTR, Param, Moka and bank card gateways, as well as bank transfer and cash on delivery. Several of the service-side measures above are built into the platform: a returns portal where customers start a return from their account or as a guest and your team approves it, carrier integrations with labels, tracking and rates for DHL, UPS, FedEx and leading Turkish carriers, and live chat that shares one inbox with tickets. Fraud screening, 3-D Secure and dispute handling remain with the payment provider you connect.
FAQ
What is a good chargeback rate?
Lower is always better, but as a reference point, Visa's VAMP flags merchants at a 0.5% ratio of disputes and fraud to payments (with a minimum count), and Mastercard's first chargeback level starts at 1.5%.
Does 3-D Secure stop all chargebacks?
No. It typically shifts liability for fraud disputes to the issuer, but it doesn't cover disputes about delivery or product quality, and the shift isn't guaranteed for every payment.
Does refunding a customer count as a chargeback?
No. A refund you issue isn't a dispute. But if the customer files a dispute anyway, networks still count it, so refund quickly and clearly before the customer goes to their bank.
Sources
- Stripe, "How disputes work," 2026: docs.stripe.com/disputes/how-disputes-work
- Stripe, "Dispute and fraud card monitoring programs," 2026: docs.stripe.com/disputes/monitoring-programs
- Stripe, "Authenticate with 3D Secure," 2026: docs.stripe.com/payments/3d-secure/authentication-flow
- Stripe, "Statement descriptors," 2026: docs.stripe.com/get-started/account/statement-descriptors
- Stripe Support, "How does Stripe support Visa Compelling Evidence 3.0?": support.stripe.com
- Visa, "Security program takes aim at payments fraud," 2025: corporate.visa.com