Refund Rate
The share of gross revenue returned to customers.
Put this metric to work: explore FlowMRR's Stripe MRR analytics to track revenue movements, retention and forecasts from your Stripe account, or see how FlowMRR compares as a Baremetrics alternative for Stripe.
The share of collected revenue returned to customers as refunds. FlowMRR divides each period's refunds by its gross receipts (payments collected, before tax, fees and refunds are taken off); lost disputes are tracked on their own line, not in the rate. It is not churn, but it often points to product mismatch, billing confusion, aggressive sales, implementation failure, or payment-quality issues.
Formula
Refund Rate = Refunds ÷ Gross receipts, for the same periodWorked example
Gross receipts $80,000, refunds $1,600 → Refund Rate = 1,600 ÷ 80,000 = 2.0%.
Other definitions you will see
Some divide refunds by net revenue (after tax or fees) instead of gross receipts, which reads higher; some add lost disputes or credit notes to refunds. Teams also differ on dating: the month the refund is issued, or the month of the original payment.
Illustrative comparisons
Billing qualityThese unsourced ranges are illustrative scenarios, not measured industry benchmarks, percentiles or recommended targets. Their qualitative labels are editorial interpretations. Compare your own cohorts using the same segment, period, currency and measurement basis.
Why it matters
Refund Rate is an early warning signal for revenue quality. Churn tells you customers left; refunds tell you customers paid and then reversed the transaction. When it spikes, inspect sales promises, onboarding failures, payment disputes, annual-plan cancellations, and pricing clarity before the issue spreads into churn.
Common mistakes
- Treating refunds as churn instead of a revenue adjustment with its own cause.
- Measuring refund count instead of refunded revenue — one enterprise refund can dominate the month.
- Overlooking partial refunds and credit notes: they often reveal plan-fit or invoice issues, even when the credit never leaves your account.
Calculating it from Stripe data
Read refunds from Stripe's Refund objects or their balance transactions, not from subscription statuses: a refund does not cancel a subscription, and a cancellation refunds nothing unless you issue one. Each refund points to a charge or payment intent, which leads back to the invoice and the subscription it paid. Partial refunds are separate Refund objects with their own amounts, so sum amounts rather than counting refunded charges. Keep only refunds that succeeded, in the smallest currency unit and in the currency of the original charge.
Credit notes are the other route on invoices. A credit note on a paid invoice can return money to the card, add credit to the customer balance or record a payment made outside Stripe; only the first is money returned. A balance credit reduces future invoices and is better tracked next to discounts. Disputes are not refunds either: the bank takes the money back and Stripe charges a dispute fee, so report them on their own line. Put tax on the same side of the fraction: a refund usually returns the tax with it, so compare refunds with collections including tax, or remove tax from both.
Then choose the month a refund belongs to. Dating it when it was issued matches cash and your bank statement. Attributing it to the month of the original charge gives the refund rate of each month's sales, which is better for spotting a bad campaign or a confusing renewal, but it rewrites past months as refunds arrive. FlowMRR's cash-flow view shows refunds, disputes, fees and tax against gross receipts per month, all from Stripe. Each refund is linked to its invoice through its charge or payment intent, and refunds that cannot be traced to an invoice are spread across that month's products in proportion to gross revenue.
Reading the result
Break refunds down by reason, plan and how long after payment they happened. Refunds in the first days after a first charge point to a sale or trial that set the wrong expectation; refunds right after an annual renewal often mean the customer did not expect to be charged, which a reminder before renewal addresses. One large annual refund can dominate a month, so read the refunded amount and the number of refunds together.
A rising refund rate tends to come before churn: customers who ask for their money back are often on their way out. Read disputes next to it. When a refund is hard to obtain, some customers go to their bank instead, which costs you a dispute fee and adds to the dispute activity card networks monitor. A clear, quick refund for legitimate cases can lower disputes.
Frequently asked questions
What is a good refund rate for a subscription business?
It depends on your refund policy, your billing and your sales motion. A money-back guarantee, annual prepayment or assisted sales with large first invoices all raise refunded amounts compared with monthly self-serve plans without a guarantee. Compare with your own history: a sudden rise matters more than the level.
Do refunds reduce MRR?
No. MRR is a run rate built from subscriptions; a refund is a cash adjustment on a past payment. If the refund comes with a cancellation, the cancellation lowers MRR; a goodwill refund on a subscription that keeps running leaves MRR unchanged but reduces revenue and cash for the month.
How do I calculate refund rate from Stripe?
Sum the amounts of succeeded refunds in the period, from Refund objects or refund balance transactions, and divide by gross collections for the same period, with tax treated the same way on both sides. With $80,000 collected and $1,600 refunded, the refund rate is 2.0%.
What is the difference between a refund and a chargeback?
You issue a refund yourself, for an amount you choose. A chargeback, which Stripe calls a dispute, is initiated by the cardholder's bank: the money is withdrawn, a dispute fee applies, and you can only contest it with evidence. Track the two separately; they have different causes and costs.