Refund Saver

Overview

Refund Saver is a feature that automates the processing of Apple refund requests.

When Apple requires additional information to evaluate a refund request, Refund Saver automatically prepares and submits a response using purchase and consumption data collected through the Magify SDK and Transaction Validator. The response is generated according to the refund processing preferences configured for your application.

This eliminates manual processing, ensures timely responses, and provides Apple with the information required to review refund requests.

In addition to automating the response workflow, Refund Saver provides a centralized dashboard where you can monitor refund activity, review processing results, and analyze refund performance for your applications.

Important

Refund Saver does not approve or reject refund requests. It automatically submits consumption data together with your configured refund preference to Apple. The final refund decision is always made by Apple.


How It Works

Refund Saver automatically processes refund requests received from Apple by combining purchase and consumption data collected through the Magify SDK, validated transaction information provided by Transaction Validator, and the configuration defined for your application.

The refund processing workflow consists of the following steps.

1. Customer Requests a Refund

A customer submits a refund request for an in-app purchase or subscription through the App Store.

2. Apple Requests Consumption Information

If additional information is required before making a decision, Apple sends a CONSUMPTION_REQUEST notification through App Store Server Notifications V2.

3. Refund Saver Prepares a Response

After receiving the notification, Refund Saver automatically:

  • retrieves purchase and consumption data collected through the Magify SDK;
  • retrieves validated transaction information from Transaction Validator;
  • applies the configured Refund Preference;
  • applies the configured Default Consent Policy;
  • generates a response that complies with Apple's requirements;
  • submits the response to Apple.

No manual action is required during this process.

4. Apple Reviews the Request

Apple evaluates the submitted consumption information together with the recommendation generated by Refund Saver.

The final refund decision is always made by Apple.

5. Review the Results

After Apple completes the review, refund requests and their outcomes become available in the Refund Saver Dashboard, where you can monitor refund activity and review the final processing results.


What You'll Need

Before using Refund Saver, make sure the following components have already been configured.

Magify SDK

The Magify SDK collects purchase and consumption information required for refund processing.

Transaction Validator

Transaction Validator validates App Store transactions and provides the transaction information used by Refund Saver.

App Store Server Notifications V2

Refund Saver relies on App Store Server Notifications V2 to receive CONSUMPTION_REQUEST notifications from Apple.

Connected iOS Application

Your iOS application must be connected to your Magify organization.

Refund Saver can process refund requests only after all required components have been configured correctly.


Verify App Store Server Notifications

Before enabling Refund Saver, verify that your App Store Server Notifications endpoint can successfully receive notifications from Apple.

Apple recommends using the Request a Test Notification endpoint to confirm that your notification endpoint is configured correctly before processing production refund requests.

For implementation details, refer to Apple's official documentation:

Step 1. Request a Test Notification

Send a request to the Request a Test Notification endpoint using the appropriate App Store Server API environment.

If the request is successful, Apple returns a testNotificationToken and sends a notification with the TEST notification type to the App Store Server Notifications URL configured for your application.

Step 2. Verify the Notification Status

Use the returned testNotificationToken to call the Get Test Notification Status endpoint.

The response indicates whether Apple successfully delivered the test notification and provides details about the delivery attempt.

If the notification was not delivered successfully, review your App Store Server Notifications configuration before enabling Refund Saver.

Important

A successful test notification confirms that Apple can deliver App Store Server Notifications to your server. It does not verify Refund Saver processing or transaction validation.


Refund Saver

Navigate to:

Configurations → Refund Saver

The Refund Saver page provides an overview of refund activity across your applications and serves as the entry point for monitoring and configuring Refund Saver.

Screenshot: Refund Saver overview

The page consists of two main sections:

  • Summary Metrics
  • Applications

Summary Metrics

The summary cards display overall refund statistics across all applications available in your organization.

These metrics provide a quick overview of refund activity without opening an individual application's dashboard.

Applications

Each configured application is displayed as a separate card.

