CardComply

SAQ A vs SAQ A-EP

SAQ A vs SAQ A-EP: the difference is one question.

If the customer types their card details into a page your business controls before those details go to your payment provider, you are SAQ A-EP. If they type into the provider's page and your site never handles the number, you are SAQ A.

That is the whole distinction. Not your size, not your volume, not which platform you use. Whether card data passes through your site.

SAQ A is roughly a dozen requirements. SAQ A-EP is the full requirement set that applies to a merchant whose site is in the payment flow. The gap between them is not a formality — it is most of the work.

The test, in plain terms

Open your checkout and watch where the card fields live.

  • The card fields are on a page with your domain in the address bar, and your site posts that data onward → A-EP.

    Even if a payment provider sits behind it. Even if your developer calls it "tokenised". Even if you never see the numbers. Passing through is enough.

  • The card fields are inside an iframe or a redirect served by the provider, on the provider's own page → A.

    Shopify's hosted checkout, Stripe Checkout, Square Online, PayPal all work this way. Your site never holds the number.

Two follow-ups that decide a lot of borderline cases:

  • Do you have a custom checkout?

    If someone built the payment form into your site, assume A-EP until proven otherwise.

  • Does your provider's documentation say "SAQ A eligible"?

    Read what it says you must have done to qualify. Eligibility usually depends on your integration method, not on the provider's name.

What each one asks for

What SAQ A actually asks for

A small number of requirements, mostly about the hosted payment page and confirming the provider carries their side. You will need written policy for a handful of them, and evidence that your checkout really is fully outsourced.

Where people trip: believing they are SAQ A when card data does pass through their site, and having no written policy at all — the most common gap we see at this level.

Effort: a few hours of your time over a week or two, plus the policies. Project work: SAQ Done Right $1,500–$3,500, starting fee up front. Retainer $500/mo.

What SAQ A-EP actually asks for

The full set of requirements for a merchant with a site in the payment flow: written policies, a change process for your website, evidence of how the checkout is built and maintained, and the controls around the systems that serve it.

Where people trip: assuming the hosted payment page takes the website out of scope. It does not. Your developer will need to answer a handful of the questions, so get them involved early rather than at the end.

Effort: about a week of elapsed time with your developer in the room for the checkout questions. Project work: SAQ Done Right $1,500–$3,500, starting fee up front. Retainer $1,000/mo.

If you take payments both ways

Online plus in-person is not one questionnaire. It is commonly SAQ A or A-EP for the website and SAQ B-IP for the terminals. The two are filed separately and both need to be current. Filing the online one and calling it done is a finding waiting to happen.

If your terminals are the bigger question, B-IP or C for multi-location merchants →

If you are not sure

Do not default to A because it is shorter. Filing the shorter questionnaire when card data passes through your site is the specific mistake that gets flagged — the answers on the form then contradict what the site actually does, and that is what a reviewer looks for.

The free Scope Check asks which payment channels you use and who handles the card data, and gives you a clear or likely answer with the reasoning. If the answer is "likely", that is the call's job: twenty minutes, no charge, and we pin it down.

Check which SAQ applies to you — free.

Twenty minutes on the phone, no charge, and we pin it down. You leave with your likely SAQ type and merchant level in writing.

CardComply provides consulting, readiness, and compliance-management services. CardComply is not a QSA company and does not perform PCI DSS assessments or issue Reports on Compliance or certifications. CardComply never collects or stores cardholder data.