- Platform
- Google Play and Google Payments
- Scope
- Reporting windows and payment-method rules vary
- Window
- Current since 17 Sept 2026
- Updated
- Last checked
Confirm whether the statement entry is from Google
Google says Play purchases use Google-related statement descriptors. Compare the date and amount with the signed-in Play order history before assigning the charge to MLBB.
A small authorization, canceled order or grouped activity can look unfamiliar while still being tied to a known account event. Keep the bank statement private.
Check family access and purchase history
Ask whether an authorized family member used the payment method and review accounts that legitimately share it. If the purchase is recognized but accidental, use Google's ordinary refund policy rather than labeling it fraud.
If the transaction is not in Google history or does not use a Google descriptor, contact the payment provider using its verified channel.
Report suspected unauthorized activity securely
For a Google transaction that remains unknown, use Google's official unrecognized-charge workflow and follow the payment-method-specific instructions shown there. Secure the Google account and payment method without sending full credentials to game support.
Save the claim reference and avoid opening parallel reports with conflicting descriptions.
Safe stopping point
Leave with a verified status or case reference
Stop when the charge is identified or an official Google or payment-provider report is created. Keep the claim reference and secure the affected account.
Sources
- Google Play Help: Charges and authorization holds
Pending charges and authorization holds. Checked 2026-09-17.
- Google Play Help: Report charges you don't recognize
Statement format, order history and reporting paths. Checked 2026-09-17.
- Google Payments Center Help: Report unauthorized charges
Charge identification and reporting destination. Checked 2026-09-17.