Skip to content

What changed in the revised SAQ A (January 2025)

By Sam Rivera, Founder, SentinelPanda · September 9, 2026 · 3 min read · PCI DSS

Requirements 6.4.3, 11.6.1 and 12.3.1 came out of SAQ A on 31 January 2025. What went in was a sentence you have to be able to stand behind.

What actually happened

PCI DSS v4.0 introduced two requirements aimed squarely at e-commerce skimming: 6.4.3, which asks merchants to inventory and justify every script on the payment page and assure its integrity, and 11.6.1, which asks them to detect unauthorised modification of that page. Both were future-dated and became mandatory on 31 March 2025.

They appeared in SAQ A, which until then had been the short questionnaire for merchants who had outsourced everything. Including them meant the smallest e-commerce merchants on the lightest form were suddenly being asked to build script inventories and tamper detection. The Council took the feedback, and on 31 January 2025 published a revised SAQ A that removed 6.4.3, 11.6.1 and 12.3.1 from the document.

The condition that replaced them

The same revision added an eligibility criterion. To use SAQ A you must now confirm that your site is not susceptible to attacks from scripts that could affect your e-commerce systems.

Note where that sits. It is not a requirement you answer inside the questionnaire; it is a condition of being allowed to use the questionnaire at all. If you cannot confirm it, SAQ A is not available to you and the next form up is A-EP, which still carries 6.4.3 and 11.6.1 in full.

Note also the scope. The removed requirements applied to the payment page. The eligibility criterion is worded around the site. Assessors have pointed out that this is arguably broader, not narrower, than what it replaced.

FAQ 1588 and the two routes

  • <strong>Route one</strong> — use techniques such as, but not limited to, those described in Requirements 6.4.3 and 11.6.1 to protect the payment page from scripts that target account data. In other words, do the work the requirements describe, without having to answer their questions formally.
  • <strong>Route two</strong> — obtain confirmation from a PCI DSS compliant third-party service provider or payment processor that their solution protects the payment page from script attacks.

Why route two is harder than it sounds

Route two looks like the easy one: ask your processor for a letter. In practice, most payment providers can speak only for what happens inside their own iframe or hosted page. They cannot see what else your site loads, which is precisely where a skimmer lives — a tag manager, an analytics snippet, a chat widget, a marketing pixel added last quarter by someone in growth.

A provider that signed a blanket confirmation would be accepting liability for code they do not control and cannot inspect. Few will. So for most merchants, route one is the real route, and the practical effect of the January 2025 revision is that the controls stayed and the paperwork went.

What this means for you

If you are on SAQ A, you have fewer questions to answer and one statement to be able to defend. The honest test is whether you can list what loads on your checkout page and say why each item is there. If you cannot produce that list, you are not in a position to confirm the condition, whatever the questionnaire now omits.

If you are on SAQ A-EP, nothing changed for you. 6.4.3 and 11.6.1 apply in full and have been mandatory since 31 March 2025.

Either way the underlying work is the same and it is not large: know your scripts, know who can change them, and know when they change.

PCI DSS 6.4.3 and 11.6.1: payment page scripts SAQ A vs SAQ A-EP SAQ A walkthrough What changed in PCI DSS 4.0.1

Run your compliance program in one workspace.