RefundHalt vs Adapty Refund Saver
Refund Saver is a strong reason to be an Adapty customer. RefundHalt is for everyone else, and for the Google Play side Adapty does not cover.
The quick answer
Adapty Refund Saver automatically shares app usage information with Apple when a refund is requested, and Adapty reports refund rate reductions of up to 40 to 50 percent for apps on their platform. If your subscriptions already run on the Adapty SDK, turning it on is one click and genuinely worth it.
The catch is the first step of their own setup guide: install the Adapty SDK and use Adapty as your subscription infrastructure. If you are not an Adapty customer, Refund Saver is not a product you can buy on its own. RefundHalt is the opposite shape: no SDK, no platform migration, works with whatever stack you have, and it also answers Google Play chargeback reviews.
At a glance
| Feature | RefundHalt | Adapty Refund Saver |
|---|---|---|
| Apple CONSUMPTION_REQUEST responses | Yes, automatic | Yes, automatic |
| Google Play chargeback reviews (orders.reviewrefund) | Yes, with evidence | No, Apple refunds only |
| Requires an SDK | No | Yes, the Adapty SDK |
| Available without the platform | Yes, standalone product | No, part of Adapty's subscription platform |
| Usage evidence source | Your server (we call one endpoint) or push API | Adapty SDK session data |
| Per-case policy rules | Yes, price, usage, prior refunds, combinators | No, published rules engine |
| Deadline fallback when data is missing | Yes, always answers in time | No, t documented |
| Paywalls, A/B testing, subscription analytics | No, by design | Yes, core platform |
| Setup | Paste two values in the store console | One click, once the SDK is integrated |
Where Adapty Refund Saver is stronger
- You already run Adapty: activation is one click and the usage data flows from the SDK you already ship.
- You want refunds, paywalls, A/B tests, and analytics from a single vendor.
- Their reported results are real: public case studies show meaningful refund rate drops for platform customers.
Where RefundHalt is stronger
- You are not an Adapty customer and do not want to re-platform your subscriptions to fight refunds.
- You sell on Google Play: chargeback reviews with usage events, IP geolocation, and a written dispute statement are RefundHalt territory.
- You want your own rules deciding each case instead of a single automated behavior.
- You want the refund engine to keep working even when your data is unavailable: the deadline fallback always answers.
Already on Adapty? Keep it primary and forward events to us
Adapty's dashboard has a field for forwarding raw Apple events. Point it at your RefundHalt webhook and keep Adapty as your primary App Store Server Notifications URL. Adapty keeps powering your paywalls and analytics; RefundHalt gets the raw refund cases. Turn Refund Saver off so only one system responds.
Pricing
Refund Saver is bundled with Adapty's platform plans, which are priced on revenue tracked through the SDK. RefundHalt is a flat, standalone price: $14.99 a month or $99.99 a year, everything included, with a 7-day free trial.
Frequently asked questions
- Can I use Refund Saver without using Adapty for subscriptions?
- No. Adapty's own setup steps start with installing the Adapty SDK and using Adapty as your subscription infrastructure. Refund Saver is a platform feature, not a standalone product.
- Does Adapty Refund Saver cover Google Play?
- Their Refund Saver page describes sharing app usage information with Apple when a refund is requested. Google Play's chargeback review flow is a separate mechanism that RefundHalt automates.
- Can RefundHalt and Adapty run side by side?
- Yes. Keep Adapty primary in App Store Connect and use its raw event forwarding to send Apple's notifications to RefundHalt. Disable Refund Saver so the two systems do not both answer the same case.
Sources
Competitor information comes from public documentation and websites, verified on the date shown. Spot something outdated? Email hello@refundhalt.com and we will correct it.