How Refunds and Chargebacks Affect SaaS Revenue

Why SaaS chargebacks and refunds matter more than they look

SaaS chargebacks and refunds both take money back out of revenue you have already recorded, but they are not the same event and they do not cost the same. A refund is a payment you choose to return. A chargeback (or dispute) is a reversal the customer’s card issuer initiates, usually without your agreement, and it carries extra fees, operational work, and risk to your payment account.

For a small subscription business, a handful of disputes can erase a month of growth on a revenue chart and, if they persist, trigger card-network monitoring. For a buyer evaluating a startup, refund and dispute history is one of the clearest signals of product quality, billing hygiene, and fraud exposure.

This guide explains how each event moves through your revenue, what processors and merchants of record charge for disputes as of October 2026, and how to keep both under control.

Refund vs chargeback: the key differences

Who starts it: a refund is started by you, often after a customer request; a chargeback is started by the cardholder’s bank.
Who controls the amount: you choose a full or partial refund; the issuer sets the disputed amount.
Extra fee: refunds usually carry none, but original processing fees are not returned on Stripe; disputes carry a dispute fee, often plus a fee to contest.
Can you win it back? A refund is your decision and final; a dispute can possibly be won by submitting evidence.
Counts toward network monitoring? Refunds do not; disputes do, whether won or lost.

Stripe’s documentation describes a dispute as occurring “when an account owner contacts their bank to contest a payment to you,” and notes that the outcome “is at the sole discretion of the account owner’s bank” (Stripe: How disputes work).

How a refund hits your revenue

On Stripe, a refund is drawn from your available balance. If the balance is too small, card refunds are held as pending until it recovers (Stripe: Refunds). Customers typically see the credit “approximately 5-10 business days later, depending upon the bank,” per the same page.

The cost is more than the refunded amount. Stripe states that its “processing fees from the original transaction aren’t returned” (Stripe: Refunds). So a fully refunded $50 domestic card payment costs you the $50 plus the original $1.75 fee (2.9% + 30¢ as of October 2026, per Stripe US pricing).

Merchants of record handle this differently. Lemon Squeezy says “the refunded amount (minus our platform fee) will be deducted from your next payout” (Lemon Squeezy: Refunds and chargebacks). It also reserves the right to issue refunds within 60 days of purchase at its own discretion to prevent chargebacks, so a refund may happen without you initiating it.

How a chargeback hits your revenue

When a dispute opens on Stripe, the card network pulls the disputed funds from your balance and holds them for the life of the dispute. Stripe “debits your Stripe balance for the disputed amount plus a dispute fee,” and you cannot issue a separate refund while the dispute is open (Stripe: How disputes work).

Key timing facts from the same documentation:

Card networks “typically allow cardholders to initiate disputes within 120 days of the original payment,” with longer windows in some situations.
After a chargeback is created, you usually have 7–21 days to respond, depending on the network.
The issuer usually takes 60–75 days to decide after you submit evidence.
The full lifecycle “can take 2-3 months.”

That means a dispute can hit your revenue months after the sale, and money can be held for months more before a decision. On a revenue chart, a dispute may show up as a negative event in a later period than the original payment.

What disputes cost, as of October 2026

Stripe (US): $15.00 when a dispute is received, plus $15.00 if you counter it. The countered fee is returned if you win; the received fee is not (Stripe pricing).
Paddle: 20 USD/GBP/EUR or 40 CAD/AUD, recovered from the seller’s balance along with the transaction amount (Paddle help).
Lemon Squeezy: $15, deducted from the next payout with the refunded amount (Lemon Squeezy docs).
Polar: $15, “regardless of outcome” (Polar pricing).
Dodo Payments: $30, listed under chargeback and dispute handling (Dodo pricing).

Check each provider’s current page before relying on these figures.

Stripe’s countered fee was introduced for disputes countered after June 17, 2025 (Stripe support). This changes the economics of fighting small disputes: countering a $20 dispute and losing costs an extra $15.

A worked example

A customer disputes a $50 monthly charge on Stripe. You counter it and lose.

Disputed amount debited: $50.00
Original processing fee (not returned): $1.75
Dispute received fee: $15.00
Dispute countered fee (lost, not returned): $15.00
Total cost: $81.75 against a $50 sale

If you had refunded the $50 when the customer first complained, the cost would have been $51.75 and no dispute would have counted against your account. That is why fast refunds for genuinely unhappy customers are often cheaper than disputes.

Dispute rates and monitoring programs

Card networks watch dispute activity. Stripe says that “the credit card processing industry standard recognizes dispute activity above 0.75% as excessive,” and that spikes or steep trends can trigger monitoring programs before that level (Stripe: Measuring disputes). It also stresses that “all disputes, whether they’re won or lost, count towards your dispute rate.”

Stripe distinguishes two measures:

