Home / Compliance guides / PCI DSS 4.0
COMPLIANCE GUIDE · PCI DSS 4.0
PCI DSS 4.0 guide: what changed and how to stay compliant
A practical guide for merchants, payment platforms and service providers that store, process or transmit card data, including the requirements that became mandatory on 31 March 2025.
Updated November 2026
PCI Security Standards Council
10-minute read
THE SHORT ANSWER
PCI DSS is the security standard for any organization that stores, processes or transmits payment card data. Version 4.0.1 is the only active version, and the future-dated requirements became mandatory on 31 March 2025, including MFA for cardholder data access, payment page script controls and targeted risk analyses. Your level decides between an assessor report and a self-assessment.
WHO NEEDS IT
If you take card payments, PCI DSS applies
Card brands and acquiring banks require PCI DSS. Your scope depends on how card data flows through your systems.
01
Merchants and eCommerce
Online and in-store merchants must protect card data and payment pages.
02
Payment platforms and fintechs
Processors, gateways and payment facilitators are service providers with stricter duties.
03
SaaS handling payments
Software that touches card data, or can affect its security, is in scope.
KEY REQUIREMENTS
The 31 March 2025 changes that matter most
§
Payment page scripts (6.4.3 & 11.6.1)
Inventory, authorise and monitor scripts and changes on payment pages to stop skimming.
§
MFA into the cardholder data environment (8.4.2)
Multi-factor authentication for all access into the cardholder data environment.
§
Targeted risk analysis (12.3.1)
Documented risk analyses that justify how often flexible controls run.
Summary only, not legal advice. Your QSA or acquiring bank confirms your validation level.
HOW TO GET COMPLIANT
From scoping to validation in four steps
1 · Scope & data flows
Map card data flows and shrink scope with tokenisation.
2 · Gap assessment
Compare your controls with PCI DSS 4.0.1 requirements.
3 · Remediate
Fix gaps, from MFA to script monitoring and logging.
4 · Validate
A self-assessment (SAQ) or a QSA report on compliance (ROC).
HOW ZUROTH HELPS
Services and proof for PCI DSS 4.0
Penetration Testing (VAPT) →
Cloud & Application Security →
24/7 Security Monitoring (SOC as a Service) →
Vulnerability & Patch Management →
Managed Detection & Response (MDR) →
SOC 2 Compliance & Audit Readiness →
ISO 27001 Certification Consulting →
API & Systems Integration →
ECOMMERCE
PCI DSS 4.0
SOC
PCI DSS 4.0 and unified compliance for multi-market retailers
Payment-page script control and one control framework across stores, eCommerce and markets.
5
frameworks mapped to one control set
Read the story →
ECOMMERCE
Managed detection & response
Cloud cost optimization
Peak-season readiness, 24/7 MDR and FinOps for omnichannel retailers
Load engineering, managed detection and response and cloud cost control before Black Friday.
3x
last year's peak as the load-test target
Read the story →
FINTECH
SaaS & MVP
API & integration
A pay-later MVP built for launch with a partner bank
Shopper app, merchant portal and credit decisioning, scoped to launch fast.
12
week fixed-scope MVP plan
Read the story →
What is the difference between PCI DSS 4.0 and 4.0.1?
PCI DSS 4.0.1 is a limited revision published in June 2024 that clarifies wording and corrects errors in 4.0 without adding new requirements. Version 4.0 was retired at the end of 2024, so assessments now use 4.0.1.
What became mandatory on 31 March 2025?
The future-dated requirements in PCI DSS 4.0 became mandatory, including multi-factor authentication for all access into the cardholder data environment, payment page script management and change detection, targeted risk analyses, stronger password rules and automated log reviews.
Do I need a QSA or can I self-assess?
It depends on your merchant or service provider level, set by the card brands and your acquiring bank. Large merchants and Level 1 service providers need an assessment by a Qualified Security Assessor. Smaller organizations usually complete a Self-Assessment Questionnaire (SAQ).
How can we reduce PCI DSS scope?
Use a PCI-compliant payment provider with hosted fields or redirects, tokenise card numbers and segment networks so card data never touches most systems. Less scope means fewer requirements, lower cost and simpler assessments, though payment page script controls may still apply.
How long does PCI DSS compliance take?
A merchant with a hosted payment page can often be ready in 4 to 8 weeks. Service providers and companies with card data in their own systems often need 3 to 6 months for scoping, remediation and assessment, followed by quarterly scans and yearly validation.
OTHER COMPLIANCE GUIDES
Need help with PCI DSS 4.0? Let's talk.
Book a free 30-minute call with a PCI DSS 4.0 specialist. You'll leave with a scope, a timeline and a fixed-price quote.
A clear scope and timeline
A fixed-price quote
No obligation, NDA on request