What is a chargeback?

A chargeback is a forced reversal of a card payment, initiated by the cardholder through their issuing bank rather than by asking the merchant. The bank debits the transaction from the merchant, charges a fee, and credits the cardholder while the case is examined. The merchant can contest it with evidence, but does not control the timing or the amount.

What is the difference between a chargeback and a refund?

A refund is the merchant returning money voluntarily, at a time and in an amount it controls, with no fee and no consequence beyond the lost sale. A chargeback is the cardholder's bank taking the money back. It adds a fee, counts against the merchant's dispute ratio, and can trigger network monitoring programmes, reserves and delayed settlement.

How long does a chargeback take?

From filing to resolution it typically runs weeks to months, because each stage has its own deadline: the merchant's response window, the issuer's review, and any escalation to pre-arbitration or arbitration. The merchant's effective deadline is set by its processor and is earlier than the network's, since the processor needs time to file the response.

What is a good chargeback rate?

There is no universal figure worth quoting, because network monitoring programmes combine an absolute dispute count with a ratio and the thresholds are revised periodically. The operationally useful target is well below whatever the current programme trigger is, since acquirers impose reserves and delayed settlement on their own judgement long before a network programme engages.

Do I get the chargeback fee back if I win?

Usually not. Winning a representment returns the transaction amount; the fee is generally charged for handling the dispute regardless of outcome, and most network monitoring programmes still count the dispute from the date it was filed. This is why prevention outperforms contesting even when your representment win rate is good.

How do you reduce chargebacks on a subscription business?

Start with the billing descriptor, since most subscription disputes are cardholders failing to recognise a charge rather than fraud. Then send a reminder before each renewal, make cancellation work in one attempt without a login wall, and answer support quickly. Those four changes remove more disputes than any representment strategy, and each applies to every future transaction.

Payments

Chargeback

A chargeback is a forced reversal of a card payment initiated by the cardholder through their issuing bank rather than through the merchant.

Beyond the lost revenue and the fee, chargebacks count against a merchant's dispute ratio, and sustained ratios above network thresholds bring monitoring programmes, higher costs and eventually loss of processing.

For subscription businesses the most common cause is not fraud but recognition: a renewal the customer forgot they had authorized. Clear billing descriptors, renewal reminders before the charge, and a cancellation path that is genuinely easier than a dispute all reduce the rate more than any representment strategy.

What happens mechanically when a chargeback is filed

A cardholder contacts their issuing bank and states a claim. The issuer decides whether the claim maps to a dispute condition it is entitled to raise, selects a reason code, and files. From that point the process runs on the network's rails and the merchant is a respondent rather than a participant.

The funds move first and the argument happens afterwards. The transaction amount is debited from the merchant, a fee is charged by the acquirer, and the cardholder is typically credited — often provisionally — while the case is open. This is the structural difference from a refund and it is the whole reason a chargeback is expensive: a refund is a decision the merchant makes at a time of its choosing, and a chargeback is a decision made about the merchant, at a time chosen by someone else, in an amount they set.

The merchant then either accepts the reversal or represents the transaction with evidence. If the issuer accepts the representment, funds return. If the cardholder maintains the claim, the case escalates to pre-arbitration and then to arbitration, where the losing side pays a network filing fee that on a typical direct-to-consumer order is larger than the order.

One detail is worth internalising early: the dispute is counted from the moment it is filed. Winning a representment returns the money. In most network monitoring programmes it does not remove the count.

The cost is not the transaction, and the ratio is not the ratio you think

Consider an example store processing 12,000 card transactions a month and receiving 90 disputes. That is a dispute ratio of 0.75 per cent. At an example chargeback fee of 15 dollars, the fees alone are 1,350 dollars, before a single reversed order or a single unit of shipped inventory is counted.

The rest of the cost arrives in layers. The revenue reverses but the goods do not come back. Staff time goes into evidence. Acquirers respond to sustained ratios with rolling reserves and delayed settlement, which is a working-capital cost rather than a fee. And the networks operate monitoring programmes that impose escalating obligations, monthly charges and, at the far end, removal from the network.

Those programme thresholds combine an absolute dispute count with a ratio, both measured monthly, and the networks revise them — one of them was restructured recently enough that most published figures are wrong. Look the current thresholds up in the network's own programme documentation rather than trusting a number in an article, this one included.

The denominator deserves the same suspicion. The networks do not agree on it: at least one programme measures this month's disputes against the previous month's transaction count. For a business with seasonal or declining volume that arithmetic inflates the ratio precisely when volume falls, and a merchant can enter a monitoring programme in a month where nothing about its disputes changed.

The four reason-code families, and what each really means on a DTC book

