Adapty Refund Saver only works inside Adapty, on Apple. Refund Sensor defends Apple refunds and Google Play chargebacks on any stack, with no SDK.
Refund Sensor
Dedicated refund-defense engine
Adapty Refund Saver
Apple-only, inside Adapty
It connects at the store and server level, answers Apple's CONSUMPTION_REQUEST and Google Play chargeback reviews, and decides each case on real signals inside the store's window, with no SDK or platform migration.
Adapty Refund Saver sends Apple usage data automatically to reduce refunds, but it lives inside Adapty: you enable it in the dashboard, adopt Adapty's SDK, and collect user consent, and it is Apple only (Adapty's docs note Google Play offers no consumption-data analysis for refunds).
Where Adapty Refund Saver is stronger, we say so right below.
| Capability | Refund Sensor | Adapty Refund Saver |
|---|---|---|
| Purpose-built for refund defense | Yes, all it does is defend refunds | No, a feature of Adapty |
| Apple refund defense (CONSUMPTION_REQUEST) | Yes, automatic | Yes, automatic |
| Google Play chargeback defense | Yes, via the Review Refund API | No, Apple only |
| Works without an SDK | Yes, store and server level | No, needs the Adapty SDK |
| Per-case, evidence-backed decisions | Yes, your rules, per case | No, automatic once enabled |
| Refund analytics by country | Yes, built-in geography map | No |
| Refund breakdown by reason | Yes, by Apple refund reason | No |
| Team members and roles | Yes | Yes |
| Cross-store refund ledger | Yes | No, Apple only |
| Deadline-safety fallback | Yes, answers within the store's window | No, not documented |
Purpose-built for refund defense
Refund Sensor
Yes, all it does is defend refundsAdapty Refund Saver
No, a feature of AdaptyApple refund defense (CONSUMPTION_REQUEST)
Refund Sensor
Yes, automaticAdapty Refund Saver
Yes, automaticGoogle Play chargeback defense
Refund Sensor
Yes, via the Review Refund APIAdapty Refund Saver
No, Apple onlyWorks without an SDK
Refund Sensor
Yes, store and server levelAdapty Refund Saver
No, needs the Adapty SDKPer-case, evidence-backed decisions
Refund Sensor
Yes, your rules, per caseAdapty Refund Saver
No, automatic once enabledRefund analytics by country
Refund Sensor
Yes, built-in geography mapAdapty Refund Saver
NoRefund breakdown by reason
Refund Sensor
Yes, by Apple refund reasonAdapty Refund Saver
NoTeam members and roles
Refund Sensor
YesAdapty Refund Saver
YesCross-store refund ledger
Refund Sensor
YesAdapty Refund Saver
No, Apple onlyDeadline-safety fallback
Refund Sensor
Yes, answers within the store's windowAdapty Refund Saver
No, not documentedAdapty can forward raw Apple events to another URL. Send them to your Refund Sensor webhook and it runs the defense, including the Google Play chargebacks Adapty does not cover, with no SDK to add.
Your app
Sends store events
Adapty Refund Saver
Subscriptions
Refund Sensor
Runs the defense
Refund Sensor
Best valueFlat monthly pricing with a free tier. No SDK, no platform migration, no percentage cut.
Start freeAdapty Refund Saver
Bundled into Adapty's paid plans; Refund Saver is not priced separately.
No. It connects at the store and server level, so there is no SDK to add and no app update to ship.
Both. Apple refund requests and Google Play chargeback reviews, from one dashboard.
Refund Sensor still responds inside the store's window with the signals available; its deadline-safety fallback means a request is never left unanswered just because data is incomplete.
Set up Refund Sensor in the time it takes to read one more support email about a refund you never got to contest.
Adapty Refund Saver
Refund Sensor
Adapty Refund Saver