Card rules, in plain English

PCI DSS 6.4.3 and 11.6.1: Payment Page Script Records Your Processor Can Actually Read

It arrives as one line in an annual questionnaire: describe how you manage scripts on your payment page under requirement 6.4.3. The owner forwards it to the web person. The web person forwards it to the agency. The agency left in the spring, and the checkout still runs everything it installed.

November 19, 2026 · 11 min read

checkout.acmeoutfitters.com · payment page inventory
Scripts on the payment step, each with a reason
Seven scripts load; two have no written reason
6.4.3 draft
Store card form codeWeb team · keep, pinned
Tag manager containerMarketing · lock down
Analytics tagMarketing · keep
Coupon pop-upSales · move off checkout
Fraud screening scriptPayments · keep
cdn.acme-chatwidget.exampleNo owner · cut
Heat map recorderNo owner · cut
Approved for the payment page4 of 7
Illustrative: sample payment page script inventory for a fictional outfitter's checkout

The short answer

PCI DSS requirement 6.4.3 asks merchants to keep an inventory of every payment page script with a written reason for each, confirm each is authorized, and assure its integrity. Requirement 11.6.1 asks for an alert when the page's scripts or security headers change as the shopper's browser receives them. Both have applied since 2025. Your checkout setup decides scope; confirm it with your acquirer or assessor.

On this page
  1. The processor's questionnaire that mentions 6.4.3
  2. 6.4.3 and 11.6.1 in words an owner can repeat to the bank
  3. Where the card number is typed decides how much applies
  4. Hosted payment fields, the scope cut to ask about first
  5. The evidence pack, file by file
  6. Where our work stops and your assessor's begins
  7. What it costs, and which stores should keep their money

The processor's questionnaire that mentions 6.4.3

Picture a fictional outfitter's checkout. It runs the store's own card form, a tag manager, an analytics tag, a heat map recorder, a coupon pop-up and a chat widget from 2021 that nobody has opened since the agency set it up. Each of those is a script: a small program the browser downloads and runs as part of the page. Most were written by somebody else, and every one of them runs on the same page as that card form, close enough to read what is typed into it.

The card rules in question come from PCI DSS, the Payment Card Industry Data Security Standard, published by the PCI Security Standards Council and passed down to merchants by the processor or bank that handles their card payments. Version 4.0.1 includes two requirements aimed squarely at the code running on the page where a card number is entered. They are not new paperwork for its own sake. They describe exactly the kind of attack that hit large brands this month.

On November 16, 2026, an attacker used a flaw at Optimizely to slip card-skimming code into testing scripts that companies loaded on their own pages. Report URI, a company that sells script monitoring, reported on November 16 and updated on November 17, 2026 that the code captured card numbers, expiration dates and security codes from sites' own forms, while cards typed into a payment company's hosted fields were out of its reach. Our Optimizely breakdown covers the rest of that day.

6.4.3 and 11.6.1 in words an owner can repeat to the bank

Both requirements were "future-dated" in PCI DSS v4.0, which retired on December 31, 2024, and they have been in effect since 2025, according to conference material hosted by the PCI Security Standards Council, read in November 2026. The table restates them. The middle column follows that material; the last two columns are our plain-English reading and our own deliverables.

PCI DSS v4.0.1 requirements 6.4.3 and 11.6.1, per the PCI Security Standards Council's conference material, read November 2026
What the requirement asksWhat it means on an ordinary TuesdayWhat we hand you
6.4.3, script managementMaintain an inventory of payment page scripts with written justification, confirm each script is authorized, and assure each script's integrityA list of every script on the page, why it is there, who said yes, and a way to show it has not been alteredThe inventory, the approval records and an integrity method chosen for each script
11.6.1, change and tamper detectionAlert to unauthorized modification of security-impacting HTTP headers and the script contents of payment pages, as received by the consumer browserSomething must notice when the page a shopper actually gets has changed, and tell a personMonitoring from real browsers and a log of every alert and what was decided about it

