Refund-Demand Review Replies: What Apple and Google Actually Let You Say

Here's the fact that should shape every refund-demand reply you write: on the App Store you cannot issue a refund yourself (Apple owns that, full stop), while on Google Play you can refund your own sales straight from Play Console. Promise money back in an App Store reply and you've written a check you literally can't cash, which turns one angry review into a second, angrier one when nothing lands.

"I want my money back" is one of the most common one-star triggers there is, and the one developers fumble most — either by ignoring it or over-promising. This is the template kit that gets it right on both stores: what you can say, what to never say, and how to word it so the next reader who scrolls past sees a company that handled it.

No — and that's the whole reason these replies are tricky. A review reply is a public message box, not a billing tool. You can point someone toward a refund or process one out of band, but the reply itself never moves money. The mechanics differ hard between the two stores, so get them straight before you write a word.

On the Apple App Store, you have zero ability to issue a refund. Every App Store and in-app purchase is Apple's transaction, and only Apple can reverse it. Users request refunds themselves at reportaproblem.apple.com (or the "Report a Problem" link in their receipt), and Apple decides — you can't approve it, speed it up, or guarantee it. So an App Store refund reply does two things: acknowledge the frustration, and route them to Apple while offering to fix whatever broke.

On Google Play, you can refund your own sales. Play Console's Order Management lets you issue full or partial refunds for orders on your app, within the window Google allows. So a Play reply can genuinely resolve it — but not from the public box. Move the person to email to verify the order (you can't confirm who's who from a review handle), then process the refund in the console. The reply promises the path, not the payout.

Whatever the store or the reason, a refund-demand reply runs on the same three beats — the same skeleton that works for [any negative review](/blog/how-to-respond-to-negative-app-reviews), just pointed at money. Srisopha et al. (EASE 2021) found the strongest predictors of a reply actually working were length-ratio and content similarity — matching your response to the real complaint — ahead of politeness or speed. Translation: a specific, matched reply beats a generic "sorry for the inconvenience" every time. So fill the skeleton with their exact situation, not a macro.

Five scenarios cover almost every "give me my money back" review you'll ever see. Each is a skeleton — the specific line you fill in live is what makes it land. Note which ones you can resolve directly (Play) versus route to Apple (App Store).

One refund demand a week, you handle by hand. But they cluster — a botched update, a pricing change, or a billing bug can spawn a dozen in a day, and if you sell internationally, half arrive in languages you don't speak, still demanding money back. That's the moment the careful reply above stops being feasible one at a time.

This is the gap [ReplyArgus](/features) closes. It watches your App Store and Google Play reviews in one inbox and drafts the acknowledge–route–fix reply for you, grounded in your past approved replies and a knowledge base auto-ingested from your store listing — so it already knows to send iOS refunds to Apple and Play refunds to your support flow. It drafts in the reviewer's own language across 100+ languages, both directions: a Japanese refund demand gets a fluent Japanese reply you can approve without reading the source. And it's approve-by-default — nothing goes out until you say so — the guardrail you want on anything touching money. This kit sits inside our broader [app review response templates](/blog/app-review-response-templates), and the same triage covers [answering one-star reviews](/blog/answer-1-star-reviews) generally.

Refund-demand reviews aren't the emergency they feel like — they're a routing problem with a fixed answer. Acknowledge the person, send iOS refunds to Apple and Play refunds through your own console, offer one clear next step, and fix the thing that caused it. Get the store mechanics right and you never write a check you can't cash.

[Start free — Argus drafts your first refund reply in minutes](/signup). No card, both stores in one inbox, each refund review answered with the right routing and in the reviewer's language, ready for you to approve — so a billing bug that spawns a dozen angry reviews doesn't cost you an afternoon. See where it fits your volume on [pricing](/pricing).