# What Is a Chargeback? How They Work and How to Prevent Them

> A complete explainer on chargebacks - how they work, why customers file them, what they cost merchants, and the prevention strategies that actually reduce dispute rates.
- **Author**: Aarthi Poonia
- **Published**: 2026-05-27
- **Category**: Payments, Chargebacks
- **URL**: https://dodopayments.com/blogs/what-is-a-chargeback-explained

---

A chargeback is the forced reversal of a card payment, initiated by the cardholder through their issuing bank rather than by the merchant. The bank investigates the customer's claim, debits the funds from the merchant's account, and credits them back to the cardholder while the dispute is reviewed.

To a customer, a chargeback feels like an undo button on a purchase. To a merchant, it is a transaction reversal plus a $15-$50 dispute fee plus, if too many chargebacks accumulate, the threat of losing the merchant account entirely. Every chargeback you receive counts against a dispute-rate threshold that the card networks (Visa, Mastercard, American Express, Discover) actively monitor.

This guide explains how chargebacks work, why customers file them, what the lifecycle looks like from filing to resolution, and how merchants can prevent and respond to disputes. It is written for SaaS, digital product, and subscription businesses where chargebacks behave differently than they do in physical retail.

## How a Chargeback Actually Works

The chargeback process involves four parties: the cardholder, the issuing bank (the cardholder's bank), the acquiring bank (the merchant's bank or payment processor), and the card network (Visa, Mastercard, etc.) acting as referee.

The flow looks like this:

```mermaid
flowchart LR
    A[Cardholder
disputes charge] -->|"contacts bank"| B[Issuing bank
reviews claim]
    B -->|"valid claim"| C[Funds reversed
from merchant]
    C -->|"merchant notified"| D[Merchant decides
to dispute or accept]
    D -->|"dispute"| E[Submit evidence
via acquirer]
    E -->|"network reviews"| F[Final ruling]
    F -.->|"merchant wins"| G[Funds returned]
    F -.->|"merchant loses"| H[Loss + fees stand]
```

The cardholder calls their bank, says "I did not authorize this charge" or "I never received the product," and the bank opens a dispute. The bank pulls the funds from the merchant immediately, before any investigation, and notifies the merchant through their acquirer or payment processor. The merchant has a response window (typically 7-30 days) to either accept the loss or fight the dispute by submitting evidence.

If the merchant fights and wins, the funds come back. If the merchant fights and loses, or chooses not to respond, the loss is final and the dispute fee stays. Either way, the chargeback counts against the merchant's dispute rate for the period.

## Why Customers File Chargebacks

Customers file chargebacks for legitimate reasons and illegitimate ones, and the mix depends heavily on the type of business. Most chargebacks fall into one of four buckets.

**True fraud (criminal card theft)** happens when someone uses a stolen card number to make a purchase. The real cardholder sees the charge, recognizes it as fraud, and files a chargeback. The merchant typically loses these because the card networks side with the cardholder by default in unauthorized-transaction cases. 3D Secure authentication shifts liability for these to the issuing bank.

**Service-not-received disputes** happen when a customer pays for something and feels they did not get it. For SaaS, this often means the customer signed up, never used the product, and decided weeks later that they were charged for nothing. For e-commerce, it means a package never arrived or arrived damaged.

**Cancellation confusion** is specific to subscriptions. The customer thought they canceled but the cancellation never went through, or they forgot they signed up for a trial that converted to paid. They dispute the charge instead of working through the merchant's cancellation flow.

**Friendly fraud** is the term for chargebacks filed by customers who received what they paid for but dispute the charge anyway - to get free product, because they regret the purchase, or because they do not remember the transaction. Industry estimates put friendly fraud at 60-80% of all chargebacks for digital products.

The reason matters because each category requires a different prevention approach. Fraud prevention is solved with 3DS and risk screening. Cancellation confusion is solved with better billing descriptors and renewal reminders. Friendly fraud is solved with strong evidence collection and an aggressive dispute response program.

## How Much Chargebacks Actually Cost

The visible cost of a chargeback is the transaction reversal plus the dispute fee. But the real cost is several multiples higher when you count everything.

| Cost Component | Typical Range |
| --- | --- |
| Transaction reversal | Full transaction amount |
| Dispute fee from processor | $15-$50 per dispute |
| Operational time (collecting evidence, responding) | 1-3 hours per dispute |
| Product or service already delivered | Cost of goods or compute |
| Acquiring bank reserve hold | 5-20% of monthly volume if dispute rate spikes |
| Card network monitoring program enrollment | $5,000-$25,000+ in fines and remediation costs |

For a SaaS business with a $99/month plan and a 1% chargeback rate, the visible cost per chargeback is about $130 ($99 reversed + ~$30 dispute fee). The hidden cost - support staff time, lost lifetime value if the customer would have stayed, and risk of card network monitoring - can push the real cost past $300 per dispute.

