How Do You Track Every Vendor Script on a Payment Page?
A tag manager loads vendors, and vendors load their own, so what runs on your checkout is a tree, not a list. This video shows how to build a complete payment-page script inventory from real sessions, what each entry needs for PCI DSS 6.4.3, and how to keep it current with a short weekly review.
Full answer: How to Build a Payment-Page Script Inventory
Transcript
To track every vendor script on a payment page, record what actually runs in your customers' browsers, in every session, including the scripts your vendors load. A list from memory, or from your tag manager, will always miss some. That's what Script Monitoring does: one tag on your payment pages, and every vendor that ran shows up in one place, with what needs your review today. Why does a list miss things? Because a tag manager loads vendors, and vendors load their own. What runs on your checkout is a tree, not a list, and the last script in a chain is often a company you've never heard of. So keep the chain, not just the list: record which script loaded each one. When an unfamiliar script appears, the chain tells you straight away which vendor brought it in. Your tag manager can't show you this. It lists the tags you configured, not what they loaded afterwards, and not anything added outside the container. For each script, record where it loads from, what loaded it, the payload hash you approved, a business reason, an owner, and when it was first and last seen. On payment pages, that's what PCI DSS 6.4.3 asks for. The hash matters because a vendor can change a file without changing its address. If you only track URLs, a changed script looks exactly like the one you approved. To approve a vendor, open it, see each script and what it touched, and write the justification. On Pro, AI drafts one for you. The approval is tied to that version of the code. When a vendor ships new code, or a new script appears, it comes back to you for review. So tracking becomes a short weekly queue of what changed, and every week you get an evidence pack for your assessor. One question to ask any tool: does it see every session? Skimmers are written to run rarely, for some visitors, at some hours. A sample can miss them. Script Monitoring reports from every session. You can see this on your own checkout today. Script Monitoring is free for 1,000 page views a month, and Pro starts at $99 a month. Start for free at scriptmonitoring.com.