Return to Cybersecurity and Data Security.
What PCI DSS is
The Payment Card Industry Data Security Standard (PCI DSS) is a security standard maintained by the PCI Security Standards Council (PCI SSC). It applies to organisations that store, process or transmit cardholder data or sensitive authentication data, or that can affect the security of that data. Compliance requirements, including how you validate compliance, are enforced through the card brands and acquiring banks, not by PCI SSC itself.
PCI DSS v4.0.1 is the current and only active version. PCI DSS v4.0 was retired on 31 December 2024. The requirements that were “future-dated” in v4.0 became mandatory on 31 March 2025, so assessments now include them.
“PCI DSS certification” explained
Organisations often say “PCI DSS certified”. Formally, you validate compliance and receive one of:
- Report on Compliance (ROC) and Attestation of Compliance (AOC): produced after an assessment by a QSA (or, in some cases, a trained Internal Security Assessor), typically required for larger merchants and service providers
- Self-Assessment Questionnaire (SAQ) and AOC: completed by eligible merchants and service providers themselves, sometimes with consultant support
Your acquiring bank or the card brands decide which validation you need, based on your level and business model.
Who needs PCI DSS in India
- Payment aggregators and payment gateways (confirm the current RBI requirements that apply to you with your compliance adviser)
- E-commerce merchants and marketplaces (scope depends heavily on whether card data touches your systems)
- Fintech and lending platforms that process card payments
- Banks’ technology and processing vendors
- BPO and contact centres that take card payments by phone
- SaaS providers whose platforms are part of customers’ payment flows (service providers)
Requirements for specific entities can also come from regulators, acquirers and contracts. These should be confirmed with your acquirer, partners and advisers.
The 12 PCI DSS requirements at a glance
| Goal |
Requirements |
| Build and maintain a secure network and systems |
1. Network security controls · 2. Secure configurations |
| Protect account data |
3. Protect stored account data · 4. Strong cryptography in transmission |
| Maintain a vulnerability management programme |
5. Protect against malicious software · 6. Develop and maintain secure systems and software |
| Implement strong access control |
7. Restrict access by business need to know · 8. Identify users and authenticate access · 9. Restrict physical access |
| Regularly monitor and test networks |
10. Log and monitor all access · 11. Test security regularly |
| Maintain an information security policy |
12. Support information security with organisational policies and programmes |
Scope is the biggest decision
PCI DSS applies to the cardholder data environment (CDE): the people, processes and technology that store, process or transmit account data, plus connected systems. Reducing scope through tokenisation, hosted payment pages, network segmentation and not storing card data can dramatically reduce effort. A good provider starts by confirming scope and data flows before testing controls.
The PCI DSS compliance process
- Confirm your role and level. Merchant or service provider, transaction volumes and the validation your acquirer or partners require.
- Map card data flows and define the CDE.
- Gap assessment against PCI DSS v4.0.1, including the requirements that became mandatory in March 2025.
- Remediation. Implement technical and process controls, policies and evidence.
- Testing. Quarterly external vulnerability scans by an Approved Scanning Vendor (ASV) where required, internal scans, and penetration tests including segmentation testing where applicable. See VAPT services in India.
- Validation. QSA assessment leading to ROC and AOC, or SAQ and AOC where eligible.
- Submit to the acquiring bank or partners as required.
- Maintain compliance year-round. Validation is annual, with ongoing scanning and testing.
Not sure whether you need a QSA or an SAQ? Tell us your business model, transaction volumes and what your bank or partner has asked for. We will discuss a suitable introduction. Ask About PCI DSS Validation
Timeline and cost factors
- Size and complexity of the CDE and the number of locations and systems in scope
- Whether scope can be reduced (tokenisation, outsourcing to PCI-compliant providers)
- Validation type (QSA ROC versus SAQ)
- Remediation required, especially for the v4.0 requirements that are now mandatory (for example stronger authentication and payment-page script controls)
- ASV scanning and penetration testing needs
- On-site assessment requirements
ConformArc does not set provider fees.
How to verify your QSA
| Provider type |
How to verify |
| QSA company (PCI DSS) |
Check the company, and ideally the named assessor, on the PCI Security Standards Council’s list of Qualified Security Assessors. |
Many payment and fintech organisations also work on ISO 27001 and SOC 2. Controls overlap, but each framework has its own scope, assessor and validation route.
- Share how you handle card payments and what has been requested.
- We clarify your role, level and validation requirement.
- We agree the introduction with you before sharing your details.
- The provider confirms scope, fees and timeline directly with you.
Tell us about your PCI DSS requirement
How do you accept card payments and what has your bank or partner asked for? We will review the details and reply about the next step.
Discuss Your PCI DSS Requirement