PCI DSS 4.0: What Changed and What Every Merchant Must Do Now
PCI DSS 4.0 became the sole active standard on March 31, 2024. The updated requirements include new authentication rules, expanded scoping guidance, and e-commerce payment page protections. Here's what you need to know.
The Payment Card Industry Data Security Standard (PCI DSS) version 4.0 officially replaced PCI DSS 3.2.1 as the only valid standard on March 31, 2024. Every business that stores, processes, or transmits payment card data is required to comply, whether you use a countertop terminal, a hosted checkout page, or a virtual terminal. Roots includes dedicated PCI compliance support with every merchant account at no extra charge.
The Biggest Changes in PCI DSS 4.0
1. Stronger Multi-Factor Authentication Requirements
PCI DSS 4.0 expands MFA requirements significantly. Under 3.2.1, MFA was required only for remote access into the cardholder data environment. Under 4.0, MFA is now required for all access to the cardholder data environment, including internal access from a trusted network. This means admin logins to payment terminals, POS systems, and any system that touches card data now require a second factor.
2. Customized Approach
PCI DSS 4.0 introduces a "customized approach" that allows organizations with mature security programs to define alternative controls that achieve the same security objective. This is primarily relevant to Level 1 merchants and service providers. Smaller merchants continue to use the defined-control SAQ approach.
3. Targeted Risk Analysis
Several requirements previously tied to an annual schedule are now driven by a documented risk analysis. Merchants must formally assess their risk environment and use that analysis to determine appropriate frequency for log review, security testing, and other controls. This flexibility requires documented methodology.
4. E-Commerce and Payment Page Protections (New)
Requirements 6.4.3 and 11.6.1 are new additions that specifically target e-commerce merchants. These require managing all payment page scripts (JavaScript, iframes, third-party elements) and implementing change- and tamper-detection mechanisms on the checkout page. This is a direct response to the rise of Magecart web skimming attacks, where attackers inject malicious scripts into payment pages to steal card data in real time. If your online checkout uses any third-party scripts, this requirement directly applies.
All Requirements Are Now Fully Active
As of March 31, 2025, all 64 previously "future-dated" PCI DSS 4.0 requirements became mandatory. As of today in 2026, there is no grace period remaining on any PCI DSS 4.0 requirement. Every merchant must be fully compliant with the complete standard, including the e-commerce script management rules (6.4.3 and 11.6.1), expanded MFA, and updated password complexity requirements. Assessors are now actively enforcing these requirements in audits and SAQs. Merchants who completed their SAQ under the old 3.2.1 framework and haven't revisited it since the 4.0 transition are very likely out of compliance.
If your last SAQ was completed before 2025, it needs to be redone
PCI DSS 4.0 SAQs include questions that simply didn't exist under 3.2.1. Completing a 3.2.1 SAQ does not satisfy 4.0 requirements. Roots' compliance specialists will walk you through an updated SAQ at no charge.
What Merchant Level Are You?
Visa and Mastercard define merchant levels by annual transaction volume, and your level determines your compliance requirements:
- Level 1: > 6 million Visa transactions/year, requires annual on-site audit by Qualified Security Assessor (QSA)
- Level 2: 1–6 million Visa transactions/year, annual SAQ + quarterly network scan
- Level 3: 20,000–1 million e-commerce Visa transactions/year, annual SAQ + quarterly scan
- Level 4: < 20,000 e-commerce or up to 1 million total transactions/year, annual SAQ + quarterly scan recommended
Choosing the Right SAQ
The Self-Assessment Questionnaire (SAQ) is the primary compliance documentation tool for most merchants. There are eight types, Roots' compliance specialists guide you to the correct one based on how you accept payments:
- SAQ A: card-not-present merchants using fully outsourced payment pages (e.g., hosted checkout via Roots e-commerce gateway), fewest controls required
- SAQ A-EP: e-commerce merchants with partially outsourced payment pages (scripts on your domain)
- SAQ B: merchants using imprinters or standalone dial-out payment terminals, no electronic storage
- SAQ B-IP: standalone IP-connected terminals that don't store card data
- SAQ C-VT: virtual terminal only, no card data storage, no payment software on merchant systems
- SAQ P2PE: merchants using point-to-point encryption solutions listed by PCI SSC, dramatically reduced scope
- SAQ D: all other merchants, the most comprehensive SAQ
How Roots Handles PCI Compliance for Merchants
Roots includes dedicated PCI compliance support with every merchant account at no extra charge. A compliance specialist guides you through the correct SAQ, conducts quarterly ASV vulnerability scans, and is available by phone or email. For merchants using Roots-certified P2PE terminal hardware, the SAQ scope is dramatically reduced, often from SAQ D to SAQ P2PE, cutting the number of required controls from hundreds to a few dozen.
P2PE reduces your compliance burden dramatically
Point-to-point encryption encrypts card data at the swipe/dip/tap, before it ever reaches your POS software. Merchants using Roots-certified P2PE terminals can use SAQ P2PE, cutting the audit scope from hundreds of controls to a few dozen.
Ready to put this into action?
Talk to a Roots Payment Solutions Expert
Free consultations, no obligation. Our experts apply exactly the concepts in this article to your specific account.