Stripe Chargeback Policy (2026): Fees, Ratio, Escalation

Stripe's chargeback policy charges a flat dispute fee on every disputed payment, and US merchants pay a second fee of the same size if they fight and lose. You get 7 to 21 days to respond, and a rate that keeps climbing puts the account itself at risk.

I've built dispute evidence packets for my own stores, and the reason code decided everything I sent. Merchants ask me about the fee. The part that decides whether you keep the account sits further down this page.

Key takeaways

• Stripe charges $15 per US dispute, win or lose.
• Fighting and losing costs $15 more, since June 2025.
• Card networks set your response window at 7 to 21 days.
• Miss that deadline and you lose automatically.
• Dispute activity above 0.75% counts as excessive.
• Stripe reaches out first, then reserves your funds.

Want the rate down before Stripe calls? Get Stripe dispute alerts on your account.

What is Stripe's chargeback policy?

Stripe's chargeback policy sets a flat dispute fee, a response window of 7 to 21 days, and a risk process that escalates with your dispute rate. The card network controls that window. US merchants pay a second fee of the same size when they fight and lose, and a rate that stays high can cost you the account itself.

Three different parties set those rules, which is why the policy feels inconsistent from the dashboard:

So a Visa dispute and an Amex dispute give you different deadlines even when the customer's complaint is identical. You can contest a dispute's merits with evidence, because the issuer judges that.

One country breaks the fee rule. Businesses based in Mexico get the dispute fee refunded when they win. Merchants everywhere else pay it either way.

Knowing what a chargeback is in general terms gets you partway. Stripe adds its own fee, its own deadline, and its own escalation process on top.

Those three run on different timescales. The fee hits immediately, the response deadline runs in days, and the escalation risk builds over months of dispute history.

Is a Stripe dispute the same as a refund?

No. A refund is money you send back by choice, and a dispute is money the customer's bank pulls back from you by force. Stripe uses "dispute" and "chargeback" for the same event.

The difference costs real money. A refund returns the purchase amount and ends there. A dispute returns that amount, adds Stripe's dispute fee, and counts against the dispute rate Stripe watches.

That third consequence is the one merchants underestimate. A refund is a bad day. A dispute is a bad day plus a mark on the account, and only that mark can eventually cost you card processing. Our guide covers chargeback versus refund on both sides of the ledger.

So refunding early is often the cheaper move, even when you'd win the dispute. Winning still leaves the dispute on your record.

The timing is what makes it work. A refund issued before the customer calls their bank never becomes a dispute, while a refund issued after they've filed doesn't cancel the case or the fee.

Watch for the customer who emails you and files with their bank the same day. Refund fast and reply fast, because whichever arrives first decides whether this shows up in your dispute rate.

What does a Stripe chargeback cost?

A Stripe dispute costs $15 in the US, and $30 total if you fight it and lose. Stripe added that second fee, charged when you counter a dispute and the issuer rules against you, on June 17, 2025.

Those are the headline numbers, and the details change the math. The amount varies by country and currency, and a few countries have no counter fee at all.

So $30 is the worst case on a US dispute, and that's the number to weigh before you decide to fight.

Our guide has Stripe's chargeback fee in full, with the country table and the break-even check.

The general chargeback fee works the same way across processors. Stripe just calls it a dispute fee.

The fee is also the smaller half of the cost. You lose the sale amount, the product you already shipped, and the staff time spent assembling evidence.

That's why the fee reads as cheap and the disputes still hurt. Merchants budget for the fee and absorb the rest without counting it.

How long do you have to respond to a Stripe dispute?

You get 7 to 21 days to respond to a Stripe dispute, and the window depends on the card network the payment ran through. Stripe states that range in its own dispute documentation.

Stripe passes through a deadline it doesn't set. The dispute travels through Visa's, Mastercard's, Amex's, or Discover's resolution rules, and each network defines its own response period. Two disputes that look identical in your dashboard can carry different due dates.

Miss the deadline and you lose.

The date is final. Stripe accepts no late submission and the issuer hears no appeal on timing.

That makes the date the first thing to check, ahead of the evidence. A packet that would have won the case is worth nothing the day after it's due.

Build the response around the earliest date you see. If disputes arrive faster than you can work them, assign one person the dashboard each morning rather than checking it weekly.