If the dispute rate crosses the card network monitoring threshold (typically 0.9% for Visa, 1.5% for Mastercard), the consequences escalate sharply. The acquiring bank may require a rolling reserve, charge per-transaction monitoring fees, or terminate the merchant account entirely. Recovering from a card network monitoring program takes 4-6 months of dispute reduction and remediation reporting.

## The Chargeback Lifecycle Step by Step

Understanding the lifecycle helps merchants know what to expect at each stage and where they have the most leverage to influence the outcome.

**Step 1 - Cardholder contacts issuing bank.** The customer reports the disputed charge. Most issuing banks accept disputes through their mobile app or phone support, often with minimal verification.

**Step 2 - Issuing bank assigns a reason code.** The bank classifies the dispute under one of the card network's reason codes - for example, Visa's 10.4 (fraud), 13.1 (service not received), or 13.2 (canceled recurring transaction). The reason code determines what evidence the merchant needs to submit.

**Step 3 - Funds are pulled from the merchant.** The acquirer reverses the transaction immediately. The merchant sees a debit on their account and a notification of the dispute.

**Step 4 - Merchant receives the dispute notice.** Through the payment processor's dashboard or webhook events, the merchant learns the dispute exists, the reason code, the deadline to respond, and the evidence requirements.

**Step 5 - Merchant submits evidence (or does not).** The merchant either accepts the loss or assembles evidence - usage logs, IP records, delivery confirmation, signed authorization, support correspondence - and submits a representment package through their acquirer.

**Step 6 - Card network ruling.** The card network reviews the evidence and rules in favor of the merchant or cardholder. The decision is communicated back through both banks.

**Step 7 - Pre-arbitration (optional).** If either party disagrees with the ruling, they can escalate to pre-arbitration, which involves additional fees ($100-$500) and a more rigorous review.

**Step 8 - Arbitration (rare).** Final escalation to the card network arbitration committee. The losing party pays the arbitration fee ($250-$500+) plus the disputed amount. Most merchants do not escalate to arbitration unless the disputed amount is very large.

The whole lifecycle from initial filing to final ruling typically takes 30-90 days. Pre-arbitration and arbitration can extend it to 6+ months.

## How Merchants Prevent Chargebacks

Prevention is far cheaper than dispute response. The most effective prevention strategies fall into three categories.

**Reduce confusion.** A surprising share of chargebacks come from customers who do not recognize the charge on their statement. Fix the billing descriptor so it includes your recognizable brand name and a support phone number or URL. Send renewal reminders 5-14 days before each subscription charge. Make cancellation flows obvious - if a customer is hunting for a cancel button, they may give up and file a dispute instead.

