PCI Self Assessment Questionnaire: Which SAQ Do You Need?
Payments Glossary

What Is a PCI SAQ? Choosing the Right Self-Assessment Form

A PCI self-assessment questionnaire is how most merchants validate PCI DSS compliance. Match your setup to the right SAQ and stop non-compliance fees.

On this page 6 sections
  1. What a PCI Self-Assessment Questionnaire Is
  2. PCI SAQ Types at a Glance
  3. Which PCI SAQ Do I Need? Match Your Setup to the Form
  4. SAQ a vs. SAQ A-EP: Hosted Checkout vs. a Self-Built Form
  5. Stop Paying the PCI Non-Compliance Fee
  6. Tips for Completing Your SAQ Accurately

Key takeaways

  • The right SAQ depends on where card numbers enter your business and whose systems they pass through. Your acquirer makes the final call.
  • A hosted checkout or iframe usually means SAQ A. Card fields built on your own page mean SAQ A-EP, even if card numbers never reach your server.
  • A monthly PCI non-compliance charge is your processor's pricing, not a card network fee or a fine. Submitting a current validation is how you remove it.
  • Any change to checkout code or payment hardware can move you to a different SAQ, so recheck after every change.

A PCI self-assessment questionnaire, or SAQ, is the form most small and midsize merchants complete to show their acquiring bank that they follow the Payment Card Industry Data Security Standard (PCI DSS). There are several SAQs, and the right one depends on a single question: where does card data touch your systems? Pick the form that matches your setup and you answer only the requirements that apply to you. Pick the wrong one and you either take on far more work than you need, or you sign an attestation that isn't true.

What a PCI Self-Assessment Questionnaire Is

PCI DSS is written and maintained by the PCI Security Standards Council (PCI SSC), a body founded by the major card networks. It is not a federal law. It is enforced through contracts. Card network rules require acquiring banks to make sure their merchants protect card data, and your merchant agreement passes that obligation down to you. If you're not sure where your acquirer ends and your processor begins, our explainer on what a payment processor actually does sorts it out.

The largest merchants are usually assessed by an outside security assessor. Smaller merchants usually validate on their own, and that is the job of the SAQ. Each SAQ is a slice of the full standard, cut down to the requirements that matter for one way of accepting cards. You work through each requirement, then sign an Attestation of Compliance (AOC), a short document that certifies your result. The AOC is what your processor actually wants on file.

Two points often get missed. First, your acquirer has the final say on your merchant level and on which SAQ you may use. Second, a PCI-compliant processor or gateway does not make your business compliant. It can shrink what you're responsible for, sometimes by a lot, but you still have to validate. A completed SAQ also isn't proof that you're secure. It's a signed statement that the listed controls are in place. For the standard behind all of this, see our plain-English guide to PCI DSS compliance.

PCI SAQ Types at a Glance

The table maps the merchant SAQs in the PCI SSC document library. The council revises the forms from time to time, so download the current version from its website instead of relying on any summary, including this one. Each form opens with eligibility criteria, and those criteria are detailed. Use the table to narrow your choice, then read the eligibility section of the actual form before you answer anything.

SAQTypical setupWhere card data goes
SAQ ACard-not-present sales fully handed off to a PCI-compliant provider's hosted payment page or iframeNever enters your systems
SAQ A-EPOnline store whose own web page builds or controls the payment form, then sends card data directly to the processorDoesn't reach your server, but your site affects its security
SAQ BImprint machines or standalone dial-up terminalsNot stored electronically; terminal isn't on your network
SAQ B-IPStandalone, PCI-approved terminals that connect to the processor over the internetNot stored electronically; terminal kept apart from other systems
SAQ C-VTOrders keyed one at a time into a web-based virtual terminalNot stored electronically; computer used in an isolated way
SAQ CPOS system or payment application connected to the internetNot stored electronically
SAQ P2PEOnly terminals from a validated, PCI-listed point-to-point encryption solutionEncrypted inside the terminal; you never hold readable card data
SAQ D for MerchantsAnything that doesn't fit the forms above, including electronic storage of card dataCovers the full PCI DSS

The PCI SSC also publishes a separate SAQ D for Service Providers, meant for businesses that handle card data on behalf of other companies. Merchants validating their own card acceptance don't use it.

Which PCI SAQ Do I Need? Match Your Setup to the Form

Start by listing every way you take a card, including the occasional phone order and the weekend market stall. Then trace each channel from the moment a card number enters your business to the moment it leaves.

Shopify and Other Hosted-Checkout Stores

If your platform runs the checkout page on its own servers, the platform collects the card data instead of you. Merchants in that position generally fit SAQ A, as long as they take no cards any other way. Confirm how your checkout is handled in Shopify's own PCI documentation and keep a copy with your records. Custom checkout scripts or apps that alter the payment step can change the answer. MannyPay supports Shopify payment processing along with other major carts.

WooCommerce, Magento and Self-Hosted Stores

On a self-hosted store, the payment plug-in decides your SAQ. A plug-in that shows a hosted page or iframe served by the gateway usually keeps you in SAQ A. When the plug-in builds the card fields on your own page with JavaScript and sends the data from the shopper's browser straight to the gateway, you're in SAQ A-EP. If card numbers ever pass through your server on the way out, the answer becomes SAQ D. The example further down shows why the line falls where it does.

Retail Counters With a Standalone Terminal

A countertop terminal that connects to the processor over the internet and isn't wired into your POS or other business systems is the classic SAQ B-IP setup. A terminal on an analog phone line points to SAQ B.

Restaurants and Bars With an Integrated POS

When the card reader talks to a POS that sits on your network, you're usually looking at SAQ C. Hardware that belongs to a validated P2PE solution is the exception. Pay-at-table handhelds fall under whichever category matches how they connect.