Dispute activity: disputes by dispute date divided by payments in the period. This is what network monitoring programs use.
Dispute rate: disputes by the original charge date. This is better for spotting which sales or campaigns attract disputes.

Merchants of record also act on excessive disputes. Lemon Squeezy notes its team “may intervene and suspend your account” where chargebacks are excessive (Lemon Squeezy docs).

Early fraud warnings and pre-dispute alerts

Not every dispute arrives without warning. Stripe receives early fraud warnings from Visa, Mastercard, and JCB issuers. Stripe says that, if you don’t refund, “about 40% of Visa and Mastercard EFWs become fraud disputes,” and suggests that refunding is typically worthwhile on charges roughly at or below your dispute fee (Stripe: How disputes work).

Paddle describes a similar flow as an MoR: when a fraud partner flags a likely chargeback, Paddle may issue a full refund before the chargeback is finalized, and a chargeback fee still applies to cover the alert (Paddle help).

How to reduce SaaS refunds and chargebacks

Most SaaS disputes fall into a few patterns: the customer does not recognize the charge, forgot about a renewal, could not find how to cancel, or the card was used fraudulently. Practical controls:

Use a recognizable statement descriptor. If customers see an unfamiliar name, they call their bank. With a merchant of record, the platform’s name may appear, so make sure your receipts mention it.
Send renewal reminders, especially before annual renewals.
Make cancellation easy and visible. A customer who cannot cancel in-app may dispute instead.
Refund quickly when the customer is clearly unhappy. It is cheaper than a lost dispute and does not count toward your dispute activity.
Respond to inquiries. Stripe warns that failing to respond to an inquiry can lead to an escalation that is “probably unwinnable.”
Keep evidence ready: login records, usage logs, terms acceptance, cancellation policy, and communications.
Screen for card testing and fraud at signup and checkout, particularly for free-trial-to-paid flows.
Track both refund rate and dispute rate monthly so a spike is visible quickly.

How refunds and disputes show up in reported revenue

Different systems treat these events differently, which is a frequent source of confusion in diligence:

Payment processor dashboards may show gross volume with refunds and disputes as separate lines.
Subscription MRR typically does not change because of a refund. Stripe calculates MRR from active subscriptions; a subscription is counted as churn when it is canceled or marked unpaid (Stripe Billing analytics).
Merchant-of-record payouts are net of refunds, dispute amounts, and dispute fees.

RevenueBug’s headline metric is trailing 30-day revenue: successful payment principal minus refunds and disputes, before provider fees. Because a refund or dispute can arrive after the original payment, the methodology notes that historical figures can change when a later refund, dispute, or correction is recorded. A verified figure is provider-derived; it is not an audit.

For founders preparing to sell, export a monthly table of gross payments, refunds, disputes (count and amount), dispute outcomes, and fees. Buyers will ask for it during startup due diligence. If refund rates are high, explain why: a generous trial-refund policy reads very differently from widespread product dissatisfaction. Use the churn and retention calculator alongside refund data, because refunds often precede churn.

Common mistakes

Fighting every dispute. With a countered fee, contesting low-value disputes you are unlikely to win adds cost.

Ignoring disputes on a merchant of record. The MoR handles the process, but fees and lost revenue still come out of your payouts.

Counting refunded revenue as growth. A launch spike followed by heavy refunds is not durable revenue. Look at net figures.

Not reconciling timing. A dispute filed in March against a December payment affects different periods depending on which date a report uses.

Partial refunds that invite full disputes. Stripe notes that customers can still dispute the entire payment after a partial refund.

Frequently asked questions

What is the difference between a refund and a chargeback?

A refund is money you choose to return. A chargeback is a reversal initiated by the customer’s card issuer through a dispute. Chargebacks add fees, can be contested with evidence, and count toward card-network dispute monitoring.

How much is a chargeback fee for SaaS?

It depends on the provider. As of October 2026, Stripe US charges $15.00 per dispute received plus $15.00 if you counter; Lemon Squeezy and Polar list $15; Paddle lists 20 USD/GBP/EUR; Dodo Payments lists $30. Check current provider pages.

What is an acceptable chargeback rate?

Stripe says the industry standard treats dispute activity above 0.75% as excessive, and that sharp increases can trigger monitoring earlier. Most businesses aim to stay far below that level.

Do refunds reduce MRR?

Not usually directly. MRR measures active recurring subscriptions, so a refund without a cancellation leaves MRR unchanged, while the refund reduces cash and transaction-based revenue. If the customer also cancels, MRR falls through churn.

How long can a customer dispute a charge?

Stripe says card networks typically allow disputes within 120 days of payment, with longer windows in some cases, such as services delivered after the payment date.

Does RevenueBug subtract refunds and chargebacks?

Yes. RevenueBug’s trailing 30-day revenue subtracts qualifying refunds and disputes reported by the connected provider. It does not subtract provider fees.