Cheaper than one refund defended.
Flat monthly pricing, no percentage cut.
Every plan includes both platforms, encrypted credential storage, and the deadline-safety fallback. Prices include VAT.
The little details worth knowing.
A look under the hood, in plain language.
Refund Sensor automatically responds to Apple refund requests and Google Play chargebacks for you. The moment Apple sends a CONSUMPTION_REQUEST or Google flags a chargeback, it gathers the purchase and consumption evidence and submits a data-backed response through the store'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 and chargeback requests you're receiving and how many are contestable.
Apple and Google both give developers an official channel to respond to Apple's CONSUMPTION_REQUEST notification and Google's chargeback-response API. Refund Sensor uses only these sanctioned mechanisms; 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 and Google expect.
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 the stores already hold, which covers the signals Apple and Google weigh 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. Google Play chargeback automation goes live August 3 via Google's official review-refund API, so you're covered on both the refund and the chargeback side.
In short, developers now get a real, time-sensitive window to contest chargebacks with evidence, and, like Apple's refund window, it's easy to miss. Refund Sensor is built to handle it automatically from day one.
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 integrations, notification handling, and response logic, and maintaining all of it as Apple and Google keep changing the rules. Refund Sensor is that system, kept current for you.
Apple refund automation is available now; Google Play chargeback automation goes live August 3.
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 every store you ship to, so the money you earned stays yours.
By creating an account, you agree to our terms and privacy policy.