Select an application to open its Refund Saver Dashboard and configure Refund Saver settings.


Refund Saver

Navigate to:

Configurations → Refund Saver

The Refund Saver page provides an overview of refund activity across your applications and serves as the entry point for monitoring and configuring Refund Saver.

Screenshot: Refund Saver overview

The page consists of two main sections:

  • Summary Metrics
  • Applications

Summary Metrics

The summary cards display overall refund statistics across all applications available in your organization.

These metrics provide a quick overview of refund activity without opening an individual application's dashboard.

Applications

Each configured application is displayed as a separate card.

Select an application to open its Refund Saver Dashboard and configure Refund Saver settings.

Refund Saver Dashboard

The Refund Saver Dashboard provides detailed refund activity for the selected application.

To open the dashboard, select an application on the Refund Saver page.

Screenshot: Refund Saver Dashboard

The dashboard includes the following sections:

  • Summary Metrics
  • Outcome Chart
  • Filters
  • Refund Request History

Summary Metrics

The summary cards display the main refund performance indicators for the selected application.

These metrics help you evaluate how much revenue was retained during the selected reporting period.

Outcome Chart

The Outcome chart visualizes refund activity for the selected reporting period.

By default, the chart displays the following metrics:

  • Refunds requested
  • Won back refunds

The chart updates when you change the reporting period or apply a product filter.

Chart Type

Use the chart controls in the upper-right corner to switch between the available visualization types.

Refund activity can be displayed as:

  • Line
  • Bar

Filters

Use the available filters to control which refund data is displayed on the dashboard.

Date Range

Use the date range selector to display refund activity for the required reporting period.

Changing the selected period updates the summary metrics, chart, and refund request history.

Product

Use the Product filter to display refund information for a specific product.

Applying the filter updates the summary metrics, chart, and refund request history.

Refund Request History

The refund request history displays detailed information about individual refund requests.

The table includes the following columns:

Use the table to review individual refund requests together with the recommendation submitted to Apple and the final refund outcome.

Store Outcome

The Store outcome column displays Apple's final processing result for each refund request.

Because Apple independently reviews every request, the final outcome may differ from the recommendation submitted by Refund Saver.

Important

Apple always makes the final refund decision.


Refund Saver Preferences

Refund Saver behavior is configured through the Preferences dialog.

To open it, click Preferences in the upper-right corner of the Refund Saver Dashboard.

Screenshot: Refund Saver Preferences

The dialog contains the following settings:

  • Enable Refund Saver
  • Refund Preference
  • Default Consent Policy

Enable Refund Saver

Use the Enable Refund Saver switch to activate or deactivate Refund Saver for the selected application.

When enabled, Refund Saver automatically processes CONSUMPTION_REQUEST notifications received from Apple and submits responses using the configured settings.

When disabled, Refund Saver does not process incoming refund requests or submit responses to Apple.

Changes take effect after the configuration is saved.

Refund Preference

Refund Preference determines which recommendation Refund Saver includes in the response submitted to Apple.

The following options are available:

Select the option that best matches your application's refund policy.

Important

Refund Preference affects only the recommendation submitted to Apple. It does not determine the final refund outcome.

The Default Consent Policy defines which consent assumption Refund Saver uses when Apple's refund request does not contain enough information to determine whether the customer has granted permission to share consumption data.

The following options are available:

Choose the policy that matches your application's privacy requirements and consent strategy.

Note

Apple recommends using the Opt-in policy when explicit customer consent is required before sharing consumption data.


Important Notes

  • Refund Saver requires App Store Server Notifications V2 to receive refund requests from Apple.
  • Refund Saver relies on purchase and consumption data collected through the Magify SDK together with validated transaction information provided by Transaction Validator.
  • Refund Saver does not collect consumption data itself.
  • Refund Saver does not validate App Store transactions itself.
  • Refund Preference affects only the recommendation submitted to Apple.
  • Apple always makes the final refund decision.