Skip to content
  • There are no suggestions because the search field is empty.

PCI DSS v4.0 – Payment Card Security Requirements Explained

An overview of PCI DSS, who it applies to (including software suppliers), why compliance matters, and how to approach payment security obligations with confidence.

PCI DSS v4.0 – Overview

What is PCI DSS?

The Payment Card Industry Data Security Standard (PCI DSS) v4.0 is a global security standard designed to protect cardholder data. It sets out technical and organisational requirements for securing environments that store, process or transmit payment card information.

PCI DSS is developed and maintained by the PCI Security Standards Council and applies to organisations involved in the payment ecosystem. Unlike ISO 27001, PCI DSS is not a broad information security framework — it is specifically focused on protecting payment card data and reducing fraud.

Compliance is typically validated through self-assessment questionnaires (SAQs) or formal audits, depending on transaction volumes and business type.


Who is PCI DSS aimed at?

PCI DSS applies to any organisation that:

  • Stores, processes or transmits cardholder data

  • Develops or manages payment applications

  • Provides services that could impact the security of payment environments

For software suppliers, PCI DSS is particularly relevant if you:

  • Integrate directly with payment gateways

  • Process card payments within your platform

  • Provide hosted payment pages or embedded checkout functionality

  • Handle card data on behalf of customers

  • Support merchants as a payment service provider

Even if card data is outsourced to a third-party processor, your organisation may still have PCI DSS responsibilities depending on how payments are integrated.


Why might PCI DSS be useful?

1. Protects Payment Data

PCI DSS establishes clear security controls to safeguard cardholder information and reduce the risk of fraud and data breaches.

2. Contractual Requirement

Compliance is typically required by acquiring banks and payment processors. Without it, organisations may be unable to process card payments.

3. Reduces Business Risk

Non-compliance can lead to fines, increased transaction fees, reputational damage and potential loss of the ability to process payments.

4. Builds Customer Trust

Demonstrating PCI DSS compliance provides assurance to customers and partners that payment information is handled securely.

5. Strengthens Security Controls

Many PCI DSS requirements — such as network segmentation, access control, logging and vulnerability management — improve overall security maturity beyond just payment data protection.


What does compliance involve?

PCI DSS v4.0 is structured around 12 high-level requirements, including:

  • Installing and maintaining secure network controls

  • Protecting stored cardholder data

  • Encrypting transmission of cardholder data

  • Implementing strong access control measures

  • Regularly monitoring and testing networks

  • Maintaining an information security policy

The level of validation required depends on transaction volume and role within the payment ecosystem. Some organisations complete annual self-assessments, while others require assessment by a Qualified Security Assessor (QSA).

PCI DSS also places increasing emphasis on continuous security monitoring rather than point-in-time compliance.


Is PCI DSS certification mandatory?

PCI DSS is not a law, but it is typically a contractual requirement imposed by payment brands and acquiring banks. If your organisation processes card payments, compliance is usually mandatory.

The specific requirements that apply to you will depend on your payment architecture and how card data flows through your systems.


How Adoptech Can Help

Understanding your PCI DSS scope can be complex, particularly for software suppliers with integrated or hybrid payment models.

Adoptech supports organisations by:

  • Helping define PCI DSS scope and responsibilities

  • Structuring controls and evidence collection

  • Aligning PCI requirements with existing security frameworks (such as ISO 27001)

  • Supporting audit preparation and compliance validation

If you would like to understand whether PCI DSS applies to your organisation, or how to approach compliance efficiently, please contact a member of the Adoptech team for further guidance.