PCI DSS requirements 6.4.3 and 11.6.1 are the two controls aimed at e-skimming: 6.4.3 makes you manage every script that runs on a payment page, and 11.6.1 makes you detect unauthorised changes to that page and its security-impacting HTTP headers. Both have been mandatory since 31 March 2025 for entities that validate against the full requirement set. With Black Friday on Friday, 27 November 2026 and Cyber Monday on 30 November 2026, the practical deadline for getting them right is your holiday change freeze, not the day itself.
This summary reflects PCI Security Standards Council (PCI SSC) publications as of November 2026. It is not legal or assessment advice; your acquirer and QSA decide how the rules apply to you.
What requirement 6.4.3 asks for
Requirement 6.4.3 in PCI DSS v4.0.1 covers all payment page scripts loaded and executed in the customer's browser. For each script you need:
- Authorisation: a method to confirm the script is approved to run.
- Integrity: a method to confirm the script has not been altered.
- Inventory: a maintained list of every script with a written business or technical justification for why it is there.
Scope includes first-party scripts and those from third and fourth parties, such as analytics, chat widgets and tag managers. If your checkout embeds a payment provider's form in an iframe, the scripts inside that iframe are the provider's responsibility, but the scripts on your page that hosts the iframe remain yours.
What requirement 11.6.1 asks for
Requirement 11.6.1 is the detective counterpart. You need a change- and tamper-detection mechanism that alerts staff to unauthorised modifications to the security-impacting HTTP headers and the script contents of payment pages as the customer's browser receives them. It must run at least weekly, or at a frequency you justify in a targeted risk analysis under requirement 12.3.1.
Weekly is a floor: a skimmer injected just before Black Friday could run all weekend before a weekly check notices it.
The SAQ A change
On 30 January 2025 the Council revised SAQ A, the self-assessment questionnaire for merchants that fully outsource card handling. Requirements 6.4.3, 11.6.1 and 12.3.1 were removed from SAQ A. In their place, a new eligibility criterion requires the merchant to confirm its site is not susceptible to attacks from scripts that could affect its e-commerce systems. The revised SAQ A took effect on 31 March 2025.
PCI SSC FAQ 1588 (February 2025) explains how to meet that criterion:
- It applies to merchants whose page embeds a provider's payment form, for example an iframe. It does not apply when the customer is redirected to the provider's hosted page.
- The merchant can either use techniques such as those in 6.4.3 and 11.6.1, run in-house or by a third party, or obtain confirmation from a PCI DSS-compliant provider that its solution, implemented as instructed, protects the page from script attacks.
- A vendor that only supplies scripts unrelated to payment, which cannot affect card data, is not treated as a third-party service provider for SAQ A.
In August 2026 the Council revised FAQ 1331. Merchants assessed through a Report on Compliance should not treat SAQ eligibility criteria as a guide to which requirements apply, unless the entity accepting their compliance has explicitly agreed. Ask your acquirer before marking 6.4.3 or 11.6.1 not applicable.
Common ways to implement the controls
The Council's March 2025 supplement, Payment Page Security and Preventing E-Skimming, covers approaches and adds no new requirements. Typical building blocks:
- Content Security Policy: a CSP restricting script sources supports authorisation, and its violation reports can feed change detection.
- Subresource Integrity: SRI hashes on static script tags support integrity. They do not suit scripts that change without notice, so those need another control.
- Tag manager governance: limit who can publish containers, require review, and keep tag managers off checkout pages where possible.
- Client-side monitoring: tools that load the page like a browser and alert on new or changed scripts and headers.
- Scope reduction: moving to a redirect or a hosted payment page removes most script exposure from your own pages.
A pre-freeze checklist
- Rebuild the script inventory from what browsers actually load on checkout, not from documentation.
- Remove scripts nobody can justify.
- Enforce CSP on payment pages, not just report-only, and make sure someone reads the reports.
- Increase monitoring frequency for the sales period and name weekend alert responders.
- Lock tag manager publishing rights for the freeze window.
- If you rely on SAQ A, keep written confirmation from your payment provider and check that your integration still matches its instructions.
Script control is the same supply-chain discipline as pinning GitHub Actions to a commit SHA. For vendor patch days in your freeze window, see the 2026 and 2027 patch calendar. More in our Security section.
Frequently asked questions
When did 6.4.3 and 11.6.1 become mandatory?
On 31 March 2025, after being future-dated in PCI DSS v4.0.
Do SAQ A merchants still need 6.4.3 and 11.6.1?
Not as line items. They must meet the eligibility criterion instead, through their own controls or their provider's confirmation, per FAQ 1588.
How often must 11.6.1 checks run?
At least weekly, or at a frequency set by a targeted risk analysis under requirement 12.3.1.
Does using a payment iframe take my checkout page out of scope?
No. Scripts on the page that embeds the iframe are still yours.