The short version

A chargeback is a charge reversal initiated not by you and not by your payment processor, but by the customer's own bank, at the customer's request. The customer tells their bank they have a problem with a charge; the bank pulls the money back from your account and returns it to the customer while it investigates. It is a consumer-protection mechanism baked into the card networks, and the first time it happens to you it feels less like protection and more like a mugging.

If you're new to accepting card payments, understanding chargebacks early saves a lot of confusion and a fair amount of money. The mechanics aren't complicated once you see the whole shape of them, and almost every panicked mistake merchants make comes from not understanding one of the parts. So let's walk through it slowly.

Why chargebacks exist at all

Credit cards became trustworthy to consumers partly because of chargebacks. The promise to a cardholder is simple: if a merchant cheats you, charges you twice, or never ships your order, you don't have to chase them — you call your bank and the bank reverses the charge. That guarantee is what made people comfortable handing card numbers to merchants they'd never met. So the system is deliberately tilted toward the cardholder, especially at the start of a dispute. That tilt isn't a bug. It's the whole reason cards work as a payment method.

Understanding this reframes the experience. A chargeback isn't the bank deciding you're a fraudster. It's the bank honoring a promise it made to its customer, provisionally, until it can find out what actually happened.

The cast of characters

Four parties matter, and confusing them is the source of most merchant frustration:

  • The cardholder — your customer. They start the dispute by contacting their bank.
  • The issuing bank — the bank that gave the customer their card. This is the party that decides the outcome. Not Stripe, not you, not your bank.
  • The acquirer / payment processor — Stripe, in this case. Stripe sits between you and the card networks, relays the dispute to you, and forwards your evidence back. Stripe is the messenger and the toolkit, not the judge.
  • The card network — Visa, Mastercard, American Express, Discover. They set the rules everyone plays by, including the reason codes and the deadlines.

When a dispute goes against you, it's the issuing bank that ruled, applying the card network's rules, with Stripe simply carrying the messages. Merchants who think Stripe decided their case are aiming their frustration at the wrong party.

Chargeback versus refund

This is the distinction that trips up nearly every new merchant, so it's worth being precise. A refund is something you do voluntarily: a customer asks, or you decide to make it right, and you send their money back through Stripe. It's fast, it's friendly, and it carries no penalty beyond the lost sale. A chargeback is something the customer's bank does, often without warning you first, and it comes with a dispute fee and a mark against your account's dispute ratio.

The two are not interchangeable, and — critically — they don't cancel each other. If a customer files a chargeback and you also issue a refund, you can pay twice: once through the refund, once if the chargeback resolves in their favor. The practical rule for beginners: handle refund requests quickly and generously before they escalate, because a resolved refund is far cheaper than a chargeback. Once a chargeback exists, don't refund on top of it — work it through the dispute process instead.

How the process actually unfolds

Here's the sequence, start to finish:

  1. The customer disputes a charge with their issuing bank, giving a reason — they didn't recognize it, never received the product, were charged twice, canceled a subscription, and so on.
  2. The bank reverses the charge provisionally and pulls the funds from your balance. Stripe notifies you and assigns the dispute a reason code and an evidence deadline.
  3. You respond — this stage is called representment. You submit evidence rebutting the customer's specific claim, plus a written explanation, through Stripe.
  4. The issuing bank reviews your evidence against the customer's claim and decides. This can take weeks.
  5. The outcome lands. If you win, the funds return to you. If you lose, they stay with the customer, and the dispute fee is not refunded either way.

The single most important thing to absorb as a beginner is what happens at step three if you skip it: a dispute with no response is lost automatically. There's no neutral default, no benefit of the doubt. Silence forfeits the case. The deadline is the most important number in the entire process.

What you can and can't control

You can't control whether a customer disputes a charge, and you can't control how their bank ultimately rules. What you control is everything in the middle: whether you respond at all, whether your evidence actually answers the claim that was made, and whether it arrives before the deadline. Disputes where the merchant has the facts — a delivery confirmation, a usage log, a signed agreement — are genuinely winnable, but only if those facts are submitted, on time, aimed at the right claim.

That's the encouraging part of the picture. The system is stacked against you at the front and fair at the back. The front is the bank keeping its promise to a customer. The back is a reviewer weighing evidence. Beginners who only ever experience the front conclude the game is unwinnable and stop showing up — which guarantees the losses they feared. Beginners who understand the back show up with the right evidence and recover money the system was always willing to give back.

A few habits that prevent disputes entirely

Some chargebacks never need fighting because they never happen. Make your billing descriptor clearly match your brand, so customers recognize the charge on their statement. Send confirmation emails customers will remember. Keep tracking numbers and delivery confirmations. Make canceling a subscription easy and asking for a refund easier than disputing. Each of these closes off a common reason a customer reaches for the dispute button instead of reaching for you.

Where Argeback fits

If you're new to all this, the operational side — watching deadlines, knowing which evidence beats which reason code, filing through Stripe correctly — is where the money is won or lost. Argeback handles that part. It connects to your Stripe account with dispute-scope access only, pulls each new dispute into a deadline-sorted inbox with alerts at 72, 24, and 3 hours, and asks a few questions tailored to that dispute's reason code so you submit the evidence that actually answers it. It drafts the written explanation, packages the evidence, and files through Stripe in one tap. The issuing bank still decides every case — but you stop losing winnable ones to a deadline you didn't know was ticking.