Skip to content
AppDues
Log in
Contact salesSign up

Automating Apple Refund Requests: Consumption Data and Handling Preferences

When a customer asks Apple for a refund, the developer is not a passive bystander. Apple opens a short window in which you can supply context about how the purchase was used, and that context can change the outcome. This guide explains the CONSUMPTION_REQUEST flow, the data worth sending, and the four handling preferences that determine whether an automated system answers on your behalf.

What Apple asks for and why the clock matters

A refund request triggers a CONSUMPTION_REQUEST notification delivered through the App Store Server Notifications API. You then have twelve hours to reply with consumption information — signals about the customer's activity and purchase history — by calling the Send Consumption Information endpoint. Apple weighs that context in its decision.

The failure mode is quiet. If nobody answers, or the reply arrives after the window closes, Apple frequently grants the refund by default. Many teams are unaware the notification exists at all, so even weak refund claims can succeed simply because no one responded in time.

The consumption data worth sending

Useful context falls into four buckets. An automated system already holding monetization data can assemble them without extra engineering:

  • Tenure: how long the customer has used the app.
  • Consumption degree: how much of a purchase has been used — for example, six months into an annual subscription counts as roughly 50% consumed.
  • Lifetime spend: total customer spend across platforms.
  • Lifetime refunds: refunds already granted to that customer across platforms.

A manual implementation can also include time spent in the app, content accessed or completed, purchase frequency, and refund history where available. The notification payload carries fields such as consumptionRequestReason that help you decide what to include.

Choosing a refund handling preference

In the dashboard, open Projects, select your iOS App Store entry, and scroll to the refund handling section. Four options are available, and the default is to do nothing:

  • Submit consumption data and let Apple decide: all required properties are sent, with no refund preference attached.
  • Always prefer granting refunds: data plus a preference to approve.
  • Always prefer declining refunds: data plus a recommendation to decline.
  • Do not handle: no response is sent at all.

Apple takes the developer's stated preference into account, so pick deliberately rather than leaving the default in place. Before enabling any option that shares consumption data, note that Apple requires you to have customer consent and to outline this in your terms and conditions. {{OWNER_CONSENT_TERMS_LANGUAGE}}

Measuring whether it works

The App Store Refund Requests Chart breaks requests down by granted, declined, and unresolved, and shows how those counts move over time. Set a handling preference and watch the trend from that date forward to see the effect.

A captured example illustrates the shape of the change: Dipsea began tracking consumption requests on October 18, then started replying with the "let Apple decide" preference on October 23. Its refund rate had been steady at 3%; within 15 days it fell to 1.9% — a 36% reduction in refund rate, saving hundreds of dollars — and that result came without a decline preference. Outcomes vary, and selecting "Always prefer declining refunds" may produce a stronger effect because Apple considers that input.

Building the response yourself

If you would rather not use a platform, the manual path has five steps:

  1. Stand up a secure server endpoint that receives App Store Server notifications.
  2. On each CONSUMPTION_REQUEST, inspect the payload — including consumptionRequestReason — to understand the request.
  3. Compile usage data: time in app, content accessed, lifetime purchase history, refund history.
  4. Send the response via the Send Consumption Information endpoint within the 12-hour window; automate this if volume is high.
  5. Log every request and track response time so you can prove reliability.

Apple's documentation covers each field and provides example payloads.

Streamline refund management and keep your focus on growth

Refund requests do not have to pull attention away from your roadmap or erode revenue. With an automated reply to Apple's CONSUMPTION_REQUEST notifications, the routine work disappears: no manual responses, no lost time, and — most importantly — no preventable refunds slipping through because a deadline passed unnoticed. That holds whether you are a solo developer or running a growth team; a dependable system for these requests frees you to keep delivering value to customers and growing the app.

To turn it on, open the handling preferences in your dashboard, choose the setting that matches your refund policy, and let the automation answer from there.

Frequently asked questions

What happens if I miss the 12-hour window?

Apple often grants the refund by default when no timely response arrives. Automating the reply is the reliable way to avoid that outcome at volume.

Do I need customer consent to share consumption data?

Yes. Apple requires that you have consent to share consumption data, and you should document it in your terms and conditions.

Does the handling preference guarantee a refund outcome?

No. Apple makes the final decision. The preference is an input it considers, not a binding instruction.