Skip to content

SAQ A vs SAQ A-EP: the one question that decides it

By Sam Rivera, Founder, SentinelPanda · September 2, 2026 · 4 min read · PCI DSS

Most merchants are told which SAQ they owe by a payment provider who has never looked at their checkout. The answer turns on one technical fact, and it is cheap to establish.

The distinction in one sentence

SAQ A covers merchants who have outsourced all card handling and all control of the payment page to a validated third party. SAQ A-EP covers merchants who have outsourced card handling but not the page — their website still determines how, where and whether the card capture happens.

That distinction sounds academic until you notice what it protects against. If your server never sees a card number but your page decides which script collects it, then anyone who can modify your page can change where the card goes. The data flow is identical right up until it is not, and the attack that exploits the difference leaves the payment processor entirely untouched.

What each integration pattern maps to

  • <strong>Redirect</strong> — the customer leaves your site for the provider's hosted page, pays, and comes back. SAQ A.
  • <strong>Iframe</strong> — the card fields are served inside an iframe whose content comes wholly from the provider. SAQ A, provided your page does not reach into or manipulate it.
  • <strong>Direct post</strong> — your page renders the card fields and posts them straight to the provider, bypassing your server. Feels like outsourcing; it is SAQ A-EP.
  • <strong>JavaScript tokenisation on your own form</strong> — your form, your markup, the provider's script turning the number into a token in the browser. SAQ A-EP.
  • <strong>Your server receives the number, even briefly</strong> — neither. That is SAQ D.

Why "we use Stripe" does not answer it

Every one of the patterns above can be built on the same processor. Stripe, Adyen, Braintree and the rest all offer a hosted page and a library you drop into your own form, and the second is more popular because it converts better and looks like your brand.

So the name of the processor tells you nothing about which questionnaire applies. What tells you is which integration your developers chose, usually years ago, for reasons that had nothing to do with compliance. A merchant can genuinely believe they are SAQ A because they never touch a card number, and be wrong, because that was never the test.

How to find out in ten minutes

Open your checkout and view the page source. If the card input fields are inside an <code>&lt;iframe&gt;</code> whose <code>src</code> points at your payment provider's domain, you are in SAQ A territory. If the inputs are in your own HTML — even if a provider's JavaScript reads them — you are in A-EP territory.

The ambiguous middle case is worth naming: some providers offer individual hosted fields, where each input is its own small iframe styled to look like your form. That is still the provider serving the fields, so it generally lands in SAQ A, but your page hosts the frame and loads the script that creates it — which is exactly why the 2025 revision of SAQ A added a condition about scripts.

The cost of getting it wrong in each direction

Claiming SAQ A when you owe A-EP means you have signed an attestation that is not true. The practical risk is not a fine arriving in the post — it is what happens after an incident, when a forensic investigator reconstructs the integration and your acquirer reads the attestation you signed. Fees for non-compliance at the time of a breach are set by the card brands and passed through by your acquirer, and they do not care that the error was honest.

Claiming A-EP when you qualify for A is harmless but expensive: roughly 140 questions instead of 30, quarterly external scans by an approved scanning vendor, and penetration testing obligations you did not need.

What to do about it

Establish the integration pattern once and write it down, with a screenshot of the page source and the date. That single artefact answers the question for your acquirer, your next auditor and whoever inherits the checkout after you.

If you are mid-redesign or about to replatform, this is the moment to choose deliberately. Moving from a direct-post form to a provider-hosted iframe is usually a day of frontend work, and it removes about 110 questions and a scanning obligation from your year, every year.

Which PCI SAQ type applies to you SAQ A walkthrough SAQ A-EP walkthrough What changed in the revised SAQ A

Run your compliance program in one workspace.