CHARGEBACKS

Chargeback vs refund: which to use and when

A refund is a credit you choose to send; a chargeback is a reversal the bank forces. What each costs, how they collide on subscriptions, and which to use.

Published 13 min read

Chargeback vs refund: which to use and when

A refund is a credit you decide to send back. A chargeback is a reversal the customer’s bank makes without asking you first. Both can return the same money to the customer, but only the chargeback adds a dispute fee, a deadline, an evidence file and a mark on your dispute ratios. While the customer can still reach you, a justified refund is almost always the cheaper way to settle a complaint. Once a dispute is open, the refund route is usually closed, and the question becomes whether to accept or contest it.

So the useful question is not which option returns the money. It is whether you still control the outcome, what letting the complaint escalate would cost, and whether a credit for the same payment is already on its way. This guide covers the difference step by step, what each route costs, where refunds and chargebacks collide on subscriptions, and how to pick the right one. The rules come from Stripe, Braintree, Adyen and Visa’s own documentation, listed in the sources.

What is the difference between a chargeback and a refund?

Refund Chargeback
Who starts it You, after a request, a return or your refund policy The cardholder, through their bank
Who controls the amount and timing You decide the amount and when to send it; banks decide when it shows The issuing bank and the card network rules
Dispute fee None Yes, set by your processor (Stripe: $15 in the US)
Counts toward dispute ratios No Yes, from the day it is opened
How long it takes About 5 to 10 business days to show on Stripe Usually 2 to 3 months on Stripe, from opening to decision
Can you contest it? Not applicable Yes, with evidence before the deadline

Approving a refund is a decision. Receiving a chargeback opens a case you have to manage. On Stripe, when a cardholder opens a dispute, the disputed amount and a dispute fee are taken from your balance straight away, and “you can’t issue a refund outside the dispute process while the dispute is open.”

Where you still have control

Before a dispute, you can look into the complaint, explain the charge, fix a billing error or approve a refund. You can also agree on a partial amount instead of treating every complaint as all or nothing.

That control has limits. You decide when to send an approved refund, but not when the customer’s bank shows it. Stripe says the customer sees the credit “approximately 5-10 business days later, depending upon the bank.” So support should keep three things apart: the refund being approved, being submitted, and arriving on the customer’s statement.

A refund also does not mean giving in to every complaint. A customer may have forgotten a renewal, missed a receipt or used the service they now dispute. The right first answer is an explanation backed by your records, followed by a refund when the complaint is fair.

How does each process work, step by step?

The refund path:

  1. The customer asks. They want money back, return something or fall under your refund policy.
  2. You check and approve. Look at the purchase, the policy and the complaint, and check whether a dispute or an earlier credit already exists on that payment.
  3. You submit the refund. The processor sends it to the customer’s bank, and the customer sees it once the bank posts it.

A support agent saying “your refund is approved” does not prove the refund went through. Keep the approval message and the processor’s confirmation as two separate records.

The chargeback path:

  1. The cardholder contacts their bank. The bank does not need your agreement to start the dispute.
  2. The money moves. On Stripe, the card network debits Stripe, and Stripe debits your balance for the disputed amount plus the dispute fee.
  3. You accept or contest. Stripe gives you usually 7 to 21 days to respond, depending on the card network. A response can include invoices, usage logs, cancellation records and customer emails.
  4. The issuer decides. After you submit evidence, the issuer usually has 60 to 75 days to decide. Submitting evidence starts a review; it does not guarantee you get the money back.

The customer’s experience differs too. With a refund, they keep talking to you. With a chargeback, they talk to their bank, and you may lose the chance to explain or repair the relationship.

What does each option cost beyond the refunded amount?

Cost Refund Chargeback
The payment The amount you choose to return The disputed amount, taken at once; you only get it back if you win
Fees No dispute fee Stripe in the US: $15 dispute received fee, plus $15 if you contest (returned if you win)
Team time Usually small Gathering evidence and watching the deadline
Service already delivered Possible loss The same loss, plus the fee and the time

The refunded amount is not the full cost of either route. A refund can leave you with the cost of a service already delivered. A chargeback adds a fee and work on top of the same loss. Stripe says that, unless your contract says otherwise, “we never return the dispute received fee”, even when you win. On Braintree, the chargeback fee is set by the processing bank and appears on your statement.

To compare the routes for your own case, use your real invoice amount and fees, not an industry average:

  • Refund now: the amount credited, any processing fee your contract keeps, and the time to approve and reconcile it.
  • Accept the chargeback: the disputed amount, the dispute fee and the time spent.
  • Contest and win: the amount recovered, minus the fees you don’t get back and the time spent on the response.

Don’t count already-delivered service twice: its cost belongs to the sale, not to the dispute. And don’t assume a won case is free. For a full breakdown by processor, see what a chargeback really costs.

After a dispute opens, the fee is already spent. It should not push you into an uneconomic contest. If the evidence is thin and the amount is small next to the work, accepting can cost less than fighting. If the records are complete and the claim is clearly wrong, a response makes sense. Refund or fight gives a decision table for that moment.

