Refund defense insights and guides
Product news, deep-dives, and practical guides on App Store refunds, Google Play chargebacks, and recovering subscription revenue.
Subscription Refund Reputation: Do Refunds Hurt App Rankings and Reviews?
Refunds cost you revenue, but do they also hurt your App Store ranking and reviews? Here's how refunds connect to ASO, retention signals, and your app's reputation.
Aug 6, 2026 · 4 min read
App Store Refund History: From 2008 to Subscription Contesting
From ad-hoc refunds in 2008 to developers finally getting to contest subscription refunds in 2024, here's how App Store refund policy evolved, and why it still favors the customer.
Aug 5, 2026 · 4 min read
Google Play Voided Purchases API vs Real-Time Developer Notifications
Google Play gives developers two ways to learn about refunds: the Voided Purchases API and Real-time Developer Notifications. Here's what each does, how they differ, and why you need both.
Aug 4, 2026 · 5 min read
Apple Refund 12-Hour Window: Why Most Developers Lose Refunds by Default
You get about 12 hours to respond to an Apple refund request. It opens at any hour, and if nobody answers, the refund is usually granted by default. Here's why that window quietly costs you.
Aug 3, 2026 · 4 min read
App Store Server Notifications V2: Complete Setup Guide
App Store Server Notifications V2 is how Apple tells your server about refunds, renewals, and more. Here's what setup involves, the parts that trip developers up, and when to skip building it.
Aug 2, 2026 · 4 min read
Apple Consumption API Consent: What Apple Actually Requires
Apple's CONSUMPTION_REQUEST doesn't tell you if the customer consented, but you can't send consumption data without valid consent. Here's what Apple requires and where consent has to live.
Aug 1, 2026 · 5 min read
What Is a CONSUMPTION_REQUEST Notification? A Field-by-Field Breakdown
Apple's CONSUMPTION_REQUEST asks for structured consumption data before it decides a refund. Here's what every field means and how each one shapes the outcome.
Jul 31, 2026 · 6 min read
Apple Refund Automation: How to Automate CONSUMPTION_REQUEST Responses
When a customer requests an Apple refund, you get about 12 hours to respond to a CONSUMPTION_REQUEST. Here's how the flow works, what data to send, and how to automate it.
Jul 30, 2026 · 6 min read
A Google Play refund won't tell you, but the Voided Purchases API will
A refund on Google Play arrives silently: the charge reverses, the customer keeps using the app, and nothing changes on your end unless you check. The Voided Purchases API is where you check. Here's the API field by field, the limits that bound it, and where the money drains when it's unwired.
Jul 28, 2026 · 5 min read
The refunds nobody consults you about: what the stores settle on their own
Only two refund flows ever ask for your evidence: Apple's consumption request and Google's chargeback review. The 48-hour Play refund, support refunds, voided purchases, unacknowledged trials all decided without you. Here's the full map of what you can prevent and what you can only record.
Jul 27, 2026 · 5 min read
The repeat refunder bills you twice, and both stores hand you the tool to spot them
Someone refunding for the fourth time isn't an unhappy customer, they're running a routine, and it costs you the returned revenue plus everything you spent fulfilling the order. Apple and Google each expose an identity field that turns those incidents into a visible pattern.
Jul 26, 2026 · 5 min read
Inside Apple's CONSUMPTION_REQUEST: the half-day that settles your refund
Every App Store refund is Apple's call, but a CONSUMPTION_REQUEST gives you a fixed window to reply with facts about the purchase. Answer well and unreasonable claims get declined. Stay quiet and the customer's account is the only version Apple hears.
Jul 25, 2026 · 5 min read