PCI DSS 6.4.3 and 11.6.1: the payment page script requirements
By Sam Rivera, Founder, SentinelPanda · September 16, 2026 · 4 min read · PCI DSS
Digital skimming does not break into your database. It adds eleven lines to a page you already serve, and nothing on your server ever looks wrong.
The attack they exist to stop
A digital skimmer is JavaScript that runs on your checkout page and sends a copy of what the customer types to an address that is not yours. It does not require access to your database, your card vault or your processor. It requires the ability to change one script that your page loads — and most checkout pages load a dozen, from several different vendors, over which the merchant has no version control.
The compromise usually happens upstream, at a tag manager, a content delivery network, an analytics vendor or a plugin. From your server's point of view nothing has happened at all. Logs are clean, the processor still receives valid transactions, and the business learns about it from its acquirer weeks later.
What 6.4.3 asks for
- A method to confirm that each script on the payment page is authorised.
- A method to assure the integrity of each script — that it is still the script you authorised and has not been swapped or altered.
- An inventory of all scripts on the page, with written business justification for why each one needs to be there.
What 11.6.1 asks for
A change-and-tamper-detection mechanism that alerts personnel to unauthorised modification of the HTTP headers and the content of the payment page as received by the consumer browser. The requirement also expects the mechanism to evaluate the page at least weekly, or at a frequency your targeted risk analysis justifies.
The detail worth sitting with is "as received by the consumer browser". Checking the file on your server does not satisfy it. The page a customer receives has passed through a CDN, a tag manager, a reverse proxy and any number of injected scripts, and the requirement is aimed at what emerges at the end of that chain — because that is where the skimmer lives.
The honest implementation picture
The inventory half of 6.4.3 is a spreadsheet exercise and it is more valuable than it looks. Most teams who sit down to list what their checkout loads find at least one script nobody can account for, usually added for a campaign that ended two years ago. Removing those is the cheapest security win available, and it shrinks everything that follows.
Integrity assurance has well-understood mechanisms — subresource integrity attributes on static third-party scripts, a content security policy that constrains what can load and where data may be sent, and server-side review of changes. None is a complete answer by itself, and the requirement deliberately does not prescribe one.
The 11.6.1 half is the part most teams buy rather than build. The products in this space monitor the rendered page from outside and alert on change. Building an equivalent is possible, and some teams do it with a headless browser on a schedule comparing a hash of the relevant DOM, but the maintenance cost is real and it is a poor use of a small engineering team.
Who this applies to
Merchants completing SAQ A-EP or SAQ D, and service providers completing SAQ D-SP, answer both requirements in full. They have been mandatory since 31 March 2025.
Merchants on the revised SAQ A no longer answer them, following the January 2025 revision — but that revision added an eligibility condition requiring them to confirm their site is not susceptible to script attacks, and the Council's own FAQ points at these two requirements as the way to do it. The questions left SAQ A. The work mostly did not.
Where to start
Start with the inventory, because it is free and it tells you how big the problem is. Open the checkout page with the browser network tab recording, list every script that loads, and for each one write down who owns it, why it is there and who can change it.
If that list has entries nobody can explain, you have found the real finding, and it predates the requirement by several years.