Why do chargebacks weigh more than refunds?

A high refund count can point to a product or billing problem, but it is not what card networks monitor. Their dispute and fraud monitoring programs count disputes, and a refund issued before a dispute does not create one.

Stripe shows two figures for this. Dispute activity is disputes divided by successful payments, by dispute date; it is the calculation the card networks’ monitoring programs use. Dispute rate links each dispute to the date of the charge, which is better for spotting fraud patterns but keeps changing, because cardholders can dispute “up to 120 days after a payment was made (and sometimes even later).”

Two consequences for your process:

  • A won case still counts. Stripe says a new dispute raises your dispute rate with that card network, and dispute activity counts disputes on the day they are opened. Winning gets the money back; the dispute is still counted.
  • Prevention and recovery are different jobs. A team measured only on money recovered will spend its time on rebuttals while billing complaints pile up. Track refund reasons next to dispute reasons, and fix the workflow behind the most frequent ones.

The thresholds and programs that apply to your account depend on the network and your processor; see chargeback ratio monitoring programs for how they work.

Some disputes start as an inquiry, where the issuer asks for clarification before a chargeback. Stripe says American Express and Discover use inquiries most often, while Mastercard and Visa no longer use them. On Stripe, you can close an inquiry without a dispute fee by giving satisfactory evidence or by issuing a full refund. “Inquiries on partially refunded charges can still escalate to a chargeback.”

Where do refunds and chargebacks collide on subscriptions?

A subscriber cancels an annual plan, support approves a refund, and the customer checks their account before the credit appears. They call their bank, convinced you didn’t follow through. Now the same payment has a refund and a dispute moving through two separate channels.

Visa has a dispute condition for exactly this: 13.6 Credit Not Processed. Its guide for merchants says these disputes “usually arise from delays, missed processing, or misunderstandings about refund timing, rather than disagreement about the original purchase itself.” It lists cases such as a refund “promised or confirmed, but was not processed” and “a credit was delayed beyond the timeframe disclosed to the cardholder.”

The double-payment risk is real. Braintree warns that customers sometimes ask you for a refund and open a chargeback at the same time, and that “you could lose double the amount of the original transaction if you refund a transaction that is also charged back.”

When a refund and a chargeback hit the same payment
  1. 01 Check the refund's status Pending, sent or failed, with its reference
  2. 02 Don't send a second credit On Stripe, no refund outside the dispute while it is open
  3. 03 Contest with proof of the refund Date, amount, ARN and a link to the disputed payment
  4. 04 Tell the customer what you can verify A reference number beats a promise

Keep one timeline per subscription

Keep the records together instead of asking support, billing and finance to rebuild the story separately:

  • Cancellation requested and recorded: the customer’s request and your system’s confirmation.
  • Access ended: when it ended and whether the customer kept using the service.
  • The last renewal charge: the payment, the invoice and the period it covered.
  • Refund approved and submitted: both the approval and the processor’s confirmation.
  • Refund status and any dispute: whether the credit was sent, and the dispute linked to the original payment.

Cancelling, ending access, a prorated refund and reversing a renewal are separate events. Treating every complaint after a cancellation as fraud damages trust; crediting every disputed charge automatically rewards abuse.

What to do when both happen

Don’t send a second credit. On Stripe, if a customer disputes a charge while its refund is pending, the refund fails with charge_for_pending_refund_disputed, and Stripe “recommends accepting or challenging the dispute instead of refunding to avoid duplicate reimbursements to the customer.”

Contest with proof of the refund. Braintree says that if you are notified of a chargeback for a refunded transaction, “we strongly encourage you to dispute it.” Adyen can defend some of these automatically, for example when more than 90 percent of the captured amount was refunded before the chargeback. Visa asks for the date and amount of the refund, the transaction identifier or acquirer reference number (ARN), and a record that clearly links the refund to the disputed payment.

Give the customer a reference. When a customer says they haven’t seen a refund, a reference number from the processor is more convincing than a promise. Stripe says the ARN can take up to 7 business days to arrive from its banking partners, and is not available when the refund was processed as a reversal.

After an early fraud warning, decide fast. An early fraud warning means the issuer has flagged the payment as possible fraud, before any dispute. Stripe says that, without a refund, “about 40% of Visa and Mastercard EFWs become fraud disputes”, and that refunding is “most worthwhile on charges at or below your dispute fee.” A refund does not remove the fraud warning itself. See Stripe early fraud warnings for the trade-offs. In NoChurn, a flagged payment can be refunded in one click, with the subscription stopped if you choose, before it turns into a dispute.

If you use Visa’s Rapid Dispute Resolution (RDR), Visa’s guide says not to issue a separate refund after accepting an RDR request unless your acquirer advises it: the case already moves the money.

Which should you use in each situation?