Every network sorts disputes into the same four families, whatever the numbering. Knowing which family a dispute belongs to tells you both whether it is worth contesting and, more usefully, which part of your operation produced it.

The families are not equally distributed on a direct-to-consumer book, and they are not distributed the way people assume. Fraud is the family everyone plans for and consumer disputes are the family that actually arrives, particularly on anything recurring.

Family	The cardholder's claim	Common real cause on a DTC book	What removes it
Fraud	I did not authorise this	Genuine card-not-present fraud, or a family member using the card	Fraud screening, 3-D Secure on risky orders, delivery to verified addresses
Authorisation	There was no valid approval	Charging after an authorisation expired, or on a declined card	Reauthorise rather than capture stale approvals; stop retrying hard declines
Processing error	The amount, currency or count is wrong	Duplicate capture, a currency shown differently from the one billed	Idempotent charge submission; showing the settlement currency at checkout
Consumer dispute	I did not get it, or it was not as described, or I cancelled	Non-delivery, a renewal the customer did not expect, a cancellation that did not take effect	Tracked delivery, renewal reminders, a cancellation path that works first time

Dispute families, the usual underlying cause, and the fix that removes them

Why most subscription chargebacks are recognition, not fraud

A recurring charge arrives on a statement weeks or months after the decision to buy it. The cardholder is reading a short string of text next to an amount, with no product image, no order number and no memory of the purchase. If that string does not obviously name the thing they bought, the bank is one tap away and filing a dispute is faster than searching their inbox.

The billing descriptor is therefore not a compliance field, it is the first line of dispute prevention. It should carry the brand the customer believes they bought from, not the registered legal entity, and where the processor supports a dynamic component it should carry something that identifies the order or the product. A descriptor naming a holding company generates disputes indefinitely and no amount of representment work compensates for it.

The rest of the recognition problem is timing and reachability. A reminder sent before a renewal converts an unexpected charge into an expected one and gives the customer somewhere to go other than their bank. A cancellation flow that completes in one attempt, without a login wall or a retention gauntlet, is cheaper than the dispute it replaces — a cancelled subscriber costs you the future revenue, and a disputing subscriber costs you the future revenue plus the charge plus the fee plus a count against the ratio.

This is also why support responsiveness is a payments metric. A customer who emails and receives an answer within a day usually does not file. A customer who emails and hears nothing files, and the dispute record will say fraud.

Preventing costs less than contesting, at every step

The interventions form a ladder, and each step down it is more expensive and returns less than the one above. Almost every merchant with a dispute problem is investing at the bottom.

The reason the ordering holds is that the top of the ladder acts on every future transaction while the bottom acts on one dispute that has already happened. A descriptor change made once alters how every subsequent statement line reads; a representment recovers at most one order and leaves the count on the ratio.

A descriptor the customer recognises. Costs nothing, applies to every future transaction, and removes the largest single category of subscription disputes.
Pre-renewal notification. One message before the charge, containing the amount, the date and a cancellation link that works without a login.
A cancellation path that is genuinely easier than calling the bank. If it is not, the bank is the cancellation path, and it charges you a fee for it.
Order and transaction detail delivered to the issuer, through the network services that surface merchant information inside banking apps at the moment the cardholder is looking at the charge.
Dispute-prevention alerts, which notify the merchant of a claim before it becomes a chargeback and allow a refund instead. It costs the sale and an alert fee, and it avoids the fee and the ratio count.
Representment, last. It is worth doing where the evidence is strong, and it is the only step on this list that cannot prevent anything.

Frequently asked questions

What is a chargeback?: A chargeback is a forced reversal of a card payment, initiated by the cardholder through their issuing bank rather than by asking the merchant. The bank debits the transaction from the merchant, charges a fee, and credits the cardholder while the case is examined. The merchant can contest it with evidence, but does not control the timing or the amount.
What is the difference between a chargeback and a refund?: A refund is the merchant returning money voluntarily, at a time and in an amount it controls, with no fee and no consequence beyond the lost sale. A chargeback is the cardholder's bank taking the money back. It adds a fee, counts against the merchant's dispute ratio, and can trigger network monitoring programmes, reserves and delayed settlement.
How long does a chargeback take?: From filing to resolution it typically runs weeks to months, because each stage has its own deadline: the merchant's response window, the issuer's review, and any escalation to pre-arbitration or arbitration. The merchant's effective deadline is set by its processor and is earlier than the network's, since the processor needs time to file the response.
What is a good chargeback rate?: There is no universal figure worth quoting, because network monitoring programmes combine an absolute dispute count with a ratio and the thresholds are revised periodically. The operationally useful target is well below whatever the current programme trigger is, since acquirers impose reserves and delayed settlement on their own judgement long before a network programme engages.
Do I get the chargeback fee back if I win?: Usually not. Winning a representment returns the transaction amount; the fee is generally charged for handling the dispute regardless of outcome, and most network monitoring programmes still count the dispute from the date it was filed. This is why prevention outperforms contesting even when your representment win rate is good.
How do you reduce chargebacks on a subscription business?: Start with the billing descriptor, since most subscription disputes are cardholders failing to recognise a charge rather than fraud. Then send a reminder before each renewal, make cancellation work in one attempt without a login wall, and answer support quickly. Those four changes remove more disputes than any representment strategy, and each applies to every future transaction.