What happens during a Stripe chargeback?

A Stripe chargeback starts when the customer complains to their bank, and the bank pulls the money back through Stripe before you get to respond. You then submit evidence and the bank rules on it. Stripe puts the full lifecycle at two to three months.

Two side paths cause most of the confusion, and each gets its own section below:

1. Inquiries and retrievals, the stage before a formal dispute.
2. Dispute withdrawals, when the customer backs out mid-process.

Start with the one that happens before any money moves.

1. Inquiries and retrievals

An inquiry is the bank asking you to explain a charge before any money moves. Amex and Discover still use this stage, and Visa and Mastercard have dropped it.

Usually the customer just doesn't recognize the charge. They see a line on their statement they can't place, so their bank asks for clarification instead of opening a dispute.

Answer the question with evidence, or issue a full refund. Stripe says either one closes the case with no dispute fee.

That makes an inquiry the cheapest exit in the whole process.

If you ignore it, the bank treats that as you agreeing with the claim, and Stripe describes the resulting chargeback as likely unwinnable.

Inquiries also arrive quietly. They land in the dashboard without the alarm a dispute carries, so a merchant checking weekly can miss the one stage that costs nothing to clear.

Treat an inquiry as a deadline. Send the order record, the delivery confirmation, and the billing descriptor the customer saw, because recognition is usually the real question.

Our explainer covers inquiries and retrieval requests and how they differ from a formal dispute.

2. Can a dispute be withdrawn?

A customer can withdraw a dispute, and you still have to submit evidence for the case to close in your favor. The withdrawal alone leaves the case open.

Merchants get caught here constantly. The customer calls, recognizes the charge, and promises to cancel the dispute, so the merchant stops working the case. The bank still needs a response on file. An unanswered dispute closes as a loss whatever the cardholder said.

Submit the evidence anyway and note the withdrawal inside it. A customer can withdraw even after a loss, so document the conversation either way.

Get the withdrawal in writing while you have the customer's attention. An email confirming they recognize the charge and asked their bank to drop it is worth attaching, because the issuer sees your file rather than the phone call.

The dispute also still counts toward your rate once it's filed. A withdrawal saves you the disputed amount, and the mark on your account stays.

What happens if your Stripe dispute rate gets too high?

Stripe contacts you first, then holds a reserve against your funds, and the card networks fine you if the rate stays high. Stripe treats dispute activity above 0.75% as excessive.

That figure is a reference point rather than a switch. Stripe's documentation says a sudden spike or steep upward trend can trigger a monitoring program before you reach it. The shape of your trend counts as much as the number.

The figure is Stripe's own internal reference. Visa and Mastercard run their monitoring programs on separate thresholds, which is why the last stage below works differently from the first two.

Our guide covers Stripe's dispute rate and how the calculation works. Here's what escalation looks like:

1. Stripe reaches out about your dispute activity.
2. Stripe holds a reserve against your funds.
3. The card networks add fines and deadlines.

Each stage costs more than the one before it.

Stage 1: Stripe reaches out

Stripe says it contacts merchants proactively when it sees higher dispute activity. This is the cheapest warning you'll get. The only cost is the work of fixing what's driving the rate.

Pull your last 90 days of disputes, sort them by reason code, and name the top one.

Most merchants find one cause behind the cluster, and each has a specific fix:

• Descriptor nobody recognizes: set it to your storefront name in Stripe settings.
• Slow delivery window: email tracking within 24 hours of the order.
• Forgotten renewal: send a reminder email seven days before charging.

Fix the top cause first, and do it in a way you can show Stripe. Add a support email and a live chat link to the order confirmation too, because a customer who can reach you doesn't need their bank.

Then send Stripe the specifics. Name what you changed, the date you changed it, and your dispute count since. A dated fix with a falling number beats a promise to do better.

Stage 2: Stripe holds a reserve

A reserve is Stripe holding back part of your funds to cover disputes and refunds it expects. Stripe weighs your dispute rate, refund rate, industry, and processing volume when it decides.

The reserve usually hurts more than the fees do. Money you've earned sits locked up while suppliers and payroll keep their schedule. That's when disputes start affecting whether you can pay people.

Stripe runs two shapes of reserve. A rolling reserve holds a share of each day's sales and releases it on a delay. A fixed reserve parks a set amount until Stripe reviews the account again.

