Crashcart Start your free trial

Card payment rules

PCI compliance for small businesses

PCI compliance for a small business means following the Payment Card Industry Data Security Standard (PCI DSS) for every way you take cards, and proving it once a year, usually with a self-assessment questionnaire your card processor asks you to sign. The card brands require it and your processor or bank enforces it. How much applies depends on how card numbers travel from the customer to the processor: the current questionnaires run from 21 requirements for a listed point-to-point encryption terminal to 233 for a business that fits none of the shorter forms, so the less card data touches your own computers and network, the less you have to do.

The standard is written by the PCI Security Standards Council, and the current version is PCI DSS v4.0.1, published in June 2024. This guide is for a shop, studio, salon, restaurant or small practice that takes cards and has nobody whose job is IT. It covers who sets the rules, which questionnaire fits which way of taking cards, what the requirements mean in plain terms, the quarterly scans, what happens if you skip it, and a checklist.

Who sets the PCI rules and who enforces them

Three groups are involved, and they do different jobs.

  • The PCI Security Standards Council writes the standard. It was founded in 2006 by American Express, Discover, JCB International, MasterCard and Visa. It publishes PCI DSS, the self-assessment questionnaires and the lists of approved scanning companies and devices. Asked whether it enforces compliance, the Council answers "No" and says "We do not monitor the implementation of standards."
  • The card brands decide who must comply and how they prove it. Visa's Account Information Security Program page says the Council "owns, maintains and manages the PCI DSS," while Visa "manages all data security compliance enforcement and validation initiatives." Mastercard runs its own Site Data Protection program.
  • Your acquiring bank or processor collects the proof. The acquirer is the bank that puts card payments into your account, often through a processor such as the company that supplied your terminal. Visa's page says "Acquirers must ensure that their merchants validate at the appropriate level," and Mastercard says merchants submit their validation documents to their acquiring bank.

PCI DSS itself says the same in Section 2: "Whether any entity is required to comply with or validate their compliance to PCI DSS is at the discretion of those organizations that manage compliance programs (such as payment brands and acquirers)." In practice, the questionnaire, the deadline and any fee for missing it all come from your processor.

PCI DSS is an industry standard, not a government regulation. Your merchant agreement with your processor is where the obligation to follow it, and the fees for not following it, are written down.

Does PCI DSS apply to a small business?

Yes, if you take cards. Section 2 of PCI DSS v4.0.1 says it is "intended for all entities that store, process, or transmit cardholder data (CHD) and/or sensitive authentication data (SAD) or could impact the security of the cardholder data," including merchants. Visa's page says "PCI DSS compliance is required of all entities that store, process or transmit Visa cardholder data."

The standard protects two kinds of card data. Cardholder data is the card number, the cardholder's name, the expiration date and the service code. Sensitive authentication data is the full magnetic stripe or chip data, the 3 or 4 digit card verification code, and PINs.

Handing payments to a processor shrinks what applies, but it does not end it. Section 2 says "Entities that outsource their payment environments or payment operations to third parties remain responsible for ensuring that the account data is protected by the third party per applicable PCI DSS requirements." A business with no card data on any of its systems still answers a short questionnaire, mostly about its vendors and its paper.

Merchant levels and the self-assessment questionnaire

Each card brand sorts merchants into levels by how many of that brand's transactions they handle in a year. The level decides how you prove compliance. Mastercard's levels, from its Site Data Protection page:

Level Mastercard and Maestro transactions a year How the merchant validates
1 More than 6 million Annual assessment and Report on Compliance
2 More than 1 million, up to 6 million Annual self-assessment questionnaire
3 More than 20,000 e-commerce, up to 1 million e-commerce Annual self-assessment questionnaire
4 All other merchants Annual self-assessment questionnaire

Visa's page lists three merchant levels. Level 1 is over 6 million Visa transactions a year, Level 2 is 1 to 6 million, and Level 3 is described as "Less than 1 million Visa ecommerce transactions annually across all channels." For Levels 2 and 3 the requirement is "Every year: Complete and submit Self-Assessment Questionnaire."

A shop with one register is far below a million card transactions, so it validates with a self-assessment questionnaire, called an SAQ. Mastercard adds a note for Level 4 that the merchant must comply with PCI DSS, "although validation of compliance to Mastercard is not required, except as required by applicable law or regulation." Your processor can still require the SAQ, and the processor is who you answer to.

