Every story verified before it goes up

Refund stories

Real cases: what happened, what the merchant said first, and what finally worked. Names shortened, personal details removed.

✓ Our case

A 7-year-old, $150 in microtransactions, and “all sales final”

What happened
A child got past the tablet passcode and made over $150 in in-app purchases.
What they said first
“Digital sales are final.”
What worked
Organizing the details into a clear, properly prepared request.
Result
Refunded in 3 days

The lesson: “All sales final” is a policy, not the last word on a purchase you never authorised.

“My 7-year-old bypassed my tablet's passcode and racked up over $150 in microtransactions. App store support said digital sales were final. Jon helped me organize the details and prepare my request. Three days later the money was back.”Jason T.
Read the app store guide → Write a request like this, free →
✓ Our case

A game that crashed on launch, auto-denied for “too much playtime”

What happened
The game crashed every time it opened. It was left running during troubleshooting.
What they said first
Refund automatically denied for exceeding the playtime limit.
What worked
Identifying the strongest points: the time on record was troubleshooting, not play.
Result
$70 refunded

The lesson: An automatic denial is a system rule, not a person's decision. Explaining what the numbers actually mean can change it.

“I bought a PC game that crashed every time I opened it. Because I'd left it running while troubleshooting, my refund was auto-denied for exceeding the playtime limit. Jon helped me identify the strongest points. I got my $70 back.”Marcus L.
Read the game refund guide → Write a request like this, free →
✓ Our case

A “30-day guarantee” with conditions nobody mentioned

What happened
Enrolled during a live launch. The 30-day guarantee turned out to have conditions that weren't mentioned upfront.
What worked
Pointing to the specific promise that wasn't kept.
Result
Refunded within a week

The lesson: Quote the exact promise. A specific broken promise is much harder to refuse than a general complaint.

“I enrolled in an online course during a live-launch push and the ‘30-day guarantee’ turned out to have conditions nobody mentioned upfront. Jon helped me point to the specific promise that wasn't kept. Refunded within a week.”Dana R.
Read the course refund guide → Write a request like this, free →
✓ Our case

Double-charged, and no way to reach a person

What happened
Charged twice for a SaaS tool her team uses.
What made it hard
Reaching an actual person at the software company.
What worked
Organizing the situation into one clear request.
Result
Duplicate charge reversed

The lesson: Billing errors are about presentation, not persuasion. Make the mistake easy to see and easy to fix.

“I was double-charged for a SaaS tool my team uses, and reaching an actual person at the software company was a nightmare. Jon helped me organize the situation into a clear request, and the duplicate charge was reversed.”Priya K.
Read the SaaS refund guide → Write a request like this, free →

What these cases have in common

Patterns across the stories above. We'll update these as more cases come in.

  • The first no usually isn't final. Two of these four were refused before they were refunded. The facts didn't change, only how they were presented.
  • Specific beats emotional. The exact charge, the exact promise, the exact timeline. Each winning request pointed at something the merchant could check.
  • One clear request beats a long argument. Every case turned on a single request built around its strongest point.

How we verify stories

✓ OUR CASE

  • We handled it ourselves, so we hold the full case file: the details, the request, and the merchant's reply.

✓ VERIFIED OUTCOME

  • Someone else's case. Before publishing, we saw the merchant's actual reply or refund confirmation, then deleted it.

No proof, no story. We never publish screenshots or receipts, to protect people's privacy. We shorten stories and remove personal details, but we never change what happened, the outcome, or what the merchant said.

Stories where the refund failed are published too. If a customer received their Refund Fairy fee back for giving feedback, their story says so. Anyone can ask us to remove their story, and we will.

Want a source we can't edit? Read our reviews on Trustpilot →

Share your refund story

Won, lost, or somewhere in between, your case could help the next person. You don't need to have used Refund Fairy.

Your story next?

See how strong your case is in 90 seconds, or write your request now. Both free.