Refund mechanics, store policy changes, and revenue defense tactics for app developers.
Google Play automatically refunds and revokes any purchase your server does not acknowledge within three days. It is an integration failure, not a customer decision, and it is fully preventable. Here is the exact rule, why it fires, and what each lost sale really costs.
Read article
The customer who refunds again and again is not an accident. Refund abuse costs you the money back plus the compute you already spent, and both stores hand you an identity signal, Apple's appAccountToken and Google's obfuscated account ID, to tie the pattern together.
Apple and Google can both send a refund out the door while the customer keeps their purchase. Here is exactly when access is removed automatically, when your server has to do it, and the one notification most integrations never handle.
Only two refund flows ever ask for your evidence: Apple's consumption request and Google Play's chargeback review. Everything else, the 48-hour Play refund, support refunds, voided purchases, unacknowledged trials, is decided without you. Here is the full map, what you can prevent, and what you can only record.
When a customer asks Apple for a refund, Apple asks you first. Here's exactly what the CONSUMPTION_REQUEST notification contains, what Apple expects back, how to answer one end to end, and why most developers silently forfeit.
Google quietly rewrote who pays when a Play purchase gets disputed with the bank. For orders placed after August 3, 2026, a lost chargeback comes out of your pocket, and you get 24 hours to fight back. What changed, what it costs, and how to be ready.
Blanket-declining every refund is as wrong as ignoring them. A field guide to measuring what refunds cost you and writing policy rules that protect revenue and your review score at the same time.