Resources

Chargebacks vs Declines: Two Different Problems

A declined payment and a chargeback can look similar in a dashboard — money you expected did not stay in your account — but they are opposite events. A decline means money never moved: the issuer refused the charge before it settled. A chargeback means money moved, settled, and was then pulled back out of your account by the issuer after the cardholder disputed it. That single difference — direction of movement — changes the timeline, the evidence, the fees, the relationship with the customer, and the playbook. Operators who treat them as one "billing problem" end up running recovery sequences on disputes and dispute responses on recoverable declines, doing both badly.

What a decline actually is

A decline happens at authorization, in the seconds when a charge is attempted. The issuer checks the card and account and answers no, with a reason category attached: insufficient funds, expired card, account closed, do not honor, and many more. No funds transfer. The subscription enters whatever dunning process you run, and in a large share of cases the story ends happily — a later retry succeeds or the customer updates a card and the relationship continues uninterrupted.

Key properties of a decline:

• Money movement: none. The charge simply does not happen.
• Timeline: instant. You know the moment it happens, with a decline code to work from.
• Customer relationship: usually intact. Most declined customers do not know anything went wrong until you tell them, and most did not intend to leave.
• Cost to you: a small authorization attempt fee and the operational cost of your recovery sequence.
• Correct playbook: recovery. Route by decline code, retry soft declines on a sensible schedule, request updated details for card problems, never retry hard declines.

The scale here matters. According to Recurly research, 20–40% of subscriber churn is involuntary, and declines are where that churn is born. Across 5.4M failed payments, insufficient funds alone is 40.6% of declines, according to Churnkey's published analysis of Stripe data. Declines are a volume business: many small, mostly fixable failures.

What a chargeback actually is

A chargeback starts after a successful charge. The cardholder contacts their issuer and disputes the transaction — claiming fraud, claiming they cancelled, claiming they do not recognize the charge, or claiming the product was not delivered. The issuer reverses the payment, debiting your merchant account for the amount plus a chargeback fee, and opens a dispute process with deadlines. You may submit evidence to contest it, the issuer decides, and the cardholder often keeps the product or service already consumed regardless of the outcome.

Key properties of a chargeback:

• Money movement: reversed. Funds you had settled are taken back, plus a fee, whether or not you ultimately win the dispute.
• Timeline: slow. Cardholders typically have weeks to months after a charge to file, and the dispute process itself runs on the issuer's schedule with strict evidence deadlines for you.
• Customer relationship: damaged or absent. The customer chose their bank over your support channel — or the cardholder is a fraudster and there was never a relationship at all.
• Cost to you: the reversed amount, the dispute fee, staff time on evidence, and a mark on your chargeback ratio, which networks monitor. Sustained high ratios bring penalties and can threaten processing itself.
• Correct playbook: dispute response and prevention. Cancel the associated subscription immediately, submit organized evidence within the deadline if the charge was legitimate, and fix the root causes feeding disputes.

Side by side

Dimension	Decline	Chargeback
When it happens	At authorization, before settlement	After settlement, when the cardholder disputes
Money movement	Never moves	Moves in, then is pulled back out
Who initiates	The issuer, automatically, at charge time	The cardholder, through their issuer
Signal you receive	Decline code immediately	Dispute notification, often days or weeks later
Customer intent	Usually none — most customers are unaware	Deliberate act, or genuine fraud
Fees	Small attempt fee	Dispute fee plus reversed revenue
Primary risk if mishandled	A saveable subscriber churns quietly	Ratio penalties, lost evidence deadlines, processing risk

Why the playbooks cannot be swapped

Running recovery on a chargeback is wasted and risky

When a chargeback lands, the underlying subscription should be cancelled immediately and the account flagged. Continuing to bill a card that has disputed you invites further disputes. Sending cheerful dunning emails to a cardholder who has told their bank the charge was unauthorized reads, at best, as disorganization. The work a chargeback demands is administrative and legalistic: preserve records, prove authorization and delivery, meet the deadline. If you want a useful boundary for what belongs to billing operations versus escalation, our overview of dunning vs collections frames where recovery work ends and harder processes begin.

