Adapty's Refund Saver answers refund requests for apps that run their subscriptions on Adapty. Refund Sensor defends Apple refunds and Google Play chargebacks for any app, whatever handles its subscriptions, with no SDK to add.
Refund Sensor
Dedicated refund-defense engine
Adapty Refund Saver
A feature inside Adapty
Refund Sensor connects at the store and server level, with no SDK and no platform switch. When Apple's CONSUMPTION_REQUEST arrives or a Google Play chargeback goes to review, it looks at that purchase's own signals and replies inside the store's window. Every Apple refund and Google case lands in one ledger.
Refund Saver answers Apple consumption requests and Google Play chargeback reviews automatically, once both stores are connected to Adapty. You set a default refund preference for each store and can override it per user. It's convenient for Adapty customers, but it lives inside the Adapty platform. Adapty's own docs say the store preference applies to every request rather than being decided case by case.
Where Adapty Refund Saver is stronger, we say so right below.
| Capability | Refund Sensor | Adapty Refund Saver |
|---|---|---|
| Purpose-built for refund defense | Yes, defending refunds is the whole product | No, a feature of the Adapty platform |
| Apple refund defense (CONSUMPTION_REQUEST) | Yes, automatic | Yes, automatic, including a prorated-refund option |
| Google Play chargeback reviews | Yes, through Google's Review Refund API | Yes, through Google's Review Refund API |
| Works without an SDK or platform switch | Yes, connects at the store and server level | No, requires Adapty as your subscription platform |
| Decisions per case | Yes, each request judged on its own signals | Partial, one default per store, with per-user overrides |
| Refund analytics by country | Yes, built-in geography map | No, not documented for Refund Saver |
| Refund breakdown by reason | Yes, by Apple refund reason | No, not documented |
| Team members and roles | Yes | Yes |
| Refund results across both stores | Yes, one ledger for both stores | Yes, saved amount, requests, and win rate for each store and combined |
| Deadline-safety fallback | Yes, replies inside each store's window | No, not documented |
Purpose-built for refund defense
Refund Sensor
Yes, defending refunds is the whole productAdapty Refund Saver
No, a feature of the Adapty platformApple refund defense (CONSUMPTION_REQUEST)
Refund Sensor
Yes, automaticAdapty Refund Saver
Yes, automatic, including a prorated-refund optionGoogle Play chargeback reviews
Refund Sensor
Yes, through Google's Review Refund APIAdapty Refund Saver
Yes, through Google's Review Refund APIWorks without an SDK or platform switch
Refund Sensor
Yes, connects at the store and server levelAdapty Refund Saver
No, requires Adapty as your subscription platformDecisions per case
Refund Sensor
Yes, each request judged on its own signalsAdapty Refund Saver
Partial, one default per store, with per-user overridesRefund analytics by country
Refund Sensor
Yes, built-in geography mapAdapty Refund Saver
No, not documented for Refund SaverRefund breakdown by reason
Refund Sensor
Yes, by Apple refund reasonAdapty Refund Saver
No, not documentedTeam members and roles
Refund Sensor
YesAdapty Refund Saver
YesRefund results across both stores
Refund Sensor
Yes, one ledger for both storesAdapty Refund Saver
Yes, saved amount, requests, and win rate for each store and combinedDeadline-safety fallback
Refund Sensor
Yes, replies inside each store's windowAdapty Refund Saver
No, not documentedYou can keep Adapty for paywalls, analytics, and subscriptions. Adapty can forward raw Apple events to another URL. Point that forwarding at your Refund Sensor webhook, and Refund Sensor handles Apple refund defense. Google Play chargeback reviews can be covered from the same dashboard. There's no SDK to add. Before you switch, turn Refund Saver off in the Adapty Dashboard, so each case gets a single reply. Google records only the first answer it receives on a chargeback review.
Your app
Sends store events
Adapty
Subscriptions
Refund Sensor
Runs the defense
Refund Sensor
Flat monthly pricing with a free tier. No SDK, no platform switch, and no percentage of your revenue.
Start freeAdapty Refund Saver
An add-on to Adapty: free while your app earns under $5K a month, then 0.2% of monthly revenue. That's on top of Adapty's platform pricing of 1% of revenue above $5K.
No. Refund Sensor connects at the store and server level, so there's no SDK to add and no app update to ship. It works the same whether your subscriptions run on Adapty, another platform, or your own backend.
Both tools answer Apple's CONSUMPTION_REQUEST and Google Play chargeback reviews. The differences are where they run and how they decide. Refund Saver lives inside Adapty and applies one preference per store, with per-user overrides. Refund Sensor works on any stack and evaluates every Apple refund and Google case on that purchase's own signals.
Refund Sensor still replies inside the store's window using the signals it has. Its deadline-safety fallback means no request goes unanswered just because some data is missing.
Set up Refund Sensor in less time than it takes to answer one more support email about a refund you never had the chance to contest.
Adapty Refund Saver