PCI Compliant Payment Processing: How to Choose a Compliant Setup

Bottom Line Up Front

If an email just landed in your inbox from your payment processor asking you to “validate PCI compliance” and you have no idea what that means — take a breath. For the overwhelming majority of small businesses, setting up PCI compliant payment processing is far less painful than the acronym soup suggests.

Here’s the short version:

  • You need to do this if you accept credit or debit cards in any form.
  • Most small merchants self-assess. You fill out a questionnaire (an SAQ) once a year, sign an attestation, and — depending on your setup — run a quarterly external vulnerability scan.
  • The work scales with how much card data you touch. If you’ve outsourced card handling to a hosted checkout page or a modern payment terminal, you may answer only a short set of questions.
  • The biggest cost lever is scope. The less cardholder data flows through your own systems, the fewer rules apply to you.

Most of the merchants I assess who panic at the word “PCI” discover their real to-do list is: confirm how payments flow, pick the right SAQ, gather a handful of documents, schedule a scan, and submit. Let’s walk through it.

What Is PCI Compliance (In Plain English)

PCI DSS stands for the Payment Card Industry Data Security Standard. It’s a set of security rules for any organization that stores, processes, or transmits payment card data. The goal is simple: keep card numbers out of the hands of criminals.

The standard was created by the major card brands — Visa, Mastercard, American Express, Discover, and JCB — who formed the PCI Security Standards Council (PCI SSC) to maintain it. The Council writes the rules, but it doesn’t police you. Enforcement flows through your acquiring bank or payment processor, which is contractually obligated to the card brands to make sure its merchants are validating compliance. That’s why the questionnaire came from them and not from some government agency.

What happens if you ignore it

Nothing dramatic on day one. Over time, though, the consequences stack up:

  • Non-compliance fees assessed by your processor, often appearing as a recurring monthly line item on your statement.
  • Liability exposure if you suffer a breach. A merchant who was not validated when card data was stolen is in a much worse position when the card brands assess costs for fraud, card reissuance, and forensic investigation.
  • Loss of card acceptance. Processors can and do terminate merchant accounts for persistent non-validation. Losing the ability to take cards is an existential problem for most businesses.

The good news

The standard is organized into six control objectives covering 12 requirements, which sounds like a lot. But you only have to satisfy the requirements that actually apply to how you take payments. A business using a standalone terminal that dials out to the processor is in a completely different world than one running a custom checkout that handles raw card numbers. The current standard recognizes this through different Self-Assessment Questionnaire (SAQ) types — and most small businesses qualify for the simplest ones.

Do You Need to Be PCI Compliant?

If you accept payment cards, yes. There’s no revenue floor, no exemption for “we only do a few transactions a month,” and no carve-out for nonprofits or sole proprietors. Accepting cards means agreeing to your merchant services contract, and that contract includes PCI DSS.

Your merchant level

The card brands sort merchants into Levels 1 through 4 based on annual transaction volume and risk history. Level 1 merchants — the largest — generally undergo a formal Report on Compliance (ROC) performed by a Qualified Security Assessor (QSA) or an internal assessor (ISA). Everyone else typically self-assesses.

Most small and mid-size businesses land at Level 4. But thresholds are card-brand-specific and can change, and your acquirer can bump you up a level after a breach or for other risk reasons. Confirm your level with your acquirer rather than assuming — it’s a one-email question and it determines your whole validation path.

About that questionnaire

The document your processor sent is almost certainly a request to complete an SAQ and sign an AOC (Attestation of Compliance). The SAQ is the self-assessment itself; the AOC is the cover document where an authorized person at your business formally attests to the results. Your processor needs the AOC on file. Some processors route this through their own compliance portal; others accept a PDF by email.

Which SAQ Do You Need?

This is the single most important decision in the whole process, because the SAQ you choose determines how many requirements apply to you. Pick the wrong one and you’ll either do far more work than necessary or submit an attestation that doesn’t reflect reality.

The deciding question is always the same: where does card data actually go?

Your payment scenario Likely SAQ Complexity
E-commerce, all payment pages fully hosted/redirected to a compliant provider A Lowest
E-commerce where your site partially controls the payment page (direct post, JavaScript-created or embedded card fields) A-EP High
Standalone dial-out terminal or imprint machine, no electronic card data storage B Low
Standalone IP-connected payment terminal, no electronic storage B-IP Low–Moderate
Virtual terminal only — staff key cards into a browser-based form on one dedicated workstation C-VT Moderate
Payment application connected to the internet (integrated POS), no electronic storage C Moderate–High
Validated P2PE solution with a listed hardware terminal P2PE Low
You store card numbers electronically, or nothing above fits D Highest