Visa also runs a Technology Innovation Program that removes the yearly validation for some U.S. merchants when at least 75% of their transactions go through chip terminals that also take contactless payments, or through a validated point-to-point encryption solution. The merchant must not store sensitive authentication data after a sale is approved and must not have been involved in a breach of card data. Ask your acquirer whether you qualify. It removes the paperwork, not the duty to follow the standard.

How the way you take cards decides how much applies

Each SAQ is written for one way of taking cards. Its first pages list eligibility criteria, and you can use it only if every criterion is true for you. If you take cards more than one way, ask your processor how it wants that reported. The current versions are in the Council's document library, and the guide to choosing your PCI self-assessment questionnaire goes through each one's criteria.

How you take cards SAQ Requirements
Terminals from a validated, PCI-listed point-to-point encryption (P2PE) solution P2PE 21
A PIN-capable card reader with a phone or tablet, from a listed SPoC solution SPoC 22
Online or phone sales where the processor's page or staff handle every card number A 27
An imprint machine or a standalone terminal on a phone line B 27
A standalone approved terminal on your internet connection, kept apart from everything else B-IP 50
Card numbers typed into the processor's virtual terminal on an isolated computer C-VT 54
Point-of-sale software on an internet-connected computer at one location C 123
Your own website delivers part of the payment page A-EP 139
Anything else, including card numbers stored electronically D 233

We counted the requirements in the current version of each SAQ on October 15, 2026; the SAQ guide has the method. "Kept apart from everything else" is the part most shops miss. A B-IP terminal on the same network as the office computers and the customer Wi-Fi fails it. The SAQ says the separation "can be achieved via network segmentation," which for a small shop usually means a separate network or VLAN for the terminals, set up on the router. Point-to-point encryption is the other big lever: the terminal encrypts the card the moment it is read, and only the processor can decrypt it. Check your terminal on the Council's list of P2PE solutions; "encrypted" in a sales brochure is not the same thing as listed.

Ten requirements appear in all nine merchant SAQs: 3.1.1 (processes for protecting stored card data are defined), 9.4.1, 9.4.1.1 and 9.4.6 (paper with card data is kept secure and shredded), the five parts of 12.8 (managing the vendors that handle your card data), and 12.10.1 (an incident response plan). Those ten are the floor for every business that takes cards.

The table also shows where the big jumps are. Moving from a terminal on your network (50) to a point-of-sale system on your network (123) more than doubles the count, because your computers come into scope. Moving from either one to a listed P2PE terminal (21) takes almost all of the computer and network requirements away.

What PCI DSS v4.0.1 asks of a small merchant

PCI DSS has 12 principal requirements, from network security controls (Requirement 1) to policies and programs (Requirement 12). A small merchant answers only the ones in its SAQ. These are the ones most small businesses meet, in plain terms, with the requirement number in brackets so you can find it on your form.

Don't keep card data you don't need

The card verification code must never be stored after the sale is approved (3.3.1.2), and neither may PINs or chip and stripe data (3.3.1). SAQ C's completion guidance says that if you write the code down while taking a phone order, you must shred the paper right after the transaction or black out the code before you store it. If you never ask for the code, the requirement is "Not Applicable."

Paper with card numbers on it must be kept secure and, when no longer needed, "cross-cut shredded, incinerated, or pulped so that cardholder data cannot be reconstructed" (9.4.6). A box of old imprint slips or phone order forms in the back room is in scope.

A spreadsheet of customers' card numbers, a photo of a card in a text message, or a card number in an email moves you to SAQ D. Stop keeping them and delete the ones you have.

Protect terminals from tampering

Most SAQs for card-present sales include Requirement 9.5.1. It asks you to keep a list of your terminals with the make, model, location and serial number (9.5.1.1), inspect them periodically for tampering or swapping (9.5.1.2), and train staff to spot tampering and to check the identity of anyone who shows up claiming to service a terminal (9.5.1.3).

Know your payment vendors

Requirement 12.8 asks you to keep a list of every service provider that handles your card data or could affect its security (12.8.1), have written agreements in which they accept responsibility for that data (12.8.2), check their PCI DSS compliance at least once every 12 months (12.8.4), and know which requirements they handle and which you handle (12.8.5). For most shops the list is short: the processor, the point-of-sale company, the online store platform, and whoever supports the terminals.

Write an incident response plan

