Google Play's 2026 chargeback shift: you now pay for lost disputes
For orders placed after August 3, 2026, Google passes the cost of lost chargebacks to developers. Here's how the new pendingRefundReviewNotification and orders.reviewrefund flow works — and how to automate it.
For years, Google Play quietly absorbed chargeback costs. That era ends on August 3, 2026: for orders placed after that date, a lost chargeback costs you the purchase price (minus Play's service fee) plus the chargeback fee.
The new evidence window
Alongside the cost shift, Google introduced a review mechanism that looks a lot like Apple's consumption request. When a chargeback lands, Play can send a pendingRefundReviewNotification through your Real-time Developer Notifications topic. You then have 24 hours to call orders.reviewrefund with your preference — APPROVE, DECLINE, or NEUTRAL — plus evidence: whether sample content was provided, a consumption percentage, and up to 1,000 usage events with timestamps and IP addresses.
Only your first answer counts
The API records only the first response per notification; later calls are silently ignored. Combined with the 24-hour deadline, this rewards systems that answer immediately and correctly — and punishes manual review queues.
What to do before August
First, make sure RTDN is configured for all notification types — the chargeback review arrives on the same topic as subscription events. Second, decide your evidence strategy: IP addresses and usage timestamps are precisely what distinguishes friendly fraud from a genuine dispute. Third, automate the response path end to end, including a fallback that fires before the deadline if a human hasn't decided.
RefundHalt ships all three: your Play topic is provisioned automatically, usage events you stream become chargeback evidence, and the deadline fallback means you never lose a dispute by silence.