**Catch fraud at checkout.** Implement [3D Secure authentication](https://dodopayments.com/blogs/3d-secure-3ds-payment-authentication) on card transactions. 3DS shifts the liability for fraud chargebacks to the issuing bank, which removes the largest chunk of merchant chargeback exposure. Add risk screening that looks at IP geography, BIN-to-billing-address mismatch, velocity (too many attempts from one source), and email reputation.

**Document the customer relationship.** Capture usage data, IP addresses, login timestamps, email correspondence, and explicit consent (especially for subscriptions). When a dispute does happen, this documentation is the evidence that wins representment cases. Companies that systematically capture this data win 30-50% of friendly fraud disputes. Companies that do not capture it win less than 10%.

For a deeper dive into specific tactics, see our [chargeback prevention guide for SaaS](https://dodopayments.com/blogs/chargeback-prevention-saas) and the [friendly fraud prevention playbook](https://dodopayments.com/blogs/friendly-fraud-prevention).

From our perspective at Dodo Payments: the economics of chargebacks favor the customer by default. The card networks designed the system to make disputes easy for cardholders because consumer trust in card payments was the goal. Merchants who treat dispute response as an afterthought lose money they did not have to lose.

## How the Merchant of Record Model Changes Chargeback Exposure

A [Merchant of Record](https://dodopayments.com/blogs/what-is-a-merchant-of-record) is a payment platform that takes legal responsibility for the transaction as the named seller. The MoR holds the merchant account, processes the payment through their acquirer, and appears on the customer's statement as the seller of record.

When a chargeback is filed against a transaction processed through an MoR, the dispute targets the MoR's merchant account, not the underlying business. The MoR handles evidence submission, absorbs the dispute fees, and carries the dispute rate impact. For a SaaS business using an MoR like Dodo Payments, chargebacks are still tracked and reported back to the business, but the operational burden and the merchant-account-termination risk sit with the MoR.

This model is most valuable for:

- Businesses selling globally where chargeback patterns vary by country
- High-ticket subscriptions where individual disputes are expensive
- Companies that lack in-house dispute response staff
- Sellers in higher-risk verticals where building merchant account relationships is hard

Dodo Payments handles the full [disputes and RDR process](https://docs.dodopayments.com/features/transactions/disputes) as part of the MoR service. Businesses retain visibility into open disputes through the merchant dashboard and can submit additional evidence, but they do not need to maintain a chargeback response team or worry about acquirer-level dispute rate thresholds.

## How to Respond When You Receive a Chargeback

For merchants who do hold their own merchant account, responding well to disputes is critical. Here is a tight response playbook.

**Triage within 24 hours.** Pull the dispute details, identify the reason code, and decide quickly whether the dispute is worth fighting. Some disputes - clear cases of true fraud where the customer never used the service - are not worth the time to contest. Most others are.

**Match evidence to the reason code.** Different reason codes require different evidence. A service-not-received dispute (13.1) requires proof of delivery or proof of access - login records, IP addresses, timestamps. A canceled recurring transaction dispute (13.2) requires proof of the original authorization and proof that no cancellation request was received. Submitting the wrong evidence is the most common reason representment cases lose.

**Submit within the response window.** Most card networks give merchants 7-30 days to respond. Miss the window and the dispute is automatically lost. Calendar reminders or automated dispute response tools help here.

**Track outcomes by reason code.** If you are losing all disputes of a particular type, the problem is structural - your billing descriptor, your cancellation flow, your fraud screening - not the individual dispute responses. Aggregate analysis tells you where to invest prevention effort.

**Use representment data to fix upstream issues.** Every dispute is a signal. A spike in 13.2 disputes means cancellation is broken. A spike in 10.4 disputes means fraud screening is weak. Treat dispute analytics as a feedback loop into your billing and risk infrastructure.

## Common Chargeback Reason Codes

The major card networks use slightly different reason code taxonomies, but they map to similar underlying customer claims. The most common ones merchants will see are:

- **Visa 10.4 / Mastercard 4837**: Card-absent fraud (unauthorized card-not-present transaction)
- **Visa 13.1 / Mastercard 4855**: Goods or services not provided
- **Visa 13.2 / Mastercard 4853**: Canceled recurring transaction
- **Visa 13.5 / Mastercard 4853**: Misrepresentation (product not as described)
- **Visa 12.6.1 / Mastercard 4834**: Duplicate processing (charged twice)
- **Visa 13.6 / Mastercard 4860**: Credit not processed (refund not issued)
- **Visa 11.3 / Mastercard 4808**: No authorization (transaction processed without valid authorization)

Each code has specific evidence requirements documented in the card network's compliance manuals. Modern payment processors typically surface these requirements in the dispute interface so merchants do not have to look them up themselves.

## FAQ

### What is a chargeback in simple terms?

A chargeback is when a customer asks their bank to reverse a card payment instead of asking the merchant for a refund. The bank pulls the funds back from the merchant, charges the merchant a dispute fee, and investigates the claim. If the bank rules in the customer's favor, the reversal is permanent.

### How long does a chargeback take to process?

Most chargebacks complete within 30-90 days from filing to final ruling. The customer files with their bank, the merchant has 7-30 days to respond, the card network reviews, and a ruling is issued. Pre-arbitration and arbitration can extend the timeline to 6+ months.

### What is the difference between a chargeback and a refund?

A refund is initiated by the merchant and processed through their normal payment flow. The customer agrees, the merchant pushes the money back, and no dispute fee is charged. A chargeback is initiated by the customer through their bank, bypasses the merchant entirely, and adds a dispute fee plus a count against the merchant's dispute rate. Refunds are always better than chargebacks for merchants.

### Can a merchant fight a chargeback?

Yes, through a process called representment. The merchant submits evidence to their acquirer arguing that the charge was valid. If the card network agrees, the funds return to the merchant. Win rates vary by reason code - well-prepared merchants win 30-50% of friendly fraud disputes but typically lose true fraud cases unless 3D Secure was used.

### What happens if a merchant has too many chargebacks?

Card networks enforce dispute rate thresholds (typically 0.9-1.5% of transactions). Merchants crossing these thresholds are enrolled in monitoring programs with fines, required remediation plans, and rolling reserves on their merchant account. Sustained high dispute rates can result in merchant account termination, after which the merchant cannot process cards at all without finding a new (more expensive) processor.

## Conclusion

Chargebacks are a structural feature of the card payment system, not an avoidable accident. Every business that takes cards will receive disputes, and the goal is to keep dispute rates low enough that they do not threaten the merchant account, win the disputes worth fighting, and absorb the rest as a cost of doing business.

The cheapest dispute is the one that never happens, so prevention pays back faster than response. Fix billing descriptors, send renewal reminders, implement 3D Secure, and build cancellation flows that customers can actually find. For businesses that do not want to manage dispute infrastructure in-house, [Dodo Payments](https://dodopayments.com) handles the full chargeback lifecycle as part of the [Merchant of Record service](https://dodopayments.com/blogs/best-merchant-of-record-platforms), absorbing dispute fees and shielding the underlying business from acquirer-level dispute rate risk.

Read more in the [chargeback prevention guide for SaaS](https://dodopayments.com/blogs/chargeback-prevention-saas) or review [Dodo Payments pricing](https://dodopayments.com/pricing) to see the MoR service in context.
---
- [More Payments articles](https://dodopayments.com/blogs/category/payments)
- [All articles](https://dodopayments.com/blogs)