This guide was originally published on the Hailbell blog.
Short answer: iOS: you can't refund App Store purchases. Apple decides. Reply fast, tell the customer how to ask Apple (or open Apple's refund sheet from your app), and send Apple consumption data if the customer agreed to it. Android: you can refund Google Play orders yourself in Play Console, so decide and do it. Your own web billing: your payment provider, your policy. In every case, look at the customer's plan and purchases before you write, answer within a day, and only offer a cheaper plan or a pause when the reason they gave makes it a fair offer.
Refund requests are easy to leave sitting. This month a founder building a support widget posted on r/microsaas that a customer's refund request reached their team's inbox marked as normal priority, sat among routine questions, and took too long (thread). They asked how others would handle it. This page is our answer for apps sold through the App Store and Google Play, where the store sits between you and the money.
Hailbell is our product, built and run by one developer, Vidur Saini. One section near the end says where it helps. The steps before it work with any inbox.
Who actually issues the refund
Checked November 17, 2026, on developer.apple.com, support.apple.com, developer.android.com and Google's Play Console and Google Play help pages.
App Store Apple handles refunds. Customers ask at reportaproblem.apple.com, or in your app through Apple's refund request sheet (beginRefundRequest, iOS 15 and later). Apple says it takes up to 48 hours to approve or deny one. When someone asks, Apple sends your server a CONSUMPTION_REQUEST notification. Then you'll get REFUND if Apple pays it, or REFUND_DECLINED if Apple says no to a request made through your app.
Google Play You can refund orders yourself in Play Console's order management, or through the Play Developer API. Refunding the latest order of a subscription removes the subscription immediately. Refunding an older order returns the money and keeps the subscription running. Google's help tells customers to contact the developer when it's been more than 48 hours since the purchase, and says the developer "can process refunds pursuant to its policies and applicable laws".
Both Cancelling isn't a refund. It stops the next renewal, and the customer keeps access to the end of the paid period. Many refund requests are really "I didn't know how to cancel".
Why refund requests get stuck
Three reasons come up again and again:
- Nobody owns them. Refunds feel like a money decision, so whoever reads the message waits for someone else to make it. Pick one person, or one rule an assistant can follow.
- You can't see the purchase. The message says "refund me", with no plan, no date and no store. You ask for a receipt, they don't reply, and two days later the request turns into a one-star review.
- The customer doesn't know which store they paid through. An iPhone user who subscribed on your website needs a different answer.
A Hacker News commenter put the App Store side bluntly: store refunds "are not that different from credit card chargebacks. They mostly happen automatically" (thread). That's mostly true, which is why your job is less about the money and more about a fast, clear answer.
1. Check four things before you reply
- The store. App Store, Google Play or your own web checkout. This decides who can refund.
- The plan and its status. Trial, active, cancelled, already refunded. A trial that converted an hour ago is a different conversation from a yearly plan in month eleven.
- The charge. When, how much, and whether it was a renewal. "I was charged and didn't expect it" after a trial ended or a yearly renewal is a common case.
- What went wrong. A bug, a missing feature, an accidental purchase, "too expensive", or a kid with a parent's phone. The reason decides whether a save is fair at all.
If your support tool doesn't show purchases, keep RevenueCat, Superwall or Play Console's order management open next to it. Ask the customer for a receipt last.
2. Reply with a template you wrote in advance
Write your policy once, in a sentence: when you refund on Google Play and your own billing, and what you say about Apple. Then keep these replies ready.
A fair request on iOS (you can't refund it, so make Apple's path easy):
Sorry about that, and thanks for telling us. App Store purchases are refunded
by Apple, not by us. You can ask here: reportaproblem.apple.com. Choose
"Request a refund" and pick this subscription. Apple usually decides within
48 hours. To stop future charges, cancel in Settings › your name ›
Subscriptions. Deleting the app doesn't cancel it.
A fair request on Google Play or web billing (you can refund it, so do):
Sorry about that. I've refunded your last payment; it should reach you
in a few days, depending on your bank. Your subscription has ended,
so you won't be charged again.
A request you decline (say why, and say what they can still do):
Thanks for writing. We refund within 14 days of a charge, and this one
was on 20 October, so I can't refund it. I've checked that auto-renew is
off, so you won't be charged again, and you keep access until 20 November.
If something in the app isn't working, tell me and I'll look at it.
On iOS a decline means little, since the customer can still ask Apple. Don't write "we can't refund you" as if that were the end of it. Point to Apple and let them decide.
3. Point people to the store's refund flow
Apple's documentation suggests calling its refund sheet "from account settings or a help menu". The system shows the purchase and a list of reasons, and the request goes to Apple. In SwiftUI it's a modifier:
// A "Request a refund" row in Settings › Help
struct RefundRow: View {
let transactionID: UInt64 // the latest transaction for this subscription
@State private var showRefund = false
var body: some View {
Button("Request a refund") { showRefund = true }
.refundRequestSheet(for: transactionID, isPresented: $showRefund)
}
}
Two things to know. The status it returns is about the request, not the refund, so don't take access away when it returns. Wait for the REFUND notification. And Apple's in-app sheet doesn't cover multiseat subscriptions; those buyers go to the web page.
On Google Play, the store's own refund flow covers roughly the first 48 hours. After that the customer is told to ask you, so a clear "Contact us" in the app matters more on Android than on iOS. When you refund in Play Console, pick the order on purpose. The latest order ends the subscription, and an older one doesn't.
4. On iOS, send Apple your side of the story
Apple says it uses "a variety of factors" to decide, including consumption data you send. When a customer asks for any kind of refund, the CONSUMPTION_REQUEST notification arrives, and you have 12 hours to answer with the Send Consumption Information endpoint. It takes things like how much of the subscription they used.
The catch is consent. Apple says you must get the customer's consent before you share their data this way, that it's separate from the App Tracking Transparency prompt, and that without consent you shouldn't respond at all. If you never asked, skip this step. If you want it, ask in plain words and record the answer per customer. If you already use RevenueCat, it can send the data for you (RevenueCat's post), and it also asks you to cover consent.
5. Turn a refund request into a save, but only when it fits
Some refund requests are really "this costs more than I use it". Those people may stay for something smaller. Others were charged by surprise, hit a bug, or bought by accident, and an offer reads as stalling. Match the answer to the reason:
- "Too expensive", still uses the app: offer a cheaper plan, such as monthly instead of yearly, or a discounted plan. On iOS, use a promotional offer, or a win-back offer once they've lapsed.
- "Not using it right now": on Google Play, pause is on by default, from one week to three months depending on the billing period. Apple has no pause, so on iOS the honest answer is to cancel and come back.
- A bug: fix it or give a date, then handle the refund anyway if they still want it.
- Surprise charge or accident: no offer. Refund it (Android, web) or send them to Apple, and tell them how to cancel.
Offer once. If they say no, process the refund or send them to the store without another try. A customer who has to fight for a refund files a chargeback or a review instead.
6. Ask for a review only after the problem is solved
If the request ended well (the bug was fixed, they took the cheaper plan, or they just thanked you for a fast refund), you can ask for a rating in the same conversation. Never make a refund depend on a review, and never ask while the refund is still open. Both stores ban incentives for ratings, and a refund that depends on a review is one. Our guide to getting more App Store reviews has the rest of the rules.
Mistakes to avoid
- Telling an iOS customer "no refunds". Apple decides, and they'll find that out. Send them to Apple politely instead.
- Refunding the latest Google Play order when you meant to keep the subscription. Refund an older order, or partly refund, if they should keep access.
- Skipping the "how to cancel" line. Without it, the same person writes again next month.
- Letting it sit. A refund request older than a day is the one that becomes a chargeback or a one-star review.
Where Hailbell helps
Hailbell is in-app support chat and push notifications for iOS, Android and web apps. For refund requests, these parts matter:
- The purchase is in the chat. Connect Superwall or RevenueCat webhooks and each conversation shows the customer's plan, whether it's active, a trial, cancelled or refunded, what they've spent and their country. A past refund shows as "Had a refund". That covers step 1 without a second tab, in the dashboard, Discord and Telegram.
- An AI that knows your refund policy and hands refunds to you. AI replies has a "Refunds and cancelling" field. The AI answers from it, for example with the Apple link and how to cancel, and when someone needs a refund or billing change it says you'll follow up and hands the chat to you. Its instructions tell it not to attach an offer to a refund request.
- Saved replies. Store the templates from step 2. The AI uses them too. With Customer's language on, a reply you write in English goes out in the customer's language.
- An offer card for step 5. When a cheaper plan fits, send a message with a button that opens one of your paywall placements. The AI can attach offers when someone says the app costs too much, but its instructions rule out refund requests, so on a refund it's your call.
- A review card for step 6. When you ask, the customer gets your message with a button to the App Store review sheet or your Play listing. With automatic asking on, a closing thanks that mentions a refund doesn't trigger it.
The gaps, honestly:
- Hailbell can't issue refunds. Google Play refunds still happen in Play Console or the Play API, and Apple's still go through Apple.
- It doesn't answer Apple's
CONSUMPTION_REQUESTor show a refund request while Apple is deciding. The chat shows a refund once Superwall or RevenueCat reports it. - Purchase details need Superwall or RevenueCat. Without them, the chat shows the device, country and anything your app passes as metadata (such as a plan name), but not purchases, spend or refunds.
- Hailbell is new, with no ticketing and no priority queue. A refund request is a chat like any other until someone answers it.
Pro is $29 a month for 10,000 monthly active users, with unlimited seats and apps. There's a 14-day trial with no card, and a 14-day money-back guarantee on the first payment: ask within 14 days, while AI replies have used under 20% of the plan's monthly AI allowance. Try Hailbell or read how purchase details work.
Questions
Can an iOS developer refund an App Store subscription?
No. Apple handles App Store refunds. The customer asks at reportaproblem.apple.com or through Apple's refund sheet inside your app, and Apple approves or denies it, usually within 48 hours. You can send Apple consumption data, with the customer's consent, to inform the decision.
Can an Android developer refund a Google Play subscription?
Yes. In Play Console's order management, or through the Google Play Developer API. Refunding the most recent order of a subscription also removes the subscription at once; refunding an older order keeps it active. Google's help tells customers to contact the developer once 48 hours have passed since the purchase.
Does cancelling a subscription give a refund?
No, on either store. Cancelling stops the next renewal and the customer keeps access until the end of the period they paid for. A refund is a separate request.
Should I offer a discount when someone asks for a refund?
Only after you know why they want one, and only when it fits the reason. Someone who was charged by surprise wants their money back, not a cheaper plan. Someone who likes the app but finds it expensive may take a cheaper plan or, on Google Play, a pause.
Where refunds sit among the other moments users quit is covered in reducing app churn with in-app support.
Top comments (0)