A SaaS refund policy is the written rule for when a subscriber gets money back: the window, full or prorated, what happens at renewal, and how to ask. Pick one model that fits what a customer costs you, clear the legal minimum in the markets you sell to, then publish the identical rule on your pricing page, checkout and terms.
Refund a 49 dollar subscription on Stripe and the processing fee from the original charge stays with Stripe. Let the same customer dispute the charge with their bank instead, and a US Stripe account also pays a 15 dollar dispute fee that is not returned even when you win. Your SaaS refund policy is the cheapest anti-chargeback tool you own. Most founders write it last, from a template, in five minutes.
This guide covers writing it once and writing it right: choosing a model that matches your cost per customer, meeting the legal floor where your buyers live, and making the promise read the same everywhere a buyer can find it. That last part is where AI-built sites slip, and no policy template mentions it.
The six questions a SaaS refund policy has to answer
A refund policy that answers fewer than six questions leaves the customer to fill in the gap, and they fill it in their favor. Every SaaS refund policy needs a position on each row below, even if the position is "no".
A refund window is the number of days after a charge during which a customer can ask for their money back and get it without having to argue a reason. Proration is refunding only the unused share of a billing period, so a customer who leaves on day 10 of a 30-day month gets back two thirds of the fee instead of all or nothing.
| Question | What you decide | What a generated template usually says | What breaks if you leave it vague |
|---|---|---|---|
| Which charges are covered? | First subscription only, or every renewal too | Nothing | A customer refunded in month 1 asks again in month 7 and quotes your own page back at you |
| How long is the window? | A number of days, counted from which charge | A number picked by the generator, often 30 | The badge on the pricing page says a different number |
| Full or prorated? | All the money back, or the unused share | "No refunds for partial periods" | Fine for business buyers, but consumer law in some markets requires charging only for days used |
| What about renewals and annual plans? | Whether a forgotten annual renewal gets refunded, and how much | Silence | Your largest refund requests, and your likeliest chargebacks, come from here |
| What about usage and credits? | Whether consumed credits or API calls are deducted | Silence | You refund someone who burned 300 dollars of model calls in a week |
| How do I ask, and how fast is it? | A channel, a response time, and when money lands | "Contact support" | The customer cannot find the channel, so they call their bank |
Six rows, about 250 words of policy. Longer than a page means it is repeating itself.
Pick a refund model that matches what a customer costs you
The right refund model follows your marginal cost. A plain subscription with near-zero cost per user can afford a generous, no-questions window. An AI product that pays for every model call cannot refund in full after heavy use without paying the customer to run up its bill. Here is the decision table I start from when a founder asks what to write.
| Your product | Refund model | Typical window | Why it fits |
|---|---|---|---|
| Flat monthly subscription, low cost per user (most indie SaaS) | Full refund on the first charge, no reason needed; after that, cancel and keep access to the end of the paid period | 7 to 14 days | A refund costs you the fee and nothing else; a fast yes is cheaper than any dispute |
| AI product with real per-use cost (LLM calls, rendering, credits) | First charge refunded minus usage, or unused credits only | 7 days, usage deducted | Protects you from refund-after-binge without turning the policy hostile |
| Annual plan | Reminder before renewal, then a prorated refund of unused months if asked soon after the renewal charge | 14 to 30 days after renewal | A customer who forgot the renewal and gets a partial refund rarely disputes; one who gets "no" often does |
| One-off or lifetime purchase | Fixed window, then final | 14 to 30 days | There is no next cycle to cancel, so the window is the whole policy |
| Sales-led contract with an order form | No self-serve refund; the contract's termination clause governs | Per contract | The signed order form beats any web page, so the web policy should point to it |
Our position for the first row, which is most of the founders reading this: make it short and unconditional. A 7-day "full refund, no reason needed" policy beats a 30-day policy with conditions attached. Every condition ("if you have not exported data", "if fewer than 10 projects were created") invites an argument, and an argument is the moment a customer decides the bank is the friendlier channel.
The legal floor: what the law sets before your policy does
This is a map of where the floor sits in the markets most indie SaaS sells to, current as of November 2026. Laws change and consumer rules depend on who the buyer is. Check with counsel before you rely on any row.
No US federal law requires SaaS refunds. Consumer law in the EU, the UK and Brazil does, for consumer buyers. In the US the risk is promising something the fine print takes back.
| Market | What the rule says | What it means for your policy | Status |
|---|---|---|---|
| European Union (consumers) | The Consumer Rights Directive gives 14 days to withdraw from a contract made online, digital services included. If the customer asked to start right away and acknowledged it, they owe a proportionate amount for the days used | A blanket "no refunds" clause does not hold against EU consumers; deducting days used can | In force; the CJEU has applied it to streaming subscriptions |
| United Kingdom (consumers) | A 14-day cooling-off period applies to online contracts today; the DMCC Act adds a second 14-day cooling-off after a renewal | Annual plans sold to UK consumers will need a renewal window too | Subscription chapter not yet in force; now expected in 2027 |
| California | The Automatic Renewal Law, amended by AB 2863 from July 1, 2025: express consent to the renewal, free-to-paid trials covered, an annual reminder, cancellation online | Not a refund law, but surprise renewals are where refund fights start; the reminder prevents most of them | In force |
| United States (federal) | The FTC click-to-cancel rule was vacated by the Eighth Circuit in July 2025; ROSCA still applies | No duty to refund, but a refund or cancel promise the terms contradict is enforcement territory | FTC restarted rulemaking in 2026 |
| Brazil (consumers) | Article 49 of the Consumer Code: 7 days to withdraw from a purchase made outside a physical store, with a full refund | Applies to online subscriptions sold to Brazilian consumers | In force since 1990 |
One distinction carries most of the weight here. Consumer law protects consumers. A founder buying a business tool on a company card usually is not one, which is why B2B SaaS has more room to set its own terms. But a self-serve checkout cannot tell a sole trader from a hobbyist, so if your product appeals to individuals at all, write to the consumer floor of your biggest market. A 7-day window works for Tabkeel because the buyer is a founder buying a tool for their product and Brazil is the home market. A consumer app selling across the EU would be under the floor with the same sentence.
Refund versus chargeback: the Stripe math
A refund is a decision you make; a chargeback is a decision the customer's bank makes for you. Both send the money back. Only one of them costs extra and goes on your record.
| Refund | Chargeback | |
|---|---|---|
| Customer gets the money | Yes, in 5 to 10 business days on most cards | Yes, often before you hear about it |
| Original processing fee | Kept by Stripe | Kept by Stripe |
| Extra fee (US account) | None | 15 USD, not returned even if you win; submitting evidence can add a second fee that is returned only on a win |
| Your time | One click in the dashboard | Assembling evidence, waiting weeks for a verdict |
| Effect on your account | None | Counts toward your dispute rate, which card networks monitor |
So the policy's real job is to make the refund path more obvious than the bank. Put the request channel inside the policy, answer within two business days, and say in the policy when the money will show up, so a customer checking their statement on day 3 does not assume you ignored them.
One rule, five places: where refund policies contradict themselves
The refund policy page is the least-read place your refund rule lives. Buyers meet it first as a line under the pricing grid, then in the FAQ, maybe at checkout, then in the terms they skim, then in the receipt. Increasingly they meet it in a chatbot answer. Every one of those has to say the same thing, with the same number, the same trigger and the same scope.
Here is how Tabkeel's own rule reads across its pages today, quoted exactly from tabkeel.com/pricing and the terms:
| Where | Exact wording |
|---|---|
| Pricing page, under the plans | "Cancel anytime, and a 7-day money-back on your first subscription." |
| Pricing FAQ | "Change your mind within 7 days of the first subscription and we refund everything. After that, cancel and it does not renew." |
| Terms, section 5 | "Within 7 calendar days of the first subscription you may withdraw and receive a full refund, per article 49 of the Brazilian Consumer Code." And: "Outside the withdrawal window, the current cycle is not refunded pro rata." |
Three wordings, one rule: 7 days, first subscription, full refund, no proration after. The pricing page also says the same thing about cancellation that the terms do: access runs to the end of the cycle already paid. When we ran the exam on our own site it read 25 pages and came back with zero findings, and the billing-integrity front was part of that pass. Sites built in a weekend often miss it, because the pricing page and the legal pages came from different chats.
The refund mismatch the billing-integrity front is built to catch looks like this:
14-day money-back guarantee. No questions asked.
All fees are non-refundable except where required by law. Refund requests are reviewed at our sole discretion.
Nobody wrote a lie. The badge came from the landing page prompt; the policy came from a template the generator reached for. Tabkeel's billing-integrity front catches this by putting both quotes side by side with the source URL on each, and hands back the correction as instructions for Claude, Cursor or v0 to carry out, not a patch:
My pricing page promises a 14-day money-back guarantee with no questions asked, but my refund policy says all fees are non-refundable and refunds are at our sole discretion. Rewrite the refund policy to grant a full refund on the first subscription charge if requested within 14 days, with no reason required, and to state that after 14 days the customer can cancel and keep access until the end of the paid period with no partial refund. Then find every other mention of refund, money-back or guarantee in the codebase (FAQ, checkout copy, emails, terms) and make each one say the same thing. List the files you changed.
The chatbot is the fifth place, and the one you cannot edit directly. Ask ChatGPT "does [your product] offer refunds?" and it answers from whichever page it happened to retrieve. If your FAQ says 14 days and your terms say 30, the buyer hears one of them, stated as fact. The fix is upstream, in making the pages agree, which is the same problem covered in controlling what ChatGPT says about your brand.
Mistakes generated refund policies ship with
- "At our sole discretion." It tells the customer there is no rule. Customers who think there is no rule do not email you; they open a dispute.
- "No refunds under any circumstances." Unenforceable against consumers in the EU, the UK and Brazil, and it reads as hostile to everyone else. If you mean "no refunds after the window", say exactly that.
- A window that matches nothing else on the site. The generator picked 30; your badge says 14; your FAQ says 7. Three numbers is worse than any one of them.
- Rules for plans you do not sell. Paragraphs about lifetime deals or enterprise invoices that never existed, copied from someone else's business. They confuse the reader and any model that reads the page.
- A dead request channel. "Email billing@" on a domain where nobody reads billing@. The request goes unanswered, and the next message the customer sends goes to their bank.
Each item is a default nobody chose, the same pattern the QA pass for an AI-built SaaS keeps finding: what the builder fills in by itself is what nobody reviews.
How to write your SaaS refund policy in one afternoon
- Name your buyers and markets. Consumers or businesses, and which countries. What goes wrong: assuming B2B when your checkout sells to anyone with a card.
- Pick one row from the model table above. What goes wrong: mixing models, a no-questions window plus a usage deduction plus a discretion clause.
- Write the six answers in plain sentences. Aim for under 300 words. What goes wrong: legal-sounding padding that a buyer, a judge and a language model all read differently.
- Copy the exact sentences everywhere the rule appears. Pricing page, pricing FAQ, the custom text on your Stripe Checkout, terms, receipt email. What goes wrong: paraphrasing, which is how 14 days becomes "two weeks" in one place and "10 business days" in another.
- Add the renewal reminder before you sell annual. What goes wrong: the first annual renewal arrives as a surprise, and so does the first chargeback.
- Recheck after every pricing change. What goes wrong: the price changes on the pricing page and nowhere else.
Step 6 is the one people skip. Before your next launch or price change, hand your domain to the exam at tabkeel.com/check: it reads the pricing page, the FAQ and the legal pages in one pass and quotes any refund or cancellation line that disagrees with another, with the most severe correction written out for free. To test only this front, the pricing versus terms checker runs on a single URL. The wider problem of the two pages drifting apart, beyond refunds, is the subject of the guide to keeping your pricing page and terms consistent, and if the same site loads trackers your legal pages never mention, your privacy policy has the same drift.
Frequently asked questions
Do SaaS companies have to offer refunds?
Not everywhere. No US federal law requires SaaS refunds, and business buyers are mostly governed by the contract. Consumers have a legal withdrawal right in some markets: 14 days in the EU and the UK for online contracts, 7 days in Brazil. If you sell self-serve to individuals in those markets, your policy cannot go below that floor.
What is a good refund window for a SaaS product?
For a flat monthly subscription with low cost per user, 7 to 14 days on the first charge with no reason required works well: short enough to stop abuse, generous enough to beat a chargeback. Selling to EU or UK consumers sets the floor at 14 days. Annual plans benefit from a separate 14 to 30 day window after each renewal charge.
Should SaaS refunds be prorated?
Prorate when the customer has used part of a long, expensive period, such as an annual plan they forgot to cancel. For monthly plans most SaaS companies refund the first charge in full within the window and do not prorate after it. EU consumer law points toward charging only for days used when a customer withdraws after asking to start immediately.
Can I write "no refunds" in my SaaS terms of service?
For business buyers, usually yes, if the pricing page and checkout say the same thing. For consumers in the EU, the UK or Brazil, a blanket no-refund clause does not override the legal withdrawal right. And anywhere, a "no refunds" clause next to a money-back badge on the pricing page is a contradiction regulators and card networks treat as misleading.
Where should a SaaS refund policy be displayed?
Everywhere the buyer decides: one line under the pricing grid, an entry in the pricing FAQ, the custom text at checkout, a clause in the terms, and the receipt email. Each place should use the same sentences with the same number of days. A standalone refund page is fine, but it is the place buyers read last.