AssetAssure
PCI DSS v4.0.1 · 6.4.3 and 11.6.1 · mandatory since 31 March 2025

Every script on your payment pages: inventoried, justified, and watched for tampering.

✓ Automates 80% of your recurring compliance work

A live inventory of every script on your payment pages, a written justification for each, and an alert the moment one changes or starts behaving like a skimmer. The evidence for requirements 6.4.3 and 11.6.1 comes out of the product, not a spreadsheet.

Make an enquiry Enquiries are answered directly by our team.
checkout.bundle.js 9f2c4a1d → {{ pulseDot }}7ac5d204
+5 −2 seen on /checkout 4 minutes ago changed, awaiting review
{{ line.n }} {{ line.sign }} {{ line.text }}
critical skimmer-pattern payment-field-access external-host
AI assessment — this version sends the card number, expiry and CVC to a host the approved version never contacted. Checkout still works, so nobody would notice.
How it works

Four steps from a shopper's browser to an approved baseline.

Discovery starts in the shopper's browser, not in a crawler, so no script a page really loads is missed.

{{ step.num }} {{ step.label }}

{{ step.title }}

{{ step.body }}
Automation

Your team does three things. AssetAssure does the other thirteen.

You
{{ item.n }} {{ item.text }}
AssetAssure, on its own
✓ {{ item.text }}
Already have CSP and SRI?

Good. They are half the answer.

{{ o.title }}

{{ o.body }}
Evidence

Three requirements. Three sets of evidence.

Each requirement maps to screens your assessor can open, filter and export.

Clause What the standard asks for What AssetAssure gives you
{{ row.clause }}

{{ row.ask }}

{{ row.proof }}
What you get

Built for the payment page, not the whole web estate.

{{ f.tag }}

{{ f.title }}

{{ f.body }}
Isolation

An isolated environment per customer.

Provisioned and operated by us. Script URLs, retrieved versions, approvals and reports live in your environment and nowhere else.

{{ d.title }}

{{ d.body }}

See it on your own payment pages.

Tell us which pages are in scope and when your next assessment is due. We reply directly with a walkthrough and a recommended approach.

Requirements covered
6.4.3 — payment page scripts authorized, integrity assured, inventoried with justification
11.6.1 — change and tamper detection on script contents and security headers
12.5.1 — inventory of in-scope components with a description of function

{{ heading }}

{{ subheading }}

{{ error }}

Your details are used only to respond to this enquiry. See our Privacy Policy.

{{ confirmation }}

No signing endpoint is configured yet, so this submission was not delivered. Set the signing endpoint to send enquiries.