Stripe doesn't publish the percentage it holds. Treat any specific figure you read elsewhere as an estimate rather than policy.

Plan your cash around the hold while it lasts. Ask Stripe in writing what would end the reserve, and keep processing normally so the review has clean months to read. Delay any inventory buy that assumed same-week payouts.

Our explainer covers rolling reserves and how the hold hits your cash flow.

Stage 3: The card networks step in

Visa's VAMP and Mastercard's ECM programs fine merchants who stay above their thresholds. These are network programs, so the fines and deadlines aren't Stripe's to waive.

Stripe warns that missing a program's deadline can end with the network refusing to process your payments. This is the part of the policy that decides whether you keep taking cards at all.

Our guide explains chargeback monitoring programs and the thresholds behind each one.

Two merchants who pulled the rate back down

Both of these Stripe merchants reversed a rising dispute rate before the card networks got involved. They fixed the rate at stage one or two, which is where the fix is cheapest.

Dropship.io peaked at a 0.93% dispute rate, above Stripe's excessive line, then brought it to 0.16% after enrolling in dispute alerts. It drew scrutiny at that peak and never entered a network program.

Tim's Coffee had already drawn a Stripe warning and payment holds, then cut chargebacks 89% and cleared the shutdown risk.

The lag is the part merchants misjudge. Your rate is measured over a trailing window, so fixes made today take weeks to show up. Waiting for a clean month before you act spends the time you needed.

Our guide covers Stripe account suspension if Stripe has already closed your account.

What are Stripe's chargeback reason codes?

Stripe passes through the reason code the card network assigns, and that code decides what evidence actually helps you. The code names the customer's claim, like fraud, product not received, or subscription cancelled.

Each network runs its own code list. The same complaint arrives as a different code on a Visa than on a Mastercard. That code sets which evidence fields Stripe asks you to fill and how the issuer scores them.

That's the whole reason to read the code before you gather anything.

The code also tells you whether to fight at all. A "subscription cancelled" dispute turns on whether your cancellation flow logged the request. When your own records show the customer did cancel, refund it and fix the flow.

Codes cluster, too. Pull three months of disputes, group them by code, and the top group usually points at one broken thing rather than a run of bad customers.

Our guide covers chargeback reason codes across networks.

How do you prevent Stripe chargebacks?

You prevent Stripe chargebacks by authenticating risky cardholders, scoring payments for fraud, and refunding warnings before they become disputes. Stripe has a native product for each of those jobs, plus a fourth that reimburses eligible disputes once they land.

Here's where each one sits:

1. 3D Secure authenticates the cardholder before the charge.
2. Radar scores risk while the charge is processing.
3. Early Fraud Warnings flag fraud before a dispute is filed.
4. Chargeback Protection reimburses eligible disputes afterward.

The first three stop disputes, and the fourth pays for them.

1. Stripe 3D Secure

3D Secure asks the cardholder's bank to verify the person paying, before the charge goes through. Stripe prices it at $0.03 per attempt on top of the transaction fee.

The main value is the liability shift. When a 3DS-authenticated payment turns into a fraud dispute, the issuing bank covers the loss instead of you.

Trigger it selectively with Radar rules rather than on every checkout. Good triggers are orders above your average order value, shipping addresses that don't match billing, and cards that already failed once on your store.

Blanket 3DS costs you conversions on good orders to stop a small share of bad ones. Our explainer covers 3D Secure and where the liability lands.

The liability shift also has limits worth knowing. It covers fraud claims, so a customer who authenticated and later says the product never arrived still files a dispute you have to answer with delivery evidence.

2. Stripe Radar

Radar scores every payment for fraud risk while it processes, then blocks or flags the ones that look wrong. It's built into Stripe and trains on payment data across Stripe's merchant base.

Radar can see things your store can't. It knows if that card has been tried at other businesses tonight, how many attempts came from that device, and whether the billing details fit the card's history.

The same card failing at ten other stores looks like one ordinary decline to you, and Stripe sees all ten.

Set your own rules on top of the default score. Send payments above your average order value into manual review, rate-limit attempts per IP address to stop card testing, and require 3DS on mid-range scores.

Blocking too aggressively costs more than the fraud it stops.