Situation Better route Why
The customer asks for money back within your policy Refund promptly Settles a fair request before it becomes a dispute
The customer disputes a charge you can show is genuine Contest with relevant evidence A valid charge shouldn’t be given up only because it was disputed
A refund is approved but not yet credited Check its status before doing anything else Avoids a duplicate credit and conflicting records
An early fraud warning arrives Refund before a dispute is filed, where it makes sense Can avoid the dispute and its fee
A dispute is already open on a payment you refunded Contest with the refund proof Refunding again could pay the customer twice

A genuine purchase is not automatically a winnable chargeback. The customer may have authorized the payment and still have a fair complaint about a cancellation or a refund that never arrived. Answer the actual claim, not only with proof of purchase.

Apply a mixed-case test

Say a customer cancels mid-cycle and disputes the last renewal. Neither a full refund nor a full contest is automatically right.

  1. Check what was used. The period billed, the access given and any use after the cancellation.
  2. Check when the cancellation took effect under your terms. A support request and a processed cancellation can have different timestamps.
  3. Check existing credits. Look at the refund’s status before approving anything else.
  4. Work out what the customer is owed. Where a partial refund is due, issue it through your processor’s normal process, and contest only the part your records support.

Defend the amount your records justify, not simply the amount you invoiced. Usage is evidence, but it does not replace your cancellation terms or the customer’s rights.

Match the process to the payment method

Card refunds and card chargebacks follow card network rules. Bank debits work differently: Stripe warns that for bank debits such as SEPA Direct Debit, Bacs Direct Debit, ACH Direct Debit and AU BECS Direct Debit, refunding while the customer’s bank also opens a dispute can mean “the customer might receive two credits for the same transaction.” Check the refund guidelines for each method before refunding a payment that may already be disputed.

If you sell through a merchant of record such as Paddle, Lemon Squeezy or Polar, refunds go through the platform and it answers disputes itself, under its own rules. On billing tools that run on top of a gateway, such as Chargebee or Recurly, the refund and the dispute still go through the gateway, so check its records too.

How do you set a refund policy that prevents disputes?

Visa’s guidance for Credit Not Processed disputes gives the basics: disclose refund eligibility and processing times before purchase, process refunds within the time you gave, avoid confirming a refund unless it is really being processed, and tell the customer when it should appear. “Promising a credit creates an expectation that it will be processed as disclosed.”

In practice:

  1. Write down who approves refunds, and separate approval, submission and arrival in what support tells customers.
  2. Give every dispute a named owner, with a backup when that person is away.
  3. Prepare evidence templates around the most common claims: invoices, usage records, cancellation history and customer messages.
  4. Record every refund against its original payment, with its status, so support can see when a refund and a dispute overlap.
  5. Review disputes each month against your processor’s requirements, next to the reasons customers asked for refunds.

To measure the process, track how many complaints you resolved before a dispute, your dispute activity, the share of eligible disputes you contested, your win rate on contested cases, the money recovered and the time spent per case. Use the right base for each: win rate on cases you contested, not on all disputes. A high win rate can hide weak recovery if eligible cases go unanswered.

A good first step: pull the last 90 days of refunds and disputes, count the complaints settled before a dispute, and look closely at every case where a promised refund and a dispute hit the same payment.

How NoChurn helps

NoChurn picks up each dispute from your payment provider with its reason, amount and deadline, builds the evidence file from invoices, usage, emails, cancel-flow history and support conversations, and drafts a reply. A person reviews it and submits it in one click before the deadline; nothing is sent automatically unless you turn on auto-submit. Pricing has no commission on recovered money. See chargebacks.

FAQ

Is a refund better than a chargeback?

For the merchant, usually yes, when the complaint is fair. A refund has no dispute fee, does not count toward card network dispute monitoring and keeps you in contact with the customer. A chargeback takes the money at once, adds a fee and counts toward your dispute figures even if you win.

Can you refund a payment after a chargeback is filed?

Usually not outside the dispute. On Stripe, you can’t issue a refund outside the dispute process while the dispute is open. Accept the dispute if the customer is owed the money, or contest it if you already refunded or the charge was valid.

What happens if a customer gets a refund and also files a chargeback?

You risk paying twice. Contest the chargeback with proof of the refund: its date and amount, the transaction identifier or ARN, and a record linking it to the disputed payment. Braintree strongly encourages disputing a chargeback on a refunded transaction.

How long does a refund take compared with a chargeback?

On Stripe, a refund usually shows on the customer’s statement about 5 to 10 business days after you send it. A dispute usually takes 2 to 3 months from opening to the final decision.

Does a refund count toward my chargeback ratio?

No. Card network monitoring programs count disputes, not refunds. A refund issued before a dispute does not create one, but once a dispute is filed, it counts from the day it is opened.

Sources

All accessed 21 November 2026.

PROMPT

Read https://www.nochurn.sh/llms.txt,
then follow https://docs.nochurn.sh/quickstart/
to add NoChurn to this app. Use a test key
(nc_test_…) until I say we go live.

Stop leaking revenue.

  • Free until $300 MRR
  • No card needed
  • Live in 10 minutes
  • No commission