Every SAQ includes 12.10.1, an incident response plan that is "ready to be activated in the event of a suspected or confirmed security incident" and includes notifying the card brands and acquirers. The SAQ guidance scales it to the business and says it "could be a simple document posted in the back office that lists who to call in the event of various situations with an annual review." For a small shop, the first call is the processor.

Write a short policy and tell staff about it

Most SAQs include a written information security policy that is shared with staff and reviewed at least once every 12 months (12.1.1, 12.1.2), and a security awareness program (12.6.1). The SAQ guidance says the awareness program can be "a flyer posted in the back office, or a periodic e-mail sent to all employees."

When your computers or network are in scope

SAQs B-IP, C-VT, C, A-EP and D reach into your network and computers. The requirements that come up most for a small business:

  • Keep payment devices apart from everything else. Restrict traffic into and out of the payment network to what is necessary (1.3.1, 1.3.2), and put a firewall between any wireless network and the payment devices (1.3.3). Change default passwords on routers and Wi-Fi equipment (2.2.2, 2.3.1). If you rely on that separation, SAQ B-IP adds a penetration test of it at least once every 12 months (11.4.5).
  • Install security updates. Critical security patches go on "within one month of release" (6.3.3). A register PC that no longer gets updates fails this, which is one more reason to plan for Windows 10 end of support.
  • Run anti-malware on the computers in scope (5.2.1, in SAQs C-VT, C and D).
  • Give everyone their own login. Each person gets a unique ID (8.2.1), shared logins are an exception (8.2.2), and accounts for people who leave are removed (8.2.5). Passwords are at least 12 characters with letters and numbers (8.3.6). The employee offboarding checklist covers removing access the day someone leaves.
  • Use multi-factor authentication for remote and admin access. Multi-factor authentication means a code from your phone or a security key on top of the password. SAQ B-IP requires it for remote access from outside your network that could reach the payment devices (8.4.3), and SAQs C-VT and C require it for administrator access into the payment environment (8.4.1).
  • Keep logs. SAQ C and D add Requirement 10, audit logs of who did what on the systems in scope, reviewed and kept.

Most of these are ordinary security work that protects a small office whether or not it takes cards. The small business cybersecurity checklist puts them in order of what stops the most common attacks.

Quarterly ASV scans

An ASV scan is an outside vulnerability scan of your internet-facing addresses, run by a company on the Council's list of Approved Scanning Vendors. Requirement 11.3.2 says the scans happen "At least once every three months," by an ASV, with problems fixed and rescans run until the scan passes.

Of the SAQs in our count, 11.3.2 appears in SAQ A, B-IP, C, A-EP and D. It does not appear in SAQ B, C-VT, P2PE or SPoC. In SAQ A it applies to a website that redirects to the processor or embeds the processor's payment form; a business that has fully outsourced mail and phone orders and has no such website marks it not applicable.

For the first year, you don't need four passing scans if the latest scan passed, you have a written policy requiring quarterly scans, and earlier problems were fixed and rescanned. After that, the requirement is a passing scan in every quarter. Ask your processor whether its compliance program includes the scans before you hire a scanning company separately.

Filling out and sending the SAQ

Each SAQ lists the same completion steps:

  1. Confirm from the eligibility criteria that it is the right SAQ for how you take cards.
  2. Work out which people, devices and paper touch card data. That is your scope.
  3. Check each requirement against what you do.
  4. Complete all three sections: your business details, the questionnaire, and the attestation.
  5. Send the SAQ and the Attestation of Compliance, with any scan reports, to whoever asked for it, usually your processor.

Each requirement gets one of four answers: In Place, In Place with a compensating control worksheet, Not Applicable, or Not in Place. SAQ D adds a fifth, Not Tested. Not Applicable answers need a short explanation in Appendix C. If something is Not in Place, Part 4 of the attestation is an action plan with a target date for compliance. The attestation is signed by the merchant's executive officer, which in a small business is usually the owner. Answer truthfully, because after a breach a forensic investigation looks at whether you were compliant at the time.

Your processor may have you answer the same questions in its online portal instead of the PDF.

What happens if you don't comply

There are two separate costs, the fees for not filing and the bill after a breach.

Fees for not filing

Visa doesn't bill merchants directly. Its page says that when a merchant does not comply, "Visa may assess a non-compliance assessment to the issuer or acquirer," and the acquirer "must not represent that Visa has imposed any assessment on the service provider or merchant." What reaches you is set by your merchant agreement.

