Web Application Development
Mobile App Development
UI/UX Design
API & Backend Development
DevOps and Cloud Solutions
Web Application Development
Mobile App Development
UI/UX Design
API & Backend Development
DevOps and Cloud Solutions

SAQ A vs SAQ A-EP: Which PCI DSS Assessment Applies?

SAQ A vs SAQ A-EP

SAQ A applies when your payment page is fully outsourced to a PCI DSS compliant provider through a redirect or an iframe your website doesn’t influence. SAQ A-EP applies when your own web server generates, hosts, or otherwise affects the security of that payment page, even if cardholder data never touches your server. Picking the wrong one is one of the most common PCI DSS mistakes e-commerce merchants make.

If you’ve ever asked your payment gateway which questionnaire you need and gotten a vague answer, you’re not alone. The two forms look similar on the surface, both apply to merchants who don’t store card data, but the actual compliance workload between them is enormous. Getting this wrong doesn’t just mean extra paperwork. It can mean failing an assessment, triggering a card brand inquiry, or discovering during fintech app development that the payment integration your team built quietly moved you from a short self-assessment into one of the longest ones PCI DSS offers.

What Is SAQ A?

SAQ A is the shortest PCI DSS self-assessment questionnaire, built for e-commerce merchants whose payment pages are entirely outsourced to a PCI DSS compliant third party, with no part of that page originating from the merchant’s own website. The merchant’s web server never receives, processes, transmits, or otherwise touches cardholder data.

What Is SAQ A-EP?

SAQ A-EP, where “EP” stands for e-commerce payments, is a far longer questionnaire for merchants whose web server is involved in the security of the payment transaction even though it still doesn’t store cardholder data directly. This covers merchants whose own page constructs the payment form, controls what loads into it, or otherwise influences the security of account data in transit, which SAQ A’s narrower scope doesn’t account for. Both questionnaires, along with every other SAQ type, are published directly in PCI SSC’s document library.

SAQ A vs SAQ A-EP at a Glance

Factor SAQ A SAQ A-EP
Who it’s for Fully outsourced payment page, no merchant involvement Merchant web server affects payment page security
Typical integration Redirect or iframe entirely from a compliant provider Direct post, JavaScript-controlled forms, custom checkout pages
Cardholder data on merchant servers Never Never stored, but the server still touches the transaction flow
Relative length Shortest SAQ available One of the longest, covering most of the full DSS requirement set
Script and change-detection controls Only required if eligibility criteria can’t otherwise be confirmed Built into the questionnaire by default
Common mistake Assuming any iframe automatically qualifies Assuming a gateway’s compliance alone covers the merchant

SAQ A vs SAQ A-EP by Payment Integration Method

The single biggest factor in which questionnaire applies isn’t your industry or your transaction volume. It’s how your checkout page is actually built.

Redirect. The customer’s browser leaves your site entirely and lands on the payment provider’s own page. SAQ A is available here, but only if that provider is itself PCI DSS compliant.

iFrame. The payment form displays inside your page, but every element of it, the fields, the scripts, the styling, must come from the compliant provider with nothing originating from your own code. PCI SSC’s own guidance on iframe and direct post eligibility states plainly that if any element of a payment page originates from the merchant’s website, the implementation isn’t eligible for SAQ A.

Direct post. Your own web server builds or renders part of the payment page, and JavaScript on that page sends card data straight to the processor without it passing through your server. This feels secure since you never see the card number, but it still requires SAQ A-EP, because your server controls what code runs on that page and an attacker who compromises your site can still tamper with the data in transit.

The 2025 Eligibility Update You Need to Know About

PCI DSS v4.0.1 added a new SAQ A eligibility requirement that took effect April 1, 2025, and a lot of merchants using iframe-based checkouts still haven’t caught up with it. PCI SSC’s official FAQ 1588 clarifies that merchants embedding a provider’s payment page through an iframe must now confirm their site is not susceptible to script-based attacks that could affect the e-commerce environment, not just confirm that the provider is compliant.

There are two ways to satisfy this. One is implementing technical controls similar to Requirements 6.4.3 and 11.6.1 of the full PCI DSS standard, which cover authorizing and inventorying every script that runs on the payment page and detecting unauthorized changes to it. The other is getting written confirmation from your payment provider that their embedded solution, deployed exactly as instructed, already includes these protections. This criterion only applies to iframe-embedded checkouts. Merchants using a full redirect or a completely outsourced payment flow aren’t affected by it.

This update exists because of a real and growing threat. E-skimming attacks, where malicious code injected into a checkout page silently copies card numbers as customers type them, don’t care whether your server technically “touches” cardholder data. A compromised script running inside your iframe can capture data before it ever reaches the provider. Our web app security checklist covers the broader script and dependency monitoring practices this kind of attack calls for.

How to Determine Which SAQ Applies to Your Business

Start with your payment provider’s own integration documentation rather than guessing. Most providers that offer redirect, iframe, and direct post options will tell you plainly which SAQ each one maps to, since they’ve been asked this question thousands of times.