Security-impacting HTTP headers sound worse than they are. A header is a short instruction the server sends along with the page, invisible to the shopper. The one that matters most here is the Content Security Policy, which tells the browser which scripts may run and where the page may send data. Our content security policy service explains how one is written. If somebody quietly loosens that header, 11.6.1 wants you to find out.

The phrase "as received by the consumer browser" carries more weight than it seems to. It means the check has to look at what a shopper's browser actually gets, not only at the files stored on your server. A vendor's script changes on the vendor's server, and a tag manager adds code after the page opens. Our script monitoring page explains why server-side file checks miss both.

Where the card number is typed decides how much applies

Scope is the word assessors use for the parts of your business a requirement covers. For these two, it turns almost entirely on one question: whose page holds the card field? The council's conference material lays out a range, summarized in the cards below. Treat it as orientation, not a ruling on your store.

Your own payment form

The card fields are part of your page's code. The material says a merchant-hosted payment form carries the full requirements. Every script on that page sits next to the card number.

Hosted fields inside your checkout

The processor draws the card boxes in an iframe, a small window into its own site, set into your page. The material places embedded iframes in between: less than your own form, not nothing.

The whole payment on the processor's site

The shopper leaves your site to pay and returns afterward. For a fully outsourced flow like this, the material says these two requirements carry none for the merchant.

A single-page app checkout

Some stores run as one long application in which pages change without reloading. The material notes that in a single-page app the whole application can be in scope.

Flat sticker of a stern cactus in a guard cap, arms crossed, guarding a terracotta cash register on cream paper, low hills behind
Requirement 6.4.3 is a guard at the register who asks every script for a reason.

One more wrinkle. The revised eligibility for SAQ A, the shortest self-assessment questionnaire, asks merchants to confirm their site is not susceptible to script attacks, rather than listing 6.4.3 and 11.6.1 outright, per the same material. So even the merchant with the lightest paperwork is asked a question about scripts. It is far easier to answer honestly with an inventory in hand.

Hosted payment fields, the scope cut to ask about first

If your checkout uses its own card form, the biggest improvement is often not a monitoring tool. It is moving the card boxes to the processor. Hosted fields look like part of your page, but they belong to the processor's site, so the scripts on your page do not touch the number typed into them. That is the line Report URI drew in its November 2026 analysis of the Optimizely case: the skimmer read sites' own forms and missed the hosted ones.

Hosted fields do not end the job. The page around them still loads your scripts, and a script on that page can still change what the shopper sees around the card boxes, which is why the revised SAQ A eligibility asks the script question at all. How hard the switch is depends on the platform and how far the checkout was customized; the estimate says which. Our ecommerce development work builds checkouts this way from the start. If yours is failing outright today, begin with the checkout emergency page instead.

Questions worth sending your processor this week

  • Which of your payment options keep card entry on your site entirely, and which place an iframe inside ours?
  • Which self-assessment questionnaire do you expect from us with each option, and does that change if we switch?
  • Do you want evidence of a script inventory or change detection for our current setup, and in what form?
  • Who at your company, or at our assessor, answers scope questions in writing?

The evidence pack, file by file

This is the part you are buying. A processor or assessor wants records, not reassurance, and the records have to survive the person who made them leaving the company. We start with a script audit of every page in the payment path, loaded in real browsers on desktop and iPhone, and build five things from it.

  1. 1

    The payment page inventory

    Every script that loads on each page in the payment path, including the ones a tag manager adds after the page opens, with its source address, what it does and the written business reason. Scripts nobody can justify go on a removal list, not into the inventory.

  2. 2

    Authorization records

    For each script, who approved it, when, and the person on your side who answers for it. A tag an agency added years ago with no owner either gets one or gets removed. If your tag manager has more publishers than anyone can name, that gets fixed here too.

  3. 3

    An integrity method for each script

    Files that should never change get Subresource Integrity, a fingerprint the browser checks before running the file. MDN's SRI documentation, last modified April 14, 2026, says a mismatched file is refused and that any change breaks the match, legitimate updates included. Scripts that change by design get a strict policy and monitoring instead.

  4. 4

    A header baseline

    A dated record of the security headers each payment page sends today, starting with the Content Security Policy, so any later change has something to be compared against.

  5. 5

    The change alert log

    Ongoing monitoring of the payment pages as the browser receives them, with every alert, who reviewed it and what was decided. This is the piece 11.6.1 expects to keep running after we hand the rest over.

