Skip to content
AppDues
Log in
Contact salesSign up

Apple Refund Handling for Subscription Apps

When a subscriber asks Apple for a refund, the decision often depends on information only the app holds: what was bought and how much of it was used.

This guide explains that request-and-response loop, shows how an automated response with configurable preferences fits into it, and gives you a checklist for deciding what to do per product.

What an automated response changes

An automated handler answers the consumption request on the developer's behalf, sending the relevant customer and purchase details immediately. Instead of a manual lookup under time pressure, the response is prepared from data the subscription platform already holds.

The second half of the feature is the preference setting. Rather than a single fixed policy, the developer chooses how each request should be treated: accept automatically, decline automatically, or pass the decision to Apple with the consumption data attached. Setup is a dashboard toggle rather than an engineering project, which matters for teams without spare client-release capacity.

Choosing a refund preference: a decision checklist

The three options delegate different things, so treat the choice as a per-product policy rather than a global switch.

  • Always accept: use when the product is low-cost, the refund volume is small, and the support cost of disputes exceeds the revenue at stake.
  • Always decline: use only when you are confident the consumption data supports it for that product and you can absorb the customer-relations fallout of a hard line.
  • Let Apple decide: the middle path — you supply the evidence and Apple weighs it. This is usually the right starting point while you learn your refund patterns.

Before enabling anything, confirm three things: that the response window is covered by automation rather than a person, that you know which products are affected, and that you have a way to read the resulting refund rate afterward.

A worked example from a photo-avatar app

MyMood AI, an app that turns selfies into photorealistic avatars, is the captured example behind this feature. As the story is recorded, the developer first noted roughly $15,000 in Apple refunds over the prior 30 days on iOS and set a reminder to check again after two weeks. In the later quote attributed to that developer, the refund rate had fallen by about half after enabling automated handling, which he described as roughly $9,000 saved.

Two cautions when reading that result. First, it is one app's reported experience at a point in time, not a forecast for yours; refund behavior varies with product type, price, and audience. Second, the saving is measured against that app's own prior baseline, so the useful takeaway is the method — record a baseline, enable the change, re-measure on a fixed date — not the dollar figure.

Two different failures, two different fixes

It helps to separate two outcomes that both look like 'a refund we didn't want.'

A missed-window refund happens because no response reached Apple in time. The fix is coverage: automation, or a named person with an alert. A decided-against-you refund happens because Apple received your data and still sided with the customer. The fix is policy and evidence quality: revisit the preference for that product, or check whether the consumption data you send is complete.

If your refund rate is high, identify which of the two is dominant before changing settings. Turning up automation will not help a product whose requests are already being answered and still granted.

ConfigureTargetTest

Frequently asked questions

What happens if a developer does not respond to Apple's refund request?

Apple grants the refund by default when no consumption information arrives within the response window, regardless of how strong the case against the refund might be. That default is the main reason teams automate the response.

What are the three refund preference options?

Always accept, always decline, and let Apple decide. The first two apply a fixed outcome; the third sends the consumption data and leaves the judgment to Apple.

Does enabling refund handling require a code release?

In the described setup it is a dashboard toggle rather than a code change, so it can be turned on without shipping a new app version.

How quickly should I expect to see a change in refund rate?

The example here re-measured after two weeks and saw a meaningful drop. Treat that as one app's timeline; set your own fixed re-check date and compare against a baseline you recorded before enabling the change.