What Is a Chargeback? A Plain-English Guide for Founders (Before It Tanks Your Stripe Account)

The Email That Ruined My Morning

It was a Tuesday in 2024. I was three sips into my coffee, half-reading Slack, when a Stripe notification landed: “You have a new dispute.”

My first thought was “oh, someone wants a refund, I’ll just refund them.” Instead I got a countdown, a case ID, and a demand for “compelling evidence” within seven days — plus a note that $15 had already been pulled from my balance. (That confusion is common enough that I wrote a whole chargeback vs refund explainer — they are very much not the same thing.) Not might be pulled. Already was.

I hadn’t done anything wrong. I hadn’t even been asked. The customer had gone straight to their bank, said the charge looked unfamiliar, and the bank yanked the money back before I got a say in it. That’s the moment I actually understood what a chargeback is, as opposed to what I’d assumed for two years of taking card payments.

If you’re running a SaaS and you’ve never had one yet — you will. This is the one you want to understand before it happens, not while you’re staring at a countdown timer.

---

A Chargeback Is Not a Refund. It’s a Bank Overruling You.

Here’s the confusion I had, and I suspect most first-time founders have it too: a refund and a chargeback look the same from the outside — money leaves your account and goes back to the customer. But who initiates it is the entire difference.

• A refund is something you choose to give. You press the button in your dashboard. You’re in control.
• A chargeback is something the customer’s bank does to you. The cardholder disputes the charge with their bank or card issuer, and the bank reverses it — pulling money out of your account, often before you even know the dispute exists.

You’re not a participant in that first step, just a bystander notified after the decision. Your payment processor — Stripe, in my case — relays the news and holds a slot open for you to argue back, if you want to. That’s the part that stings for a solopreneur: it’s not your call anymore. Someone else’s bank made a unilateral decision about your money, and now you’re playing defense.

---

Why Chargebacks Happen (It’s Rarely What You Think)

I assumed, naively, that chargebacks meant stolen credit cards. Sometimes that’s true. But after going through a handful of them across two different products, the actual mix looks more like this:

1. Genuine fraud. Someone’s card got compromised, a stranger used it to buy your $29/month plan, and the real cardholder disputes a charge they never made. Legitimate, and not much to fight.

2. “I don’t recognize this charge.” The sneaky one, and it hits SaaS the hardest. Your billing descriptor — the text on the customer’s bank statement — says something cryptic like STRIPE*XKQ92LABS instead of your product name. The customer panics and disputes it. They weren’t lying. They genuinely forgot what “XKQ92LABS” was, because it was never your product name to begin with.

3. Dissatisfaction, or “friendly fraud.” The customer used your product, decided they didn’t like it, and instead of emailing you for a refund, just called their bank. Not that friendly — it’s the path of least resistance, because disputing a charge is faster and free, while a refund request means waiting on you.

4. Subscription confusion. They forgot they were on a recurring plan and disputed the renewal instead of canceling first. Annual plans are especially bad for this — a customer who signed up 11 months ago has forgotten your product exists until the renewal hits their statement.

Categories 2 through 4 make up the overwhelming majority of chargebacks a small SaaS actually sees. Real stolen-card fraud is rarer than you’d expect for a product with no physical inventory to resell.

---

What a Chargeback Actually Costs You

This is the part that made me stop shrugging chargebacks off as “just a refund, whatever.” A chargeback costs you more than the transaction amount, and it costs you regardless of the outcome.

On Stripe, you’re charged a flat dispute fee — currently around $15 in the US — the moment the dispute is filed, whether you fight it or not. If you submit evidence and contest it, Stripe added a second fee on top of that in 2025, just for countering the dispute, refunded only if you win. Lose, and you’ve paid twice: once for the dispute existing, once for trying to defend yourself.

So the real math on a $50/month subscription chargeback isn’t “lose $50.” It’s lose $50, plus a $15 fee, plus however many hours you spend pulling login logs and support threads together — and there’s still a real chance you lose anyway, because card networks lean toward the cardholder by default. Multiply that by a few disputes a month and you’re not looking at a rounding error. You’re looking at a line item.

---

The Part Nobody Warns You About: Your Processor Account Is at Risk

Chargebacks aren’t just a per-incident cost. They’re a reputation score, and both Visa and Mastercard are watching it.

Visa runs a monitoring program (VAMP, which folded its older dispute- and fraud-monitoring programs into one ratio) tracking disputes-plus-fraud against your total volume. That threshold has gotten stricter, not looser — it tightened from 2.2% down to 1.5% in most regions in 2026. Cross into “excessive” territory and your acquirer eats per-transaction fines, which they pass straight down to you.

Mastercard runs something similar: hit 100 chargebacks in a month and a 1.5% chargeback-to-transaction ratio, and you’re enrolled in their Excessive Chargeback Program. Cross 300 chargebacks and 3% and you’re in the “high excessive” tier, with fines that escalate the longer you stay there.

