Subscription audit

Decoding Cryptic Charges on Your Bank Statement

Why the name on your statement rarely matches the brand you signed up with, and how to actually identify a mystery charge.

"SQ *WLNSHOP014," "PP*DIGITALSVC," "TST* Monthly Plan" — if you've ever stared at a statement line trying to figure out what you actually bought, you're not missing something obvious. Payment processors routinely display something other than the brand name you'd recognize, and there's a specific reason for it.

Why the name doesn't match

Many small and mid-sized businesses process payments through a third-party processor — Square, PayPal, Stripe, or a similar service — rather than running their own merchant account. The statement descriptor that shows up on your bank statement often reflects that processor's naming convention, an abbreviated version of the business name, or even the processor's own generic label, rather than the consumer-facing brand you interacted with. A parent company operating several consumer brands can compound this further, showing its corporate name instead of the specific product or app you're actually subscribed to.

Step 1: Search the exact text, in quotes

Copy the descriptor exactly as it appears — including asterisks, abbreviations, and numbers — and search it in quotation marks along with a word like "charge" or "subscription." Because so many people encounter the same unfamiliar descriptors, forums and consumer sites frequently have threads specifically identifying what a given code corresponds to.

Step 2: Cross-reference the amount and the date

If a text search doesn't turn up an answer, work backward from what you know: the exact amount and the day of the month it recurs. Compare that against subscriptions you know you have, including ones on old promotional pricing that might not match the "current" price you'd expect if you searched only by cost.

Step 3: Call your bank for a merchant lookup

Banks have access to more detailed merchant information than what displays on your statement or app, including the merchant's registered business name and sometimes a contact number, even when the descriptor itself is unhelpful. This is a legitimate, often underused step — call the number on the back of your card and ask specifically for a "merchant lookup" on the transaction in question.

Step 4: Check your email for a receipt around the same date

Search your inbox (including spam and promotions folders) for the exact charge amount, around the date it first appeared. Subscription receipts often arrive by email even when the on-screen confirmation was easy to miss, and the receipt will typically show the actual product name tied to a processor's cryptic billing descriptor.

Step 5: If it's still unidentified, treat it as unauthorized

If you've exhausted these steps and genuinely can't identify a recurring charge, don't let uncertainty stop you from disputing it. A charge you can't identify, after a real effort to trace it, is a legitimate candidate for a formal dispute with your card issuer — see our guide on getting a refund after an unwanted renewal for how that process works, and consider whether the charge might still be in a reversible pending state, covered in our guide to stopping a pending charge.

A pattern worth remembering

Once you identify a cryptic descriptor, write down what it actually corresponds to somewhere you'll find it again — a note in your phone, a line in a spreadsheet. The exact same unclear descriptor will very likely reappear on your next statement, and there's no reason to re-solve the mystery every month.

Common descriptor patterns worth recognizing

A few patterns show up repeatedly and are worth learning to recognize on sight: an asterisk in the middle of a name (like "SQ *" or "PP*") usually indicates the payment was processed through Square or PayPal respectively, with the text after the asterisk being the merchant's own (often abbreviated) identifier. A statement line ending in a string of numbers is often a store or location ID rather than meaningful text. And a name that looks like a completely different company than what you signed up with is sometimes the parent company or the payment processing subsidiary handling billing on the actual brand's behalf — this is common enough with newer, smaller apps that it shouldn't automatically read as suspicious on its own.

Building your own reference list over time

Every cryptic descriptor you successfully identify is one you'll never need to re-research, provided you write it down somewhere durable. A simple running note — descriptor text, what it actually is, and the date you figured it out — becomes genuinely useful after a year or two, both for your own future statement reviews and, if you ever need to explain a charge to a family member managing a shared account, a ready reference instead of starting the search from scratch.

This kind of identification work is exactly what DeadSubs automates: it reads every transaction on an uploaded statement, matches merchant descriptors to known services, and tells you specifically what each charge is and whether it looks like something you've likely forgotten about. See how it works.