One company, 132 names
In our lookup data, PayPal accounts for 132 distinct descriptor strings. Amazon, across its variants, accounts for 202.
Those are not counts of transactions. They are counts of *different ways the same company's billing appears on a statement* — and every one of them is a separate string that a person might fail to recognise.
The full leaderboard of descriptor-generating merchants:
| Merchant | Distinct descriptors |
|---|---|
| PayPal | 132 |
| Amazon (all variants) | 202 |
| 76 | |
| Cash App | 58 |
| Square | 55 |
| Whop | 50 |
| Apple | 43 |
| Bank of America | 34 |
| McDonald's | 27 |
Payment processors dominate it. That is the finding, and it has a specific cause.
The mechanism
When you buy from a small business, one of two things is true about how the payment settles.
The business has its own merchant account. Its own name leads the descriptor. You will probably recognise it.
The business uses a payment platform. The platform holds the merchant account, the money settles to the platform, and the platform's identifier leads the descriptor. The business name gets the remaining characters — if any.
The second case is now overwhelmingly common, because platforms removed the need for a small business to negotiate its own acquiring relationship. The side effect landed entirely on the statement: an intermediary's name where the merchant's used to be.
Reading the prefixes
Most processor descriptors follow a recognisable shape. The separator is usually an asterisk, and the useful part is what comes after it.
| Prefix you see | What it means |
|---|---|
| SQ * | Square — the text after is the business name, often truncated |
| PP* or PAYPAL * | PayPal — merchant name or the seller's PayPal account name follows |
| TST* | Toast — restaurant point-of-sale |
| WPY* | WePay |
| CASH APP* | Cash App — commonly a person-to-person transfer |
| APPLE.COM/BILL | Apple — an app, subscription or media purchase |
| GOOGLE * | Google — Play purchase, subscription or service |
Two practical warnings.
The name after the prefix may not be the trading name. Platforms often carry the account holder's legal name or their chosen account label, neither of which needs to match the shopfront.
Truncation cuts the wrong end. With the prefix consuming several characters of a short field, the merchant name is what gets cut — often to an unrecognisable fragment.
Why Amazon is its own category
Amazon's 202 descriptor variants come from a different cause: it is not one storefront but many billing surfaces — marketplace orders, digital purchases, video, groceries, the membership itself, Audible, and more. Each bills under its own descriptor, and shipments within a single order can bill separately, so one order becomes several statement lines that do not obviously belong together.
The tell is the amount pattern rather than the name: several charges on nearby dates that sum to an order total you do recognise.
Identifying a processor charge, in order of speed
- Go to the processor, not the bank. Your PayPal activity, Square receipts, or Cash App history will name the business directly. This is by far the fastest route and people reliably skip it.
- Search the post-prefix string in quotes. Exact match finds others who asked first.
- Match on amount in your email. The receipt uses the name you know.
- Check the date, allowing a day or two of drift between purchase and posting.
- Ask the bank for the full merchant name and MCC. Your bank sees fields your statement does not print.
The processors most likely to be behind a charge you cannot place
Ranked by how often they generate a descriptor somebody could not identify, the pattern is consistent: the more merchants a platform serves, the more ways its name reaches a statement.
- PayPal — used both as a checkout button on other people's sites and as a person-to-person service, so a PayPal line can be a purchase, a transfer, or a subscription billed through a third party.
- Square — overwhelmingly small physical businesses. The name after the prefix is whatever the owner typed when setting up, which may be a legal entity, a nickname, or a location.
- Cash App — usually person-to-person, which makes it the hardest to place, because the counterparty is a person rather than a business with a searchable name.
- Toast — restaurants specifically, which narrows it usefully: if you see a TST prefix, you ate somewhere.
- Apple and Google — aggregators rather than processors in the same sense, but the effect is identical. One label covers every app, subscription and media purchase across the platform.
The practical upshot is that the prefix tells you which system to go and search, and that search is nearly always faster than calling your bank.
What this means for identifying charges generally
Roughly half of the descriptors people bring us cannot be confidently traced to a merchant on the string alone, and processor prefixes are the largest single reason. It is worth internalising the consequence: a charge you cannot recognise is usually a formatting problem, not a fraud problem.
Strip the prefix and start there.