None of these thresholds care that you’re a two-person SaaS with 40 customers. Cross the line and the networks flag your processor, who has every right to review, restrict, or terminate your account to protect its own standing. I’ve read enough Stripe horror-story threads to know this isn’t theoretical: accounts get closed over chargeback ratios, sometimes with funds frozen for months. For a solopreneur with $0 buffer, that’s not a rough week. That’s the business.

---

How to Actually Fight a Chargeback

You can win these. I’ve won some and lost some, and the difference usually came down to preparation, not luck.

• Evidence, evidence, evidence. Login timestamps, IP addresses, usage logs showing the customer used your product after the “unauthorized” charge, the sign-up email confirming they created the account, any support thread proving they were engaged, not confused.
• Your terms of service and billing description, shown clearly at checkout — proof the customer agreed to a recurring charge, not a one-time payment they were surprised to see again.
• A clean paper trail on cancellations. If they say “I tried to cancel and couldn’t,” you need logs showing your cancel flow actually works.
• Speed. Card networks give you a window — often 7 to 20 days depending on the network and case type — to respond. Miss it, and you lose by default, however strong your case would have been.

Tools like Chargeflow automate this evidence-gathering and submission process for founders who don’t want to hand-build a dispute packet every time — worth knowing about once you’re seeing more than one or two a month.

---

The Founder-Specific Prevention Playbook

Fighting chargebacks after the fact is damage control. The actual leverage is upstream, and it’s mostly free.

Fix your billing descriptor. The single highest-leverage five minutes you can spend. If your customer’s bank statement shows SP*7X9QLABS instead of your product’s name, you’re manufacturing “I don’t recognize this charge” disputes out of thin air. Set a clear, recognizable descriptor in your processor’s dashboard — your product name, not your holding company’s LLC. I once inherited a project where the descriptor was the founder’s shell company from a completely different failed startup. Customers had no chance.

Make cancellation embarrassingly easy. The biggest driver of friendly fraud is a customer who wanted to cancel, couldn’t find how, and disputed instead. If canceling needs an email to support and a three-day wait, you’re begging for chargebacks. A visible “cancel subscription” button is cheaper than the chargebacks it prevents.

Send a receipt and a renewal reminder. An email the moment a charge goes through, and — for annual plans especially — a heads-up before renewal. It’s the difference between “oh right, I forgot about this” and “I don’t recognize this.”

Respond to refund requests fast. Take four days to reply and they’ll dispute the charge in the meantime, because their bank answers faster than you do. A same-day refund is always cheaper than a chargeback: no fee, no ding to your dispute ratio, no risk to your account.

---

Why a Merchant of Record Changes the Math Entirely

This is the part that made me rethink payments for the projects I run out of India. When you use raw Stripe, you’re the merchant. Every chargeback is your chargeback — your dispute ratio, your fee, your account at risk with the card networks.

A Merchant of Record like Paddle or Dodo Payments sits between you and the networks differently. They process the transaction under their own merchant account, so the chargeback ratio Visa and Mastercard are watching is theirs, not yours. Paddle in particular tends to absorb a meaningful chunk of chargeback liability directly rather than passing every cost through — worth a lot if your product is consumer-facing and naturally sees higher dispute rates than a boring B2B tool.

Lemon Squeezy is also a Merchant of Record and handles the dispute process for you, but it typically passes the dispute fee straight to the seller’s payout rather than eating it — a different trade-off, not a knock on them. I went deeper on the actual fee structures in Paddle vs Lemon Squeezy.

For founders in India, where Stripe is invite-only anyway thanks to RBI rules, this isn’t even optional — you’re choosing a Merchant of Record from day one, so pick the one whose chargeback handling matches your product. I wrote the full breakdown in Stripe alternatives for Indian founders, and if confusing renewal charges are the real source of your disputes, the recurring billing guide covers doing that part right.

---

The Bottom Line

A chargeback isn’t a customer service problem. It’s a banking mechanism that happens to land on your desk looking like one. The bank moves first, you find out second, and the fee shows up whether you deserved it or not.

The founders who get hurt by chargebacks aren’t usually the ones who did something wrong — they’re the ones who left a cryptic billing descriptor unfixed for eight months, or made canceling annoying enough that customers picked the faster, angrier path instead. Fix the descriptor. Make canceling a button, not an email chain. Answer refund requests before the customer’s patience runs out. That’s most of the battle, and it’s free.

The rest — the evidence-gathering, the network thresholds, the actual fight — is just paperwork you hope you rarely need. But now, at least, you’ll know what’s happening the next time that Stripe email lands in your inbox before your coffee’s even finished.

This is the Broken Engineer Guide. I over-engineer everything, fail at business, but share the learnings so you can win.