A few real-world translations:

  • Countertop terminal from a modern provider: usually SAQ B or B-IP depending on whether it connects over a phone line or your network. If your provider’s solution is on the PCI SSC’s validated P2PE listing, you may qualify for the shorter SAQ P2PE instead — ask them directly.
  • Shopify, a fully hosted checkout, or a redirect to your processor’s payment page: typically SAQ A. Your website never touches the card number.
  • An embedded payment form on your own checkout page (common with WooCommerce plus embedded card fields): this is usually SAQ A-EP, and it’s a meaningful step up — your site influences how the payment page is delivered, so your web server comes into scope.
  • Phone orders keyed into your gateway’s browser portal: generally SAQ C-VT, assuming that workstation isn’t doing double duty for everything else.
  • Card numbers written on order forms, saved in a spreadsheet, or sitting in your CRM: that’s SAQ D, and the honest advice is to stop storing them. Your gateway almost certainly offers tokenization, which replaces stored PANs with meaningless tokens and can collapse your scope dramatically.

If you’re unsure — and plenty of businesses genuinely are, especially when they have both a storefront and a website — our free SAQ Wizard asks a handful of plain-language questions about how you take payments and tells you which questionnaire fits. It takes a few minutes and costs nothing.

How to Complete Your SAQ

What it looks like

An SAQ is a structured list of yes/no questions mapped to the applicable PCI DSS requirements, plus a section where you describe your environment. Question counts vary by SAQ type and between revisions of the standard, so don’t anchor on a number you read somewhere — the practical point is that SAQ A is short and SAQ D is long.

A merchant with a clean SAQ A setup can often finish in an afternoon. SAQ A-EP or D realistically takes weeks, because answering honestly means implementing controls you may not have yet.

What “yes” actually means

Each answer is an assertion that a control is in place today. “Yes” to a question about unique user IDs means every person with access to in-scope systems has their own account — no shared logins. “Yes” to a question about default passwords means vendor defaults were changed on your router, terminal, and any payment-adjacent system.

If you can’t answer yes yet, that’s not a failure — it’s your remediation list. Fix it, then answer honestly. Never attest to a control you haven’t implemented; the AOC is a signed statement, and it will be examined closely if you’re ever breached.

Documentation to gather

  • A simple network diagram and a cardholder data flow diagram showing where card data enters, travels, and leaves
  • An inventory of payment terminals, serial numbers, and locations
  • Your information security policy and acceptable use policy
  • Evidence of annual security awareness training for staff who handle payments
  • A written incident response plan with who to call
  • Your vendor list and confirmation that your processor, gateway, and hosting provider maintain their own compliance
  • Recent ASV scan reports, if applicable

The quarterly ASV scan

If your environment includes internet-facing systems in scope — your website, a firewall with a public IP, an IP-connected terminal environment — the current standard requires quarterly external vulnerability scans performed by an Approved Scanning Vendor (ASV). Only ASVs accredited by the PCI SSC can produce a passing scan report that satisfies this.

The scan probes your public IP addresses and domains for known vulnerabilities, then issues a report. If vulnerabilities above the failing threshold are found, you remediate and rescan until you pass. Schedule scans early in each quarter so you have time to fix findings before the quarter closes. Our ASV scanning service handles the quarterly cadence and gives you remediation guidance alongside the raw findings.

Note that SAQ A and SAQ B merchants often have no in-scope external systems, which may mean no scan requirement. Confirm with your acquirer rather than guessing in either direction.

Submitting

Complete the SAQ, sign the AOC, attach passing scan reports if required, and upload or email the package to your processor’s compliance portal. Keep a copy. You’ll need it next year as a baseline.

What It Costs

Pricing varies by provider and environment, so treat the following as shape rather than precise figures — get quotes.

Item What drives the cost Typical effort
Compliance platform / guided SAQ Number of merchant locations Modest annual subscription
ASV scanning Number of public IPs and domains scanned Quarterly, per-IP pricing
Remediation work How much card data your systems touch One-time, highly variable
QSA-led ROC Level 1 merchants; complex environments Substantially higher — an engagement, not a subscription
Penetration testing Required where the standard’s scope rules call for it Annual engagement