Running dispute logic on a decline loses saveable customers

The mirror error is just as common in smaller teams: a failed payment gets treated as a hostile event. The subscription is cancelled on the spot, the customer gets a stern notice, and no retry or update path is offered. But the customer did nothing — their bank balance dipped two days before payday, or their bank reissued their card. Treating an accident like an accusation converts a recoverable billing event into genuine voluntary churn, because now the customer has a reason to leave. The full framework for this side of the house is the involuntary churn guide.

Where the two problems touch

Declines and chargebacks are distinct, but they share a border, and operators should know where it is.

• Unrecognized charges. A customer who does not recognize a legitimate renewal on their statement may dispute it rather than contact you. What began as a healthy paid renewal becomes a chargeback. Clear billing descriptors are the main preventive, which is why the descriptor problem gets its own article.
• Retry abuse. Repeatedly attempting a card after hard declines can push a cardholder from passive to angry, and angry cardholders dispute earlier successful charges too. Disciplined retry caps protect you on both sides of the border.
• Cancellation friction. A customer who tried to cancel, could not find the path, and then gets charged again often disputes instead of emailing. Easy cancellation is dispute prevention, paradoxically and reliably.
• Fraud screening. A spike in declines at signup — cards being tested — can precede a wave of chargebacks from the accounts that got through. Decline patterns at acquisition are an early-warning signal for dispute volume later.

Staffing the two problems differently

Decline recovery rewards systems: automated routing, timed retries, branded outreach, card-update pages, and a save offer at the end of the sequence. It runs continuously and improves incrementally — according to Churnkey's published analysis of Stripe data, each additional dunning email touch adds roughly 1–2 points of recovery, which is the kind of marginal gain a system compounds. Chargeback handling rewards process discipline: a named owner, a deadline calendar, an evidence checklist, and a monthly review of dispute reason codes to find the fixable root causes — descriptors, cancellation paths, renewal reminders — that generate disputes in the first place. One is an engine. The other is a hygiene practice. Budget and measure them separately, or the urgent noise of disputes will always eat the quiet, compounding value of recovery.

The bottom line

A decline is a charge that never happened, usually by accident, usually fixable, and worth a patient automated recovery sequence. A chargeback is a settled charge forcibly reversed at the cardholder's request, carrying fees, deadlines, and ratio risk, and worth an immediate cancellation plus a disciplined evidence process. Keep the money direction straight — never moved versus moved and taken back — and the right playbook follows every time.

Frequently asked questions

Is a chargeback worse than a decline?

For the merchant, yes, in almost every case. A decline costs a small attempt fee and a chance to recover the payment. A chargeback reverses revenue you already had, adds a dispute fee, consumes staff time on evidence, and counts against your chargeback ratio, which networks monitor with penalties for sustained high levels.

Can a declined payment turn into a chargeback?

Not directly — a decline means no money moved, so there is nothing to reverse. But the behaviors around declines connect the two: retrying hard declines aggressively or billing a customer who believes they cancelled can provoke disputes on other, successful charges from the same account.

Should I keep billing a customer who filed a chargeback?

No. Cancel the associated subscription immediately and flag the account. Continuing to charge a cardholder who has disputed a charge invites additional disputes and fees, and ongoing service after a chargeback also weakens your position in the dispute process.

Why did my customer dispute instead of contacting support?

The most common reasons are that they did not recognize the charge on their statement, could not find an easy cancellation path, or found their bank's dispute button faster than your support address. Clear billing descriptors, easy cancellation, and renewal reminders prevent a large share of these friendly disputes.

Do chargebacks count as churn?

Effectively yes — the subscription should be cancelled when a chargeback lands, so the customer is gone. But track chargebacks separately from churn in your reporting, because the causes, costs, and fixes are entirely different from both voluntary cancellations and decline-driven involuntary churn.