Checkout7 min read

PCI DSS 6.4.3 and 11.6.1 for Shopify Merchants: Script Inventory

What PCI DSS 6.4.3 and 11.6.1 ask for, what Shopify covers as a Level 1 provider, what stays with you after the SAQ A change, and how to keep a script inventory.

In this guide
  1. What the two requirements say
  2. What Shopify covers
  3. What stays with you
  4. The SAQ A change in January 2025
  5. How to keep a script inventory
  6. Where Custos: Store Security Scan fits
  7. FAQ

PCI DSS requirements 6.4.3 and 11.6.1 are about the scripts that run on payment pages: 6.4.3 asks you to keep an inventory of them, with a reason for each one, and to confirm each is authorized and unchanged; 11.6.1 asks for a mechanism that alerts you when those scripts or the page’s security headers change. On Shopify, the checkout and its card fields are Shopify’s, and Shopify says it is certified Level 1 PCI DSS compliant. Your storefront, the apps and pixels you add, and the questionnaire you fill in remain yours. Whether 6.4.3 and 11.6.1 apply to your store, and which evidence is enough, is decided by your acquirer or your Qualified Security Assessor (QSA), not by Shopify or by any app.

This guide explains what the two requirements say, how the January 2025 change to SAQ A affects most Shopify merchants, and how to keep a script inventory if your acquirer asks for one. It is not legal or compliance advice.

What the two requirements say

Both were introduced in PCI DSS v4.0 as future-dated requirements and have been mandatory since 31 March 2025. The current text is PCI DSS v4.0.1, in the PCI Security Standards Council’s document library.

Requirement 6.4.3 covers all payment page scripts that are loaded and executed in the consumer’s browser. For each, you need:

  • a method to confirm that the script is authorized;
  • a method to assure the integrity of the script;
  • an inventory of all scripts, with a written business or technical justification for why each is necessary.

Requirement 11.6.1 asks for a change- and tamper-detection mechanism that alerts personnel to unauthorized modification, including new, changed and removed items, of the security-impacting HTTP headers and the script contents of payment pages as received by the consumer’s browser. It runs at least weekly, or at the frequency your targeted risk analysis under requirement 12.3.1 sets.

Both exist because of web skimming: code added to a payment page that copies what shoppers type.

What Shopify covers

Shopify states that it is certified Level 1 PCI DSS compliant and that this compliance extends by default to the stores on its platform (Shopify: PCI compliance). In practice:

  • Checkout runs on Shopify. The checkout pages are hosted and served by Shopify.
  • The card fields are Shopify’s. Card numbers are typed into a secure frame hosted by Shopify, not into your storefront’s code.
  • Checkout customization runs through Shopify’s tools. Checkout UI extensions, Shopify Functions and web pixels take the place of hand-written scripts in checkout; pixels run in a sandbox (Shopify Help Center: checkout extensibility).

That covers a large part of what 6.4.3 and 11.6.1 are worried about. It doesn’t cover everything around it.

What stays with you

  • Your storefront. The home page, product pages and cart load your theme, your app embeds and your pixels. A script there can’t read inside Shopify’s card frame, but it can show a fake payment form or send shoppers to a fake checkout before they ever reach Shopify’s. Our guide on finding a malicious or injected script in a Shopify theme covers what that looks like.
  • What you add to checkout. Checkout apps, extensions and pixels are code you chose to run around the payment step.
  • Your questionnaire. Your acquirer, not Shopify, asks you for your annual self-assessment questionnaire (SAQ) or report. Shopify’s certification is evidence about Shopify; your answers are about your business.
  • Your accounts. Who can change your theme, apps and checkout settings. See the Shopify store security checklist.

The SAQ A change in January 2025

Most online merchants who outsource card handling fill in SAQ A, the shortest questionnaire. Its January 2025 revision removed requirements 6.4.3 and 11.6.1 from SAQ A and added an eligibility criterion instead: the merchant confirms that its site is not susceptible to attacks from scripts that could affect the merchant’s e-commerce system.

The PCI SSC explained the criterion in FAQ 1588 (February 2025) and on its blog:

  • It applies to merchants whose web page embeds a payment provider’s payment page or form, such as an iframe.
  • It does not apply to merchants whose site redirects shoppers to the payment provider, or who fully outsource payment.
  • A merchant who must meet it can do so in one of two ways: use techniques such as those in 6.4.3 and 11.6.1, deployed by the merchant or a third party, or obtain confirmation from its PCI DSS compliant payment provider that the provider’s embedded solution protects the payment page from script attacks when implemented as instructed.

