Google Play developer reference

Google Play chargeback protection: the complete developer guide

Google Play now lets developers send a recommendation for eligible chargebacks under refund review. The window is 24 hours, the first answer counts, and ordinary refunds are outside this process.

Direct answer

You cannot contest every Google Play refund. When Google sends a PendingRefundReviewNotification for an eligible chargeback, you have 24 hours to submit an approve, decline, or neutral suggestion with relevant usage evidence. Google makes the final decision.

Response window
24h
Eligible cases
Chargebacks
First reply
Final
Integration
Managed

Which Google Play refunds are eligible

The review-refund flow is for eligible chargebacks under Google Play’s refund review process. It is not a general appeal system for ordinary customer refunds, cancellations, or every reversed purchase.

Google identifies an eligible case by sending a PendingRefundReviewNotification through Real-time developer notifications. If that event is absent, the order is not waiting for a developer suggestion through this API.

How the review-refund API works

After the pending-review notification arrives, the developer sends a suggestion through orders.reviewrefund. The recommendation can approve the refund, decline it, or remain neutral. Google reviews the suggestion and supporting information, then makes the final decision.

Only the first suggestion is considered. A late correction cannot replace it, which makes deterministic policy and accurate matching important.

  • Approve when your policy supports the customer’s request.
  • Decline when the available purchase and usage evidence supports that recommendation.
  • Neutral when the evidence is not strong enough for either recommendation.
  • Include relevant usage events when your product records them.

The two-paste setup

RefundHalt manages the Google Cloud side in its own project. When you add an app, the backend provisions a dedicated Pub/Sub topic, authorizes Google Play to publish to it, and creates a signed push subscription to your private app webhook.

In Play Console, invite play-access@refundhalt.iam.gserviceaccount.com so RefundHalt can call the Play Developer API for your package. Then paste the generated topic name into Monetization setup under Real-time developer notifications. You never need to open Google Cloud or download a service-account key.

How RefundHalt answers in time

The 24-hour clock starts with Google’s pending-review notification. RefundHalt validates the signed delivery, matches the order, applies your default policy plus ordered rules, submits the first suggestion, and records the final result.

Every eligible request is handled automatically. There is no manual-review queue that can miss the deadline while waiting for a teammate.

Important limits and cost changes

Google decides the outcome. A decline suggestion is evidence, not a guaranteed win, and the process only applies when Google marks the chargeback as eligible for review.

Google’s developer policy says that for applicable orders placed on or after August 3, 2026, developers may be responsible for the refunded amount plus the chargeback fee when a chargeback is lost. Confirm the current policy in Play Console and the official support documentation.

Official sources

This guide was last verified on July 17, 2026. Store policies and APIs can change, so use the primary documentation below as the final authority.