Related terms

Payments

Chargeback

A chargeback is a forced reversal of a card payment initiated by the cardholder through their issuing bank rather than through the merchant.

What happens mechanically when a chargeback is filed

The cost is not the transaction, and the ratio is not the ratio you think

The four reason-code families, and what each really means on a DTC book

Family	The cardholder's claim	Common real cause on a DTC book	What removes it
Fraud	I did not authorise this	Genuine card-not-present fraud, or a family member using the card	Fraud screening, 3-D Secure on risky orders, delivery to verified addresses
Authorisation	There was no valid approval	Charging after an authorisation expired, or on a declined card	Reauthorise rather than capture stale approvals; stop retrying hard declines
Processing error	The amount, currency or count is wrong	Duplicate capture, a currency shown differently from the one billed	Idempotent charge submission; showing the settlement currency at checkout
Consumer dispute	I did not get it, or it was not as described, or I cancelled	Non-delivery, a renewal the customer did not expect, a cancellation that did not take effect	Tracked delivery, renewal reminders, a cancellation path that works first time

Dispute families, the usual underlying cause, and the fix that removes them

Why most subscription chargebacks are recognition, not fraud

Preventing costs less than contesting, at every step

The interventions form a ladder, and each step down it is more expensive and returns less than the one above. Almost every merchant with a dispute problem is investing at the bottom.

A descriptor the customer recognises. Costs nothing, applies to every future transaction, and removes the largest single category of subscription disputes.
Pre-renewal notification. One message before the charge, containing the amount, the date and a cancellation link that works without a login.
A cancellation path that is genuinely easier than calling the bank. If it is not, the bank is the cancellation path, and it charges you a fee for it.
Order and transaction detail delivered to the issuer, through the network services that surface merchant information inside banking apps at the moment the cardholder is looking at the charge.
Dispute-prevention alerts, which notify the merchant of a claim before it becomes a chargeback and allow a refund instead. It costs the sale and an alert fee, and it avoids the fee and the ratio count.
Representment, last. It is worth doing where the evidence is strong, and it is the only step on this list that cannot prevent anything.

Frequently asked questions

What is a chargeback?: A chargeback is a forced reversal of a card payment, initiated by the cardholder through their issuing bank rather than by asking the merchant. The bank debits the transaction from the merchant, charges a fee, and credits the cardholder while the case is examined. The merchant can contest it with evidence, but does not control the timing or the amount.
What is the difference between a chargeback and a refund?: A refund is the merchant returning money voluntarily, at a time and in an amount it controls, with no fee and no consequence beyond the lost sale. A chargeback is the cardholder's bank taking the money back. It adds a fee, counts against the merchant's dispute ratio, and can trigger network monitoring programmes, reserves and delayed settlement.
How long does a chargeback take?: From filing to resolution it typically runs weeks to months, because each stage has its own deadline: the merchant's response window, the issuer's review, and any escalation to pre-arbitration or arbitration. The merchant's effective deadline is set by its processor and is earlier than the network's, since the processor needs time to file the response.
What is a good chargeback rate?: There is no universal figure worth quoting, because network monitoring programmes combine an absolute dispute count with a ratio and the thresholds are revised periodically. The operationally useful target is well below whatever the current programme trigger is, since acquirers impose reserves and delayed settlement on their own judgement long before a network programme engages.
Do I get the chargeback fee back if I win?: Usually not. Winning a representment returns the transaction amount; the fee is generally charged for handling the dispute regardless of outcome, and most network monitoring programmes still count the dispute from the date it was filed. This is why prevention outperforms contesting even when your representment win rate is good.
How do you reduce chargebacks on a subscription business?: Start with the billing descriptor, since most subscription disputes are cardholders failing to recognise a charge rather than fraud. Then send a reminder before each renewal, make cancellation work in one attempt without a login wall, and answer support quickly. Those four changes remove more disputes than any representment strategy, and each applies to every future transaction.