Skip to content
Services
PCI DSSISO 27001SOC 2GDPRPenetration TestingNIST CSFvCISODORA
Company
Case StudiesPartnersTrust CenterBlogGlossaryFAQFree AssessmentContact
Industries
FintechHealthcarePaymentsSaaS
AboutResourcesVeedar

SAQ-A vs SAQ-D: Which PCI DSS Self-Assessment Questionnaire Do You Need?

SAQ-A and SAQ-D sit at opposite ends of the PCI DSS self-assessment spectrum. SAQ-A is the shortest questionnaire for merchants who have fully outsourced card data handling to a PCI DSS–validated third party and never touch card data on their own systems. SAQ-D is the longest, covering all applicable PCI DSS requirements, because it's for merchants and service providers whose systems store, process, or transmit cardholder data directly.

The gap between them isn't paperwork — it's the difference between an audit that takes days and one that takes months. Which one applies to you is decided by architecture: where card data flows, and how much of it ever touches your infrastructure. That's the question CTOs and heads of engineering actually need answered, because the SAQ you land on is really a verdict on how big your cardholder data environment (CDE) is.

What is a Self-Assessment Questionnaire (SAQ)?

Per the PCI Security Standards Council, an SAQ is the "reporting tool used to document self-assessment results from an entity's PCI DSS assessment." It's one of two ways to validate compliance, the other being a full Report on Compliance (RoC), typically performed by a Qualified Security Assessor (QSA). Either route ends in an Attestation of Compliance (AoC) — the document merchants and service providers use to formally attest to their results, and the one your processor or enterprise customer actually asks for.

Not every company qualifies for an SAQ. Larger merchants, most service providers, and anyone a payment brand or acquirer designates for closer scrutiny may be required to complete a full RoC instead.

SAQ-A vs SAQ-D: the core comparison

SAQ-A, the light path:

  • Who it's for: Card-not-present merchants (e-commerce, MOTO) that fully outsource all cardholder data functions to PCI DSS–validated third parties.

  • Typical architecture: Redirect or hosted iframe/hosted fields to a compliant payment gateway; card data never touches your servers.

  • Cardholder data environment: Minimal to none — front end and back office typically out of scope.

  • Relative length: Shortest questionnaire.

  • Typical first-time effort: Days to a few weeks.

  • Common trigger: Using a hosted payment page, hosted fields, or a redirect checkout from a validated provider.

SAQ-D, the full path:

  • Who it's for: Any merchant or service provider whose systems store, process, or transmit cardholder data directly, and that doesn't qualify for a shorter SAQ.

  • Typical architecture: Card data handled, stored, or transmitted on your own systems — custom checkout, in-house tokenization, direct API integration to a processor.

  • Cardholder data environment: Broad — most infrastructure touching payment flows is in scope.

  • Relative length: Longest questionnaire — covers all applicable requirements.

  • Typical first-time effort: Weeks to several months, depending on true scope.

  • Common trigger: Owning any part of card capture, storage, or processing, or being a service provider to other merchants.

Final eligibility for any SAQ type is confirmed by your acquirer or QSA against the current SAQ Instructions and Guidelines — eligibility criteria can be updated between versions.

The single decision that moves you between them

The line between SAQ-A and SAQ-D is almost always the same architectural question: does cardholder data ever touch a system you control?

  • Redirect or hosted fields to a validated gateway — the card number goes from the browser straight to the processor, never to your servers. This keeps a merchant in SAQ-A territory.

  • Card data hits your own servers, database, or code — even briefly — and you move toward SAQ-D, because that infrastructure is now part of your CDE.

  • You're a service provider yourself (a gateway, PSP, EMI, or card program serving other merchants) — you're very likely a SAQ-D or full-RoC candidate.

This is why "SAQ-A vs SAQ-D" is really a scoping question, and why scope reduction is the highest-leverage PCI DSS decision a payment company makes.

How to shrink your scope before you pick a questionnaire

  1. Use hosted payment fields or a redirect checkout. If a validated gateway's iframe or hosted page collects the card number, your servers never see it.

  2. Tokenize early, and don't store raw PANs anywhere you don't have to.

  3. Segment your network so the systems that touch cardholder data are isolated from everything else.

Get these right, and a company that assumed it needed a full RoC often qualifies for a materially shorter SAQ.

Comments

Be the first to comment.

Leave a comment