The short answer: most charges people do not recognize turn out to be legitimate purchases hiding behind a confusing descriptor, a billing aggregator, a family member's purchase, or a forgotten trial. Disputing a legitimate charge as fraud can backfire — the merchant's evidence will show delivery to your account, and a pattern of such disputes can hurt future claims. Work this checklist first; it takes ten minutes and it decides whether your next step is a merchant refund, a cancellation, or a fraud report.
Some of the most-searched “unknown charge” descriptors are aggregators, not merchants: app-store billing (Apple, Google) that groups many apps under one name; payment processors (PayPal, Stripe, Square) that show the processor instead of the seller; and marketplace or delivery platforms that bill under the platform name. If the descriptor is an aggregator, log into that aggregator's order history — the underlying purchase is listed there, with the seller's name and the item. That one step identifies a large share of mystery charges.
Before reporting fraud, ask everyone who uses your devices or saved cards: children buying in-game items, a partner's subscription, a family member using a shared streaming account. This matters beyond embarrassment — if a purchase was made on a shared device with a saved card, a fraud dispute built on “I never authorized this” will run into the merchant's device and delivery evidence (and, for Visa card-absent fraud claims, the CE 3.0 history rule). A family purchase is a refund-or-cancel problem, not a fraud problem, and handling it as one keeps your dispute record clean.
If the checklist comes up empty, treat it as unauthorized: lock or freeze the card immediately, call the bank the same day, and follow up in writing the same day (see our calling-vs-writing guide — for credit cards, the FCBA's 60-day written window is what protects you). For credit cards, federal law caps your unauthorized-use liability at $50 and most issuers waive even that. For debit cards, report speed decides your liability tier ($50 within 2 business days of learning of the loss, up to $500 within the 60-day statement window, potentially unlimited after it) — so do not spend days investigating a charge you are sure is fraud.
Keep the fraud report factual: “I do not recognize this charge, I did not authorize it, and no one in my household did” — if that last part is not true, do not say it. A false fraud claim is itself a problem: banks treat it as friendly fraud, and a pattern of false claims can lead to account closure and, in serious cases, legal consequences.
If you identify the charge but it is wrong — duplicate, wrong amount, cancelled subscription still billing, item never delivered — the route is a merchant dispute, not a fraud report: contact the merchant first for a refund, then file a chargeback under the right reason code (duplicate, cancelled recurring, services not rendered) within the network's roughly 120-day clock. Use the Do I Have a Case? Checker to test which route fits, and the Deadline Calculator to check the clock before it closes.
Work the checklist: match amount and date over a two-week window, search the descriptor in your email, check the aggregator's order history (Apple, Google, PayPal), and ask household members. Most mystery charges are identified within ten minutes.
Not until you have checked. A fraud dispute on a legitimate purchase will meet the merchant's delivery and device evidence and fail — and a pattern of such disputes damages your credibility for genuine claims. Identify first, then choose fraud vs merchant dispute.
Usually not — pending transactions are authorization holds, not final charges. Wait for it to post or drop off. The exception is fraud: if you are sure the card is compromised, lock the card and report it immediately rather than waiting.
No — it is an unauthorized-by-you purchase, but not third-party fraud in the bank's sense, and the merchant's records will show delivery to your account and device. Contact the merchant or platform for a refund first (app stores have family-purchase refund routes) rather than filing a fraud dispute.
Sources (checked October 26, 2026): Fair Credit Billing Act, 15 U.S.C. §§ 1666, 1643 (written billing-error notice, $50 unauthorized-use liability cap); Regulation E, 12 CFR §§ 1005.6, 1005.11 (liability tiers by reporting speed, error-notice rules); Visa Compelling Evidence 3.0 (device/IP matching for card-absent fraud disputes, in force October 24, 2026) for the shared-device discussion.
This guide is general information only — not legal or financial advice. Last updated: October 26, 2026.