Processors can also charge their own fees. As one example, Wells Fargo's published merchant services fees list a PCI Compliance Program fee of $10.00 a month per merchant ID and state that "PCI non-compliance fees apply" for Level 3 and Level 4 merchants. Look for the same lines on your own statement and in your agreement.

After a breach

Visa's What To Do If Compromised (version 10.0, effective June 25, 2026) sets the timeline for any business that suspects card data was stolen:

  • Report the event to Visa within three calendar days of finding evidence that raises a reasonable suspicion, and notify your acquiring bank immediately.
  • Send an incident report to Visa and your acquirer within three calendar days after that.
  • If Visa requires it, sign a contract with a PCI Forensic Investigator within five business days. Visa may instead require an independent investigation by a qualified firm.
  • Preserve evidence. Visa says not to log on to or change passwords on the affected systems, not to turn them off or restart them, and to disconnect them from the network by unplugging the network cable.

Visa's page also says non-compliance assessments "may be waived if there is no evidence of PCI DSS non-compliance prior to, and at the time of a data breach, as demonstrated during a forensic investigation." An honest, current SAQ and the evidence behind it count after a breach.

Card brand rules don't replace your state's data breach notification law, which may require notice to customers and state officials on its own deadlines.

What changed with PCI DSS v4.0.1

PCI DSS v4.0 was retired on December 31, 2024, so v4.0.1 is the only current version. Requirements that v4.0 introduced as best practices became mandatory on March 31, 2025. The 12-character password minimum is one of them; before that date the standard allowed seven characters.

The SAQs for v4.0.1 were published in October 2024. SAQ A was revised in January 2025 to remove the payment page script requirements (6.4.3 and 11.6.1) and the risk analysis tied to them (12.3.1), and to add the eligibility criterion about script attacks. If your processor's portal or your last PDF says v3.2.1 or v4.0, the questions have changed since you last answered them.

How to make PCI DSS smaller for your business

Every step that keeps card data off your own equipment moves you to a shorter SAQ.

  • Take online payments on the processor's hosted page or embedded form, not a form your website builds.
  • Use a terminal from a listed P2PE solution if your processor offers one. It is the shortest card-present SAQ.
  • Put payment terminals on their own network, separate from office computers and customer Wi-Fi.
  • Stop writing down card numbers and codes, and shred what you have.
  • Key phone orders into the terminal, or use a computer kept apart from the rest of the network for the virtual terminal.

PCI compliance checklist for a small business

  1. List every way you take cards: counter, phone, mail, website, invoices, mobile.
  2. Ask your processor which SAQ they expect, when it is due, and whether scans are required.
  3. Read the eligibility criteria for that SAQ and confirm every one is true.
  4. Find and remove stored card data: spreadsheets, emails, texts, photos, old paper.
  5. Shred card data on paper when you no longer need it, and lock up what you keep.
  6. List your terminals with make, model, location and serial number, and inspect them on a schedule.
  7. Train staff to spot tampering and to check the identity of anyone servicing a terminal.
  8. Put terminals on their own network, apart from computers and customer Wi-Fi.
  9. List your payment vendors, keep their agreements, and collect their compliance status every year.
  10. Write a one-page security policy and incident response plan with your processor's phone number at the top.
  11. If computers are in scope: updates within a month, anti-malware, one login per person, 12-character passwords, multi-factor authentication for remote and admin access.
  12. Run quarterly ASV scans if your SAQ includes 11.3.2.
  13. Complete, sign and submit the SAQ and Attestation of Compliance, and keep a copy.
  14. Set a date to do it again next year.

Doing it again every year

The SAQ is a yearly snapshot, but the requirements apply every day. A new terminal, a new card reader on a tablet, a new online store or a staff member who starts keying phone orders into the office PC can each change which SAQ fits. Review how you take cards whenever one of those changes, and before every renewal.

Crashcart, which runs IT for small offices, follows PCI DSS for any business that takes cards. It turns off guest and unused accounts on your computers each morning (2.2.2), installs updates every week in your restart window (6.3.3), walks you through putting customer Wi-Fi on a guest network that can't reach your computers or terminals (1.3), and drafts your security policy (12.1.1) and incident response plan (12.10.1). It logs every check and fix with the date and the requirement, and the PCI evidence pack bundles that log with your signed documents. You complete and sign the questionnaire on your processor's form. The page for shops and studios shows each part.

This is general information, not legal advice. For your situation, ask your attorney.

More in this topic

Crashcart runs IT and security for small offices for $35 a computer a month. Start a 14-day free trial.