RevenueCat is a full platform for running subscriptions, and refund handling is one feature inside it. Refund Sensor does a single job: defending refunds across the App Store and Google Play, one case at a time, using the purchase data behind each request.
Refund Sensor
Dedicated refund-defense engine
RevenueCat
Subscription platform
When Apple sends a CONSUMPTION_REQUEST, or a Google Play chargeback goes to review, Refund Sensor pulls the transaction details for that purchase, including delivery, usage, and price. It sends a reply inside the store's deadline, then records the outcome in a ledger that covers both stores.
RevenueCat's Refund Control lets you set refund preferences by customer group, filtered by things like platform, country, or first purchase date. It replies to Apple and Google with that preference. If you already run your subscriptions on RevenueCat, it's a convenient built-in option. It sends a preference rather than per-purchase usage data.
Where RevenueCat is stronger, we say so right below.
| Capability | Refund Sensor | RevenueCat |
|---|---|---|
| Purpose-built for refund defense | Yes, defending refunds is the whole product | No, a subscription platform with refund handling built in |
| Apple refund defense (CONSUMPTION_REQUEST) | Yes, automatic, with each purchase's own data | Yes, automatic, using Refund Control policies |
| Google Play chargeback defense | Yes, delivery and usage evidence through Google's Review Refund API | Yes, a refund preference through Google's Review Refund API |
| Per-purchase usage data in replies | Yes, based on price, usage, and refund history | No, its docs say it doesn't send per-transaction consumption or usage data |
| Refund analytics by country | Yes, built-in geography map | Yes, Refund Rate chart can be segmented by country |
| Refund breakdown by reason | Yes, by Apple refund reason | No, not documented |
| Team members and roles | Yes | Yes |
| Refund-defense ledger across both stores | Yes, every case on both stores, with its outcome | Partial, granted, declined, and unresolved counts in Refund Control |
| Deadline-safety fallback | Yes, replies inside each store's window | No, not documented |
| Flat pricing, no revenue share | Yes, flat monthly, with a free tier | No, free up to $2,500 in monthly tracked revenue, then 1% of tracked revenue (refund handling at no extra cost) |
Purpose-built for refund defense
Refund Sensor
Yes, defending refunds is the whole productRevenueCat
No, a subscription platform with refund handling built inApple refund defense (CONSUMPTION_REQUEST)
Refund Sensor
Yes, automatic, with each purchase's own dataRevenueCat
Yes, automatic, using Refund Control policiesGoogle Play chargeback defense
Refund Sensor
Yes, delivery and usage evidence through Google's Review Refund APIRevenueCat
Yes, a refund preference through Google's Review Refund APIPer-purchase usage data in replies
Refund Sensor
Yes, based on price, usage, and refund historyRevenueCat
No, its docs say it doesn't send per-transaction consumption or usage dataRefund analytics by country
Refund Sensor
Yes, built-in geography mapRevenueCat
Yes, Refund Rate chart can be segmented by countryRefund breakdown by reason
Refund Sensor
Yes, by Apple refund reasonRevenueCat
No, not documentedTeam members and roles
Refund Sensor
YesRevenueCat
YesRefund-defense ledger across both stores
Refund Sensor
Yes, every case on both stores, with its outcomeRevenueCat
Partial, granted, declined, and unresolved counts in Refund ControlDeadline-safety fallback
Refund Sensor
Yes, replies inside each store's windowRevenueCat
No, not documentedFlat pricing, no revenue share
Refund Sensor
Yes, flat monthly, with a free tierRevenueCat
No, free up to $2,500 in monthly tracked revenue, then 1% of tracked revenue (refund handling at no extra cost)You don't have to change how you run subscriptions. Keep RevenueCat for purchases, paywalls, and analytics, and let Refund Sensor handle refund defense on both stores. Connect your store accounts, forward Apple's notifications to your Refund Sensor webhook, and you're set. There's no SDK, no migration, and no code. One step matters: set RevenueCat's Refund Control to "Do not respond to refund requests." That way only one tool answers each case. Google keeps just the first reply it receives, so two tools racing to answer would undercut each other.
Your app
Sends store events
RevenueCat
Subscriptions
Refund Sensor
Runs the defense
Refund Sensor
Flat monthly plans, with a free tier to start. No share of recovered revenue and no per-refund fee, so the price stays the same as your subscriptions grow.
Start freeRevenueCat
Free up to $2,500 in monthly tracked revenue, then 1% of tracked revenue. Refund Control is included at no extra cost.
No. Refund Sensor handles one thing: refund defense. Keep whatever runs your subscriptions, whether that's RevenueCat, another platform, or your own backend. Refund Sensor takes over answering Apple's refund requests and Google Play chargeback reviews. If you use RevenueCat, set its Refund Control to "Do not respond" so the two tools don't both reply.
It looks at each request on its own terms: the transaction, whether the item was delivered and used, the price, and the customer's refund history. It then sends a reply inside the store's review window and records the result. Apple and Google still make the final decision.
Both. On the App Store, it answers every CONSUMPTION_REQUEST. On Google Play, it answers each chargeback review through Google's Review Refund API, including delivery and usage evidence, within Google's 24-hour window.
A single preference can't weigh the facts of each purchase. Refund Sensor is built for defending refunds case by case: it reviews every request, replies inside the store's window, and shows you exactly what happened.
RevenueCat