Don't recognize a card charge? Check the details, not just the name

You don’t have to solve the name before calling

If your card is missing, you think your account details were stolen, or you suspect a charge wasn't authorized, skip the receipt hunt. The CFPB says to contact your bank or card provider immediately when you suspect an unauthorized debit or charge (page last modified June 17, 2025). You don't need a completed spreadsheet or a merchant's explanation to make that call.

Open the issuer's app yourself or use the number on the back of your card. If the card is missing, use contact details on a statement or the issuer's official website. Don't substitute a support number from a search advertisement or an unfamiliar charge-lookup page. Tell the issuer what you noticed and ask what to do about the card as well as the transaction.

The checks below are for a name you can't place, not a reason to postpone reporting suspected unauthorized use. If that suspicion arises halfway through, stop researching and contact the issuer then.

Open the transaction, not just the list of charges

Start in the issuer's own app or online account and open the individual charge. For example, Chase's dispute help says account transaction details can include the merchant's name, phone number and your past activity with that merchant. The information available at your issuer may differ, but this is a better starting point than a shortened label in a budgeting app.

Copy the full original description, including prefixes, spaces, numbers and anything after an asterisk. Record the amount and currency, posted date, transaction date if shown, and whether the entry is pending or posted. Keep those dates separately rather than replacing one with the other. If you're working from a PDF, note its page so you can find the same line again.

Pending status is useful information, but it isn't a verdict. Chase, for example, says a credit-card charge must post before a dispute can be opened, while its same help page tells customers to call immediately if they think someone used their account without permission. A restriction on an online dispute button is not an instruction to wait before reporting a security concern. Ask your own issuer how it handles the pending entry.

Look for a purchase you remember making

A receipt is more useful than a familiar-looking company name because it gives you something independent to compare. Search your email, order history or paper receipts for the exact amount, then look at what was bought and which card was used. The FTC's credit-card guidance, dated May 2022, recommends keeping receipts so transaction details are available when a charge needs correcting.

Compare the purchase date on the receipt with the transaction date as well as the posted date. Don't reject a possible match just because the receipt and posting dates differ. Conversely, an equal amount on a nearby date is only a lead. Look for the order reference, purchase description and payment details that connect the records; don't quietly ignore a different amount or currency to make them fit.

If someone else is authorized to use the account, ask about the specific purchase without asking them to share a login or their whole purchase history. A private message with the description, amount and date is enough to start: “Do you recognize this purchase, and do you have the receipt?” Capital One's explanation, dated March 10, 2026, identifies authorized-user purchases as one reason a transaction may be unfamiliar to the main cardholder. Knowing who made a purchase helps you investigate it; a vague “maybe that was me” doesn't explain the charge.

The billing name may not be the shop name

The words on a statement need not match the sign above the door. Capital One's guide explains that a business can use a different registered name, a parent company or a third-party billing partner. That gives you possible names to compare with a receipt or order account. It does not establish that the charge belongs to a business you used.

Payment processors also have their own description formats. In Stripe's statement-descriptor documentation, a card description can combine a business prefix, an asterisk and space, and a transaction-specific suffix. Stripe says the descriptor should reflect the business's “Doing Business As” name, and warns that some banks may display the information incorrectly or not at all. The page does not show an editorial date.

So a prefix may be a useful clue to the biller, while the text after it may describe the purchase. But Stripe's format isn't a dictionary for every card transaction. An asterisk alone doesn't tell you which processor handled a payment, and a recognizable prefix doesn't tell you who authorized it. Keep both parts when asking the issuer about the entry.

One $35 receipt doesn’t explain two $35 charges

Here's a fictional example, not a report about a real merchant. Your statement has two posted USD charges, both described as RUNCLUB* OCT EVENT. You find a separate receipt dated October 8, 2026 for a $35 October event registration. It gives you a candidate purchase to investigate, but you have no second receipt.

The two charges total $70. The receipt records $35, leaving $35 beyond the value documented by that one receipt. That arithmetic does not establish an overcharge. It shows why you can't use the same receipt to explain both entries.