An assessor cannot audit a feeling of safety. It can audit a list with a name next to every line.

Where our work stops and your assessor's begins

What we do

  • Build the script inventory from what real browsers load
  • Record approvals and a named owner for every script
  • Set an integrity control for each script and write the browser policy
  • Run change monitoring on the payment pages and keep its log
  • Hand everything over in a form your assessor can read

What we do not do

  • Certify compliance or issue any attestation
  • Decide which self-assessment questionnaire you file
  • Rule on your scope for the card brands
  • Give legal advice after a suspected card exposure
  • Promise that you will pass an assessment

If you suspect cards have already been skimmed, the order changes: preserve the evidence, contain the script, and call your processor, attorney and insurer before anyone starts cleaning. Our script compromise response page covers those first hours. If nobody inside the business will own this list after we finish, a fractional CTO can hold it.

What it costs, and which stores should keep their money

We respond the same business day; our hours are on the contact page. Payment page script work is from $575, depending on complexity, with a written estimate before work starts. The number moves with how many pages sit in the payment path, how many scripts and tag containers they load, whether the checkout is your own form or hosted fields, and whether a browser policy exists. Ongoing monitoring is added to a hosting and maintenance plan, where plans start from $55 a month, and is quoted with the estimate.

Keep your money if the whole payment happens on your processor's site and your acquirer agrees nothing on your pages is in scope. Keep it if your assessor already supplied a tool and you only need someone to read the alerts; ask the assessor first. If you just want to know what loads on your checkout today, start with the free website health check or site audit, and see the website security overview for the rest of this section.

DataCram is a San Antonio web studio, building for the web since 1999 and working with stores across the US by phone, video and a shared project page. See our work or call (210) 346-0848.

Questions owners ask about website security

Possibly, in part. The PCI Security Standards Council's conference material places embedded iframes between a merchant-hosted form and a fully outsourced flow, and the revised SAQ A eligibility asks merchants to confirm their site is not susceptible to script attacks. Your acquirer or QSA decides your scope. We can build the inventory and controls either way.

No. We are not a Qualified Security Assessor and we do not certify compliance. We build the controls 11.6.1 describes, change detection on the payment page as the shopper's browser receives it, and keep the alert log your assessor can review. Whether that satisfies the requirement for your business is the assessor's call.

Usually not by itself. A policy controls which scripts may run and where a page may send data, which supports authorization. Requirement 6.4.3 also asks for a written inventory with a reason for each script and a way to assure each script's integrity. The policy is one control in the pack, alongside the inventory, the approval records and monitoring.

Any JavaScript that runs on a page in the payment path: your own code, the processor's code, analytics, tag managers, chat widgets, testing tools and anything a tag manager adds after the page loads. The safest inventory starts from what a real browser actually loads, not from a list somebody remembers from the launch.

They were future-dated requirements in PCI DSS v4.0 and have been in effect since 2025, after v4.0 retired on December 31, 2024, according to conference material hosted by the PCI Security Standards Council. If your processor raised them only recently, the records can still be built now; ask what timeline the processor expects.

From $575, depending on complexity, with a written estimate before work starts. The number of pages in the payment path, the scripts and tag containers they load, and whether you use hosted fields move the price. Ongoing monitoring is added to a hosting and maintenance plan and quoted with the estimate.

Keep reading

Free · No obligation

Find out what runs on your payment page

Tell us your platform, how card entry works today and what your processor asked for. We reply the same business day with what we would check first and a written estimate.

Which of these sounds like you? (pick any)

Rather talk now? Call (210) 346-0848.

CallGet a quote