What this variant means
This registry groups this wording with GOOGLE *SVCS; check the identity evidence before treating it as the same merchant.
GOOGLE *SVCS suggests a Google-related payment, but the inspected Google documentation does not map SVCS to one product. Compare Google payments and Play purchase records, account by account. A Google prefix cannot establish that you authorized the payment or that it is a subscription.
What do the parts of GOOGLE *GOOGLE PLAY mean?
- GOOGLE *
- A payment-processor prefix this registry groups under GOOGLE* charges. The text after the asterisk usually names the specific business or product. Prefix guide →
A prefix is less specific than a purchase record
Google’s payments help says its product charges start with Google. Its Play guidance lists developer-name, app-name and content-type descriptors. Those examples do not document this page’s exact SVCS suffix or establish that every Google product uses one unified billing line.
Begin with Google payments Subscriptions and services and open the relevant product’s transactions. For a possible Play purchase, also check Play order history. Record which account and product contains a match rather than assuming one account shows every payment made using your card.
Sources for this section: Google: report unauthorized payments · Google Play: charges you do not recognize. See the claim limits below.
Check pending entries before calling them duplicates
Google explains that a canceled purchase or a recently added card can leave a pending authorization. Some purchases can show an authorization alongside the charge. Check the bank’s status for each entry and compare the actual order history if two payments appear to have posted.
Illustrative example: a $2.99 pending entry beside a $2.99 posted debit is a different problem from two posted $2.99 debits. Neither pattern identifies the service from price alone. Ask the issuer whether the pending entry is an authorization and use the product’s order record to assess any duplicate.
Sources for this section: Google: report unauthorized payments. See the claim limits below.
Report unexplained activity through the right product
Google suggests checking whether family or friends with account or card access made a purchase. If you still believe the payment was unauthorized, use its product-specific reporting flow and notify the payment provider. Google Play’s reporting periods depend on the payment method; they are provider-process limits, not a substitute for the issuer’s applicable rights.
Refund eligibility and unauthorized-charge reporting depend on the product and transaction. Use the current route linked from the official product help page, and save the claim reference and response. The GOOGLE prefix alone does not establish an automatic refund entitlement.
Does GOOGLE *SVCS tell me which app charged me?
The inspected documentation does not define SVCS. Use the product transaction history or request expanded merchant details from the issuer.
What if there is no matching Google Play order?
Check other Google products and accounts. If the purchase is not in Play history, do not apply a Play policy to it merely because the entry begins with Google.
Sources for this section: Google: report unauthorized payments · Google Play: charges you do not recognize. See the claim limits below.
Frequently asked questions
Is GOOGLE *GOOGLE PLAY the same as GOOGLE *SVCS?
The registry groups GOOGLE *GOOGLE PLAY with GOOGLE *SVCS, but their shared merchant identity is unconfirmed. Ask your issuer for the merchant or ACH originator details and compare the amount and date with your own records.
The original descriptor
This line is a variant of GOOGLE *SVCS in this registry. Read the evidence limits in the full entry and confirm the relationship with your issuer.
Part of a family
GOOGLE *SVCS is one of the GOOGLE* charges and Bank of America statement codes and Wells Fargo statement codes registry groups. A shared group does not establish who billed your transaction.
Independent reference — not affiliated with Google LLC. Billing names and policies change; verify with the merchant or your bank before acting.
Sources and evidence
Sources may support different parts of this page. A company homepage does not establish a statement descriptor, refund policy or contact detail. Check the claim notes and your own receipt before acting.
Descriptor identity unconfirmed · Checked 2026-10-08
Reviewed the retained entry against the cited official pages. Removed unsupported prices, transaction-suffix meanings, authorization assurances and copied actions; exact source scope and remaining identity limits are recorded.
- Official Google examples support the prefix but do not identify the SVCS suffix.Sources: Google: report unauthorized payments (checked 2026-10-08) · Google Play: charges you do not recognize (checked 2026-10-08)
- Pending authorizations differ from posted duplicate payments.Sources: Google: report unauthorized payments (checked 2026-10-08)
- Use the product-specific process; no universal automatic refund eligibility.Sources: Google: report unauthorized payments (checked 2026-10-08) · Google Play: charges you do not recognize (checked 2026-10-08)
- Google: report unauthorized payments https://support.google.com/paymentscenter/answer/9074244?hl=en
Google prefix, product/account purchase checks and authorization examples. · Checked 2026-10-08
- Google Play: charges you do not recognize https://support.google.com/googleplay/answer/2851610?hl=en
Play descriptor examples, order-history check and payment-method-specific reporting routes. · Checked 2026-10-08
Descriptor identity unconfirmed · pending · About UnknownCharges