CHARGEBACKS

How do chargebacks work? A step-by-step guide

How a chargeback works, step by step: who holds the money, the deadlines that decide the case, which evidence answers which reason, and how to prevent it.

Published 13 min read

How do chargebacks work? A step-by-step guide

It’s a Tuesday morning and your payments dashboard shows a line you haven’t seen before: a $49 monthly charge marked disputed, with a reason code, a deadline, and a note that the amount has already been pulled back. You would have refunded it in a second if the customer had asked. Nobody asked.

That’s the moment most subscription businesses start asking how chargebacks work, and most explanations answer the wrong question. They cover fraud screening. They rarely explain where the money sits while the case is open, how short your response window really is, or which records decide the outcome.

What follows is the sequence a payments specialist would walk a new client through: who holds the money at each stage, what evidence answers which claim, and why a chargeback is a documentation contest that begins after the reversal.

What is a chargeback, and how is it different from a refund?

A chargeback is a card dispute the cardholder opens with their own bank, and it can reverse a payment without the merchant agreeing to anything. That one fact explains most of the confusion.

A refund is a return to the shop. The customer brings back a faulty kettle, explains the problem, and the shopkeeper decides whether to refund, replace, or refuse. A chargeback is a call to the referee. Play stops mid-game, both sides are asked what happened, and someone who has never met either of you makes the call.

Several parties sit in that chain. The cardholder is your customer. The issuing bank holds their card account, takes the complaint, and decides the outcome. The acquiring bank processes your payments and passes the dispute down to you. The card network, Visa or Mastercard, carries the messages between them and sets the rules both banks follow.

Control is what separates the two processes. You don’t choose to return the money, the funds can leave your account before anyone asks for your side, and the decision belongs to the issuer rather than to you. It’s also not only about stolen cards. Customers dispute services they never received, goods that arrived damaged, charges that appeared twice, and renewals that continued after they cancelled.

A chargeback is a reversal followed by a documentation contest. Your job is to make the record speak before the decision gets made.

How does a chargeback move from the customer to you?

The clearest way to see how chargebacks work is to follow one disputed charge through the network. Take a $49 subscription billed on 1 April and disputed on 9 April. Every stage has someone who acts, and something you should be doing while it happens.

Stage Who acts What happens Merchant action
1. Customer disputes Cardholder Claim filed with the issuing bank Watch for the dispute notice and note the deadline
2. Issuer review Issuing bank Claim reviewed; transaction sent back through the network Note the reason code and response window
3. Funds debited Acquirer or payment provider Disputed amount and a dispute fee debited from the merchant Plan for the cash impact
4. Accept or contest Merchant Accept the loss or submit evidence Decide before the deadline
5. Evidence forwarded Acquirer and card network Evidence sent to the issuer Confirm the submission was accepted
6. Final decision Issuing bank Chargeback stands or is reversed Record the outcome and close the case

Visa describes its dispute lifecycle as a structured process “by defining stages, responsibilities, and timeframes”. The issuer reviews the customer’s claim and, if it meets the criteria, sends the transaction back through the network to your acquirer. You then either accept it or submit evidence inside the response window: invoices, delivery records, usage logs, refund policies, customer communications, proof of authorization.

Where does the money sit at each stage?

Money moves before argument. On Stripe, for example, the provider “debits the disputed amount, plus a dispute fee” from your balance when the chargeback is created. Nothing has been decided at that stage. You’re out the amount plus the fee, and the case is now yours to win back.

The clock is slow. Stripe says the full dispute lifecycle “can take 2-3 months to complete”, and that once you submit evidence, the issuer usually has 60 to 75 days to decide, depending on the card network. For a subscription business, revenue, fees and the customer relationship all stay unresolved after the debit. The better your transaction-level timeline, covering authorization, accepted billing terms, service access, cancellation requests, refunds and prior undisputed payments, the faster you can answer when the notice lands.

In recurring cases, the question the issuer is weighing is narrower than merchants expect: can you show valid authorization, clear renewal terms, continued delivery of the service, and a cancellation process that was available and honored?

Which two deadlines decide the case?

Two clocks run at once, and only one of them is yours.

The cardholder’s clock is generous. Stripe notes that card networks typically allow cardholders to open a dispute within 120 days of the original payment, and longer in some situations. Your clock is short: Stripe puts the response window at usually 7 to 21 days, depending on the network, and your acquirer may set its own cut-off. Visa’s dispute guide is blunt about it: if you or your acquirer miss the response window, “the case may be automatically lost even if your evidence is strong”. Chargeback time limits explains which windows apply to each network and what to do when a notice arrives late.

