NewCheckout script watch: every script on your checkout, listed and approved, for PCI DSS 6.4.3 and 11.6.1.See how it worksFree store scan

Checkout script watch

Know every script on your checkout, and the moment one changes

Card skimmers hide in scripts on the checkout page. StoreOnCall opens your checkout like a shopper a few times a day, lists every script it finds, and alerts you when something new appears. Nothing is added to your store.

The checkout script watch, in 45 seconds. The store and scripts are examples.
Every script, listed

Each script on checkout with where it comes from, when it first appeared and a fingerprint of its code, including inline scripts.

Approved, with a reason

Your team approves each script with a short reason why checkout needs it. Your own site's scripts can be approved in one go.

Alerts when it changes

A script from a new outside domain is urgent, for the owner and the developer. Changed code, new inline scripts and security header changes go to the developer.

Approval that expires on change

When an approved outside script's code changes, it needs approving again. Your own scripts stay approved through releases.

Evidence for your assessor

Download the inventory, approvals and full change history as CSV, or print a summary as PDF.

After every release

Checked every 6 hours, and about 5 minutes after each deployment StoreOnCall sees.

PCI DSS 4.0.1

What the standard asks for

Requirement 6.4.3 asks merchants to keep an inventory of every script on payment pages, each one authorized, with a written reason. Requirement 11.6.1 asks them to detect unauthorized changes to those scripts and to the page's security headers, as the shopper's browser receives them, at least every seven days. Both have been mandatory since 31 March 2025.

The script watch gives you the inventory, the approvals and the change alerts, with evidence to show your assessor. Whether your setup meets PCI DSS is your assessor's decision.

Read-only

Nothing is installed on your checkout. We look from outside, like a shopper.

No card or customer data

The test shopper never pays and never types customer details.

Magento and BigCommerce

Built for how their checkouts load: release versions and per-visit tokens are not reported as changes.

Honest about limits

A check every few hours can miss a script shown only to some shoppers or at some hours. Tools that run inside every shopper's browser catch more.

How a check works

  1. Open the storeA real browser visits the home page and a product, the way a shopper does.
  2. Fill a cartIt adds the product to the cart, through the store's own add-to-cart button or cart API.
  3. Open checkoutIt opens checkout and waits for it to finish loading, then stops. It never pays.
  4. CompareEvery script and security header is compared with the last check and your approved list.

Questions

Checkout script questions

Does it make my store PCI compliant?

No tool can promise that; your assessor decides. The script watch gives you the script inventory with approvals and the change alerts that requirements 6.4.3 and 11.6.1 ask for, with evidence you can hand over.

Do I need to add a script or install anything?

No. It checks from outside, the way a shopper's browser sees the page. On Magento the plugin also tells us about deployments, so we check again soon after each release.

How often does it check?

Every 6 hours, about 5 minutes after each deployment we see, and whenever you press Check now.

Will every release flood us with alerts?

No. Magento's release folders, build hashes, per-visit tokens and security nonces are ignored, so a normal release is quiet. Your own scripts stay approved through releases; outside scripts must be approved again if their code changes.

Which plans include it?

Every plan and the free trial, during early access.

See what runs on your checkout

Start the free trial: the first check runs within minutes of adding your store.

Scan my store freeBook a demo