Merchant tool
Unknown charge explainer
Paste one raw descriptor and get a likely merchant read plus next step before you inspect the full statement.
Start with the free manual tool. If you want the real document view after that, analyze a statement PDF.
Choose The Right Tool
Need a billing descriptor lookup instead?
Use the billing descriptor page when the query is framed around processor or merchant descriptor terminology.
Open descriptor lookup →Need recurring-charge context?
Use recurring charges when the unknown line looks like a subscription, processor, or merchant that keeps repeating.
Open recurring-charge tool →Need the full statement context?
Use the analyzer when you want nearby transactions, repeated merchants, and full-statement patterns instead of a one-line guess.
Analyze a statement PDF →Free tool
Decode one raw descriptor before you inspect the whole statement
The explainer handles one descriptor at a time. That keeps it useful for search intent without replacing the real value of the analyzer, which is seeing the whole statement context.
Descriptor explainer
Paste one raw line from the statement. This tool is for one descriptor, not the whole document.
Card purchase, bill, or outgoing movement
Looks like an Amazon retail, marketplace, Prime, digital, or Whole Foods descriptor. Common variants: AMZN MKTP, AMAZON.COM, AMZNPrime, Amazon RETA, Amazon Digital, AMZN Digital Svcs.
Best manual read from the pasted descriptor.
Pattern-match confidence, not a guarantee.
Check Amazon order history, digital orders, Prime renewals, Subscribe & Save shipments, and family member purchases.
Usually legitimate, but the underlying merchant may be hidden or abbreviated.
Natural next step
One-line explanation first, statement-level answer next
If the descriptor still feels ambiguous, the next useful move is uploading the full statement so you can see nearby transactions, recurring merchant patterns, and all the other lines that give the charge context.
What it gives you
Fast enough for a first pass
Each tool is intentionally narrow. The job here is a clean estimate, not a fake replacement for a full statement analysis.
Built for descriptor intent
Works well for raw processor-style or abbreviated merchant descriptors that people copy straight from the statement.
Good for first-pass triage
Can hint at likely subscription or processor patterns before you do the full investigation.
Strong handoff to statement analysis
Naturally leads into the analyzer because one line is rarely enough to fully resolve a charge.
Who this is good for
This is the cleanest new merchant-intent entry point short of uploading the full statement.
People Googling random descriptors
Useful when a charge line looks cryptic and you want a fast first-pass explanation before digging deeper.
Shoppers checking suspicious charges
Good for working out whether the line looks like Amazon, PayPal, Stripe, a processor, or a recurring digital service.
Support or ops teams
Fast enough for quick customer-facing triage when you only have one line copied from a statement.
Charge-decoder content traffic
Natural bridge from merchant-code blog content into a tool with a clear path to full statement analysis.
Deeper context
How to read a bank statement descriptor
Most descriptors follow a predictable pattern. Once you know the parts, almost any line decodes in seconds.
Prefix (1–4 chars)
Identifies the card network or processor — POS, ACH, SQ*, SP*, STRIPE*, PAYPAL*, AMZN, APL*, GOOG*. This tells you the payment rail before the merchant.
Merchant name (truncated)
The actual brand, abbreviated to fit the 22-character display limit. Look for vowels dropped, dollar signs, asterisks, or numeric suffixes — they are formatting, not part of the name.
Reference / location
City, state, store number, or transaction ID. Useful for matching to a receipt — 'WALMART #4821' identifies the specific store, 'AMZN MKTP US*RT4KZ8' includes the order reference.
Phone number
Many recurring billers append a customer service line. Searching the phone number on Google often resolves the charge faster than searching the merchant name.
Deeper context
When the descriptor still looks unfamiliar
These checks resolve roughly 80% of unrecognized charges within 5 minutes.
Search the exact string in quotes
Paste the descriptor in quotes into Google. Other people's statement screenshots often surface as the top result with the brand identified.
Match the date and amount to your inbox
Search Gmail, iCloud, or Outlook for the exact dollar amount. Confirmation emails almost always include the brand name even when the bank shows a processor.
Check Amazon, Apple, and Google subscriptions
Apple.com/bill, GOOGLE *Cloud, and AMZNPrime cover most digital recurring charges. Each platform has a 'Subscriptions' page in account settings showing every active subscription.
Check recently-canceled trials
Free trials from 14–30 days ago that you forgot to cancel are the most common 'unknown' charge by volume.
Deeper context
Red flags worth disputing
Some patterns warrant skipping further investigation and going straight to a chargeback.
Multiple small auth-and-reverse charges
Card testers run small ($0.50–$5) authorizations to validate stolen card numbers. If you see several small charges from unfamiliar merchants in a single day, dispute them and request a new card.
Foreign currency you don't travel for
Charges in EUR, GBP, INR, or BRL when you never use the card abroad — especially when paired with a foreign-transaction fee — almost always indicate compromised card data.
ACH from an unrecognized merchant
ACH debits require explicit authorization. If you see a recurring ACH and never opened that account, file an unauthorized-debit dispute under Regulation E within 60 days.
Charges right after a data breach
If you used the card at a breached merchant within the last 90 days, treat any unrecognized charge as suspect and request a card replacement.
Supporting guides
Read the article version if you want more context
The tool gives you the quick read. These posts explain the thresholds, use cases, and document expectations behind the result.
FAQ