Your finance director forwards an email from the auditor with one line highlighted: a question about payment page scripts. She asks whether your website is compliant. You have always understood that PCI was handled by the payment processor, which is why you chose one, and nobody has ever raised it before.
It is a fair question with a genuinely specific answer. The answer depends on one technical detail about how your donation form is built, and most associations do not know which side of that line they are on. Sorting it out takes about ten minutes and it is worth doing before an auditor asks rather than after.
One thing said plainly up front. A note before any of this. We build and maintain websites. We are not a QSA, we do not perform PCI assessments, and nothing here is a compliance determination for your organization. Your acquiring bank and your assessor decide what applies to you. What follows is the plain-language version of what the standard says, so you can have a better conversation with them.
The Two Requirements Everyone Is Talking About
PCI DSS v4 introduced two requirements aimed squarely at the page a cardholder sees. Requirement 6.4.3 covers payment page scripts: a method to confirm each script is authorized, a method to assure the integrity of each script, and an inventory of all scripts with written justification for why each one is necessary. Requirement 11.6.1 requires a change and tamper detection mechanism that alerts personnel to unauthorised modification of the HTTP headers and the content of payment pages as received by the consumer browser.
The reason this surfaced this year. Both moved from best practice to mandatory on April 1, 2025. That date is why this is turning up in audit conversations now.
The Part Most Coverage Gets Wrong
Search this topic and you will mostly find content from companies that sell script monitoring, and it tends to imply every merchant with a payment page must build a full script inventory and deploy tamper detection. For a large share of associations, that is not what the standard asks.
Here is what actually changed. In January 2025 the PCI Security Standards Council published a revised SAQ A that removed requirements 6.4.3 and 11.6.1, along with 12.3.1, taking effect March 31, 2025. In their place the Council added an eligibility criterion: the merchant confirms that their site is not susceptible to attacks from scripts that could affect the merchant's e-commerce systems.
And the scope is narrower still. Per the Council's FAQ 1588, that criterion applies to merchants using an embedded payment page, meaning an iframe. It does not apply to merchants who use a redirect or who fully outsource payment functions. And a merchant can meet it either by implementing script protections themselves or by obtaining confirmation from their payment provider that the embedded solution includes those protections when implemented correctly.
Read the alternative in that sentence. That last clause is the one worth reading twice. For many associations, satisfying this is an email to your processor, not a project.
So Which One Are You?
Everything turns on how the donation or dues form actually reaches the visitor. Open your donation page and look at what happens when someone clicks to give.
- A redirect. The visitor leaves your site entirely and lands on the processor's domain to enter card details, then comes back. The SAQ A eligibility criterion regarding scripts does not apply to redirect merchants. This is the simplest position to be in and it is common among smaller nonprofits.
- An embedded form, in an iframe. The card fields appear on your page but live inside an iframe served by the processor, so the card data never touches your server. This is where the eligibility criterion applies, and where the conversation with your processor matters.
- Fields rendered by your own site. The card fields are part of your page, or your page collects and posts the data, or your AMS handles it inside your site. This is a different SAQ entirely, and 6.4.3 and 11.6.1 apply in full. If this describes your site, that is the finding, and it is a bigger conversation than a blog post.
One honest observation. If nobody at your organization can say with confidence which of those three you have, that is the actual first task, and your web team can answer it in minutes.
What Loads on a Donation Page Anyway
Whichever category you fall into, it is worth knowing what runs on that page, because associations accumulate more than they realize. A typical donation page loads some combination of an analytics tag, a tag manager container that can inject anything without a code change, a chat widget, one or more advertising pixels added for a campaign that ended two years ago, a font service, an accessibility overlay, and an AMS embed.
Count them on your own site. Each of those is somebody else's code executing on the page where your donors type their card numbers. That is not an argument to remove them all. It is an argument for knowing the list, which is useful whether or not any requirement obliges you to write it down.
There is a second reason this is worth doing. We have written about the same collection of scripts as a performance problem. This is the other reason to care about them, and the inventory serves both purposes.
The Ten-Minute Version
None of this requires buying anything to get started.
- Establish which model your donation form uses. Redirect, embedded iframe, or fields on your own page. Your web team or your processor can confirm it immediately.
- Ask your payment processor a direct question. Ask specifically whether their embedded payment solution includes protections against script attacks when implemented correctly, and ask for that in writing. If you are on an iframe, that written confirmation is what the eligibility criterion contemplates.
- Get a list of what loads on the page. Open the page, view source, and list every third-party domain it calls. A developer can produce this in a few minutes. Note what each one is for and who asked for it.
- Remove what nobody can account for. Anything nobody can justify should come off, starting with pixels from finished campaigns. This reduces your exposure regardless of which SAQ you complete.
- Take the answers to your acquirer. They determine which SAQ is appropriate for your environment. Nothing you read online, including this post, substitutes for that.
When This Is Not Your Problem
If your association takes donations through a hosted page on your processor's own domain, and your website simply links to it, this is largely settled for you. The card data never passes through anything you control, and the script requirements are not aimed at your site.
Equally, if your organization takes a handful of checks a year and a small number of online gifts through a platform like a hosted giving page, the right answer is to confirm your model with your processor and move on. Compliance work that outstrips the risk is its own kind of waste, and we would rather say so than sell you a project.
Where This Leaves You
The reason this falls through the cracks is structural. Finance owns the relationship with the processor. The website belongs to communications or to an outside agency. The requirement lands on the page, which sits between the two, and pages between two owners belong to nobody.
Somebody has to know what loads on your donation page and why. That is a modest job, it does not require a compliance specialist, and it is far cheaper to do on an ordinary Tuesday than in the week an auditor asks.
Stop Fighting With Free Platforms
Our partnership plans give associations and nonprofits a dedicated web team without the overhead of hiring one. From ongoing maintenance to full-scale builds, every plan includes strategy, development, and support tailored to organizations like yours.