Google Play's 2026 chargeback shift: you now pay for lost disputes
For orders placed after August 3, 2026, Google Play splits chargeback costs with developers. Here's exactly how the new pendingRefundReviewNotification and orders.reviewrefund flow works, step by step — and how to automate it.
Key takeaways
- For orders placed after August 3, 2026, a lost Google Play chargeback costs the developer the purchase price (less Play's service fee) plus the financial institution's chargeback fees.
- Google now asks for your side first: a PendingRefundReviewNotification arrives through RTDN and you have 24 hours to answer via orders.reviewrefund.
- Your evidence is not just for Google. Play uses it to contest illegitimate chargebacks with the bank on your behalf.
- Evidence can include a consumption percentage and up to 1,000 usage events with timestamps, IP addresses, and coarse locations.
- Only the first response per notification counts. Later calls are silently ignored, and they still return an OK status.
- Manual review queues cannot survive a 24-hour, first-answer-wins window. The response path has to be automated end to end.
First, what this is actually about. A chargeback is not a normal refund: the customer skips you and the Play Store entirely and disputes the charge with their bank or card issuer. For years Google quietly absorbed the cost when those disputes were lost. In 2026 that changes, in both directions: Google says it prevented 3.4 billion dollars of fraud and abuse on Play in 2025 and is adding stronger guardrails, and in exchange, developers start sharing the cost of the chargebacks that do get through. The new Review Refund API is your lever in that deal: it lets you hand Google the evidence it needs to fight illegitimate disputes with the bank, on your behalf.
For orders placed after August 3, 2026, a lost chargeback is no longer Google's problem alone. Here is the official cost split:
| Orders before Aug 3, 2026 | Orders after Aug 3, 2026 | |
|---|---|---|
| Who absorbs a lost chargeback | Shared: you carry most of it | |
| What you lose | Nothing directly | Purchase price (less Play's service fee) plus the bank's chargeback fees |
| What Google covers | Everything | The service fee cost for the transaction |
| Can you contest it | No mechanism | Yes: 24-hour evidence window |
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 that requires developer review, Play sends 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.
How to respond, step by step
1. Make sure the notification can reach you
The review request arrives on the same RTDN topic as your subscription events, so RTDN must be enabled for all notification types in Monetization setup. If you only stream subscription notifications, chargeback reviews will pass you by silently.
2. Read the token, find the buyer
The notification carries two things you need: the order id and a pendingRefundToken. The token is your proof of standing; the response is rejected without it. Look the buyer up by the obfuscatedAccountId you attached with setObfuscatedAccountId at purchase time. If you never attached one, matching a chargeback to a user is guesswork, so fix that first.
3. Build the evidence and answer within 24 hours
POST to orders.reviewrefund for that order with the androidpublisher OAuth scope. The body is small:
| Field | Required | Notes |
|---|---|---|
| pendingRefundToken | Yes | Echo the token from the notification |
| sampleContentProvided | Yes | Was a trial or preview available before purchase |
| refundPreference | Yes | APPROVE, DECLINE, or NEUTRAL |
| consumptionPercentageMilliunits | No | 0 to 100000; 45200 means 45.2% |
| consumptionUsageEvents | No | Up to 1,000 events: time, IP, coarse location, description |
Each usage event can carry a consumptionTime, the IP address it happened from, a coarse location, and a free-text description up to 5,000 characters. That combination, where and when the product was actually used, is precisely what distinguishes friendly fraud from a genuine dispute.
What to do before August
- Make sure RTDN is configured for all notification types — the chargeback review arrives on the same topic as subscription events.
- Start attaching an obfuscated account id to every purchase so chargebacks can be matched to real users and their usage.
- Decide your evidence strategy: IP addresses and usage timestamps are precisely what distinguishes friendly fraud from a genuine dispute.
- Automate the response path end to end, including a fallback that fires before the deadline if no data is available.
RefundHalt ships all of it: your Play topic is provisioned automatically, your usage data becomes chargeback evidence (with IP geolocation attached), and the deadline fallback means you never lose a dispute by silence.
Frequently asked questions
- When does the Google Play chargeback change take effect?
- It applies to orders placed after August 3, 2026. Chargebacks on older orders follow the previous rules, so the financial impact phases in as new orders accumulate.
- What does a lost chargeback actually cost?
- Per Google's official policy article: the developer carries the purchase price (less Play's service fee) plus the associated chargeback fees from the financial institution, while Google continues to cover the service fee cost. On small purchases the bank's fee can exceed the price of the product.
- What evidence does orders.reviewrefund accept?
- Your verdict (approve, decline, or neutral), whether sample content was provided, a consumption percentage in milliunits, and up to 1,000 usage events, each of which can carry a timestamp, an obfuscated account id, an IP address, a coarse location, and a short description.
- Can I change my answer after submitting?
- No. Google records only the first response per notification and silently ignores everything after it, while still returning an OK status. The first answer has to be the right one.
- Is the Review Refund API mandatory?
- No, it is optional. But for orders after August 3, 2026 you are paying for lost chargebacks either way, so skipping the one mechanism that lets Google contest them on your behalf means eating the losses silently.
Sources and further reading
RefundHalt
Revenue protection for the App Store and Google Play
Keep reading
The refunds you cannot contest: what Apple and Google decide without asking you
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.
Apple's CONSUMPTION_REQUEST, explained: the 12 hours that decide your refund
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.