Every declined good order is a customer who buys somewhere else. Check your decline rate weekly in the Radar dashboard, and loosen any rule whose block rate climbed without a matching drop in disputes.

3. Early Fraud Warnings

An Early Fraud Warning is the issuer telling you a payment looks fraudulent before the customer disputes it. Stripe sources them from Visa TC40 and Mastercard SAFE reports. It says 80% become a fraud dispute if you do nothing.

That figure is the whole reason to act on them. The warning arrives while a refund is still possible. Return the money and close the case, or hold the charge and take the dispute with its fee attached.

Refund the small ones and fight the big ones. Stripe's own analysis puts the break-even near your dispute fee, and says refunding stops paying off once a charge runs about a third above it.

Set that threshold once in your alert dashboard so the refund fires automatically below it. On the US fee, that puts the automatic line just above the fee itself, and a large charge is worth reading the evidence first.

Watch the direction when you configure it. Merchants routinely set the rule backwards and auto-refund only tiny charges, which quietly leaves every expensive warning sitting unhandled until it becomes a dispute.

4. Stripe Chargeback Protection

Chargeback Protection reimburses eligible disputed charges, up to $25,000, for 0.40% of every transaction it covers. It pays out after a dispute lands.

Eligibility is the catch, because coverage is gated by reason code. Fraud-type disputes qualify. Everyday ones like product not received or subscription cancelled don't, so the disputes most stores get fall outside it.

Our explainer covers Stripe Chargeback Protection and the exact codes.

A reimbursed dispute still counts against your dispute rate. You get the money back and the dispute still counts, so protection alone won't keep you out of a reserve.

That makes it a revenue tool. Run it alongside prevention if your fraud losses justify the cost, and treat the rate as a separate problem.

Alerts work the other way. A charge you refund from an alert never becomes a dispute, so it never enters the rate calculation at all. Our Stripe prevention app guide compares the categories.

Stopping disputes before they file is the job Chargeback.io's Stripe integration does.

How do you fight and win a Stripe dispute?

You win a Stripe dispute by answering the specific reason code the issuer assigned. The issuer scores your submission against that code's criteria.

That's why the dashboard asks for particular documents. Stripe templates the evidence request to the code.

A "product not received" case wants delivery confirmation and tracking. An "unauthorized" case wants AVS and CVC results, device data, and prior undisputed orders.

A thick packet of the wrong evidence loses to a thin packet of the right evidence. Reviewers score against a checklist.

Read the code first, pull only what it asks for, then write a short cover statement tying each document to the claim.

Our chargeback rebuttal template has the structure.

Write it for someone reading fast. Open with one line stating what the customer claimed and what your evidence shows, label each attachment by what it proves, and keep the whole thing to a page.

Skip the fight when the numbers say so. On a low-value order a won dispute barely clears the fees, so refund the small ones and spend the hour on a case worth winning.

When should you use chargeback insurance?

Chargeback insurance is worth it when your dispute losses cost more than the premium, which usually means high-ticket or high-risk merchants.

Run the arithmetic before you buy:

1. Multiply your monthly dispute count by your average order value.
2. Add the dispute fee for each one.
3. Compare that total to the premium and its coverage limit.

Our guide covers chargeback insurance and what the policies exclude.

Insurance also leaves your dispute rate alone. A reimbursed loss is still a filed dispute, so a policy protects the revenue and does nothing about the escalation path above.

Whether a policy pays off comes down to what it excludes. Policies commonly carve out the same everyday reason codes that make up most disputes, so check the covered list against your own reason-code mix.

FAQ

Can I get sued or blacklisted for too many chargebacks?

Stripe won't sue you over a high dispute rate, but you can land on the MATCH list that acquirers check before approving an account. A listing lasts five years and makes getting a new processor hard.

Does closing my Stripe account early avoid a chargeback?

No. A dispute already filed proceeds to a decision, and Stripe can recover the disputed amount and the fee from your remaining balance.

Do chargebacks follow me to a new Stripe account?

They can. Stripe links accounts by business details and ownership, and a MATCH listing follows the owner rather than the business name.

Is a Stripe dispute different from a chargeback?

No. Stripe uses "dispute" as its term for what the card networks call a chargeback, and both mean a forced reversal started by the cardholder's bank.