How a Shopify store fits these cases, and whether Shopify’s confirmation is enough for your acquirer, is a question for your acquirer or QSA. Ask them which route they expect before you build anything. Some will accept the provider’s confirmation; others, especially for larger merchants or those with a heavily customized checkout, ask for script evidence.

How to keep a script inventory

If your acquirer or QSA wants evidence for 6.4.3 and 11.6.1, or you simply want to know what runs around your payment step, the work is the same.

1. Decide which pages are in scope

Agree with your assessor which pages count as payment pages for your store. Commonly discussed are the cart, the checkout up to the payment step and the customer account pages. Write the list down; it is the first line of your evidence.

2. List every script on those pages

Open each page in a browser with the developer tools on the Network tab and record every script: its address (or “inline” for code inside the page), where it comes from (your theme, an app, a pixel, Shopify) and the date you first saw it.

3. Write a justification for each one

One line per script: why your store needs it. “Payment provider’s fraud check, required by our contract” is a justification. “Installed by the last agency” is not. Scripts nobody can justify are candidates for removal.

4. Record what you authorized

Integrity means you can show the script is still the one you approved. For your own files that can be a hash of the content; Subresource Integrity (integrity attributes) works for scripts whose content never changes. For app scripts that update often, record a hash of the content you reviewed and when, and review again when it changes.

5. Detect changes and security headers

Repeat the listing at least weekly, or as often as your targeted risk analysis says, and compare: new scripts, changed content, removed scripts, and changes to headers such as Content-Security-Policy and Strict-Transport-Security. Each change needs someone to look at it and either authorize it or remove it.

6. Keep the evidence

Keep the inventory, the justifications, the change log and who approved what, with dates, for the period your assessor asks about.

A simple inventory can be a spreadsheet:

Script Page Source Justification Content hash Authorized by, date Last checked
https://cdn.example-reviews.com/widget.js Cart Reviews app embed Shows product reviews in the cart sha256-… Store owner, 3 Nov 17 Nov

Steps 2, 4 and 5 are the ones that are hard to keep up by hand, because app scripts change on the app’s servers without any change in your theme.

Where Custos: Store Security Scan fits

Custos: Store Security Scan has a PCI script report built for this evidence:

  • Its daily shopper walk opens your cart, your checkout up to the payment step and your customer account pages (once the test account is set up), and records every script those pages load and the security headers they send, with the SHA-256 of each script’s content.
  • You authorize each script with a written reason. The app records the content you authorized, your reason, your name and the time.
  • If an authorized script’s content changes, its status becomes Changed since authorized and the change log records it. New, changed and removed scripts and headers go into the scan’s alert email.
  • You can export a printable report, a scripts CSV and a change log CSV for a period of 30, 90, 180 or 365 days.

What it does not do:

  • It does not make your store compliant. It is evidence you can give your QSA or acquirer, not a certification or an assessment.
  • It does not cover Shopify’s card fields. They are Shopify’s frames, and Shopify is responsible for them.
  • It does not see between scans or pages the walk didn’t reach. The report shows how many scans ran, how many reached checkout and the longest gap between two checkout checks.
  • It never places an order or types into checkout. The walk stops at the payment step.

Install Custos: Store Security Scan from the Shopify App Store to start an inventory of the scripts on your payment-related pages.

FAQ

Is my Shopify store PCI compliant automatically?

Shopify states that its Level 1 PCI DSS compliance extends by default to stores on its platform. You still answer your acquirer’s questionnaire for your business, and your acquirer decides what evidence they need from you.

Do PCI DSS 6.4.3 and 11.6.1 apply to Shopify stores?

It depends on how your acquirer or QSA sees your setup. Since January 2025, SAQ A no longer lists the two requirements but asks you to confirm your site isn’t susceptible to script attacks, either with techniques like 6.4.3 and 11.6.1 or with your payment provider’s confirmation. Ask your acquirer which they expect.

What is a payment page script inventory?

A list of every script that runs on your payment pages, with a written reason why each one is needed, a way to show it hasn’t changed since you approved it, and a record of changes over time.

How often must I check for script changes under 11.6.1?

At least once a week, or as often as your targeted risk analysis under requirement 12.3.1 says.

Can an app certify my store for PCI DSS?

No. An app can collect evidence such as an inventory and a change log. Only your assessment, reviewed by your acquirer or a QSA, decides whether you meet PCI DSS.