Chargeback Software for SaaS: Real 2026 Pricing (Stripe vs ChargeMate vs Chargeflow)
The 30% tax on your revenue that nobody warns you about
Most founders spend their first two years optimizing two numbers: churn and acquisition cost. Both are real. Both get attention. Neither is where a profitable SaaS business quietly leaks money.
The leak is chargebacks. A customer disputes a card payment, your processor reverses the charge, and the money leaves your account until you win the case. You also eat a flat fee for the dispute itself, usually $15 to $20. Lose, and the fee stays. Win, and some processors refund it and some do not.
Here is the arithmetic that should scare you. Stripe charges a $15 fee when a dispute arrives, plus another $15 if you submit evidence (disputes opened after June 17, 2025). For a $29 monthly subscription, that is a $30 bill to defend $29 of revenue. The math only works if you win and your processor returns the countered fee. If you lose, you are out $30 on a $29 sale.
Scale that up. Ten disputes a month on a $200 average charge is $3,000 in revenue at risk and $300 to $600 in dispute fees before you write a single line of evidence. That is why chargeback software exists, and why the pricing structure of those tools matters more than most founders realize.
What a chargeback actually is, and why the fee is per dispute
When a cardholder disputes a charge, two separate things leave your account. The first is the disputed amount, which you can recover by winning. The second is the chargeback fee, which covers the cost of processing the dispute through the card network. You do not control the second one, and it does not scale with the size of the sale.
That last point breaks small merchants. A $9 renewal and a $900 enterprise invoice carry the same dispute fee. For a $9 product, defending the charge literally costs more than the revenue. Your dispute strategy has to be different for each, and most software treats them identically.
Card networks such as Visa and Mastercard charge dispute fees to acquirers, not directly to you. Your acquirer folds those network costs into the per-dispute fee in your merchant agreement. That is why the same Visa chargeback can cost $0 with one provider and $50 or more with another. Your contract matters more than the brand on the processor.
One fee that catches people: per Stripe’s documentation as of November 2026, contesting a Visa compliance dispute requires agreeing to an additional $500 network fee, refunded only if you win. Pre-arbitration and arbitration carry similar filing fees. Most merchants never escalate that far, and that is not cowardice, it is arithmetic.
Chargeback fees by processor (2026)
These are US figures pulled from each provider’s own pricing and help pages as of November 2026. Fees vary by country and can be overridden by a negotiated contract, so treat your own fee schedule as the final word.
| Processor | Fee per dispute (US) | Refunded if you win? |
|---|---|---|
| Stripe | $15 dispute received fee, plus $15 dispute countered fee if you respond | Countered fee: yes. Received fee: no, unless your contract says otherwise |
| PayPal (account disputes) | $15 standard, $30 high volume | Standard: generally not charged if you win. High volume: charged regardless |
| PayPal (card chargebacks) | $20 | Not stated on PayPal’s fee page |
| Braintree | $15 | No, non-refundable regardless of outcome |
| Square | No separate dispute fee | Not applicable. If you lose, the original processing fee is not returned |
| Shopify Payments | $15 (varies by country) | Yes |
| WooPayments | $15 (£15 UK, €15 eurozone) | Yes, automatically if you challenge and win |
| Adyen | Set in your merchant agreement | Per contract |
| Checkout.com | Custom pricing, charged whether you accept or challenge | Per contract |
| Klarna (direct merchants) | $15 standard, $30 excessive tier | Only on certain outcomes |
| High-risk merchant accounts | Set by contract, commonly $25 to $100 | Usually not |
Two structural differences matter more than the absolute numbers. Square charges no dispute fee at all, and PayPal refunds its standard dispute fee when you win. Stripe charges two separate fees. For a high-volume subscription business, the fee structure alone can justify a processor review.
The four pricing models, and where each one breaks
Chargeback software falls into four buckets, and founders regularly pick wrong because the differences are large.
1. Do it yourself with your processor’s dashboard
Free. Every major processor has a dispute portal where you upload evidence and submit a response. Stripe’s built-in submission costs nothing on top of the $15 countered fee, and that countered fee comes back if you win.
This is the right answer for most founders starting out, and I will keep saying it. If you handle fewer than five disputes a month, do it by hand. The tooling exists to solve a volume problem, and paying a vendor to save you two hours a month is how you end up with a $2,400 annual subscription for a job you would rather do yourself.
2. Subscription pricing (software only)
You pay a flat monthly fee and still do all the work. Typical range is $50 to $300 a month, which sounds reasonable until you realize you are buying a template generator, not an outcome.
Disputifier sits in this tier at $49 to $299 a month depending on plan, and works with Stripe, PayPal and a handful of others. This model makes sense if you have high dispute volume and genuinely want to review every response before it goes to the bank. It makes no sense if your goal is to stop thinking about disputes.
3. Success fee (percentage of recovered funds)
You pay nothing upfront and give the vendor a cut of what they recover. The typical range is 20% to 40%. Chargeflow charges 25% of what it wins, with no monthly fee, and connects to Shopify, Stripe, PayPal, Braintree and Adyen.
Here is the trap nobody mentions. A 25% success fee sounds cheap until you remember the percentage applies to the disputed amount, not to your profit, and the fee comes out of money you already paid in dispute fees. On a $150 dispute you win, you hand over $37.50. Do that ten times a month and you are paying $375 a month for a tool that competes against a $9 flat fee.
4. Per-response pricing
You pay per AI-generated response, no monthly minimum. ChargeMate lists from $0.82 per response, with a free plan covering three cases a month, and it works with any processor. Disputifier’s lower end sits at $0.50 to $2 per case on top of its SaaS subscription.
This is the model that makes the most sense for a volume you cannot predict. At $0.82 per response, 100 responses a month costs $82. At a 25% success fee on a $150 average dispute, the same 100 responses at a 50% win rate costs $1,875. Per-response wins by a wide margin at volume.
5. Retainer / enterprise agencies
Full-service firms that take the whole case: gathering evidence, writing the rebuttal, managing deadlines. Chargebacks911 runs $1,000 to $5,000+ per month. Midigator runs $1,000 to $3,000+ per month. You are buying the outcome, not the software.
My honest take: the retainer tier is priced for companies handling hundreds of disputes a month, where each prevented chargeback is a five-figure recovery. For a founder with twenty disputes a quarter, it is the most expensive way to solve the problem.
Running the numbers: what each model costs at your volume
Let us take a real case. Assume a $150 average disputed amount and a 50% win rate, and compare the three mainstream models monthly. SaaS pricing covers the software only, so you still have to do the work.
| Monthly disputes | Per-response (at $0.82) | Success fee (25% of a $150 win) | SaaS subscription ($200/mo) | Cheapest |
|---|---|---|---|---|
| 10 | $82 | $375 | $200 | Per-response |
| 20 | $164 | $750 | $200 | Per-response |
| 50 | $410 | $1,875 | $200 | Subscription |
| 100 | $820 | $3,750 | $200 | Subscription |
| 200 | $1,640 | $7,500 | $200 | Subscription |
Two things fall out of this table. First, the crossover between per-response and subscription pricing sits somewhere around 30 to 40 disputes a month, once you price in your own time. Second, success fee pricing is the most expensive option at every volume except the very smallest. If a vendor pitches you on a percentage of recovery, ask what happens at scale. The answer gets worse for you as you grow.
One more variable changes everything: Stripe’s Smart Disputes product, which charges 30% of each dispute you win, with no fee on losses. On a won $1,000 dispute, that is $300 plus the $15 dispute fee, leaving you $685. A flat $9 per win looks better the moment the dispute amount climbs past about $30. That is the entire argument for the flat-fee tier, and it is a much stronger argument than the vendor marketing decks suggest.
Stripe Smart Disputes: free setup, expensive ceiling
Smart Disputes is Stripe’s built-in automation. When an eligible dispute arrives, Stripe assembles an evidence packet from the payment record, card checks, customer details and network signals. Do nothing, and Stripe submits that packet just before the deadline. No setup, no integration, no vendor call.
The limitation sits in the same place as the strength. Stripe can only use what Stripe can see. It does not know whether your customer logged in to your product, downloaded the course they claim they never received, or kept using your software for four months after filing a fraudulent transaction claim. For digital businesses, that usage data is usually the strongest evidence you have, and it is invisible to Stripe.
There is also a 30% fee on won disputes, and Stripe decides eligibility based on reason code, payment method, available evidence and cost. Some disputes never qualify for automation at all.
So when does Smart Disputes make sense? When your disputes are tiny, under roughly $30, because 30% of a win beats a flat $9. When you have no usage data, support history or policies to contribute, because a third-party tool would have little more to work with. And when you want zero setup and are content to let Stripe decide what goes to the bank.
Skip it when your disputes are large. Annual SaaS plans, courses, coaching retainers, agency work. Those are exactly the disputes where product usage logs tip the decision.
One warning before you buy anything
If you use a third-party tool to respond, turn off Smart Disputes auto-submission before you run them together. Stripe will submit its own packet first, and Stripe usually accepts evidence only once per dispute. You can end up with your vendor’s carefully researched response sitting unused because Stripe already filed.
The fix takes about a minute. In the Stripe Dashboard, go to Settings, then Disputes, and turn off automatic submission of Smart Disputes evidence. Then confirm your third-party tool is the one actually filing.
What good dispute evidence looks like
Tools help, but evidence quality decides cases. If you are assembling your own responses, these are the things that actually move a dispute outcome:
- Product usage logs with timestamps. Logins, API calls, feature usage, seat counts. This proves the customer received what they paid for. It is also the strongest evidence you have and the one Stripe cannot access.
- IP addresses and device fingerprints. Matching the login IP to the IP used for the payment suggests one person, not a fraud ring.
- Support ticket history. A customer who opened tickets asking how to use the feature they are now claiming was never delivered is undermining their own case.
- Delivery confirmations and download records. For courses and digital goods, a timestamped download receipt is close to a verdict.
- Your refund and cancellation policy. If the customer ignored a clear policy, that is a defense. If your policy is vague or buried, do not lean on it.
- Cancellation timestamps. A customer who cancelled voluntarily and then disputed the charge months later is making a weak case, and the record says so.
The common thread: every one of those comes from a system you own, not from your payment processor. Stripe sees the payment. You see the behavior.
Prevention is worth more than recovery
Every tool in this category will sell you on recovery rates. Some are genuinely good at it. But a chargeback you never receive is worth more than one you win, because recovery means you have already paid the fee, eaten the dispute, and spent founder hours on it.
The prevention levers are unglamorous and they work:
- Clear delivery evidence at purchase time. Send a receipt with a timestamp, a login link, and a plain statement of what they bought. Send it from a domain that looks like your company, not a no-reply address.
- Descriptor names customers recognize. A statement line reading “SERVICE XYZ LLC 888” is what creates the fraudulent claim in the first place. “CLOUDPAY 888” creates a stranger’s name to dispute.
- Quiet cancellation flows. Make cancelling easy and obvious. A good chunk of fraudulent disputes come from customers who wanted to cancel, could not find the button, and filed with their bank instead. That customer would have been a cancellation, not a chargeback.
- Risk-based authentication on your own checkout. If you run your own payment flow, use 3DS on higher-risk transactions.
- Watch the rate, not the count. Chargeback rates are usually measured as a percentage of total charges. A high ratio is what triggers network monitoring and your account getting flagged. A handful of disputes on a large volume is much less dangerous than ten on a small one.
How to pick
Here is the decision, stated plainly:
- Fewer than 5 disputes a month: Handle it yourself in your processor’s dashboard. Do not buy anything.
- 5 to 30 disputes a month, predictable: A flat-fee per-response tool. Per-response pricing wins here, and you get AI-drafted responses without a success-fee tax.
- 30 to 100 disputes a month: Compare a subscription plan against per-response at your actual volume. At this size the subscription usually wins, but you need someone reviewing each response.
- Over 100 disputes a month: You are in retainer or full-service territory, and you should negotiate enterprise pricing directly. At this volume you also need a prevention program, because software cannot outrun a broken payment experience.
- Your disputes are mostly under $30: Do the math carefully. It may genuinely be cheaper to accept the loss than to contest it. Defending a $9 charge costs $30 in Stripe fees.
And one rule that overrides all of the above: if your dispute amount is large and you have usage logs, a flat-fee tool that can read your logs will beat both Stripe Smart Disputes and any percentage-based vendor. The 30% fee only looks cheap if you do not have evidence worth adding.
The one-hour setup
If you do nothing else this week, do this:
- Pull your last 90 days of disputes from your processor dashboard. Count them. Calculate the total dollar amount and your average dispute size.
- Find your processor’s dispute fee in your contract, not on their pricing page. If your contract is silent, ask them in writing. The number they email you is the one that matters.
- Compute the 30% version: disputes times fee times 3. That is roughly what a full retainer costs, so you know whether you are in the market for one.
- Check whether Smart Disputes auto-submission is on. If you are evaluating a third-party tool, turn it off first.
- Export your product usage logs to somewhere you control, with timestamps. The next dispute will be easier to win with them.
That is an hour of work that will tell you whether this problem is worth software yet. For most founders reading this, the answer is no, and that is fine. For the ones whose chargeback ratio is creeping up, it is the most valuable hour you will spend on payments this month.