The honest comparison: for a typical self-assessing merchant, a year of compliance tooling and scanning typically costs far less than the non-compliance fees many processors charge over the same period — and it’s not remotely in the same universe as the costs that follow a breach, which can include forensic investigation by a PFI (PCI Forensic Investigator), card reissuance assessments, and legal exposure.

A caution: PCI compliance is not a guarantee against a breach. It is a baseline of risk reduction that also puts you in a defensible position if something goes wrong.

Staying Compliant Year-Round

The most common mistake I see is treating validation as an annual fire drill. Compliance is a point-in-time attestation about a continuous state. You sign the AOC in March; the controls have to hold in August too.

Practical habits that keep it manageable:

  • Calendar your scans. Four per year, scheduled in advance, with buffer for remediation.
  • Set a renewal reminder 60 days before your AOC anniversary.
  • Review firewall rules and user access periodically — per the current standard’s cadence — and keep the notes.
  • Reassess when things change. Switching gateways, redesigning your checkout, adding a new location, moving from a redirect to an embedded payment form, or starting to store card data all can change your SAQ type. That last one in particular: moving from a hosted checkout to embedded fields can push you from SAQ A to SAQ A-EP, a significant jump.

Our compliance dashboard exists for exactly this. It tracks your SAQ status, scan schedule, open remediation items, and renewal dates so nothing quietly lapses between annual cycles.

FAQ

I only take a handful of card payments a month. Do I really have to do this?

Yes. There’s no minimum transaction volume that exempts a merchant. The upside is that very low-volume merchants with simple setups usually qualify for one of the shortest SAQ types, so the actual workload is small.

What’s the difference between an SAQ and an AOC?

The SAQ is the questionnaire where you assess each applicable requirement. The AOC is the short attestation document you sign confirming the results, and it’s typically what your acquirer files. You generally complete both and submit them together.

Does my payment processor being PCI compliant make me compliant?

No. Your processor’s compliance covers their systems, not yours. You still have obligations around your network, your staff, your terminals, and your website — though using a compliant provider does reduce how many of those obligations apply to you.

Can I just answer “yes” to everything to get it over with?

Please don’t. The AOC is a signed attestation, and inaccurate answers become a serious liability if you’re ever breached and a forensic investigator reviews your documentation. Answer honestly and treat the “no” answers as a remediation plan.

Do I need a QSA?

Most small merchants don’t. QSAs are generally required for Level 1 merchants and for complex environments needing a formal ROC. If you’re self-assessing, you can still engage a QSA for advice without commissioning a full assessment.

What about Sensitive Authentication Data — the CVV code?

SAD — full track data, card verification codes like CVV2/CVC2/CID, and PINs — must never be stored after authorization, under any circumstances. If you find CVVs in a spreadsheet, a ticketing system, or a call recording, that’s an urgent problem to remediate.

How long does compliance take the first time?

A clean SAQ A setup can be done in an afternoon. SAQ B or B-IP might take a few days of gathering documentation. SAQ A-EP, C, or D environments often take weeks to months, mostly spent implementing controls rather than filling in forms.

What if I fail my ASV scan?

Failing is normal and expected, especially on the first scan. You receive a findings report, remediate the issues, and request a rescan — the requirement is a passing scan each quarter, not a perfect first attempt.

Where to Start

Here’s the sequence that works: confirm your merchant level with your acquirer, map how card data actually flows through your business, identify the correct SAQ, close the gaps, scan if required, and submit. Then set reminders so next year is a review rather than a rediscovery.

And wherever you have a choice, choose the option that keeps card data out of your systems entirely. Hosted checkout pages, validated P2PE terminals, and tokenization aren’t just security best practices — they’re the difference between a short questionnaire and a long one. Designing for pci compliant payment processing from the start is dramatically cheaper than retrofitting it later.

PCICompliance.com is built to carry you through all of it. We serve thousands of merchants and service providers, from single-location retailers to multi-site enterprises, with everything in one place: a free SAQ Wizard that pinpoints exactly which questionnaire you need, an ASV scanning service that handles your quarterly external vulnerability scans with remediation guidance attached, and a compliance dashboard that keeps your deadlines and open items visible year-round — backed by people who do this every day.

Start with the free SAQ Wizard, or talk to our compliance team if you’d rather have someone look at your setup with you first. Either way, you’ll know where you stand in far less time than that questionnaire email suggests.

Leave a Comment

1,650 PCI scans completed this month