PCI Payment Page Requirements — check payment page scripts

Lints checkout and payment pages against PCI DSS v4.0.1 Requirements 6.4.3 and 11.6.1 — script authorization, SRI integrity, written justification and tamper detection. Mandatory since 2025-03-31. Runs entirely in your browser — nothing is uploaded.

Same engine as the VS Code extension, byte for byte.

PCI Payment Page Requirements — check payment page scripts
Example result

Get the full version $29

Sweep the whole workspace and write the dated PCI DSS 6.4.3 script inventory to a file in your repo — every file, every script, every justification status, dated, yours to commit and diff.

One payment, one licence key for this tool. The key is shown right after payment.

QSA assessment time bills at roughly $200 an hour; this is $29 once.

Buy the full version — $29

Need more than this one? ReadyStack Pass opens all 609 files and 521 full versions — $29/month or $199/year. See the Pass →

Questions people ask

What does this actually do?

It reads a checkout or payment page and reports it against PCI DSS v4.0.1 Requirements 6.4.3 and 11.6.1. Fourteen checks: missing subresource-integrity hashes, integrity without crossorigin, unversioned vendor SDKs, tag managers on the payment page, unsafe-inline and wildcard hosts in script-src, unnonced inline blocks, missing written justifications, and no declared tamper detection.

Who is it for?

Developers and agencies who build custom checkout pages on Stripe, Braintree, Adyen, Square or Checkout.com rather than redirecting to a hosted page, and who have to sign an SAQ A-EP or SAQ D. If your payment page is a page you wrote, 6.4.3 and 11.6.1 are yours to answer.

Why is a free tool not enough?

An SRI hash generator gives you one hash. A CSP evaluator grades one header. Neither knows that Requirement 6.4.3.3 also wants a written business or technical justification stored per script, that a tag manager on the payment page voids the allowlist, or that an integrity attribute without crossorigin is skipped by the browser.

What is free and what costs money?

Checking the payment page open in your editor is free and complete: all fourteen checks, every finding, every requirement number, no key, no watermark, no counter. Paid is scope and ownership — sweeping the whole workspace and writing the dated script inventory to a file you keep in the repo.

What would this cost with a person?

QSA assessment time bills at roughly $200 an hour, and building a script inventory with justifications is a per-page exercise repeated at every release. This extension is $29 once. It does not replace an assessment; it stops you arriving at one with findings you could have read yourself.

Ask about this tool

One question, answered by the person who built it. Your email only if you want the answer sent.

Embed this tool on your site (free)

Paste this code into your page. It runs in your visitor’s browser and stays up to date. Nothing your visitors type is stored.

 All embeddable tools

For businesses: your name and logo instead of ours, and each visitor’s result + e-mail in your inbox (only when they tick consent) — Pro from $19/month. See Pro →

Email me this result
A copy of what you see above, in your inbox — the tool stays free, nothing here is locked.
ENDEJAESPT

Find a tool