Two companies, 119 different mystery strings
In our 2026 study of 35,171 unrecognizable charges, Google descriptors appear in 76 distinct confusing forms and Apple in 43 — both in the top ten of all companies, ahead of nearly every retailer in America.
Neither company is doing anything unusual. The confusion is built into how app-store billing works — and once you see the mechanism, these become some of the *easiest* charges to identify, because both companies keep a complete, searchable receipt trail. You just have to know it exists, and that your bank statement is the wrong place to look.
The merchant of record is not who you think you paid
When you subscribe to a meditation app, a dating service, or a cloud-storage plan through an iPhone or Android phone, the developer never touches your card. Apple or Google is the merchant of record: they charge your card, take their cut, and remit the rest to the developer.
The descriptor pipeline only carries the merchant of record's identity. So the statement says APL*APPLE.COM/BILL or GOOGLE *PAYMENT — and the thing you actually bought, the one detail that would jog your memory, never enters the payment system at all. One descriptor, a thousand possible merchants behind it.
This is the same masking pattern we documented for payment processors like PayPal and Square, with one crucial difference: the platforms keep the answer key, and they let you look at it.
Why one company still produces dozens of descriptor variants
If the platform is always the merchant, you might expect exactly one Apple string and one Google string. Our data shows 43 and 76 instead, because the descriptor mutates as it travels:
- Product lines get their own forms. A Google hardware order, a Workspace invoice, a Play purchase, and a YouTube Premium renewal each leave differently shaped lines, some with the product after the asterisk and some without.
- Banks truncate and reformat. The same charge can print as APL*APPLE.COM/BILL, APPLE.COM/BILL, or a cut-off fragment of either depending on the bank's field width — three "different" descriptors for one biller.
- Developer names leak in. Some Play Store lines carry the developer's registered business name, which often resembles neither the app nor Google.
Multiply a handful of billing systems by dozens of bank formatting habits and you get scores of variants — every one of them resolving to the same two receipt pages below.
Tracing an Apple charge in two minutes
- Go to reportaproblem.apple.com and sign in with your Apple Account. It lists every charge on the account — and you can search by the exact dollar amount when the item name means nothing to you.
- No match? Check Settings → [your name] → Subscriptions on your iPhone for renewals, including ones in a free-trial-just-ended state.
- Still no match — check the family. In a Family Sharing group with purchase sharing on, one card pays for everyone, and the organizer's statement shows charges made on other people's devices.
Tracing a Google charge in two minutes
- Read the suffix first. Google's descriptors often carry a hint after the asterisk: GOOGLE *YouTube, GOOGLE *Google One, GOOGLE *Domains — or the developer's own name for a Play Store purchase, which can make a legitimate Google-billed charge look totally unrelated to Google.
- Then open payments.google.com (or Play Store → profile → Payments & subscriptions) and match the amount and date against the full transaction list.
- As with Apple: family payment methods and kids' devices explain a large share of "I never bought this" cases.
When the answer key comes up empty
If a charge exists on your statement but in no Apple or Google account your card touches, you've likely found real fraud — commonly card testing, where stolen numbers are verified through small digital purchases before bigger ones. Our guide to small test charges covers the pattern; the short version is that the card number itself is burned, and replacing it matters more than disputing the $1.99.
Either way, the order of operations is the point. For app-store descriptors, the platform's own receipt page settles nine cases out of ten *before* you're on hold with a bank — the opposite of the untraceable codes that fill the rest of our data, where the statement is all you'll ever get.