For entry A, the amount and nearby date make the receipt a candidate match, not confirmation that this is the charge it belongs to. Compare its order and payment details. If the link remains unclear, ask the issuer; you can also ask a business you recognize through contact details on your receipt. Entry B stays unresolved. Don't rename both entries “event registration” or delete the second as a duplicate just because their text and amounts are identical. Suspected unauthorized use goes straight to the issuer, not to the business for an explanation first.

Even if a web search returns an event with the same name and a $35 registration price, that only gives you another lead. The search result cannot connect either charge to your card or establish that you authorized it.

Use a web search to find a lead, not a verdict

A web search is optional, not a step you have to finish before calling. If you want to search the merchant wording, leave account numbers and other personal details out of the query. You're looking for a possible business to compare with your records, not a website to certify the charge as safe.

A charge-lookup page might confidently say “this is legitimate.” That statement cannot tell you who used your card or whether you allowed the payment. Don't enter card details, banking credentials or security codes to unlock an answer. If a possible merchant emerges, reach it through contact information in an existing order account or receipt rather than trusting a number supplied by that lookup page.

If the charge is still unexplained, contact the issuer rather than continuing to hunt for a reassuring search result. Say that you cannot identify it, and describe any specific reason you suspect unauthorized use. A missing receipt alone doesn't settle what happened, and neither does a familiar name.

Give the issuer the facts and ask what comes next

A short account of what you know is easier to act on than a guessed merchant name. For the fictional second charge, you could say this on the call or in the issuer's secure messaging service:

I don't recognize the $35 posted on October 12, 2026, described as RUNCLUB* OCT EVENT. There's also a $35 charge posted on October 9. I found one October 8 event receipt, which may relate to the earlier entry, but nothing explaining the second. I'm reporting the second charge because I can't identify it. Can you check the transaction details and tell me what I need to do next?

If you suspect unauthorized use, say so directly instead of using that neutral wording. Ask for a case reference, any steps needed to secure the account, and instructions for following up in writing. Don't postpone the initial contact because you haven't gathered every receipt.

Asking who a merchant is does not necessarily start a billing-error dispute. The FTC guide below says the issuer does not have to follow that dispute process if you ask only for clarification without also disputing a billing error. Tell the issuer what you're reporting and ask how to submit the right notice.

For US credit-card billing errors, don't rely on a phone call alone to preserve your dispute rights. The FTC's May 2022 guide says to write to the address for billing inquiries, not the payment address. Your letter must reach the issuer within 60 days after the first bill containing the error was sent to you. Include your name, address, account number and a description of the error in that letter to the issuer, not in a public lookup form. Send copies, not originals, of supporting documents and keep a copy of the letter. The FTC recommends certified mail with a return receipt as proof of delivery. The 60-day period is a deadline for the written notice, not time to wait before reporting a suspicious charge.

Don't apply that credit-card process to a debit-card charge. The CFPB's debit-account guidance, reviewed August 28, 2026, explains different rules, including shorter reporting periods when a card, security code or PIN is lost or stolen. Contact the bank immediately and ask which process applies, including any written follow-up it needs.

A credit-card dispute doesn't put the whole bill on hold. The FTC guide says you're still expected to pay the part that isn't in question, including finance charges on that amount. If a payment is coming due, ask the issuer which charges are under investigation and what remains payable.

Keep the unresolved entry visible

Keep the original statement line beside your notes, with the date you contacted the issuer, the case reference and the next action it gave you. Write “candidate receipt” when that's all you have, and record an explanation only when you have the supporting details. If someone else is helping, share just what they need, not a full statement or account login.

A paper note is enough for one charge. If you're tracking several, the statement review log gives you a place to keep outstanding questions; our review-log guide explains how to tie notes back to the original rows. Neither identifies merchants nor submits a report to your issuer.

We opened the linked FTC, CFPB, Chase, Capital One and Stripe pages on October 17, 2026, and independently checked the fictional amounts using Python Decimal. We did not access a live card account, test an issuer's reporting screens or identify a real charge. The example remains a candidate match and an unresolved entry, not a decision about either payment.