- Platform
- Android · Google Play purchase
- Scope
- Policy and legal rights vary by purchase and jurisdiction
- Window
- Current since 17 Sept 2026
- Updated
- Last checked
Verify the order and requested outcome
Use Google Play purchase history to identify the exact MLBB transaction and account. A pending authorization, declined attempt and completed order are different states, and only the matching completed order belongs in a refund request.
Decide whether the problem is an undelivered item, an accidental family purchase or suspected fraud because Google provides different routes for those situations.
Read the live policy before submitting
Google says refund handling depends on the purchase and elapsed time and can involve Google Play or the developer. Use the linked policy at the time of the request rather than a copied deadline.
Where local law supplies additional rights, the live Google policy and applicable law control; this guide does not determine eligibility.
Submit once and keep the result
Sign in to Google's official refund workflow, select the matching order and give the accurate reason. Save the confirmation and any status reference privately.
Do not submit duplicate requests or ask a third party to log into the Google account. If Google directs the case to the developer, use MLBB's verified support route with the order evidence.
Safe stopping point
Leave with a verified status or case reference
Stop when Google records the request or directs it to the developer. Keep the order and case references and wait for the official result before opening another case.
Sources
- Google Play Help: Problems with in-app purchases
Connectivity, payment status, restart, developer support and refund sections. Checked 2026-09-17.
- Google Play Help: Apps, games, and in-app purchases refund policies
Google Play refund-policy timing and developer-contact guidance. Checked 2026-09-17.
- Google Play Help: Request a refund on Google Play
Signed-in refund request workflow. Checked 2026-09-17.