Grow your app's revenue by stopping refunds you never even saw.
Refund Sensor is an automatic refund protection service for iOS apps. It answers every Apple CONSUMPTION_REQUEST with real transaction evidence, before Apple's deadline, so the revenue you earned stays with you.
of eligible requests defended
setup · no SDK · no code changes
revenue defended to date
800+ Apps protected
on the App Store
DefendingRequested
Reviewing
Refund Sensor
Declined
Lumen
premium.yearly · $39.99
Refund rate
Money we've kept in developers' pockets, so far.
Refund revenue we've defended for developers by challenging unfair refunds, automatically.
- TTaller - Height Predictor$4,820refund protected
- QQR Code: Generator & Scanner$1,260refund protected
- OOCR Text Scanner Image To Text$3,190refund protected
- PPatna Gam Parivar$780refund protected
- VVPN Proxy - Fast and Secure$2,450refund protected
- FFind My Property: Buy & Sell$5,940refund protected
- RRock ID: Crystal Identifier$1,610refund protected
- SStreet View - Map & Navigation$990refund protected
- MMushroom Identifier By Picture$2,130refund protected
- LLive Traffic - Street View$3,560refund protected
The refunds you never see.
12 hours on Apple. 24 on Google. Miss either window, and the refund goes through.
The 12-hour window most iOS teams don't know exists
When a customer asks the App Store for a refund, Apple sends a CONSUMPTION_REQUEST via App Store Server Notifications V2 and gives you about 12 hours to reply. Ignore it and the refund goes through. Most iOS teams never even wire up the notification.
Apple expects a response before the window closes.
Chargebacks and voided purchases decided without your input
Google Play only asks for your input on chargeback reviews: about 24 hours to reply via the Review Refund API. Every other refund and voided purchase (support refunds, 48-hour Play refunds, unacknowledged trials) happens in the background. You find out once the money and the entitlement are already gone.
No real-time notification wired up.
Live defense in about five minutes.
Connect your account, paste one URL, next refund answered inside the deadline.
Step 1 · Connect your store account
Add your App Store Connect API key. We verify it, encrypt it, and list the apps you can defend so you just tick the ones you want. No SDK, no code changes, no app resubmission.
App Store ConnectIssuer ID, Key ID, and the .p8 file. Encrypted at rest.
Step 2 · Finish in App Store Connect
Paste the Server Notifications URL we generate into App Store Connect, then send Apple's test notification. Once it arrives and we verify it, your app is connected.
App Store ConnectStep 3 · We start defending
When Apple asks whether a refund is warranted, it does not wait long: you get about 12 hours. Refund Sensor responds inside that window, every time, and tracks the outcome so you can see exactly what you kept.
App StoreEverything refund tools quietly skip.
The full toolkit for defending Apple refunds, on one screen.
Answered inside Apple's deadline
Apple gives you about 12 hours to respond to a refund request. Refund Sensor replies inside that window, every time, with a decline preference and a documented reason attached.
App StoreAnswered24/7 active refund defense
Refunds land at 3am, on weekends and over holidays. A service, not a person, sends the reply before the deadline whether you are online or not. Over-cap requests are still recorded, and upgrading re-defends anything still inside Apple's window.
Every app, one dashboard
Watch and defend App Store refunds for all your apps from a single account, with no second tool and no second setup.
App StoreConnectedInbound and outbound webhooks
Inbound, we receive and verify every store notification. Outbound, we relay each verified event straight to your own systems, so your stack always stays in sync. Already have a URL wired up? Keep it and forward events to us.
For the whole team
Invite developers, managers and sales & marketing under one account, each with per-role permissions. Manage every app together, with no shared passwords and no separate logins.
One clean case per refund
Apple can fire five or six notifications for a single refund. We fold them into one timeline with the final decision, so nothing gets lost in the noise.
See why customers refund
Apple's refund reasons, broken down by app, product and country, so you can fix the real cause instead of guessing at it.
Live in minutes, no SDK
Paste your store keys and pick the apps to defend. No SDK, no code changes and no new app build to ship. You are answering refunds the same afternoon you sign up.
What we don't touch.
Encrypted keys, official APIs only. Nothing in logs.
Official App Store Server API
We respond to Apple refund requests through Apple's own server APIs, nothing unofficial.
AES-256-GCM encryption
Your store credentials are encrypted at rest and in transit with a rotating key.
No personal user data stored
We only log transaction and subscription details, never your customers' personal data.
Read-only access to your app
We never push code, change settings or touch users. Just listen for refund events and reply.
Cheaper than a single defended refund.
Straightforward refund defense pricing: one flat monthly fee, with no cut of what we recover and no per-refund charges.
Every plan covers the App Store, with encrypted credential storage and the deadline-safety fallback. Google Play chargeback defense is temporarily unavailable. Prices in USD. GST/VAT charged where applicable at checkout.
Devs who stopped losing sleep to the refunds tab.
Real notes from builders who let Refund Sensor take the boring, bruising part of shipping off their plate.
Everything you need before you decide.
A look under the hood, in plain language.
Refund Sensor automatically responds to Apple refund requests for you. The moment Apple sends a CONSUMPTION_REQUEST, it gathers the purchase and consumption evidence and submits a data-backed response through Apple's own API, no manual work, no missed deadlines.
If you don't respond inside the store's window, the platform decides with zero input from you, and the default leans toward the customer. Every ignored request is money you hand back silently. Refund Sensor makes sure you never miss that window.
Yes. Most developers never measure it, because these losses are deducted quietly from your payouts. Refund Sensor surfaces exactly how many refund requests you're receiving on the App Store and how many are contestable.
Apple gives developers an official channel to respond: the CONSUMPTION_REQUEST notification. Refund Sensor uses only this sanctioned mechanism; it doesn't bypass or trick anything.
No. Responding to a CONSUMPTION_REQUEST is exactly what Apple built the notification for, you're following their intended workflow, not gaming it. Refund Sensor submits factual purchase data, which is precisely what the stores ask you to provide.
Be cautious of any tool that promises that, because the platform always makes the final call. What Refund Sensor guarantees is that every eligible request gets a fast, evidence-backed response, which is what tips borderline cases your way and stops the easy, avoidable losses.
It pulls purchase and consumption signals from your store account and, optionally, your own app usage data, then formats them into the exact response Apple expects.
No. Refund Sensor connects at the store and server level, so there's no SDK to install and no app update to ship. You can go live without touching your codebase.
Even with no SDK, Refund Sensor uses the transaction and consumption data Apple already holds, which covers the signals Apple weighs most heavily. Adding your own usage data sharpens the response further, but it's optional, not required.
Apple App Store refund requests are fully supported today. On Apple we handle every CONSUMPTION_REQUEST. Google Play chargeback defense is temporarily unavailable, and we are not connecting new Android apps. Apps already connected stay connected, and those customers do not need to do anything.
As of August 3, 2026, Google Play shifts chargeback costs to developers: the order amount minus the service fee, plus a card-network fee that's typically $15 to $25 per case. In exchange, Google opened the Review Refund API and gives you about 24 hours to submit evidence. Google Play chargeback defense is temporarily unavailable in Refund Sensor, so please check Play Console for new chargebacks.
By default, Refund Sensor works from store-held transaction data, which doesn't require new consent.
Yes. Credentials are encrypted and used only to communicate with the store APIs on your behalf. A full legal suite, Privacy Policy, Terms of Use, DPA, Refund and Cookie policies, are already in place.
You could respond by hand, but the windows are tight and volume compounds, miss one and you lose by default. Building it yourself means owning the store-API integration, notification handling, and response logic, and maintaining all of it as Apple keeps changing the rules. Refund Sensor is that system, kept current for you.
Not right now. Apple App Store refund automation is live, and you can defend refunds within about 5 minutes of connecting. Google Play chargeback defense is temporarily unavailable, and we are not connecting new Android apps. Apps already connected stay connected, and those customers do not need to do anything.
Happy to help. Reach us at [email protected] and we'll get back to you directly.
Your refunds don't wait.
Neither do we.
Connect your app once. No dashboards to babysit, no tickets to triage, no weekend fire drills. Refund defense runs on its own across your App Store apps, so the money you earned stays yours.
By creating an account, you agree to our terms and privacy policy.