Credit Card Data Breach at a Small Business: What to Do
Chargebacks, Fraud & Security

Card Data Breach at Your Business? A Step-by-Step Response Plan

Suspect a credit card data breach at your small business? Follow this step-by-step plan for containment, processor calls, forensics and state notice laws.

Woman in a red hijab, face mask and plastic gloves shopping in a candy and bulk food store with produce shelves behind

Photo: Pixabay

On this page 7 sections
  1. Signs of a Credit Card Data Breach at a Small Business
  2. First 24 Hours: Contain Without Destroying Evidence
  3. Payment Card Breach Response Starts With Your Processor
  4. Forensic Investigation and PCI: Who Pays
  5. Customer Notification and State Breach Laws
  6. Network Assessments After a Merchant Data Compromise
  7. Preventing a Second Breach

Key takeaways

  • Disconnect affected systems from the network, but leave them powered on and untouched. A wiped machine loses the evidence that limits how many cards land in scope.
  • Call your processor first, then your cyber insurer and a breach attorney, before anyone makes a public statement.
  • Card network rules and state breach notification laws are separate obligations. Meeting one never satisfies the other.
  • The network assessments that follow a compromise are different from the routine assessment fees on your statement. Your merchant agreement decides how they reach you.

If you suspect a credit card data breach at your small business, your first hour comes down to two moves made in order. Disconnect the affected systems from the network without wiping them or turning them off. Then call your payment processor. Your cyber insurer and a breach attorney come next, on the same day. Everything else about what to do after a data breach, from the forensic work to the bills, starts on firmer ground when those first steps are right.

Many owners don't discover a compromise themselves. Often the first warning comes from the processor. If that call came to you, return it using the number printed on your statement, not a number left in a voicemail, and ask for a case number. Then ask for the instructions in writing.

Signs of a Credit Card Data Breach at a Small Business

Outside alerts follow a set path. Card-issuing banks watch for fraud. When fraud turns up on a group of cards whose only shared history is a purchase at your business, the issuers flag you as the common point of purchase. That report moves through the card network to your acquirer (the bank that sponsors your merchant account) and from there to you. A pattern only stands out after fraud has hit many cards, so the theft behind that phone call is weeks old, not hours.

You can spot warning signs yourself, and they look different in each channel:

  • Retail counters: a PIN pad with a loose or bulky faceplate, or a cable that wasn't there yesterday.
  • Restaurants and bars: a remote access program on the POS server that nobody remembers installing, or a support vendor's login active at 3 a.m.
  • E-commerce stores: a checkout page loading a script from a domain you don't recognize, or new fields on the payment form.
  • Hotels: property management system logins at odd hours, or a shared inbox full of emailed card authorization forms.

Refunds you never issued and deposits that don't match sales are signals too. A monthly card reconciliation that matches deposits to sales is where those gaps tend to show up first. For background on how an approved sale becomes a deposit, see our guide to authorization vs capture. Treat any suspicion as real until someone qualified rules it out.

First 24 Hours: Contain Without Destroying Evidence

Your instinct will be to clean house by reinstalling the POS software and restoring the website from a backup. Resist it. Rebuilding a system erases the logs and file timestamps an investigator uses to date the intrusion and count the exposed cards.

DoWhy
Unplug the network cable or disable Wi-Fi on affected machinesStops data from leaving while keeping the system intact
Leave compromised computers powered onMemory contents vanish at shutdown, and investigators want them
Take the e-commerce checkout offline or switch to a hosted payment page, after clearing it with your processorStops new card numbers from being captured
Write a timeline of who noticed what, and when each system was touchedInvestigators and insurers will ask for it
Preserve firewall, router, POS and web server logsLogs are how an investigator dates the intrusion
Keep everyone, including your IT vendor, from "fixing" anythingCleanup destroys evidence, and investigators will want to examine vendor access too

You still need to take payments. Ask your processor whether you can run sales on a standalone terminal over a cellular connection or a separate, clean network while the main system stays isolated. Never plug a new device into the network you think is compromised. If you need replacement hardware for the counter in the meantime, look at our smart terminals and ask which setup works on an isolated connection.

Give your staff one sentence for customers ("We're looking into a technical issue and will share more when we can") and tell them not to post about it. Public statements wait until your attorney has seen them.

Payment Card Breach Response Starts With Your Processor

Your processor is your day-to-day contact, and the acquiring bank behind it answers to Visa and Mastercard for your account. Merchant agreements require prompt reporting of a suspected compromise. Find the data security or incident section of yours and note any deadline it sets.

Have these ready when you call:

  1. Your merchant ID and every business location
  2. What you observed and when you first noticed it
  3. Every system that touches card data, from the countertop terminal to the payment gateway
  4. Names and contact details for the outside vendors who support those systems
  5. Everything you have done since, including any changes

Then ask whether a forensic investigation will be required, and by what date. Ask too whether the acquirer plans processing limits or a reserve held against your deposits, and get one named contact for the case. If MannyPay processes your cards, reach the MannyPay team through our contact page and ask for the incident to be logged.

