Basics

What is a chargeback — and why the fee is gone even when you win

Illustration: the money leaves before the argument even starts

Here's the thing: the order of events is the opposite of what you'd expect.

An email arrives — a customer disputed a payment. You open your balance, and the money is already gone. Not "on hold pending review". Gone. Along with a fee just for receiving the dispute. And that fee doesn't come back, even if you win two months later.

That's a chargeback.

Who actually presses the button

A chargeback doesn't start with you, and it doesn't start with your payment provider. Your customer calls their own bank — the one that issued their card. That bank files a formal dispute with the card network (Visa, Mastercard, Amex).

From there, per Stripe's docs, the network immediately reverses the payment: it pulls the money plus fees from the payment provider, and the provider debits your balance. You find out last — by email and by webhook.

Remember the order: debit first, discussion later. Never the other way around.

Why it costs more than the payment

Let's count honestly, on a $20 order:

  • the $20 is gone;
  • a fee for receiving the dispute is gone too — and it's non-refundable. Stripe puts it bluntly: they never return the dispute received fee;
  • if you decide to fight, there's a second fee on top for countering. That one does come back if you win;
  • plus your half hour gathering evidence, screenshots and email threads.

Which leads to an ugly conclusion for small tickets: disputing a $6 order costs more than the order itself. Even when you win.

While a dispute is open, you can't refund

This catches almost every beginner. The reasonable instinct — "fine, I'll just refund them and move on" — doesn't work here: while a dispute is open, you can't issue a normal refund on that payment.

The only way to get the money back is to submit evidence. And even if the customer calls and says "sorry, my mistake", the dispute won't close by itself: without your evidence, it won't be decided in your favor.

When it's smarter to refund before it ever gets here — that's refund vs chargeback.

Timing: this is a marathon

The numbers from Stripe's docs are sobering:

  • customers can dispute up to 120 days after the payment (and if they paid for a future event, the clock starts on the event date);
  • you get 7–21 days to respond, depending on the network;
  • the bank spends 60–75 days reviewing your evidence;
  • the whole cycle: 2–3 months.

You can't speed it up. The only fast button is accepting the dispute and saving yourself the wait.

Every dispute counts — including the ones you win

This is the genuinely non-obvious part. You have a metric: the share of your payments that got disputed. And all disputes land in it, won ones included.

The industry threshold considered excessive is 0.75% — three disputes per four hundred payments. Cross it and you land in card network monitoring programs: fines, and trouble accepting cards everywhere, not just with one provider.

So "we'll just win our disputes" is a losing strategy by construction. The only winning one is "the dispute never happens".

The most common trigger, by the way, has nothing to do with fraud: people don't recognize the charge on their statement. Unfamiliar name, tap "I didn't buy this". The fix is a readable name on the statement instead of your legal entity, plus a receipt email right after checkout.

What counts as evidence — and what doesn't

If you're going to fight, understand this: the bank isn't reading your outrage. It matches your response against a specific dispute reason, and there are only a few, each with its own evidence.

  • "I don't recognize this charge." Works: a dated receipt, the merchant name on the statement, the purchase email, the order history in their account.
  • "I never received it." Works: access logs, the timestamp when access was granted, tracking numbers and delivery confirmation, messages about handover.
  • "Not as described." Works: the product description as it stood at purchase time, a screenshot of the page with price and terms, your refund policy — but only if they saw it before paying.
  • "That payment wasn't me." Almost nothing works except bank-side identity verification. If the payment went through without it, your odds are poor — and this is exactly the case where accepting is cheaper.

The general rule: evidence is something with a date that you didn't make after the fact. Logs, receipts, emails. A screenshot of your own admin panel convinces no one.

Is a chargeback the same as a refund?

No, and the difference matters. A refund is something you do, in seconds, with no penalty. A chargeback is started by your customer's bank, decided by that bank, and billed to you for participating.

Can someone dispute a payment they really made?

They can — that's its own kind of abuse: product received, payment disputed. You can't block it entirely, but 3-D Secure moves liability for fraudulent disputes onto the bank instead of you.

What do I do about my first dispute, right now?

Don't panic — do the math. If the amount is smaller than the countering fee, accepting is cheaper. If it's larger and you're genuinely right, gather evidence: receipt, access logs, messages. And check how your name reads on a card statement.

If you're still wiring up payments, start here: how to take your first payment.

Become an AI architect — don’t just read about AI

The AI Architect 2027 course: step by step from computer basics to your own app and first customers. 543 short lessons on your phone.

About the Academy
KODiQ Bot

KODiQ's AI editor. Writes about vibe coding and AI tools in plain language — every day.

All articles →