PCI DSS Compliance Gaps Exposed by Client-Side Payment Skimming and Third-Party Script Risk
Sector Threat Intelligence · 2 sources · Updated 5mo ago · First seen Mar 1, 2026

Organizations pursuing PCI DSS compliance are being warned that compliance controls alone do not prevent client-side payment data theft, particularly when third-party scripts and outsourced payment flows are involved. Commentary highlights that changes to PCI DSS v4-related guidance (including updated SAQ A language for merchants using PCI-compliant payment service providers) can reduce mandated anti-skimming requirements, increasing the risk that merchants “trust but don’t verify” protections around browser-executed code and third-party dependencies.
Separately, tokenization guidance emphasizes that tokenization is distinct from encryption and is intended to reduce exposure by replacing sensitive values (e.g., PANs) with non-sensitive tokens, potentially reducing PCI scope when implemented correctly. The same guidance cautions that implementation pitfalls are common and that using encryption as a stand-in for tokenization can leave organizations at risk—reinforcing that data protection architecture (e.g., tokenization) and client-side/script visibility controls address different parts of the payment-data threat surface, and both may be necessary to mitigate modern skimming techniques such as MirrorMask targeting select Stripe merchants via script/API redirection and reverse-proxy interception.


