When a business learns its checkout page was compromised, the news almost never arrives as a security alert. It arrives as money behaving strangely. Chargebacks cluster. A processor holds back part of a deposit. Sales reports stop tying to what actually landed in the bank.
Owners read breach coverage and think about passwords. The first thing you're likely to notice is your deposits, and that makes this a bookkeeping problem before it's an IT one.
Why Small Sites Are Now Worth Attacking
The old comfort was arithmetic. Breaking into a small retailer took a person's time, and a person's time was worth more than the card numbers on a site doing modest volume. That math has changed.
In September 2026, BleepingComputer reported on a campaign built from research by a security firm that recovered the attacker's own server. The operator chained automated tools to scan for weaknesses and exploit them, compromising at least 27 companies in a five-day stretch and planting card skimmers on at least 119 websites. More than 600,000 card records came from just two of those companies. The operator's own notes put the cost at a mean of $25.46 per completed scan.
Twenty-five dollars a target is the part worth sitting with. At that price, nobody needs your site to be lucrative. They need it to be reachable. "We're too small to be worth attacking" was a reasonable thing to believe when attacks cost real labor, and it isn't anymore.
Two caveats are worth stating. This is one firm's research rather than a government advisory, and no victim is named, so you should treat the specific numbers as that firm's accounting rather than as an established record. The pattern is what matters here, and the pattern is consistent with where this has been heading for a while.
How a Card Breach Shows Up in Your Books
A skimmed merchant almost never detects the theft themselves. Card networks notice first, because fraud analysts see a cluster of stolen cards that share one common recent purchase. By the time anyone tells you, the cards have been used elsewhere.
What you see is chargeback volume that doesn't match your experience. You are not looking at one disputed order from an unhappy customer. You are looking at several in a short window, often for transactions that seemed ordinary when they came through.
That's worth treating as a signal rather than as noise. Chargebacks are routine in isolation and informative in clusters, and a bookkeeper watching the bank feed is usually the first person positioned to notice the shape of it.
Then Your Cash Timing Changes
When chargebacks climb, a payment processor protects itself. That usually means a reserve, where a percentage of each settlement is withheld, or a delay in funding, or both. Forensic review and card-brand assessments can follow.
Here's why this lands in your books before anyone uses the word breach. Revenue looks normal, because the sales happened. Deposits don't, because part of them is being held. The gap between the two is exactly the kind of thing that gets written off as a timing quirk for a month or two, which is a month or two you didn't need to lose.
If settlements stop matching sales and nobody can explain why, that question deserves an answer the same week, not at quarter-end.
What to watch: A run of chargebacks, a settlement that doesn't tie to the day's sales, a processor reserve you didn't negotiate, or fees you can't name. Any one of those is worth a call. Together they're a pattern.
And Sometimes the Records Themselves Are Gone
The campaign above included a cleanup step. After the card data was copied out, the attacker's instructions were to wipe the source fields in the retailer's own database, apparently to cover the theft. BleepingComputer reports this caused operational disruption and data loss at several retailers.
This is the detail most likely to get exaggerated in retelling, so it is worth being precise. What's documented is card data removed from store databases and the resulting data loss, not a blanket deletion of order history. But the principle holds for your books either way. If data inside your store can be altered or destroyed by someone who got in, then your store is not a reliable archive, and the records you rely on for reconciliation can thin out without anyone touching your accounting file.
That is an argument for something unglamorous. Your accounting system, your bank, and your processor should each hold enough detail that you could reconstruct a month without the store's database. Most small businesses discover whether that's true at the worst possible moment.
What Actually Reduces the Risk
The strongest protection is structural. If card details never touch a page you control, there is nothing on your site to skim. Hosted checkout, where payment fields are served by the processor rather than embedded in your own page, moves that exposure off your plate. A self-hosted cart keeps it.
Past that, the honest list is short and mostly about ownership. Someone should be responsible for your website, and at a small business that's usually nobody. The store was built by a contractor who may still have access, the tag manager login is shared, and no one has looked at what scripts load on the checkout page since launch. Knowing who and what still has access is the cheapest control available, and it's the same discipline that protects your financial systems.
Keep your payment platform and plugins updated, since the automated scanning in this campaign looks for known weaknesses rather than inventing new ones. And on the books side, reconcile often enough that a week of strange deposits stands out while it's still a week.
If You Think It's Happened
Call your processor first and ask directly whether a reserve or a review has been placed on your account, because they often know before you do. Get your web developer to look at what's loading on the checkout page. Preserve records rather than cleaning them up, since they're evidence now. And report it to the FBI at ic3.gov.
In your books, stop treating the unexplained settlement gap as a timing issue and start tracking it as its own item. You'll need that history for the processor conversation, and possibly for your insurer.
The Bottom Line
A card breach reaches your books as chargebacks, then as a reserve that changes your cash timing, then as reports that stop tying out. If you sell online and your sales detail and your deposits have been drifting apart since no one can quite say when, that's worth a hard look rather than a shrug.
At Salt & Sand Bookkeeping, noticing when the money stops behaving normally is part of the job. We record what cleared, and we ask why it cleared that way.
See how we approach clean, reviewed books: Our Bookkeeping Services
Questions about your books? Reach us at info@saltandsandbookkeeping.com or (619) 304-SALT (7258).
Deposits not tying to sales? Let's figure out why together.
Schedule a Free Consultation