RevenueCat manages subscriptions, and refund handling is one preference inside it. Refund Sensor is built for one job: defending refunds case by case, on real signals, across the App Store and Google Play.
Refund Sensor
Dedicated refund-defense engine
RevenueCat
Subscription platform
The moment Apple sends a CONSUMPTION_REQUEST or Google flags a chargeback for review, it gathers the transaction and consumption signals, decides the case on its own facts, and submits a data-backed response inside the store's window, then shows you the outcome in a cross-store ledger.
RevenueCat treats refunds as a platform setting: a per-app preference with per-customer overrides on Apple, and a preference through Refund Control on Google Play. Convenient if you already run RevenueCat, but it is one setting, not a per-case, evidence-backed defense.
Where RevenueCat is stronger, we say so right below.
| Capability | Refund Sensor | RevenueCat |
|---|---|---|
| Purpose-built for refund defense | Yes, all it does is defend refunds | No, it is a subscription platform |
| Apple refund defense (CONSUMPTION_REQUEST) | Yes, automatic, per case | Yes, automatic |
| Google Play chargeback defense | Yes, with evidence via the Review Refund API | Yes, a preference via Refund Control |
| Per-case, evidence-backed decisions | Yes, on price, usage, and history | No, a preset preference |
| 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-defense ledger | Yes, both stores in one ledger | No, subscription analytics only |
| Deadline-safety fallback | Yes, answers within the store's window | No, not documented |
| Flat pricing, no revenue cut | Yes, flat monthly with a free tier | No, 1% of tracked revenue |
Purpose-built for refund defense
Refund Sensor
Yes, all it does is defend refundsRevenueCat
No, it is a subscription platformApple refund defense (CONSUMPTION_REQUEST)
Refund Sensor
Yes, automatic, per caseRevenueCat
Yes, automaticGoogle Play chargeback defense
Refund Sensor
Yes, with evidence via the Review Refund APIRevenueCat
Yes, a preference via Refund ControlPer-case, evidence-backed decisions
Refund Sensor
Yes, on price, usage, and historyRevenueCat
No, a preset preferenceRefund analytics by country
Refund Sensor
Yes, built-in geography mapRevenueCat
NoRefund breakdown by reason
Refund Sensor
Yes, by Apple refund reasonRevenueCat
NoTeam members and roles
Refund Sensor
YesRevenueCat
YesCross-store refund-defense ledger
Refund Sensor
Yes, both stores in one ledgerRevenueCat
No, subscription analytics onlyDeadline-safety fallback
Refund Sensor
Yes, answers within the store's windowRevenueCat
No, not documentedFlat pricing, no revenue cut
Refund Sensor
Yes, flat monthly with a free tierRevenueCat
No, 1% of tracked revenueYou do not have to change how you run subscriptions. Forward Apple's notifications to your Refund Sensor webhook and it takes over the refund defense across both stores, no SDK, no migration, no code.
Your app
Sends store events
RevenueCat
Subscriptions
Refund Sensor
Runs the defense
Refund Sensor
Best valueFlat monthly with a free tier. No percentage of recovered money, no per-refund fee.
Start freeRevenueCat
Free up to $2,500 in monthly tracked revenue, then 1% of tracked revenue; refund handling is included.
No. Refund Sensor does one thing: refund defense. It works with whatever you use for subscriptions and takes over answering Apple's refund requests and Google Play chargebacks.
It evaluates each request on its own signals, the transaction, consumption data, price, and refund history, then responds within the store's review window and records the outcome.
Yes. It answers Apple's CONSUMPTION_REQUEST and submits evidence-backed responses to Google Play chargeback reviews through Google's Review Refund API.
Don't leave refund handling to a setting. Refund Sensor evaluates each case, responds within the store's window, and shows you exactly what happened.
RevenueCat
Refund Sensor
RevenueCat