Glossary/SAQ (Self-Assessment Questionnaire)

What is a SAQ (Self-Assessment Questionnaire)?

A Self-Assessment Questionnaire (SAQ) is a form that businesses fill out to demonstrate their compliance with PCI DSS requirements. The SAQ type you need depends on how you accept card payments, with simpler questionnaires available when card data never enters your environment.

Understanding the PCI DSS Self-Assessment Questionnaire

The Self-Assessment Questionnaire is a validation tool created by the PCI Security Standards Council. It allows merchants and service providers to report the results of their own PCI DSS assessment. Rather than hiring an external assessor for every business that handles card payments, the SAQ provides a structured way for organisations to evaluate and document their security controls.

Every business that accepts, processes, stores, or transmits cardholder data must validate its PCI DSS compliance. For most small and mid-sized businesses, the SAQ is the primary method of doing so. Larger organisations processing millions of transactions annually typically require a formal audit by a Qualified Security Assessor (QSA) instead.

The Different SAQ Types

There are several SAQ types, each designed for a specific card acceptance method. The most common include:

  • SAQ A — For merchants that have fully outsourced all cardholder data functions to PCI DSS-validated third parties. This is the shortest and simplest questionnaire, with around 22 requirements.
  • SAQ A-EP — For e-commerce merchants that partially outsource payment processing but whose website could affect the security of the transaction.
  • SAQ B — For merchants using imprint machines or standalone dial-out terminals with no electronic cardholder data storage.
  • SAQ B-IP — For merchants using standalone, PCI-listed payment terminals connected via IP, with no electronic cardholder data storage.
  • SAQ C — For merchants with payment application systems connected to the internet but no electronic cardholder data storage.
  • SAQ C-VT — For merchants manually entering a single transaction at a time via a virtual terminal on a computer connected to the internet.
  • SAQ D — The most comprehensive questionnaire, covering all PCI DSS requirements. This applies to merchants and service providers that do not fall into any other SAQ category.

Why Your SAQ Type Matters

The difference between SAQ types is significant. SAQ A contains roughly 22 requirements, whilst SAQ D contains over 300. Reducing your SAQ scope saves time, money, and administrative burden. More importantly, it typically means your systems handle less sensitive data, reducing your risk of a breach.

How to determine your SAQ type

Your SAQ type depends on your payment acceptance channels and how cardholder data flows through your systems. If card data never touches your environment — because it is captured by a third-party service — you may qualify for a simpler SAQ. If your staff handle card numbers directly, or if your systems store or process card data, you will likely need a more comprehensive questionnaire.

Completing Your SAQ

Each SAQ contains a series of yes-or-no questions about your security controls. For each requirement, you must indicate whether the control is in place, not in place, or not applicable. You must also provide an explanation for any controls marked as not applicable. Once completed, the SAQ is submitted alongside an Attestation of Compliance (AOC) to your acquiring bank or payment brand.

Many businesses find the SAQ process challenging because it requires detailed knowledge of how card data moves through their systems. Working with a payment solution that reduces your scope can dramatically simplify the process.

How Paytia Uses This

Paytia's secure payment solutions are specifically designed to reduce your PCI DSS scope and simplify your SAQ. When you use Paytia's DTMF suppression technology for telephone payments, card numbers entered by the caller never reach your contact centre environment. Your agents cannot hear, see, or access the card data at any point during the call.

This means businesses using Paytia can typically qualify for SAQ A or SAQ A-EP rather than the much longer SAQ D. Instead of answering over 300 compliance questions, you may only need to complete around 22. Paytia is PCI DSS Level 1 certified — the highest level of certification — so the security of the payment capture is already validated on your behalf.

By removing card data from your telephony environment entirely, Paytia not only makes compliance easier but also reduces the risk and cost associated with handling sensitive payment information.

Frequently Asked Questions

How many SAQ types are there?

There are nine SAQ types (A, A-EP, B, B-IP, C, C-VT, D for merchants, D for service providers, and P2PE). The one you need depends on how your business accepts and processes card payments.

Can Paytia help me reduce my SAQ scope?

Yes. Because Paytia's DTMF suppression ensures card data never enters your contact centre, most businesses using Paytia can qualify for SAQ A instead of the much longer SAQ D, reducing the number of compliance requirements from over 300 to around 22.

How often do I need to complete a SAQ?

You must complete and submit a SAQ annually to your acquiring bank or payment brand to maintain your PCI DSS compliance validation.

See how Paytia handles saq (self-assessment questionnaire)

Book a personalised demo and we'll show you how our platform works with your setup.

Request a Demo