---
title: "PCI DSS v4.0.1 explained for card payments | Quantlix"
description: "PCI DSS is the card industry's security standard for anyone who stores, processes or transmits card data. Learn what v4.0.1 requires and how it affects software."
canonical: "https://quantlix.com/en/standards/pci-dss/"
last-updated: 2026-11-16
---

Source: https://quantlix.com/en/standards/pci-dss/
Language: en
Description: PCI DSS is the card industry's security standard for anyone who stores, processes or transmits card data. Learn what v4.0.1 requires and how it affects software.

**PCI DSS** [Security and resilience](https://quantlix.com/en/standards/#security)

# PCI DSS: the security standard for payment card data

PCI DSS is the Payment Card Industry Data Security Standard, a set of technical and operational requirements for every organization that stores, processes or transmits payment card account data.

[Discuss your project](https://quantlix.com/en/contact/) [Read the key points](https://quantlix.com/en/standards/pci-dss/#standard-overview)

## At a glance

**Full name**

Payment Card Industry Data Security Standard: Requirements and Testing Procedures

**Published by**

PCI Security Standards Council (PCI SSC)

**Type**

Industry security standard, enforced through payment brand and acquirer programs

**Current version**

v4.0.1, published June 2024; v4.0 retired 31 December 2024; future-dated requirements effective 31 March 2025

**Applies to**

Merchants, processors, acquirers, issuers and service providers that store, process or transmit account data, or can affect its security

**Last reviewed**

November 16, 2026 (2026-11-16)

## In plain terms

### Key points

- PCI DSS v4.0.1 is the only active version. It replaced v4.0, which was retired on 31 December 2024.
- Its 12 principal requirements sit under six goals, from secure networks and protected account data to monitoring and security policy.
- Requirements that v4.0 marked as future-dated became effective on 31 March 2025 and now apply to every assessment.
- The PCI SSC maintains the standard, while payment brands and acquirers decide who must validate compliance and how.
- The Council took comments on v4.0.1 from June to July 2026 as the first step toward the next version; no release date has been announced.

### What is PCI DSS?

PCI DSS, the Payment Card Industry Data Security Standard, is **the baseline set of security requirements for protecting payment card account data**. It is published by the PCI Security Standards Council (PCI SSC), a body founded by the major card brands, and it applies to every organization that stores, processes or transmits cardholder data or sensitive authentication data, or that could affect the security of that data.

It exists so one common standard protects card data wherever it travels, from a checkout page to a processor’s data center. Customers can pay with confidence, and merchants and providers get a clear, shared description of what good protection looks like.

### What PCI DSS covers

The 12 principal requirements are grouped under six goals:

- **Build and maintain a secure network and systems.** Network security controls and secure configurations for every system component (requirements 1 and 2).
- **Protect account data.** Protect stored account data and use strong cryptography when it crosses open, public networks (3 and 4).
- **Maintain a vulnerability management program.** Protect systems from malicious software and develop and maintain secure systems and software (5 and 6).
- **Implement strong access control measures.** Restrict access by business need to know, identify and authenticate users, and restrict physical access (7, 8 and 9).
- **Regularly monitor and test networks.** Log and monitor all access to system components and card data, and test security regularly (10 and 11).
- **Maintain an information security policy.** Support security with organizational policies and programs (12).

### Versions, dates and validation

The current version is **PCI DSS v4.0.1**, published in June 2024 as a limited revision of v4.0 (March 2022). It corrected and clarified wording and added no new or deleted requirements. Version 4.0 was retired on 31 December 2024. The requirements v4.0 had marked as future-dated, such as multi-factor authentication for all access into the cardholder data environment and controls over scripts on payment pages, became effective on 31 March 2025.

In June 2026 the Council opened a six-week request for comments on v4.0.1, describing it as the first step toward the next version and asking how the standard should respond to new technology such as AI. When we checked in November 2026, no release date had been announced.

The PCI SSC maintains the standard but does not enforce it. Payment brands and acquirers define merchant and service provider levels and decide whether you validate with a Report on Compliance from a Qualified Security Assessor or with a Self-Assessment Questionnaire.

### How it shows up in software projects

- **Scope reduction first.** Tokenization, hosted payment fields and segmentation keep card data out of most of your systems, which shrinks what must be assessed.
- **Payment page integrity.** Scripts on pages that handle payments are inventoried, authorized and monitored for unauthorized changes.
- **Strong authentication.** Multi-factor authentication covers all access into the cardholder data environment, including administrators and remote access.
- **Secure development.** Bespoke and custom software is built with code review, developer training and protection against common attacks, as requirement 6 expects.
- **Logging and retention.** Audit logs cover access to system components and account data and are kept for at least 12 months, with the latest three months immediately available.

### How we work with PCI DSS

We design and build payment flows that keep card data out of places it does not need to be: [e-commerce solutions](https://quantlix.com/en/services/ecommerce-solutions/) that use your payment provider’s hosted fields or tokens, [cloud architecture](https://quantlix.com/en/services/cloud-architecture/) with segmented networks and tight access, and [web applications](https://quantlix.com/en/services/web-application-development/) with monitored payment pages and audit logs. We document data flows and scope, so your assessor sees a clear picture.

Validating compliance belongs to your organization, your assessor and your acquirer; we help you design, build and evidence the technical controls. Card security matters across [retail and e-commerce](https://quantlix.com/en/industries/retail-and-ecommerce/) and [hospitality](https://quantlix.com/en/industries/hospitality/), and service providers often run PCI DSS alongside [SOC 2](https://quantlix.com/en/standards/soc-2/).

## Where it applies

Industries where this standard often shapes the work.

- ### [Financial Services](https://quantlix.com/en/industries/financial-services/)

  Digital banking, insurance operations and fintech platforms
- ### [Retail & E-commerce](https://quantlix.com/en/industries/retail-and-ecommerce/)

  Connected stores, online commerce and personalized shopping experiences
- ### [Airlines & Aviation](https://quantlix.com/en/industries/airlines-and-aviation/)

  Airline operations, maintenance planning and passenger experiences
- ### [Hospitality](https://quantlix.com/en/industries/hospitality/)

  Guest experiences, booking platforms and hospitality operations

## Related standards

[All standards](https://quantlix.com/en/standards/)

- SOC 2

  ### [Assurance reports for service organizations](https://quantlix.com/en/standards/soc-2/)

  SOC 2 is an attestation report in which an independent CPA firm examines a service organization's controls relevant to security, availability, processing integrity, confidentiality or privacy.
- ISO/IEC 27001

  ### [Information security management systems](https://quantlix.com/en/standards/iso-iec-27001/)

  ISO/IEC 27001 is the international standard for an information security management system (ISMS): the policies, risk process and controls an organization uses to protect information and keep improving.
- DORA

  ### [Digital operational resilience for EU finance](https://quantlix.com/en/standards/dora/)

  DORA is the EU regulation that requires banks, insurers, investment firms and other financial entities to manage ICT risk, report major incidents, test their resilience and control technology providers.
- ISO 20022

  ### [Financial messaging standard](https://quantlix.com/en/standards/iso-20022/)

  ISO 20022 is the international standard for building financial messages from a shared business model. It is now used for cross-border payments on Swift and by major high-value payment systems.

## Services that support this work

The services we usually bring to projects that involve this standard.

[View all services](https://quantlix.com/en/services/)

### [E-commerce solutions](https://quantlix.com/en/services/ecommerce-solutions/)

Quantlix develops online storefronts and commerce integrations, connecting product discovery, checkout and order operations into a coherent shopping experience.

### [Cloud architecture](https://quantlix.com/en/services/cloud-architecture/)

Quantlix designs cloud infrastructure around workload requirements, security boundaries, operational visibility and cost, with an explicit path for deployment and recovery.

### [Web application development](https://quantlix.com/en/services/web-application-development/)

Quantlix designs and builds web applications with responsive interfaces, business logic and system integrations, balancing accessibility, performance and maintainability.

## Questions, answered

What teams usually ask us about this standard.

**Is PCI DSS a law?**

PCI DSS is an industry standard, not a law in itself. It usually applies through your agreements with acquiring banks and the payment brands, which set the validation rules and the consequences of not meeting them.

**What is the current version of PCI DSS?**

Version 4.0.1, published in June 2024. It clarified v4.0 and added no new requirements. The PCI SSC took comments on it from 3 June to 20 July 2026 to plan the next version, and when we checked in November 2026 no newer version had been published.

**Do we need a QSA assessment?**

It depends on your validation level, which the payment brands and your acquirer set. Larger merchants and service providers usually need a Report on Compliance from a Qualified Security Assessor (QSA), while others may complete a Self-Assessment Questionnaire (SAQ).

**How can we reduce PCI DSS scope?**

Keep account data out of systems that do not need it. Hosted payment fields from a validated provider, tokenization and network segmentation all shrink the cardholder data environment, though the pages that host or redirect to payment forms still need protecting.

**Can software be PCI DSS certified?**

PCI DSS assesses an entity's environment, not a product. Payment software is covered by separate PCI SSC programs, such as the PCI Secure Software Standard.

## Official sources

Read the official text before relying on any detail. What applies to you depends on your role, your location and the version in force.

- [PCI DSS on the PCI Security Standards Council website](https://www.pcisecuritystandards.org/standards/pci-dss/)
- [PCI SSC: PCI DSS v4.0.1 published (June 2024)](https://blog.pcisecuritystandards.org/just-published-pci-dss-v4-0-1)
- [PCI SSC: Request for comments on PCI DSS v4.0.1 (June 2026)](https://blog.pcisecuritystandards.org/request-for-comments-pci-data-security-standard-pci-dss-v4.0.1)

These guides explain each standard in plain terms. They are not legal advice, and they do not state that any product or organization conforms to a standard.

## Planning software around this standard?

Tell us which systems are involved and what you need to show. We will help you build the requirements in from the start.

[Discuss your project](https://quantlix.com/en/contact/)
