Google Play chargeback defense.
Of all the ways money leaves a Google Play app, only one lets you argue back: a chargeback under review. Refund Sensor listens for Google's real-time notifications and sends your decline preference, with delivery and usage evidence, through the Review Refund API the moment a review opens. That's well inside Google's 24-hour window. Every other Google Play refund and voided purchase is tracked in the same dashboard as your App Store cases.
- Review Refund API
- No code changes
- Free to start
From chargeback signal to defended revenue
What changed on Google Play on August 3, 2026
For orders placed after August 3, 2026, Google Play shares chargeback costs with developers. When a buyer wins a Google Play chargeback, you now pay the order amount minus Google's service fee, plus the fee their bank or card network charges. Google covers only its own service fee. Alongside the change, Google opened the Review Refund API and gives you 24 hours to send evidence on each chargeback review. Refund Sensor answers those reviews for you, so a missed window is never the reason you lose a case.
A chargeback review is the only point where Google asks for your side. Everything else runs without you. A buyer can request a refund on Google Play within 48 hours of purchase, and Google decides on its own, usually within a day. After 48 hours, Google points them to you, the developer. Either way, a Google Play Store refund shows up only after the money and the entitlement are gone. That's a real difference from Apple, which asks developers for consumption data on most refund requests.
Refund Sensor covers both sides. It answers every 24-hour review window, and it keeps a record of each Android Play Store refund Google settles on its own. Most teams have no view of those at all. With both in one place, you can finally see where Android revenue goes and which products lose the most.
Everything you need for Android chargeback defense
Real-time developer notifications
We set up and verify Google Play's real-time developer notifications over Pub/Sub. Refund and lifecycle events reach you within seconds, not days later in a payout report.
Voided purchase tracking
Every voided or refunded purchase is logged and matched to its original order, so no Play Store refund slips past unseen. Google decides these on its own, so we record them rather than contest them.
Chargeback review defense
When a chargeback goes to review, we send your decline preference with delivery and usage evidence through Google's Review Refund API, well inside the 24-hour window. Google records only the first reply, so we make sure that reply is complete. Live now.
One dashboard for both stores
Google Play cases sit next to your App Store cases, with the same timelines, success-rate analytics, and revenue-protected reports.
No code changes
Everything runs through Play Console and Google's APIs. Nothing to add to your app, and no release to push.
Encrypted, least-privilege access
A scoped OAuth token reads financial data and manages orders, and nothing more. Secrets are encrypted at rest, and we don't collect your users' personal data.
What you need before you start
Play Console access
On the same Google account you'll connect with.
Two account permissions
"View financial data" and "Manage orders and subscriptions" for the app you want to protect.
A Google Cloud project
A home for the Pub/Sub topic that carries Google's notifications. We handle everything else.
From connect to first defended chargeback
Sign in, grant two permissions, and Refund Sensor takes it from there.
- 1
Continue with Google
In the connect wizard, choose Google Play and sign in with Google. Approve the requested access, and we store an encrypted OAuth refresh token. There's no service-account JSON file to download or rotate.
- 2
Grant Play Console permissions
In Play Console, open Users & permissions and give the connected account the two permissions listed above for this app.
- 3
Let us set up real-time notifications
Refund Sensor creates the Pub/Sub topic and push subscription in your Google Cloud project, gives Google Play permission to publish to it, and registers it as your app's notification endpoint. Nothing to paste into Play Console.
- 4
Wait for the first refund event
You can't trigger a real refund on demand, so your app card shows "Awaiting first refund event" until one arrives. If automatic setup ever fails, the card names the exact permission that's missing.
- 5
Chargebacks start defending automatically
From then on, every chargeback review gets a decline preference backed by delivery and usage evidence, and every other refund or voided purchase is tracked in your dashboard.
Google Play refund questions
Usually, yes. Chargebacks tend to be few but costly. Disputed orders often skew larger, and since August 2026 each lost case also carries a bank fee. Your dashboard separates contestable cases from the rest from day one, so you can judge the value against your own numbers rather than a benchmark.
Because Google opens a review only when a buyer disputes the charge with their bank, and that's the one case where it asks for your input. Every other Google Play refund is decided without you. It's a real difference between the stores, not a limit in Refund Sensor. One more thing to know: a Google Store refund, for hardware like a Pixel phone, is a separate process outside Play billing and isn't covered here.
No. You sign in with Google and grant two Play Console permissions. We create the Pub/Sub topic and connect notifications for you. There's nothing to paste into Play Console and no code to write.
No. You're sending a refund preference through Google's own Play Developer API, backed by factual delivery and usage evidence. That's the path Google built for this, so you're using it as intended.
Yes. Connect an app now with no card. Apple refund defense and Google Play chargeback defense are both live. Paid plans come in as your volume grows, and the pricing page has the details.
There's no way to trigger a real refund event on demand, so your app card shows "Awaiting first refund event" until one arrives. If a permission is missing, the card names it, so you're never left guessing whether the connection is live.
Yes. It's live now and runs on the same verified pipeline that already handles our App Store defense. Chargeback replies go out in real time, well inside Google's 24-hour window.
Yes. We use a scoped OAuth token that only reads financial data and manages orders, and secrets are encrypted at rest. We don't collect your users' personal data.
No. Everything happens server to server, between Refund Sensor and Google. Your app and purchase flow don't change, and customers see Google's decision the way they always have.
Defend your Google Play revenue
Connect your app now. Google Play chargeback defense is live, so you're covered from your very first refund event. It's free to start, with no credit card and no code changes.