Two more calls belong in the first day. Read your cyber policy's notice clause now. It sets the reporting deadline and names any panel of investigators and lawyers you must use, and late notice or an off-panel hire puts coverage at risk. A breach attorney advises on whether to hire the forensic firm through counsel, which helps protect the findings. Counsel also advises on reporting to law enforcement, such as your local FBI or U.S. Secret Service field office.

Forensic Investigation and PCI: Who Pays

When a card network requires an investigation, a forensic firm the networks have approved for payment card compromises has to do the work. Your acquirer will tell you the requirement and point you to the approved firms. A capable in-house IT person or your POS vendor doesn't qualify, however good they are.

That investigator reconstructs the intrusion from entry point to exit. Its report also states whether you were compliant with PCI DSS (the card industry's data security standard) when it happened. Findings go to the networks through your acquirer.

Expect to pay for the investigation yourself, since the contract is between you and the firm. Price rises with the number of locations and systems in scope. Get a written scope and estimate before work starts, and check what your insurance policy reimburses.

Illustrative: How the Exposure Window Changes the Card Count

These numbers are illustrative and don't come from any real case. Picture a restaurant running 200 card transactions a day, with malware on its POS server for 90 days before anyone noticed. Assume 40% of those transactions were repeat visits by cards already counted once.

  • Transactions in the window: 200 × 90 = 18,000
  • Unique cards, after removing repeats: 18,000 × 0.60 = 10,800

Now suppose the owner wiped the server, and the investigator can't establish when the malware arrived. Without a provable start date, the investigator has to work back to the earliest date the evidence can't rule out. Each extra day adds about 200 transactions to the scope. A wider window means more customers to notify and more accounts in any issuer recovery claim. Preserved logs keep the count tied to cards that were actually exposed.

Customer Notification and State Breach Laws

Card network rules and state law are separate obligations, and meeting one doesn't satisfy the other. Network rules reach you through your merchant agreement. Notification duties come from state statutes, and they follow where affected customers live, not where your business sits. One incident at an online store, or at a hotel with out-of-state guests, brings several states' laws into play.

States define personal information differently. Under many state laws, a card number alone falls below the line, while a name plus the card number and the security code or password needed to use it triggers notice. Deadlines and required notice contents vary by state. So do the rules on telling the state attorney general and on whether encrypted data is exempt.

All of this is legal territory, so treat this section as general information, not advice. Have a qualified attorney map your obligations state by state before any letter or email goes out.

Network Assessments After a Merchant Data Compromise

"Assessment" means two different things in payments, and owners mix them up. The card brand assessment fees on your monthly statement are routine network charges on every sale. A merchant data compromise brings a different kind: amounts a network levies against your acquirer for security failures, or to help issuers recover fraud losses and card reissuance costs.

Those bills go to the acquirer, not to you. Your merchant agreement's indemnification and fee sections decide whether and how they pass through. Size tracks the number of accounts involved and whether you were PCI DSS compliant at the time. If an amount reaches you, ask for the network documentation behind it. For the routine fees on your statement, our guide to credit card processing audits and whether to pay someone to cut fees explains how a fee review works.

Around the assessment sit the bills you pay directly: the forensic firm, legal counsel, customer notices, credit monitoring if you offer it, replacement equipment, and sales lost to downtime. Afterward, expect your PCI compliance validation to face closer scrutiny than before. In serious cases the acquirer closes the account, and a terminated merchant can land on a database other acquirers check when you apply elsewhere. Check whether your cyber policy names network assessments as covered, because some policies handle them apart from other breach costs.

Preventing a Second Breach

Your investigator's report lists what failed, and your acquirer will want proof of each fix before restoring normal processing. Start with access. Change every password, and either put vendor remote access behind multi-factor authentication or remove it. Delete any stored card numbers you don't need.

Next, shrink how much card data your systems touch at all. Encryption at the card reader and tokenization (replacing the card number with a stand-in value) leave a compromised POS holding little worth stealing. Our explainer on tokenization vs. encryption for merchants covers which one does what. Fixes differ by how you sell:

  • Restaurants can bring payment to the table on handheld terminals, so cards stay in the guest's sight.
  • Retailers should inspect every PIN pad at shift change.
  • Online sellers can move card entry off their own servers with a hosted payment page or embedded payment fields. Ask your payment gateway provider which option it supports, and keep plugins current.
  • Hotels should replace emailed card forms with secure payment links.

If the breach exposed aging equipment, ask about encrypted card readers when you compare POS systems. A free quote from MannyPay gets a reply from a specialist within one business day.

Do one thing today, breach or no breach. Find the data security section of your merchant agreement, then copy your processor's incident contact number onto paper and keep it away from any computer an attacker could reach.

About the author

Marcus Bennett

Marcus Bennett is Payments Risk & Compliance Analyst for Beyond the Swipe, covering high-risk processing, chargebacks, rolling reserves, frozen merchant accounts and fraud prevention.

This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.

Related reading