Repository navigation
|
My app was flagged or rejected on Google Play for this. Play billing without chargeback dispute handling (developer now bears the cost). Which guideline is this, how do I find it in my project, and how do I fix it before I resubmit? |
Replies: 1 comment
|
Guideline. Play Console. Updates to refund protection and chargeback cost responsibility (support.google.com/googleplay/android-developer/answer/17068375) (Google Play) Severity in the playbook. medium What triggers it. For orders placed after 3 August 2026 Google Play no longer absorbs chargebacks. the developer bears the purchase price less the service fee plus the card-network chargeback fee (typically USD 15 to 25 per dispute). An app uses Play billing but never handles the PendingRefundReviewNotification real-time developer notification or calls the Review Refund API, so every fraudulent dispute is lost by default. Not a rejection cause, a revenue-and-fraud exposure that lands on the developer's account. What to search your code for. How to fix it. Subscribe to real-time developer notifications, handle PendingRefundReviewNotification, and call the Review Refund API within 24 hours with the refund preference and purchase-usage evidence so Google Play can contest illegitimate chargebacks. Reconcile chargeback fees in your revenue model. The guard reports this as This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run |
Guideline. Play Console. Updates to refund protection and chargeback cost responsibility (support.google.com/googleplay/android-developer/answer/17068375) (Google Play)
Severity in the playbook. medium
What triggers it. For orders placed after 3 August 2026 Google Play no longer absorbs chargebacks. the developer bears the purchase price less the service fee plus the card-network chargeback fee (typically USD 15 to 25 per dispute). An app uses Play billing but never handles the PendingRefundReviewNotification real-time developer notification or calls the Review Refund API, so every fraudulent dispute is lost by default. Not a rejection cause, a revenue-and-fraud exposure that lands on the…