Check old habits too. A spreadsheet of regulars' card numbers kept for phone orders counts as electronic storage, and electronic storage rules out most of the shorter forms. Paper tabs with card details must be locked up and properly destroyed under the requirements your SAQ includes.

Phone and Mail Orders

Keying orders into a web-based virtual terminal on a computer set aside for that purpose can fit SAQ C-VT. If staff key phone orders into your POS instead, the POS's SAQ applies.

Businesses With More Than One Channel

A store with a Shopify site and a counter terminal has two setups. Acquirers handle this differently. Some accept one SAQ per channel. Others want a single assessment that covers everything, and that can push you toward SAQ D. Ask your processor before you start.

When PCI SAQ D Is the Only Fit

SAQ D for Merchants is the catch-all. You land there when you store card numbers electronically or when card data passes through your own web server. You also land there whenever no shorter form's eligibility criteria fit. It is the full standard, and for a small business it is a large project.

Often the cheaper move is to change the setup instead of filling out the long form. Swapping a self-built checkout for a hosted one, or replacing a stored card file with your gateway's tokens for repeat customers, can put you on a much shorter SAQ. The change has to be real and complete before you claim the shorter form.

SAQ a vs. SAQ A-EP: Hosted Checkout vs. a Self-Built Form

This is the most misunderstood line in the standard, because the two checkouts can look identical to a shopper. Here is an illustrative comparison. Assume two online-only stores that sell the same products through the same PCI-compliant gateway. Neither one stores card numbers.

Store 1 embeds the gateway's iframe. The boxes where the shopper types a card number are a window onto a page served by the gateway. The store decides where that window sits on its checkout page, but its own code never sees the digits. That points to SAQ A.

Store 2 builds its own card fields. The owner wants checkout to match the brand, so the developer writes the fields into the store's own page and uses the gateway's JavaScript library to send the data straight to the gateway, which returns a token. Card numbers never reach the store's server. But the page collecting them belongs to the store. If an attacker plants a malicious script on that page, the script can capture numbers as shoppers type them, and the gateway has no way to stop it.

That is why Store 2 lands in SAQ A-EP. The A-EP form carries far more requirements than SAQ A, including web server hardening and external vulnerability scanning, as set out in the form. Picture a third store that posts the form to its own server before forwarding the data to the gateway. Card data now passes through systems the store controls, and that points to SAQ D.

One misreading causes much of the confusion: "We use tokenization, so we're SAQ A." Tokenization protects card data after it has been captured. What decides your SAQ is who serves the page or fields where the number is entered.

SAQ A doesn't mean you have no web security duties. Recent versions of SAQ A ask merchants to confirm their site is protected against scripts that could tamper with the payment page or the redirect to it. Read that eligibility wording in the current form before you sign. Also make it a house rule that any checkout change triggers a PCI recheck. A new theme or a developer's quick fix can move you from A to A-EP with a single edit.

Stop Paying the PCI Non-Compliance Fee

Many processors add a monthly charge when they don't have a current validation from you on file. Statements label it differently, often as a PCI non-compliance or non-validation fee. Either way, it is your processor's pricing. It is not a card network fee, and it is not a government fine. Some processors also bill a separate PCI program fee for access to their compliance portal. That is processor pricing too, so ask what it buys you.

The cost is easy to underestimate because it arrives in small pieces. Find the charge on your statement and multiply it by the number of months it has appeared. That total is what not validating has cost you so far, and on many statements the charge keeps running until you submit. Set it against an afternoon spent on SAQ A or SAQ B-IP. Our guide to what normal processing fees look like can help you put it in context.

  1. Find the charge on your statement and note the month it started.
  2. Ask your processor which SAQ it has assigned you and how to reach its compliance portal. Compare that SAQ with how you take cards today.
  3. Complete the SAQ along with any scans it requires. Sign the AOC and submit it.
  4. Check the next statement to confirm the charge is gone. If it isn't, ask why in writing.

If a processor won't explain a fee or tell you how to remove it, take that seriously. It is one of the red flags to spot in a processing company.

Tips for Completing Your SAQ Accurately

Read eligibility first. If you can't truthfully check every eligibility box, you're on the wrong form. Stop and pick another one.

Sketch your card flow. A single page showing each device and website, plus the vendors and connections behind them, will answer most eligibility questions on its own.

Collect your vendors' AOCs. Ask your gateway and your POS or e-commerce platform for theirs. Several SAQs ask you to confirm that your service providers are compliant and that you monitor them.

Answer honestly. "In place" should mean in place today. The AOC is a signed statement, and after a breach, investigators compare it with what they actually find. Our card data breach response plan shows what that process looks like.

Explain "not applicable" answers. Some forms require a written justification for each requirement you mark as not applicable.

Put the dates on a calendar. Validation is typically annual, and any scan schedule is set out in the SAQ itself. Your acquirer sets your deadline.

Get help when the stakes are high. If you land in SAQ D, or your setup doesn't fit any form cleanly, a qualified PCI professional is worth the fee. This article is general information, not legal or compliance advice.

Your scope is also a choice you make when you buy equipment and software. Hosted payment gateways and standalone or P2PE-listed terminals can keep you on a shorter form, while a POS system wired into your network usually adds requirements. Start with last month's statement: look for a PCI line, then ask your processor which SAQ it has on file for you. If you're replacing hardware or rebuilding checkout, request a free quote and a MannyPay specialist will respond within one business day to talk through setups that fit how you sell.

About the author

Adrian Reyes

Adrian Reyes is Senior Payments & Fintech Editor for Beyond the Swipe, covering credit card processing, merchant accounts, payment technology and processing fees.

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