Merchant Rails What happens to a card payment between the tap and the deposit.

Merchant Rails

PCI IN PRACTICE

PCI Compliance for a Small Merchant, in Practical Terms

By Baruch Mackliff · · 6 min read

PCI is a contract term rather than a law, your questionnaire is decided by how your payments are wired, and rewiring is what makes the work smaller.

Most owners meet PCI as a fee on a statement or an email demanding a questionnaire by Friday. It is neither of those things. PCI DSS is the card data security standard written by the council the card networks set up, and you agreed to follow it when you signed your merchant agreement.

That matters for a practical reason. It is a contract term, not a statute, so it is enforced by your acquirer and by the card networks rather than by a regulator, and the consequences arrive as charges on your account, as liability after a breach, and in the worst case as the loss of your ability to accept cards. The current version of the standard is version four, which replaced the older one and brought its remaining requirements into force during 2025.

Your level, and the questionnaire that goes with it

Merchants sit in levels based on annual transaction counts, with the largest at level one and nearly every small business at the bottom. Your acquirer assigns your level and should tell you on request. For most small merchants, validation means completing a self assessment questionnaire once a year, attesting to it, and running an external scan if any part of your setup faces the internet.

The questionnaire has versions, and the version you qualify for is worth more than any other detail here. A short one runs to a page count you can finish in an afternoon. The long one runs to hundreds of questions and assumes you have a network to describe.

Which one you get is decided by architecture:

So the first question is not how to answer the questionnaire. It is whether you can change the wiring so that a shorter questionnaire applies. Moving a checkout from your own form to a hosted page is usually a day of work and it removes most of the annual burden permanently.

Where small merchants actually get breached

The standard is long. The failures are boring and repetitive.

Card numbers written down. On an order form in a drawer, in a notebook by the phone, in the notes field of a booking system, in an email a customer sent because your form was broken that day. Every one of those is card data you are now responsible for protecting. The fix is to stop creating them and to destroy the ones you have.

Card numbers in email and messaging. Customers will send them. Your reply should ask them to use a payment link instead, and the message containing the number should be deleted rather than filed.

Recorded phone calls. If you take orders by phone and your system records calls, the recordings may contain the card security code. Storing that code after authorization is prohibited outright, and a recording is storage.

Default passwords. On the router, on the terminal, on the point of sale software, on the camera system sharing that network. This is the oldest finding in the field and it is still the finding.

One flat network. Payment devices sharing a network with guest Wi-Fi, the back office computer and whatever a supplier plugged in last spring. Separate the payment devices. On a small site this is a setting on decent equipment, not a project.

Skimming code on an online checkout. Attackers modify a script on the payment page and copy the fields as the customer types. Version four of the standard added requirements aimed at exactly this, covering which scripts are allowed to run on a payment page and detecting unauthorized changes to it. If you run your own checkout, this is the part to read closely.

What follows a compromise

The standard exists because of what happens afterward, and the sequence is worth knowing before it ever applies to you.

Fraud shows up on many cards at once, the networks trace the accounts back to a common point of purchase, and your acquirer is notified before you are. Depending on the size of the exposure you may be required to engage a forensic investigator from an approved list, at your own cost, and to give that investigator access to your systems. Assessments covering fraud losses and the cost of reissuing cards are billed to your acquirer, and your merchant agreement is what passes them along to you.

Having been compliant at the time does not make that sequence disappear. It changes the conversation considerably, and the attestation you filed is the only evidence of it you will have. State breach notification law sits on top of all of this and has nothing to do with your processor, which means the payments side being resolved does not mean you are finished.

The fee, and what turns it off

The monthly non-compliance charge on your statement is your processor's, and it is switched on by a missing attestation and switched off by a filed one. It is often the largest recurring line on a small merchant's bill, and it is entirely avoidable.

Find out who your processor uses for the questionnaire portal, log in, complete it honestly, and file the attestation. If the portal is asking you questions that do not match your setup, you are answering the wrong version and should ask your acquirer to confirm which one applies before you continue.

Answering dishonestly to clear a fee is a poor trade. The attestation is the document that gets pulled first after an incident, and a signed statement saying you segmented a network you never segmented turns a security problem into a different kind of problem.

The routine, once a year

Put it on the calendar in the same month each year and give it an afternoon.

  1. Confirm your level and your questionnaire version with your acquirer, in writing, and keep the reply.
  2. Complete the questionnaire against what is actually installed today rather than what was installed when you last filled it in.
  3. Run the external scan if anything in scope faces the internet, fix what it finds, and rescan until it passes.
  4. File the attestation and save a copy somewhere that is not the portal.
  5. Collect your vendors' attestations. Your gateway, your point of sale provider and anyone else touching payments should hand you theirs on request. A vendor that will not produce one is telling you something.
  6. Write down what changed. New terminal, new website, new phone system, new person handling orders. Those are the changes that quietly move you onto a different questionnaire, and finding out next year is worse than knowing now.

Common questions

do i have to be pci compliant if i use a card terminal

Yes. Every business that accepts card payments agreed to the security standard in its merchant agreement, and a standalone terminal does not remove the obligation, it only shortens the questionnaire you have to complete. A terminal using a validated encryption solution keeps the card data out of your hands entirely, which is the shortest version of the work available to a shop with a counter.

what is a pci non compliance fee

It is a charge your processor adds each month while your annual security attestation is missing or expired, and it is billed by the processor rather than by any card network. Completing the questionnaire and filing the attestation stops it, usually from the following billing cycle. Owners often pay this one for years because nothing on the statement explains which document turns it off.

which pci saq applies to my small business

It depends on how card data reaches the payment, not on how large you are. A shop with a standalone terminal, an online seller whose checkout is hosted entirely by the payment provider, and a business keying orders into a browser page each use a different short questionnaire, while anything that touches or stores card numbers in your own systems lands on the long one. Your acquirer confirms which applies to your account, and that answer should be in writing.

More on this