There’s a second problem most merchants discover too late: the deadline to gather evidence is the same deadline. You can’t assemble three months of support history in the final 48 hours with any confidence.

Which habit saves the most cases?

Write the response deadline on the dispute the day you open it, and treat the disputed amount as at risk until the final decision arrives rather than as money you’ll get back. Then collect the record while the customer’s timeline is still fresh: the authorization, the terms accepted at signup, the logins, the cancellation history, the emails.

Which evidence answers which dispute reason?

Fraud is only one category. Every “item not received”, “not as described” and “still billing me after I cancelled” sits outside it, and in those cases the customer usually recognizes your name and has a complaint about the service itself. Visa groups its reasons into four categories: fraud, authorization, processing errors and consumer disputes, each with its own conditions.

That changes what a response has to do. By the time a dispute reaches you, the money has already left your account, and the reason code on the notice is the only question you get to answer. A reason code works like the prompt on an exam: a brilliant answer to a different question still earns zero marks.

Dispute reason What the customer claims Evidence that answers it
Unauthorized transaction The customer says they did not make the purchase Authorization record, device or IP consistency, verified account access, prior undisputed payments
Product or service not received The customer says nothing was delivered Delivery record, service access logs, usage timestamps after the purchase
Defective or not as described The customer says the item or service did not match the description Checkout description and terms, support exchanges, proof of fulfillment
Duplicate charge The customer says they were billed twice Transaction log showing separate charges and what each one paid for
Cancelled recurring charge The customer says they cancelled but were still billed Cancellation timestamp, confirmation sent, renewal notices, usage after the cancellation date

For each network’s codes, see chargeback reason codes for subscriptions or look up a code in the chargeback reason codes tool.

Why does the reason code decide which evidence matters?

Say a SaaS customer cancels on 3 March, gets billed on 1 April, and disputes it as a cancelled recurring charge. Your instinct is to send the whole account history. The decisive proof is narrower: the timestamp of the cancellation request, whether the cancellation completed or stalled halfway through your flow, whether a confirmation went out, what the renewal notice said, and whether anyone logged into the account after 3 March. If your records show the customer clicked cancel but never finished the final confirmation step, that detail can decide the case.

The same discipline applies to every reason code. A delivery dispute needs a delivery record, not a refund policy. A duplicate claim needs a transaction log that shows two distinct charges and what each one paid for.

Evidence answers the reason on the notice. Nothing else counts, however well organized it is.

So build a separate workflow for each reason family: unauthorized transactions, non-receipt, dissatisfaction, duplicate billing and cancelled recurring payments. One generic fraud response will lose the cases where the customer knows exactly who you are.

How do you build an evidence package that wins?

Representment is the contested version of the case. You submit a package through your acquirer, the issuer weighs it, and the chargeback is either reversed or upheld. Visa’s guide says it plainly: “Effective responses focus on relevance and clarity, not volume.”

What three jobs must every exhibit do?

Visa’s dispute guide says evidence is most effective when it does one or more of three things: it clearly links the transaction to the cardholder, it shows the cardholder took part in or benefited from the transaction, and it confirms the transaction was processed, fulfilled and billed according to agreed terms. A folder of screenshots does none of those on its own.

Three jobs every exhibit must do
  1. 01 Link the transaction to the cardholder Authorization record, payment credential, account and login details
  2. 02 Show they took part or benefited Logins, usage after the charge, device or IP consistency
  3. 03 Prove it was billed on agreed terms Accepted terms, renewal notice, invoice, cancellation log

Every exhibit also needs an anchor. Tie each one to the disputed charge using identifiers such as the last four digits or token of the payment credential, the transaction amount, and the customer’s account details. An invoice with no reference to the disputed transaction is a story about someone, possibly your customer.

For a digital subscription, the records that carry weight are login and usage timestamps, device and IP consistency, plan and renewal disclosures, consent or acceptance records, invoices, cancellation logs, refund history and support correspondence. For card-not-present fraud disputes, Visa’s Compelling Evidence 3.0 looks at at least two prior undisputed transactions on the same payment credential, with a consistent device ID or IP address and other identifiers such as the customer’s account or login. Send only the fields needed to prove identity, authorization, delivery and contractual compliance. Full card numbers and unrelated personal data don’t help the decision and create a data problem of their own.

Rule of thumb: if an exhibit doesn’t help link the cardholder, show their participation, or prove delivery on agreed terms, leave it out of the package.

