onshore
Products / Collect and protect

One bad script can empty a checkout. Now you'll know.

A checkout or KYC page can be emptied by a single compromised third-party script. Page protection keeps a list of what runs on those pages and tells you when that list, or a script's contents, changes.

/checkoutReport only
cdn.yourbank.ng/app.jsApproved
tag.analytics.example/t.jsApproved
cdn.unknown-host.example/x.jsNew script
widgets.chat.example/w.jsFile changed
The problem

Skimmers arrive through trusted tag managers and analytics snippets, long after the page was reviewed.

How it works
01

Protect a page

Send a report-only header. Nothing gets blocked yet.

02

Approve what's there

Scripts appear as needing a decision. Approving one records its hash.

03

Enforce when ready

Switch to the enforcing header, which blocks anything not on the list.

What's included

Three signals

Browser reports, a watcher script and a scheduled server scan each see something different.

Script inventory

A named, written reason for every script on the page.

Change detection

A change to an approved file raises an alert.

Alerts and webhooks

Get a signed event when a new script appears.

Blocks skimmers

Once enforcing, the browser refuses scripts that are not approved.

Helps with PCI work

Supports the script inventory and change detection that card-page rules ask about.

Who uses this

Start with one leak.

Tell us which flow worries you most. We'll show you what it would take to keep it onshore.