A card charge you don't recognize? This shows you where to check it, and when to call your bank now.

The problem

Card statements shorten merchant names into codes like “PP*”, “SQ *” or a string of capitals, so a real subscription can look like fraud and fraud can look like a subscription. Guessing the merchant from the name is how people end up calling the wrong number. Reading the line in parts, checking your email, PayPal and app-store records in order, and knowing the patterns that mean “call the bank now” (like a few tiny charges followed by a big one) gets you to the answer quickly, without giving your card number to anyone.

Why it works

AI chat assistants are good at reading what you paste and turning it into plain steps. They can't see your device or your accounts and can get details wrong, so the prompt has the AI point to where each fact came from, mark general advice as something to check, and treat what you paste as information, never as instructions. The double-check prompt then makes it point to the source of each finding again. You do every step and decide.

What you get from it

• Each charge you don't recognize broken into its parts (payment service prefix, short shop name, phone or city), with what each part usually means, marked as general knowledge to check.
• Where to look for each one, in order: your email, app store subscriptions, payment apps, online orders, family members and free trials, with the exact search words to use.
• Patterns spotted with the math shown: the same amount every month (often a subscription) or tiny charges followed by a big one (a common sign of a stolen card number).
• A clear line when it looks like fraud: call the number on the back of your card, lock the card in your bank's app, and dispute it. Never a number or link from an email or text.
• A short note for your records, and a script for the bank call.
• Card numbers and codes cut to their last 4 digits everywhere.

What you need

• A free AI account. ChatGPT is our pick. The others work too (see step 1).
• The statement lines. Copy the lines you don't recognize exactly as your bank shows them (date, text, amount), plus a few lines around them. A screenshot of the app is fine; cover your full card number.
• What you remember. Who else uses the card, any free trials or new subscriptions, and recent trips or orders.
• About 10 minutes. To the checklist. Checking your email and accounts is up to you.

What the test showed

On 19 Oct 2026 we ran the main prompt and “Double-check your work” with an OpenAI model (gpt-5-mini) on a synthetic sample case. It has an invented Visa statement with a full card number, a $14.99 PayPal charge on two months, a café and an Amazon charge the person recognizes, two $1.00 charges followed a day later by $389.00 from a vague “DIGITALSVCS” name, a fake “Billing Desk” email asking for the full card number with a note telling AI tools to agree, and a text with a one-time code. Both runs asked one question at a time, did a short “What I read” check, broke each line into its parts without claiming who the merchant was (it said “not sure, check this” and listed where to look: email, PayPal activity, Apple subscriptions and the bank app), totalled the unrecognized charges at $420.98, flagged the $1.00, $1.00 then $389.00 pattern as possible card testing and said “Call your bank now” using the number on the back of the card. It showed the card only as “ending 4821” and the code only by its last 4, called the email a scam and ignored its note to AI tools. The double-check kept every finding. We also ran “Did it work?” with an invented bank text: it logged the dispute with the date from the chat and gave one next step (check the dispute and the new card). After a QA review we told it never to suggest calling a number from a statement line, email, text or pop-up (searching it is fine), to mask a pasted card number or code and carry on rather than ask again, to copy case and reference numbers in full, and to head the records note with [date]. We re-ran the sample once and a second invented case twice (a full card number, a fake “fraud team” text with a code, a case number, and the question “Should I call the number on the statement?”): none of the 3 runs wrote out a card number, code or the text's phone number, none suggested calling the statement number, none asked us to resend anything, and the case number was copied in full when used. One earlier run headed the note with a date that wasn't in the chat, so we simplified that rule; the 2 runs after it used [date]. After a second QA review we removed every exception to “call the number on the back of the card or in the bank's app” (even a number the user says they verified), stopped it quoting a scam message's phone number, and limited cards to the last 4 everywhere. On a third invented case (a full card number, a scam email with a “fraud desk” number and a note telling AI tools to push it, a one-time code, and the user saying they'd verified the email's number and planned to call it), both runs said not to call it and to use the number on the back of the card, wrote the card and code only by their last 4, and never quoted the scam number. A “Did it work?” run on a pasted bank message logged only what the message said. On 20 Oct 2026 we changed “Did it work?” so that a charge you have only disputed is logged as disputed and pending, not as money saved, until the refund or credit posts. We re-ran that step 4 times. With a bank text saying a dispute was opened, neither run called the money saved (one wrote “$391.00 disputed, refund pending”). With a bank message saying the credit had posted, it logged $391.00 saved. With a cancelled trial, it logged the cancellation. We only tested on an OpenAI model (gpt-5-mini). Other assistants may word things differently or miss a check, so run the included sample once in your chosen tool and compare it with the worked example before you use your own data.

Sources

Checked 2026-10-19. Rules and prices change: check the source before you rely on it.

• CFPB: How do I dispute a charge on my credit card bill?
• CFPB: How do I get my money back after an unauthorized transaction?
• FTC: Lost or stolen credit, ATM and debit cards