Refund Protection
Tell Apple and Google Play how you want refund requests and chargebacks handled for your app.
Refund Protection lets Superwall answer the stores' refund questions for your app with the preference you choose. This could result in fewer refunds being issued based on the context you provide:
- App Store (iOS): Superwall responds to Apple's refund requests. See App Store.
- Google Play (Android): Superwall answers Google Play's chargeback reviews. See Google Play.
Each app has its own setting, and the App Store and Google Play settings are independent. Configuring one never turns on the other. Turning Refund Protection on requires a plan that includes it. Turning it off never does.
App Store (iOS)
Refund protection sends Apple the purchase and usage context it asks for each time someone requests a refund on your iOS app.
To open it, click Integrations in the sidebar, then Refund protection in the App Store section. The row shows for iOS apps where Superwall has made refund protection available. If you don't see it, contact Superwall support. In the legacy dashboard, it's the Refund Protection section under Settings.
Refund protection options
Choose an option in the Refund requests card. There are four:
- Do not handle (default): The default option, which means Apple will handle refunds as they see fit.
- Ask Apple to grant all refunds: This option will inform Apple to grant all refunds, regardless of the context you provide.
- Ask Apple to decline all refunds: This option will inform Apple that you wish to default to declining refunds. For example, if you have an app that has a credits-based system and a user requests a refund, you may want to try and decline that refund if the services were provided.
- Submit data and let Apple decide: This option will inform Apple that you wish to submit data to them for each refund request. This data could be used to help Apple make a more informed decision on whether to grant or decline the refund.
Your choice saves as soon as you pick it, and the page shows Enabled for any option other than Do not handle. Before you turn it on:
- You need your users' permission to share their usage data with Apple.
- Your plan has to include refund protection.
- You need an Owner, Admin or User (Legacy) role in Superwall to change it. If your project access is Restricted, you also need the Admin project role for the app's project.
Logs
The Logs card lists up to 10 of the most recent refund requests Apple sent for this app in the last 30 days:
| Column | What it shows |
|---|---|
| When | When the request arrived. Hover for the time in UTC. |
| Status | Sent, Ignored or Errored. Sent means Apple accepted Superwall's response. It isn't Apple's refund decision. |
| Transaction ID | The purchase the request is about. |
| Product | The product that was purchased. |
| Environment | Production or sandbox. |
| Reason | The reason the customer gave. It isn't Apple's decision either. |
If there are none in that time, the card says No refund protection events yet.
In-App Purchase key
Refund protection needs your app's In-App Purchase key. The App Store Connect card at the bottom of the page shows only that key:
- Missing: click Set up with Apple in the card's header, or Enter manually. If another app in your organization has a key, you can Import it instead. Set up with Apple sets up both of your app's keys, keeping any that still work, and sets the server notification URL unless the app tracks revenue with RevenueCat. See Set up with Apple.
- Saved: the card shows Connected and the key's ID, with Replace and Remove.
For more on the keys, see App Store Connect API Key and In-App Purchase Key.
Google Play (Android)
Refund Protection for Google Play is rolling out app by app. If your Android app's Refund protection page says Refund protection isn't available, contact Superwall Support to turn it on for your app.
When someone disputes a Google Play purchase with their bank (a chargeback), Google opens a refund review and asks for your preference before it decides. Superwall answers each chargeback review for your app with the response you choose, using the Google Play service account you connected for revenue tracking.
Google makes the final decision, so a response doesn't guarantee an outcome. Superwall sends Google your preference and one yes/no answer about the purchase. It never sends usage or consumption data.
For background, see Google's guide to refund and chargeback suggestions. Google Play and developers share chargeback costs for orders placed after August 3, 2026.
Requirements
- Google Play revenue tracking connected for the app, with its service account and real-time developer notifications.
- The Manage orders and subscriptions permission for that service account in Play Console. Google requires it to accept an answer. It's one of the permissions granted in step 3 of the revenue tracking setup.
- A plan that includes Refund Protection.
Set up Refund Protection
- 1
Open Refund protection
In the new dashboard at app.superwall.com, open your Android app and click Integrations in the sidebar. In the Google Play section, click Refund protection.
- 2
Choose a response
Under Chargeback reviews, choose a Response. It applies to every chargeback review for this app. See Response options.
- 3
Answer the trial question
Set Trial or sample before purchase to Yes if the app offered a free trial, a sample, or information about what it does before purchase. Otherwise, choose No. Google receives this answer with every response.
- 4
Save
Click Save changes. Both answers save together. While a response other than Do not respond (default) is saved, the Refund protection row on the Integrations page shows Enabled.
Response options
| Response | What Superwall sends Google |
|---|---|
| Do not respond (default) | Nothing. Google handles the chargeback without your input. |
| Ask Google Play to refund | A preference to approve the refund. |
| Ask Google Play to decline | A preference to decline the refund. |
| Let Google Play decide | A neutral preference, leaving the decision to Google. |
How Google Play chargeback reviews work
- Chargebacks only. Superwall answers the reviews Google opens for chargebacks. Other refund reviews aren't answered.
- 24-hour window. Google accepts an answer within 24 hours of opening the review. Superwall answers inside that window and skips reviews that are past it.
- The first answer is final. Google keeps only the first answer to a review. Changing your setting later can't replace an answer already sent.
- Changes apply from the next review. A saved setting is used from the next chargeback review on.
- One setting per app. The same response applies to every chargeback review for the app. There are no per-customer or per-segment rules.
- No activity log yet. Unlike the App Store page, the Google Play page doesn't list recent requests.
- Your webhooks are unchanged. If Google Play's notifications are forwarded to your own webhook, refund review notifications still reach it as before, whether or not Refund Protection is on.
How is this guide?