Cybersecurity & Data Security

PCI DSS Compliance and QSA Assessment Support in India

Last reviewed: 2026-11-07

Has your acquiring bank, card network, payment partner or customer asked for PCI DSS compliance, a Report on Compliance or an Attestation of Compliance? Tell us how your business handles card payments and what has been requested.

ConformArc reviews your requirement and, where a suitable provider is available, introduces you to a PCI DSS specialist, including a PCI SSC-listed Qualified Security Assessor (QSA) company where an independent assessment is required.

Discuss Your PCI DSS Requirement

Card payment environment being reviewed for PCI DSS compliance

At a glance

What to send with your enquiry

  • Business model and how payments are accepted (online, POS, phone, recurring, stored credentials)
  • Payment service providers, gateways and processors you use
  • Approximate annual card transaction volumes by brand
  • Whether your systems store, process or transmit card data
  • What your acquirer or partner has requested (ROC, AOC, SAQ type, ASV scans)
  • Any previous PCI DSS validation and its date

What a specialist can help with

  • Confirmation of your role (merchant or service provider) and the validation your acquirer or partner requires
  • Card data flow mapping and cardholder data environment (CDE) scoping
  • Gap assessment against PCI DSS v4.0.1 and a remediation plan
  • Support for Approved Scanning Vendor (ASV) scans and penetration testing, including segmentation testing where applicable
  • From a QSA company: Report on Compliance (ROC) and Attestation of Compliance (AOC), or support for an SAQ and AOC where eligible
Scope and report acceptance. ConformArc is not a QSA and does not assess PCI DSS compliance. Assessments are performed by the selected QSA company or, where permitted, by your organisation through a Self-Assessment Questionnaire. Do not send card data, network diagrams or credentials through the public form.
Role clarity. Enquiry support and specialist introductions. ConformArc is not a QSA. PCI DSS assessments, validation decisions and any regulatory or card-brand requirements remain with the QSA company, your acquirer, the card brands and the relevant authorities.

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

  1. Confirm your role and level. Merchant or service provider, transaction volumes and the validation your acquirer or partners require.
  2. Map card data flows and define the CDE.
  3. Gap assessment against PCI DSS v4.0.1, including the requirements that became mandatory in March 2025.
  4. Remediation. Implement technical and process controls, policies and evidence.
  5. 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.
  6. Validation. QSA assessment leading to ROC and AOC, or SAQ and AOC where eligible.
  7. Submit to the acquiring bank or partners as required.
  8. 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.

How ConformArc helps

  1. Share how you handle card payments and what has been requested.
  2. We clarify your role, level and validation requirement.
  3. We agree the introduction with you before sharing your details.
  4. 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

Frequently asked questions

Is PCI DSS mandatory in India?

PCI DSS is an industry standard enforced through card brands and acquiring banks. Requirements for specific Indian entities may also come from regulators and contracts. Check with your acquirer, partners and compliance adviser.

What is the difference between a QSA assessment and an SAQ?

A QSA company performs an independent assessment and produces a Report on Compliance. An SAQ is a self-assessment completed by an eligible organisation. Your acquirer or the card brand rules determine which applies.

We use a payment gateway. Do we still need PCI DSS?

Usually yes, but your scope may be much smaller, often an SAQ. It depends on how your website or app integrates with the gateway.

Which PCI DSS version applies now?

PCI DSS v4.0.1. Version 4.0 was retired on 31 December 2024, and the formerly future-dated requirements have been mandatory since 31 March 2025.

How often must we validate?

Annually, with quarterly ASV scans where required, plus ongoing testing.

Will ConformArc assess our compliance?

No. ConformArc introduces suitable providers. QSA companies perform independent assessments.

Sources / further reading

Requirements can change. Confirm the current route and applicable edition for the specific product before starting the project.

Discuss your PCI DSS requirement

How do you accept card payments and what has your bank or partner asked for?

We use your details to respond to this enquiry. If a suitable external specialist could help, we will tell you who we propose to contact and ask before sharing your name, contact details or project information. The specialist may then contact you about this request. Read the Privacy Notice. See also how we choose providers.

Related options for PCI DSS compliance.

Add more details (optional)

We use your details to respond to this enquiry. If a suitable external specialist could help, we will tell you who we propose to contact and ask before sharing your name, contact details or project information. Please do not include passwords, confidential documents or sensitive personal information.