SAQ A is the shortest PCI DSS self-assessment questionnaire there is. It is not a reward for using a payment provider, and it is not a statement that your checkout is safe. The SAQ A eligibility criteria describe one narrow situation: a merchant who has pushed every card data function out to validated third parties and keeps nothing electronic of their own. Plenty of UK merchants file it. Fewer still qualify on the day they file it, and fewer again qualify six months later, after a theme update and three new tags.
This piece walks the criteria against a real checkout, rather than restating the standard. It is written for the people who have to defend the page.
What the SAQ A eligibility criteria actually require
In plain English, SAQ A is for card-not-present merchants who have outsourced all payment processing to PCI DSS validated third-party service providers. You do not electronically store, process or transmit cardholder data on your own systems or premises. Any cardholder data you retain is on paper, and that paper did not arrive electronically. You have confirmed that the providers handling the card data are validated, and you hold evidence of it.
For the e-commerce channel there is a further condition about the payment page itself, which is covered further down. It is the part most merchants skim past.
Eligibility is per channel, not per company
An SAQ A claim for your website says nothing about the phone line in customer services where staff key card numbers into a virtual terminal, and nothing about the card machine in the shop. Each payment channel is assessed on its own facts. Merchants with a MOTO line sitting behind a fully outsourced website are common, and the phone channel is usually the one that drags the overall picture somewhere else.
Self-attested is not self-granted
Your acquirer sets the reporting requirement. The card brands set merchant levels. You do not decide that SAQ A applies to you; you decide, on the facts, whether you meet the criteria, and the acquirer accepts or rejects that. An attestation of compliance is a signed statement about your environment. It is only as good as the facts behind it, and the facts are checked by a forensic investigator after a breach, not before.
Read the current document, not a summary
The wording has changed, and it changed in a way that matters. Open the current SAQ A from the PCI Security Standards Council document library and read the eligibility section yourself. Do not rely on a blog paraphrase, including this one. A checklist copied from a 2022-era summary understates what you are now signing.
The two checkout integrations that qualify, and the one that does not
Full redirect
The shopper clicks pay and the browser leaves your site for the provider’s domain. Card details are typed on a page you do not serve, do not style and cannot script. Eligibility here is the easiest thing in PCI to demonstrate: the address bar changes, and the network log shows the document request going to the provider.
Provider-hosted fields in an iframe
The page looks like yours. The card number input is not. It is rendered inside an iframe served from the provider’s origin, so the primary account number never enters your document object model and never touches your servers. Hosted payment fields are the cheapest way to take skimming risk off your own code, and under the current SAQ A this integration is in scope for the questionnaire, with the script condition attached.
Inline fields and direct post
If the card number input is an element in your own HTML, if your JavaScript reads it, validates it, reformats it or posts it anywhere, you are transmitting cardholder data. Tokenisation that happens after your script has already seen the PAN does not help. That is SAQ A-EP territory, whatever the integration guide’s marketing page implies about being “PCI compliant out of the box”.
The check that settles it in thirty seconds
Open your live checkout in a browser. Right-click the card number field and inspect it. If the element sits inside an iframe whose src points at your payment provider, the field is theirs. If it is a plain input in your own page source, it is yours. One observation separates an SAQ A integration from an SAQ A-EP one, and it takes less time than reading the questionnaire.
The script condition inside SAQ A eligibility that most merchants miss
The SAQ A set was reworked under PCI DSS v4.0.1. Script-attack protection, which previously appeared as questions inside the questionnaire, was restructured so that the merchant now confirms, as a condition of eligibility, that the site is not susceptible to attacks from scripts affecting the e-commerce system. The practical effect is blunt. Script control is no longer a box you tick inside SAQ A. It is part of the price of being allowed to use SAQ A at all.
The wider standard sets out what this looks like in requirements 6.4.3 and 11.6.1, both mandatory since 31 March 2025: an inventory of every script on the payment page with written business justification and authorisation, and a mechanism that detects unauthorised change to the payment page as received by the consumer browser.
Why does the parent page matter when the card fields are in someone else’s iframe? Because the page around the iframe decides what the shopper sees. A script with DOM access can draw a convincing card form on top of the real one, collect the number, then pass the details through so the payment still succeeds. It can reposition the iframe, listen for keystrokes elsewhere in the flow, or harvest the billing address and email that travel with a stolen PAN. The iframe keeps the number out of your systems. It does not keep an attacker off your page. Stop treating SAQ A as a security conclusion; it is a scope statement.
Cheap ways to hold the line
- A dated inventory of every script the checkout loads, one line of justification each, diffed weekly by a script that fetches the page and lists its resources.
- A Content Security Policy in report-only mode with a reporting endpoint, collecting violations before you enforce anything.
- Subresource Integrity hashes on third-party scripts you do not control.
SRI has a real cost, and it is worth naming. When the supplier updates their file, the hash no longer matches and the browser refuses to load it. Decide now who receives that alert, how quickly they can verify the new file and re-pin the hash, and what the checkout does in the meantime. A broken reviews widget is survivable. A broken wallet button on a Friday night is not.
How merchants quietly lose eligibility between assessments
Nobody announces this. The attestation stays in the folder, correct on the day it was signed and wrong by March.
Marketing adds a tag. Google Tag Manager fires on all pages by default, the container has four editors, and a new remarketing script now has full DOM access to the payment page with no developer review. Auditing the container is usually the single highest-value hour in this whole exercise.
A platform upgrade swaps the integration. Themes and payment plugins get updated, and the new version of the module renders an inline card form instead of hosted fields, because the inline version converts marginally better. The upgrade note says “improved checkout”. Nobody re-reads the eligibility criteria.
A supplier script lands. Live chat, reviews, session replay, an express wallet, a heatmap trial someone started and forgot. Each one inherits everything the page can see.
Or you migrate gateway. New provider, new integration method, same attestation.
The incidents that explain why investigators look hard at this
Ticketmaster UK in 2018 is the case to know. The skimming code arrived through Inbenta, a supplier chat widget loaded onto payment pages. Card handling had been outsourced. The page around it carried third-party JavaScript nobody had inventoried. The ICO fined Ticketmaster UK £1.25m in November 2020.
British Airways, the same year, came the other way: modified first-party script, inside code the airline controlled, for which the ICO issued a £20m fine in October 2020. Two routes in, both landing on the same page. Both belong in a script inventory, which is why “we wrote that file ourselves”is not an exemption.
Then there is the platform itself. In September 2020, Sansec reported roughly 2,000 Magento 1 stores skimmed over a single weekend through an unpatched, end-of-life platform. Outsourcing card capture does not outsource the security of the store that frames it. An SAQ A claim does not survive an admin panel anyone can reach. There is more pattern in the eight incidents and three routes in, if you want the comparison.
SAQ A, SAQ A-EP or SAQ D: working out which one fits
The dividing line in one sentence: SAQ A is for merchants who control neither the page that collects the card details nor, in practice, much of what happens around it, while SAQ A-EP is for merchants whose own website affects the security of the payment transaction even though the card data never lands on their servers.
Dropping to SAQ A-EP is not a formality. The question set is far longer and reaches into your own web servers: change control, secure development, vulnerability scanning by an ASV, logging, access control, penetration testing. Budget for the scanning and the remediation, not just the paperwork.
SAQ D for merchants becomes unavoidable once cardholder data genuinely touches your systems, or once you are doing something none of the shorter questionnaires describes. Claiming SAQ A to dodge that is the expensive option. After an incident, the forensic investigator reconstructs what the browser actually loaded and compares it with what you attested. A false attestation changes the commercial conversation with your acquirer, and not in your favour.
Before you choose, put three questions in writing. To the provider: which integration are we on, exactly, and which elements render from your domain? Ask for the responsibility matrix showing which PCI DSS requirements they manage and which remain yours. To the acquirer: given that integration, which SAQ do you require from us? Keep the answers.
The evidence pack that makes an SAQ A claim hold up
An attestation is a claim. The pack is what turns it into a defensible one.
- A current attestation of compliance, or listing evidence, for every third party in the payment flow. Refreshed annually, with the expiry date noted somewhere a human will see it.
- A dated script inventory for the checkout page, one line of justification per script, with the name of whoever authorised each one. If you cannot justify it, remove it. A chat widget has no business on the page where card numbers are typed.
- Change-detection output or report-only CSP violation logs, retained. This is the difference between a payment page being watched and a payment page being described.
- A re-check routine tied to deployments, plugin updates and supplier changes, not to the annual assessment date. Ten minutes after each release beats one afternoon each January.
The pack matters most on the worst day. Investigators reconstruct the page as the browser received it, and Ticketmaster is the standing reminder that a supplier script can sit for weeks on a page the merchant believed was fully outsourced. There is a fuller walkthrough of how to prove SAQ A script eligibility, including what the inventory should contain.
The short version
SAQ A eligibility turns on where the card fields are rendered and what else is allowed on the page around them. Run the DOM check on your own checkout today. Read the current SAQ A wording rather than a summary of an older one. Inventory the scripts, put CSP into report-only, pin what you can with SRI, and keep the output. If the inline card form is in your own HTML, you are not an SAQ A merchant, and saying so now costs far less than saying so afterwards.
Frequently Asked Questions
What are the SAQ A eligibility criteria for an e-commerce merchant?
All card data functions are outsourced to PCI DSS validated third-party service providers, you do not electronically store, process or transmit cardholder data on your own systems or premises, any cardholder data you retain is on paper and was not received electronically, you hold evidence that the providers are validated, and the payment page condition relating to script attacks is met. The exact wording sits in the current SAQ A document, and it has changed since v4.0, so read the live version.
Does an embedded payment iframe still qualify for SAQ A, or only a full redirect?
Both integrations can fall within SAQ A, provided the card inputs are served from the provider’s domain and your own code never touches the card number. A full redirect is simply easier to evidence, because the browser visibly leaves your site. With an iframe, the page that frames it still has to be kept clean, because that is where injected overlay forms appear.
What is the difference between SAQ A and SAQ A-EP eligibility?
SAQ A applies where the payment page content comes from the validated provider. SAQ A-EP applies where your own website affects the security of the transaction, typically because card fields render in your DOM or your JavaScript handles the data before tokenisation, even though the card data is never stored on your servers. SAQ A-EP carries a much longer question set covering your web servers, change control, vulnerability scanning and logging.
Do PCI DSS requirements 6.4.3 and 11.6.1 apply if I use SAQ A?
The v4.0.1 SAQ A set restructured how script-attack protection is handled, so those requirement numbers are not simply answered as questions within the questionnaire. The underlying protections still sit inside the eligibility condition about scripts, and both requirements have been mandatory across PCI DSS since 31 March 2025. In practice, a script inventory with justification and a change-detection mechanism on the payment page is the work either way.
Who decides whether my business can use SAQ A?
Your acquirer sets the validation and reporting requirement, informed by the card brands’ merchant levels. You determine, honestly and on the facts of your integration, whether you meet the criteria, and you sign the attestation. If the facts and the attestation disagree, the gap surfaces during a forensic investigation, which is the most expensive moment to find it.
