When a user of your app asks Apple or Google for a refund, it almost always gets granted because you never contest it with consumption and usage data. You bear the full loss.
From August 3, 2026, Google also starts billing developers the purchase price plus bank fees on chargebacks; this means not only will you lose the original purchase price, but the bank also charges you extra money for this as well, about ~$15-30 dollars per chargeback (or even more)
RefundHalt contests these refunds for you automatically, with your app user's real usage evidence.
Setting up ALL your IOS and Android apps for automatic refund protection is extremely easy; it takes less than 3 minutes, you only need to copy and paste some values. No SDK installation is required.
Refund rates across my apps and some test users went from about 9% to ~1.9%, early data shows.
What would stop you from using this?
ungreased0675•14h ago
kedv•14h ago
Apple and Google literally have APIs for developers to provide evidence (This is what RefundHalt does for developers), but like 95% of developers don't have a server to intercept these notifications and respond in time. RefundHalt does not automatically stop a refund. Apple and Google decide that; it only provides the evidence.
And yes, services like this already exist. RevenueCat responds to Apple's consumption requests for its users; Adapty has Refund Saver, there are a lot of services like this for Stripe as well.
freakynit•13h ago