Table of Contents
- A ten-minute routine that catches more than a careful read
- The four line types worth a second look
- Why a charge for a few cents matters more than a big one
- The lines that are fraud but do not look like it
- The information gain: your protection clock runs from the statement, not from the theft
- Before you dispute, look up the descriptor
- What to do when you find one
- A note on how to use this
- Frequently asked questions
Read the statement in this order: smallest amounts first, then anything recurring, then anything you recognize but cannot date, then the large items. Most people do the opposite and scan for a big unfamiliar number, which is exactly the line fraud is least likely to produce first. The genuinely diagnostic signs are a charge of a few cents or a few dollars from an unfamiliar merchant, a duplicate that posted twice, a subscription whose amount changed quietly, and a debit whose merchant name you cannot connect to anything you did.
A ten-minute routine that catches more than a careful read
Checking a statement is a matching exercise, not a reading exercise. The aim is to account for every line, not to spot a suspicious one, because fraud that succeeds is fraud designed to look unremarkable.
- Sort by amount, ascending, if your bank's app allows it. Start at the bottom.
- Account for every line under about ten dollars. These are the ones people wave through, and they are the ones that matter most, for the reason in the next section.
- Check every recurring item against what you expect to pay, not against what you paid last year.
- Look for duplicates: the same merchant, same amount, same day or one day apart.
- List anything whose merchant name you cannot place, then look those names up before deciding anything.
- Read the non-transaction lines too: address changes, new payee confirmations, statement delivery changes, and new device or contact-detail notices.
Do this once per statement cycle. Once per cycle is not an arbitrary rhythm; it is tied to the deadlines described below.
The four line types worth a second look
| Line type | What it looks like | Why it matters |
|---|---|---|
| Micro-charge from an unknown merchant | A few cents to a few dollars, often out of state or overseas, sometimes several within minutes | Classic card testing: someone is checking whether a stolen number is live before spending on it |
| Quiet duplicate | Same merchant, same amount, posted twice | Sometimes a genuine processing error, sometimes a replayed transaction; either way it is refundable only if noticed |
| Recurring amount that changed | A subscription posting more than it used to, or a trial that converted | The most commonly missed loss, and often not fraud at all, which is why nobody looks at it |
| Unrecognized descriptor | A merchant name you cannot match to any purchase | Could be a parent company name, could be unauthorized use. Requires a lookup, not an instant dispute |
Why a charge for a few cents matters more than a big one
A stolen card number is worthless to a criminal until they know it works. The standard method, described publicly by the card networks and payment processors themselves, is to run a tiny transaction, often a small donation or a cheap digital purchase, and see whether it is approved. Mastercard's own consumer-facing explanation of card testing makes the point directly: those one, two and three cent charges should not be shrugged off, because an approved micro-charge tags the number as live and moves it toward being sold or spent.
The practical consequence is that the small line is an early warning and the large line is a consequence. If you catch the test, you can have the number reissued before anything real is spent. If you only look for large amounts, you find out afterward. When you report one of these, say specifically that you believe your card number has been tested, and ask for a new card number rather than only a refund of the small amount, because a refund alone leaves the compromised number active. If the exposure came from a physical reader rather than an online breach, our guide on how to spot a card skimmer covers that side.
The lines that are fraud but do not look like it
Not every fraudulent line arrives as an unfamiliar merchant. Three patterns hide inside things you recognize.
The refund that came with a request. A credit you did not expect, especially if someone then contacts you saying they overpaid and asks you to send some back, is the setup described in refund and overpayment scams. The credit on the statement can be real while the money behind it is not.
The new payee or standing instruction. A transfer to a payee you did not set up, or a small regular debit that started recently, points at account access rather than card exposure. That is a different problem with a different response, covered in account takeover fraud.
The administrative line. Address changes, statement-delivery changes, or a new contact number confirmed on the account often appear before the money does, because redirecting where the bank sends notices is a common preparatory step. These lines are not transactions, which is precisely why they get skipped.
The information gain: your protection clock runs from the statement, not from the theft
This is the part almost no article on statement-checking says, and it is the reason the routine above is worth having at all. Consumer protections in the US are keyed to notification deadlines, and several of those deadlines are measured from the date the statement was sent, not from the date the transaction happened. A statement you do not open is a deadline running down in the background.
| Payment type | Governing rule | The deadline in outline |
|---|---|---|
| Debit card and other electronic transfers | Regulation E, implementing the Electronic Fund Transfer Act (12 CFR 1005.6), per CFPB guidance | Report a lost or stolen access device within two business days of learning of it and liability is capped at the lesser of the unauthorized amount or a low statutory figure, currently stated as $50. Report later and the cap rises. Unauthorized transfers appearing on a periodic statement should be reported within 60 days of that statement being sent |
| Credit card | Fair Credit Billing Act, enforced by the FTC | Liability for unauthorized use is limited to $50, and billing disputes must be sent within 60 days of the statement date. The creditor must acknowledge the dispute within 30 days and resolve it within two billing cycles, and no more than 90 days |
Two things follow from this. First, the figures and windows above come from the regulations themselves and can be amended, so confirm the current text with the CFPB, the FTC, or your own bank rather than relying on this page. Second, and more usefully, the deadline is what turns statement-checking from a chore into a protection. Many card issuers and networks advertise zero-liability policies that are more generous than the statutory minimum, but those policies are conditional on prompt reporting, which returns you to the same point.
Outside the US, equivalent protections exist under different names and different clocks: chargeback rights through the card scheme rules, and national payment-services regulation covering unauthorized transactions. The mechanism is universal, the deadline is not, so find your own regulator's published timeframe. Our guide on how to report financial fraud lists the relevant bodies by country.
Before you dispute, look up the descriptor
The honest limitation of everything above: an unrecognized line is not automatically fraud, and disputing a legitimate charge has costs. Merchant descriptors frequently show a parent company, a payment processor, or a trading name that shares nothing with the shop's sign. A subscription bought through an app store may appear under the platform's name. A hotel or car rental may show an authorization hold that later drops off.
So before you file: search the exact descriptor text, check the date against your calendar, and ask anyone else with a card on the account. Filing a dispute against a genuine merchant, sometimes called friendly fraud in the industry, can cost you the goods, the relationship with the merchant, and occasionally the account itself if it becomes a pattern. Five minutes of checking protects the strength of your real disputes.
What to do when you find one
Call the number on the back of your card or on the statement, not a number from a search result or an email, for the reasons in our guide on fake customer service number scams. Report the specific transaction, say clearly whether you authorized any part of it, and ask three questions: is the card number being reissued, is the dispute being logged formally under the applicable rule, and what is the reference number. Write down the date, the time, and the name of the person you spoke to. If more than one line looks wrong, treat the account as compromised rather than treating each charge separately.
A note on how to use this
This page cites the CFPB's guidance on Regulation E, the Fair Credit Billing Act as enforced and published by the FTC, and the card networks' own published descriptions of card testing, as checked in August 2026. It is general information and not legal or financial advice. FinMateMastery is not an authority, cannot review your account, and cannot recover your money. Rules, liability limits and deadlines differ by country and can change, so confirm them with your own bank or national regulator. Please also read our full Disclaimer and our pillar guide on how to protect yourself from financial fraud online.
Frequently asked questions
How often should I check my bank statement for fraud?
Once per statement cycle at minimum, because several consumer protections are keyed to the statement date rather than the transaction date. Transaction alerts are a useful supplement, since they shorten the gap between an unauthorized transaction and your phone call, but alerts can be missed and a statement review catches what alerts do not cover, such as a subscription amount that changed.
Is a charge of a few cents worth reporting?
Yes, and it is often more informative than a large one. Small charges from unfamiliar merchants are the standard method for confirming that a stolen card number is live. Report it, and ask for a new card number rather than only a refund, since a refund leaves the compromised number in circulation.
What if I do not recognize a merchant name but the amount looks like something I bought?
Look up the exact descriptor before doing anything else. Descriptors often show a parent company, a processor, or a trading name. Disputing a legitimate charge has real costs, so a few minutes of checking is worth it.
Does checking my statement protect me legally?
It preserves your position. Deadlines under Regulation E and the Fair Credit Billing Act are measured in days from the statement being sent, so an unopened statement is a window closing. Checking does not create a right, but missing the window can limit one.
Someone used my card but I still have it. How is that possible?
Card-present theft is only one route. The number itself can be exposed through a merchant data breach, a skimmed reader, or a phishing page, and used online without the physical card. That is why the response is a reissued number rather than simply keeping the card safe.