Next, confirm whether anything on your own domain constructs, styles, or scripts the payment form, even indirectly. A single line of custom JavaScript touching the checkout page can be the difference between SAQ A and SAQ A-EP.

If you’re using an iframe, get written confirmation from your provider that their solution meets the new script-protection criterion from FAQ 1588. Without that confirmation, or without implementing equivalent controls yourself, you may not be eligible for SAQ A even on an integration that used to qualify under older guidance.

When the answer still isn’t clear, your acquiring bank or the relevant card brand has the final say, not your payment gateway’s sales team and not a generic compliance checklist found online. PCI SSC’s own SAQs for PCI DSS v4.0.1 bulletin is a good starting reference if you want the eligibility language in its original form rather than a secondhand summary.

What Happens If You Pick the Wrong SAQ

Self-selecting the wrong questionnaire isn’t just a paperwork error. If an acquirer or card brand later determines that SAQ A-EP’s scope actually applied to your environment, your attestation of compliance can be invalidated retroactively, which matters most if a breach happens in the meantime. Payment card networks can also require merchants to move to a more rigorous assessment after a disputed or non-compliant filing, sometimes alongside increased transaction fees.

The more common failure mode isn’t malicious shortcutting. It’s a merchant whose payment integration changed, a developer added a custom field, a marketing script got embedded near checkout, a new upsell widget touched the payment page, without anyone revisiting which SAQ still applied. Reassessing eligibility whenever the checkout flow changes is cheaper than discovering the gap during an incident response.

Mobile and In-App Payment Pages

The same logic extends to mobile. An app that opens a payment page inside a WebView or in-app browser the way a mobile site would needs the same redirect-versus-iframe-versus-direct-post analysis applied to it, and a native SDK that collects card details directly inside the app introduces its own separate PCI DSS considerations entirely outside SAQ A and A-EP. Getting this architecture right from the start, rather than retrofitting it after launch, is a core part of how we approach secure mobile app development.

Building or Updating a Payment Page the Right Way

Whichever SAQ you land on, the underlying engineering decisions are what actually determine your real-world risk, not just your paperwork burden. Secure web application development practices around script management, content security policies, and payment page isolation reduce exposure regardless of which questionnaire you file.

The backend side matters just as much. How your systems communicate with a payment processor, whether through a direct API integration or a hosted checkout handoff, shapes both your SAQ eligibility and your actual attack surface. Our guide to third-party API integration best practices covers the patterns that keep that connection secure.

If you’re planning a new storefront or checkout flow rather than retrofitting an existing one, deciding your payment architecture during ecommerce app development rather than after launch avoids most SAQ A-EP surprises entirely.

For the broader compliance picture beyond just these two questionnaires, our complete guide to PCI DSS for payment apps covers scope, tokenization, and the rest of the standard this post builds on.

Get Your Payment Architecture Right the First Time

SAQ A and SAQ A-EP aren’t just compliance paperwork categories. They’re a direct reflection of how much of your payment flow your own code actually touches, and that architecture decision affects your security posture long before anyone fills out a questionnaire. If you’re building or rearchitecting a checkout experience and want the integration method to match the compliance outcome you’re expecting, talk to our team before the build starts, not after the assessment.

Frequently Asked Questions

Can I use SAQ A if I use an iframe for payments?

Yes, but only if every element of that iframe originates from a PCI DSS compliant provider with nothing from your own site involved, and as of April 2025, only if you can confirm the page is protected against script-based attacks under FAQ 1588’s criteria.

Why does direct post always require SAQ A-EP?

Because your web server builds or influences the payment page even though cardholder data bypasses it, which means a compromise of your site could still affect the integrity of that data in transit.

How much longer is SAQ A-EP than SAQ A?

Substantially longer. SAQ A covers a narrow set of controls focused on basic system hygiene, while SAQ A-EP covers most of the full PCI DSS requirement set, including vulnerability management, access control, logging, and payment page script protections.

Does my payment gateway being PCI compliant automatically make me eligible for SAQ A?

No. The gateway’s own compliance is necessary but not sufficient. Your integration method, and since 2025, your ability to demonstrate script-attack protection on an iframe, both factor into eligibility.

What triggered the 2025 change to SAQ A eligibility?

PCI SSC added the new criterion to address e-skimming, where malicious scripts injected into a checkout page capture card data directly from the browser regardless of whether the merchant’s server ever technically touches it.

Who decides which SAQ my business should use?

Ultimately you’re acquiring a bank or the card brands involved. Your payment provider can tell you which SAQ their specific integration method typically maps to, but the final determination rests with your acquirer.

Table of Contents

Picture of Muntaha Binte Saleem

Muntaha Binte Saleem

Let’s Build Something Great
Still Thinking It Over?

Submit your details and our team will reach out to discuss how we can bring your app or software idea to life.

Web Development Mobile Apps Custom Software