Your refund page was written for the product you sold three months ago
For the last few weeks I've been going through small SaaS launches the way a paying customer would. Pricing page first, then the terms and the refund policy. The most common problem I run into isn't a bug in the app at all. It's two pages that stopped agreeing with each other.
Some real ones, names left out. A refund policy that talks about "Pro/Team" and annual plans, while the pricing page sells Basic, Pro and Studio, monthly only, through a different checkout. A launch post that promises 40 free credits when the pricing page says 100. A homepage that says photos never leave the browser, and a privacy policy that says they reach the servers. Credit that "never expires", and terms that don't mention credit once.
None of this breaks anything on launch day. It shows up later, when a customer asks for money back and quotes the page that suits them, or when a payment dispute gets judged against the policy you actually wrote.
The fix is boring and takes maybe twenty minutes. Every time pricing changes, open the terms, refund policy, privacy policy, FAQ and your launch posts, and search each one for every plan name and every number.
I do QA for a living, mostly manual checks before launch. My last full audit ended at 36 findings across 44 of 48 checks, 4 critical. Pages that disagree don't look scary in a list like that, but they're the cheapest thing to fix before a customer quotes one back to you.
When you last changed your pricing, did the terms change the same day?
The plan-name example would make me pause before paying. If the policy doesn't mention the plan I'm choosing, I have to guess whether it covers me. Useful reminder that these mismatches can lose trust before anyone asks for a refund.