How do you pull the package together?

  1. Confirm the exact dispute reason on the notice, including the reason code. Everything after this step depends on it.
  2. Pull the dated timeline for that specific customer, from first authorization through the charge in question.
  3. Match each exhibit to the disputed transaction, checking that the amount, date and credential reference line up.
  4. Write a short cover narrative that answers the reason directly, in the order the issuer will read it. Visa asks for evidence that is clear and easy to read, and in English or with an English translation.
  5. Submit before the deadline, then confirm your acquirer accepted the upload.

The failure mode to avoid is the general statement that the service was used and the customer was happy. It wins nothing, because it never addresses what the customer claimed. For a field-by-field version of this list, the SaaS chargeback evidence checklist goes through each document type.

What happens before and after the decision?

On some networks, an issuer may first send an inquiry (also called a retrieval request) asking for transaction details. This is not a chargeback yet. Stripe says inquiries are used mainly by American Express and Discover, and that Visa and Mastercard no longer use them; an inquiry answered with evidence or a full refund closes without a dispute fee. Answer it with the same care: a customer who didn’t recognize your billing descriptor may drop the complaint once someone explains the charge. The differences are covered in chargeback vs dispute vs retrieval request.

When a formal chargeback exists, the issuer has two paths after reviewing your package.

Outcome What happens to the money What you do next
Issuer reverses the chargeback The disputed amount returns to you Record the decision and keep the package intact
Issuer upholds the chargeback The debit stands and you absorb the amount Log the reason and fix the underlying gap

If the dispute cannot be resolved between the issuer and the acquirer, Visa’s lifecycle allows it to be escalated to Visa for a final ruling. A lost chargeback is not proof you did anything wrong. It can reflect an unresolved service issue, an issuer decision that weighed the customer’s account of events more heavily, or evidence that didn’t arrive or didn’t answer the reason code. Treat the outcome as information about the record you kept, not a verdict on your business.

Which routine is worth keeping after each decision?

  1. Record the outcome and reason code against the customer’s timeline while the case is fresh.
  2. Compare the reason against your submitted exhibits to find what was missing or misfiled.
  3. Fix the root cause, whether that’s ambiguous cancellation steps, a missing renewal notice, or a billing descriptor nobody recognizes.
  4. Decide in advance which future cases are worth contesting, so weak claims don’t consume the hours strong ones need.

The cheapest chargeback you’ll ever handle is the one that never becomes a chargeback, settled with one clear email and a refund.

How do you prevent disputes and organize your response?

Many disputes never give you a chance to fix anything: the customer goes straight to their bank. Visa’s guide lists the preventable causes it sees most: incorrect or missing transaction details, unclear return or refund policies, delays in delivery, and customers not recognizing the business name on their statement. It also says that if a customer reaches out to you directly, you should respond quickly and refund promptly when a refund is legitimate, which “can help avoid a formal dispute altogether”.

A customer who can’t identify your charge, can’t reach support, or can’t work out how to cancel will call the bank instead of the shop.

Why is prevention a billing clarity problem?

  • Use a recognizable billing descriptor. Put the trading name the customer knows on the statement, not a legal entity they’ve never seen.
  • Send a confirmation at purchase and a short notice before each renewal, so the amount and date are never a surprise.
  • Make cancelling visible. A customer hunting through account settings for a cancel button is a customer opening their banking app.
  • Offer the refund before escalation. On a small disputed amount, a refund costs less than a representment package and preserves the relationship.
  • Answer support fast. A quick reply can prevent the bank call that would otherwise follow.

The changes that cut disputes in subscription businesses, from cancellation paths to renewal notices, are set out in how to prevent subscription chargebacks.

A quick test: read your statement descriptor out loud, then ask whether a customer who signed up eight months ago would connect it to your product.

What does a weekly response routine look like?

  1. Set an alert for every network and acquirer deadline and check it weekly, not when a case feels urgent.
  2. Keep a dated record per customer covering authorization, accepted terms, service access, cancellations, refunds and communications.
  3. Sort open disputes by reason and run a separate workflow for each category.
  4. Decide which cases you’ll contest before the window closes, because weak cases eat the hours strong ones need.
  5. Give one person responsibility for reviewing every reply before it goes out.

You don’t need a large budget to run this routine. You need the deadline, the record and one reviewer. Open your payment dashboard today and write down the response deadline for every open dispute. It’s the one task here that costs nothing and protects the most.

How NoChurn helps

NoChurn picks up each dispute from your payment provider with its reason, amount and deadline, gathers the evidence it already has for that reason (invoices, usage after the charge, renewal reminders, cancel flow history, support conversations) and drafts a reply that a person reviews and submits in one click before the deadline. On an early fraud warning, you can refund in one click to avoid the dispute and its fee. See chargebacks.

Sources

All accessed 19 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