How to handle refund requests in a subscription app

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:

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

  1. The store. App Store, Google Play or your own web checkout. This decides who can refund.
  2. 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.
  3. 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.
  4. 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:

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

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 gaps, honestly:

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.

Questions about handling refunds from your support chat? Start a chat with us.