Refund Saver

Overview

Refund Saver 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 based on the Refund Saver preferences configured for your application.

This automates the submission of the information Apple requires to evaluate refund requests and helps ensure timely responses.

Refund Saver also provides a centralized dashboard where you can monitor refund activity and review refund performance across your applications.

How It Works

Refund Saver processes Apple refund requests by combining purchase and consumption data collected through the Magify SDK, validated transaction information provided by Transaction Validator, and the Refund Saver preferences configured 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.

4. Apple Reviews the Request

Apple reviews the response submitted by Refund Saver before making the final refund decision.

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 review refund activity and 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 the purchase and consumption data 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 requires App Store Server Notifications V2 to receive CONSUMPTION_REQUEST notifications from Apple.

For setup and verification instructions, see Verify App Store Server Notifications.

Connected iOS Application

Your iOS application must be connected to your Magify organization.

Refund Saver is ready to process refund requests after all required components have been configured successfully.

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 send a test notification to your configured App Store Server Notifications endpoint. After sending the request, use the Get Test Notification Status endpoint to confirm that the notification was delivered successfully.

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

Refund Saver

After completing the required setup and verifying your App Store Server Notifications integration, you can configure Refund Saver in the Magify dashboard.

Navigate to Configuration → Refund Saver.

The Refund Saver page provides an overview of refund activity across your applications and allows you to access the dashboard for each application.

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.

Initial Setup

If Refund Saver has not yet been configured for an application, the Initial Setup page is displayed instead of the Refund Saver Dashboard.

The page displays the current integration status and the remaining configuration steps required before Refund Saver can be enabled.

Complete all required setup steps before enabling Refund Saver.

The page consists of the following sections:

Requirements
Setup Steps

Requirements

The notification banner at the top of the page highlights the integrations required to use Refund Saver.

Before enabling Refund Saver, make sure the following components are configured:

- Magify SDK

- Transaction Validator

- App Store Server Notifications V2

Setup Steps

The setup wizard guides you through the required configuration steps.

Step	Description
Set up a Transaction Validator	Configure Transaction Validator to validate App Store purchases before enabling Refund Saver.
Enable Refund Saver	Enable Refund Saver after all required prerequisites have been completed.

Completed steps are marked automatically.

The information panel on the right provides a brief overview of Refund Saver and its purpose.

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.

The dashboard consists of 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.

Metric	Description
Refunds requested	Total value of refund requests submitted by customers.
Won back refunds	Total value of refund requests that were not approved by Apple.
Won back refunds rate	Percentage of requested refund value that was retained.

These metrics provide a quick overview of refund performance for 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:

Column	Description
Requested at	Date and time when the refund request was received.
Responded at	Date and time when Refund Saver submitted a response to Apple.
Resolved at	Date and time when the final processing result became available.
Original transaction ID	Original App Store transaction identifier associated with the purchase.
Transaction ID	App Store transaction identifier associated with the refund request.
User	User associated with the transaction.
Product	Product included in the refund request.
Price	Value of the requested refund.
Rule applied	Refund Preference rule used to generate the recommendation.
Recommendation	Recommendation submitted by Refund Saver to Apple.
Store outcome	Final processing result returned by Apple.

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.

Refund Saver Preferences

Refund Saver behavior is configured through the Preferences dialog.

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

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 saving the configuration.

Refund Preference

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

The following options are available:

Preference	Description
Always decline	Refund Saver always recommends declining refund requests.
Decline first refund request, grant next ones	Refund Saver recommends declining the customer's first refund request and approving subsequent requests.
Always refund	Refund Saver always recommends approving refund requests.
No preference	Refund Saver does not include a preferred outcome in the response submitted to Apple.

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

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:

Policy	Description
Opt-out (default)	Assumes that consumption data can be shared unless the customer has explicitly opted out.
Opt-in	Assumes that consumption data cannot be shared unless explicit customer consent is available.

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

Important Notes

Refund Saver requires App Store Server Notifications V2 to receive CONSUMPTION_REQUEST notifications 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.