Skip to main content
For Indian merchants, fintechs, aggregators and platforms

PCI DSS Compliance and v4.0.1 readiness, for businesses in India

PCI DSS is enforced by your acquirer, not by a regulator, and its cost is decided by how much of your stack touches card data. We find the data first, cut the scope, then close what is left.

  • Every card data flow mapped before the boundary is drawn
  • Scope cut first, so controls are paid for once
  • Gap list against v4.0.1, including the 2025 requirements
  • Questionnaire prepared or assessor briefed, then kept alive
Reviewed by Industry Experts & Startup Specialists.
Last Updated: 
FREE Consultation Get Started @ ₹299 ₹0

Get Expert Consultation

Share Your Business Requirement

Instant Response 100% Confidential Expert Advice

Encrypted in transit We do not sell your data

Requirements to meet
12
Self-assessment routes
8
External scan cadence
90 days
The only active version
v4.0.1

Our partners & associations

Client RatingRazorpay TrustedZoho Partner
FAQs

Frequently asked questions about PCI DSS compliance

38 questions taken from real search queries, acquirer onboarding checklists, PCI Security Standards Council guidance and the way assessments actually run in India.

The decision
PCI DSS validation ends in one document either way: an Attestation of Compliance. What differs is who does the testing behind it. A self-assessment questionnaire is completed by you against the requirements that apply to your architecture, and your own officer signs the attestation. A Report on Compliance is produced by an independent Qualified Security Assessor, which is mandatory for Level 1 merchants and Level 1 service providers, and is often imposed after a breach. Your acquiring bank or payment aggregator decides which applies, sets the deadline, and is the entity the attestation is filed with.
  • Self-assessmentOne of 8 questionnaires, signed by you
  • Assessor-ledReport on Compliance by a Qualified Security Assessor
  • Who decidesYour acquirer or payment aggregator
  • What is filedThe Attestation of Compliance, every year
PCI DSS self-assessment compared with an assessor-led Report on Compliance
DimensionSelf-assessment questionnaireReport on Compliance
Who performs the testingYour own team, against the applicable requirementsAn independent Qualified Security Assessor, onsite and by sampling
Who signs the attestationAn executive officer of your companyThe assessor signs the report; your officer signs the attestation
Who it is required forMerchant Levels 2 to 4 and Level 2 service providersLevel 1 merchants, Level 1 service providers, and often after a breach
Typical elapsed timeWeeks once remediation is complete6 to 10 weeks of fieldwork after remediation, plus reporting
Evidence expectationsHeld by you and produced if the acquirer asksSampled and tested item by item during fieldwork
CadenceAnnual, with quarterly scans in betweenAnnual, with quarterly scans in between

The mistake that repeats the whole exercise

Choosing a questionnaire that does not match how your payment page is actually delivered. SAQ A assumes every element of the payment page reaches the browser only and directly from a compliant provider. If your own server renders any part of that page, the honest answer is SAQ A-EP, which carries a far larger requirement set. An attestation on the wrong questionnaire is rejected on review, and the evidence exercise starts again.

Why ProTax

Frequently asked questions about PCI DSS compliance

38 questions taken from real search queries, acquirer onboarding checklists, PCI Security Standards Council guidance and the way assessments actually run in India.

Discovery before design

We look for card data where it is not supposed to be, in application logs, ticket attachments, call recordings and old backups, because a boundary drawn before discovery is a boundary that fails at assessment.

Scope cut, then controls

Redirection, network tokens, retiring old stores and segmenting the network remove requirements permanently. Every system taken out of scope is a set of controls you never have to buy, run or evidence again.

The right validation route

Eight questionnaires exist and only one fits your architecture. Picking the wrong one produces an attestation your acquirer rejects, which costs a quarter and repeats the whole evidence exercise from the start.

Built to survive the year

Validation is annual but the obligations are continuous. We set the scanning, testing and review calendar so the next attestation is a formality rather than the same scramble twelve months later.

FAQs

Frequently asked questions about PCI DSS compliance and the privacy laws

Key takeaway
PCI DSS is the Payment Card Industry Data Security Standard, published by the PCI Security Standards Council, the body founded in 2006 by American Express, Discover, JCB International, Mastercard and Visa. It applies to every entity that stores, processes or transmits payment card account data, and it is enforced through contract: the card brands impose it on acquiring banks, and acquirers impose it on merchants and service providers. The current version is v4.0.1, published in June 2024 and the only active version of the standard since 1 January 2025. The 51 requirements that v4.0 introduced as future-dated became mandatory on 31 March 2025, so nothing in the standard is optional on a timeline any more.
  • Who publishes itPCI Security Standards Council, founded 2006
  • Who enforces itYour acquirer, under the merchant agreement
  • Version in forcev4.0.1, sole active version since 1 Jan 2025
  • What you produceAn Attestation of Compliance, renewed annually

The contractual nature of the standard is what makes it behave differently from every other security framework a business meets. There is no regulator to appeal to, no grace period written into a statute, and no partial credit: a requirement either applies to you and is met, or it applies and is not. What there is instead is a counterparty, your acquiring bank or payment aggregator, which decides your level, sets your deadline and receives your attestation.

That also explains why the cost of a programme varies so widely between businesses of the same size. The standard scales with the CDE, the cardholder data environment, and that environment is a consequence of architecture rather than revenue. A company that never lets a card number reach its own servers answers a short questionnaire. A company that stores PAN data in its own database answers the whole standard, every year, for as long as it keeps doing so.

ProTax security compliance team reviewing a payment card data flow diagram with an engineering lead in India Assessment ready

What a readiness programme produces

These are the artefacts an assessor asks for and an acquirer expects to see, and they are the same artefacts that answer an enterprise customer's security questionnaire months before any attestation is signed.

  • Card data discovery results across databases, logs, backups and endpoints
  • Data flow diagrams and a network diagram showing the CDE boundary
  • Scope reduction plan: redirection, tokenisation, retirement, segmentation
  • Gap assessment against v4.0.1 with owners and target dates
  • Policy set, plus a targeted risk analysis for every self-set frequency
  • Evidence pipeline, control calendar and the scanning and testing schedule
FAQs

Frequently asked questions about PCI DSS compliance

38 questions taken from real search queries, acquirer onboarding checklists, PCI Security Standards Council guidance and the way assessments actually run in India.

Where the PCI DSS obligation comes from for a business operating in India
SourceWhat it requiresWho it lands on
Merchant agreement with your acquirerValidation at the level the acquirer assigns, by the route and deadline it sets, with the attestation filed to itEvery merchant taking card payments, whatever its size
RBI (Regulation of Payment Aggregators) Directions, 2025A payment aggregator shall ensure that the infrastructure of its merchants is compliant with security standards like PCI DSS and PCI SSF, as applicablePayment aggregators, and through onboarding, their merchants
The same Directions, Annexure 1Customer card credentials shall not be stored within the database or the server accessed by the merchantMerchants onboarded by any Indian payment aggregator
The same Directions, reporting scheduleSubmission of the Attestation of Compliance and the Report on Compliance, alongside vulnerability assessment and penetration test reportsAuthorised payment aggregators, to the Reserve Bank of India
The same Directions, system audit clauseAn annual system audit including a cyber security audit, conducted by CERT-In empanelled auditorsAuthorised payment aggregators
Card-on-file tokenisation frameworkCard credentials replaced by network tokens for saved-card use cases, keeping the card number with issuers and networksMerchants and aggregators offering a saved-card experience

The practical effect of the 2025 Directions is that the question is no longer whether an Indian merchant should hold an attestation, but which one and by when. Aggregators now collect attestations at onboarding and at renewal because their own filings to the Reserve Bank depend on it, and an onboarding that stalls for want of a signed attestation stalls the revenue behind it.

The second effect is more useful than it looks. Because Indian rules keep card credentials out of merchant systems, the architecture most Indian merchants already run is the architecture that produces the smallest assessment. The work is usually not building new controls but proving that card data really does stay where the design says it stays, which is where discovery earns its place.

Tokenisation shrinks the scope; it does not close the file

A network token is not account data, so a system holding only tokens is out of scope for the requirements that protect stored card numbers. What remains in scope is the path the real card number takes on its way to the provider: the payment page and everything that assembles it, the redirect or iframe, the scripts loaded into the customer's browser, and any support process where a number can be read aloud or pasted. Those are exactly the areas the newest requirements target, so a tokenised merchant still validates, just against a much shorter list.

FAQs

Frequently asked questions about PCI DSS compliance and the privacy laws

38 questions taken from real search queries, acquirer onboarding checklists, PCI Security Standards Council guidance and the way assessments actually run in India.

Systems that hold the data

Anything that stores, processes or transmits account data sits inside the environment by definition, including the queue that carries an authorisation message and the log line that captured one by accident.

Systems merely connected to them

A jump host, a directory service, a monitoring agent, a build pipeline or a backup server can be in scope without ever seeing a card number, because it can reach the environment or affect its security.

Segmentation, tested annually

Segmentation is not mandatory, but without it a flat network puts every system in scope. Where it is used to reduce scope, the controls have to be tested at least every 12 months, or every 6 for service providers.

Third parties and their attestations

Providers that handle card data on your behalf carry their own obligations, and you are expected to hold their attestations, know which requirements they cover for you and record where each responsibility sits.

The whole programme in three moves

Step 1. Find every place card data lands, including the places nobody designed for it, because discovery decides where the boundary can honestly be drawn. Step 2. Remove or isolate everything the business can operate without, since scope removed is scope you never defend again. Step 3. Apply the controls to what is left, and keep producing the evidence that proves they ran, because the attestation is annual but the obligations are continuous.

FAQs

Frequently asked questions about PCI DSS compliance

38 questions taken from real search queries, acquirer onboarding checklists, PCI Security Standards Council guidance and the way assessments actually run in India.

Payment card data elements and whether they may be retained after authorisation
Data elementFamilyMay it be stored after authorisation?
Primary Account Number, the card numberCardholder dataYes, only when rendered unreadable wherever it is stored
Cardholder nameCardholder dataYes, protected in line with the rest of the environment
Expiry dateCardholder dataYes, protected in line with the rest of the environment
Service codeCardholder dataYes, protected in line with the rest of the environment
Full track data from stripe, chip or equivalentSensitive authentication dataNever, in any form, including encrypted
Card verification value printed on the cardSensitive authentication dataNever, in any form, including encrypted
PIN or PIN blockSensitive authentication dataNever, in any form, including encrypted

Where the card number is displayed rather than stored, masking applies: the maximum a screen may show is the bank identification number and the last four digits, and anyone needing more than that has to have a documented business justification. Where it is stored, rendering it unreadable means strong cryptography, keyed hashing across the whole number, truncation, or tokens backed by properly protected mappings.

The prohibition on sensitive authentication data is the requirement most often broken by accident rather than by design. It is broken by a debug flag that logs the full authorisation request, by a support agent pasting a verification value into a ticket, and by a call recording that captures a number read aloud. Each of those is a storage event, and each is found by discovery rather than by reading the architecture diagram.

A card number in a log file is a card number in scope

The most common finding in a first assessment is account data sitting in application logs, ticket attachments, call recordings, database exports or a backup taken years ago and never reviewed. Every one of those pulls the system holding it into the cardholder data environment, along with everything connected to it. This is why discovery runs before the boundary is drawn rather than after, and why it is repeated periodically instead of being treated as a one-off exercise at the start of the programme.

FAQs

Frequently asked questions about PCI DSS compliance

38 questions taken from real search queries, acquirer onboarding checklists, PCI Security Standards Council guidance and the way assessments actually run in India.

PCI DSS self-assessment questionnaires and the businesses each one fits
QuestionnaireWho it is forThe condition that decides eligibility
SAQ AE-commerce or mail and telephone order merchants who have outsourced all account data functionsNo account data touches your systems, and every payment page element comes only and directly from a compliant provider
SAQ A-EPE-commerce merchants whose own site controls how the payment page is deliveredYou never receive account data, but your server influences the page or the script that collects it
SAQ BMerchants using imprint machines or standalone dial-out terminalsNo internet connection carrying account data and no electronic storage of it
SAQ B-IPMerchants using standalone approved terminals with an IP connectionTerminals are validated, isolated, and no account data is stored electronically
SAQ C-VTMerchants keying transactions into a hosted virtual terminalOne isolated device, a provider-hosted terminal, and no electronic storage
SAQ CMerchants running a payment application connected to the internetThe payment application is on a system with internet access, with no electronic storage of account data
SAQ P2PEMerchants using only terminals in a validated point-to-point encryption solutionThe solution is listed as validated, and no account data is stored electronically
SAQ DEvery other merchant, and every service provider eligible to self-assessAnything that does not fit above, including any electronic storage of account data

The line between SAQ A and SAQ A-EP is where most e-commerce merchants spend their scoping time, and it is a technical question rather than a commercial one. If the customer is redirected to the provider, or the payment fields sit inside an iframe served entirely by the provider, SAQ A is available. If your own page renders the fields, or your own script posts the data onward, the answer is SAQ A-EP and roughly ten times the requirement set.

What changed for SAQ A, and what changed again in 2026

From 31 March 2025, the Council removed Requirements 6.4.3 and 11.6.1 from SAQ A itself and replaced them with two eligibility criteria: every element of the payment page delivered to the browser must originate only and directly from a compliant provider, and the merchant must confirm its site is not susceptible to script attacks that could affect its e-commerce systems. On 4 August 2026 the Council revised FAQ 1331, so treating those requirements as not applicable in a Report on Compliance now requires confirmation from the acquirer or payment brand, rather than agreement with an assessor alone.

FAQs

Frequently asked questions about PCI DSS compliance

38 questions taken from real search queries, acquirer onboarding checklists, PCI Security Standards Council guidance and the way assessments actually run in India.

Merchant levels by annual card transaction volume, and the validation each one carries
LevelAnnual transaction volumeHow validation is performed
Level 1More than 6 million transactions a year, or any merchant a brand designatesReport on Compliance by a Qualified Security Assessor or an Internal Security Assessor, plus quarterly scans by an Approved Scanning Vendor
Level 21 million to 6 million transactions a yearAnnual self-assessment questionnaire plus quarterly scans by an Approved Scanning Vendor
Level 320,000 to 1 million e-commerce transactions a yearAnnual self-assessment questionnaire plus quarterly scans by an Approved Scanning Vendor
Level 4Below 20,000 e-commerce transactions, or up to 1 million across all channelsAnnual self-assessment questionnaire, with scanning and reporting as the acquirer requires
Service provider Level 1More than 300,000 transactions a year stored, processed or transmittedAnnual Report on Compliance by a Qualified Security Assessor, plus quarterly scans
Service provider Level 2Up to 300,000 transactions a yearAnnual SAQ D for service providers, plus quarterly scans

A breach can change your level overnight

Volume is the usual route into Level 1, but it is not the only one. A card brand can designate any entity a Level 1 merchant at its discretion, and after a confirmed compromise it routinely does, moving a business that was self-assessing to assessor-led validation with a forensic investigation running alongside. Planning a programme on the assumption that this year's volume fixes next year's obligations is how a company ends up commissioning a Report on Compliance with no evidence pipeline behind it.

FAQs

Frequently asked questions about PCI DSS compliance and the privacy laws

38 questions taken from real search queries, acquirer onboarding checklists, PCI Security Standards Council guidance and the way assessments actually run in India.

The six PCI DSS control objectives and the 12 requirements beneath them
Control objectiveRequirementWhat it covers in practice
Build and maintain a secure network and systems1. Network security controlsFirewall and equivalent controls between the environment and everything else, with reviewed rulesets and documented flows
Build and maintain a secure network and systems2. Secure configurationsVendor defaults removed, hardening standards applied to every system component, and configuration drift managed
Protect account data3. Protect stored account dataRetention limits, sensitive authentication data never kept, the card number rendered unreadable, and key management that stands up to testing
Protect account data4. Protect data in transmissionStrong cryptography for account data crossing open public networks, with an inventory of the certificates and protocols in use
Maintain a vulnerability management programme5. Protect against malicious softwareAnti-malware coverage, periodic evaluation for systems deemed not at risk, and anti-phishing controls for users
Maintain a vulnerability management programme6. Secure systems and softwarePatching to defined timelines, secure development practices, code review, and management of the scripts on a payment page
Implement strong access control measures7. Restrict access by business needLeast privilege by role, access granted by a defined approval path, and reviews that produce a signed record
Implement strong access control measures8. Identify users and authenticate accessUnique identity for every user, no shared accounts, multi-factor authentication into the environment, and password rules that meet the current thresholds
Implement strong access control measures9. Restrict physical accessControls over facilities, media, devices and their disposal, including periodic inspection of point-of-interaction terminals
Regularly monitor and test networks10. Log and monitor all accessAudit trails for every access to the environment, time synchronisation, protected logs, and reviews that are actually performed
Regularly monitor and test networks11. Test security regularlyInternal and external vulnerability scanning, annual penetration testing, segmentation testing, and detection of unauthorised change
Maintain an information security policy12. Policies and programmesThe policy set, risk analyses, awareness training, third-party management, and an incident response plan that has been tested
FAQs

Frequently asked questions about PCI DSS compliance and the privacy laws

38 questions taken from real search queries, acquirer onboarding checklists, PCI Security Standards Council guidance and the way assessments actually run in India.

Requirements introduced in PCI DSS v4 that became mandatory on 31 March 2025
RequirementWhat it asks forWhy it catches teams out
6.4.3 Payment page scriptsEvery script loaded into the payment page is inventoried, authorised, and its integrity assuredNobody owns the tag manager, and analytics scripts arrive on the payment page through marketing rather than engineering
11.6.1 Tamper detectionA mechanism that alerts on unauthorised change to the payment page content and its HTTP headersIt is a new capability rather than a policy, so it needs tooling and an owner before the assessment, not during it
8.4.2 Multi-factor authenticationMulti-factor authentication for all non-console access into the cardholder data environment, for every roleOne legacy path, a break-glass account or a vendor jump host is usually still single factor
8.3.6 Password strengthA minimum of 12 characters, or 8 where the system genuinely cannot support 12, with complexity appliedLegacy systems and service accounts inherit an old standard nobody has revisited
12.3.1 Targeted risk analysisA documented analysis justifying every frequency the entity sets for itselfPolicies say quarterly with no reasoning recorded, which is now a finding rather than a preference
5.4.1 Anti-phishingMechanisms that protect users from phishing attacks, technical rather than only educationalAwareness training exists, but the technical control behind it is assumed rather than evidenced
11.3.1.1 Lower-severity findingsVulnerabilities not ranked high or critical are managed rather than ignoredThe backlog of medium findings has never had an owner or a treatment decision
12.10.7 Card data found outside scopeIncident response is triggered when account data is discovered where it should not beDiscovery finds card numbers and the finding goes to a backlog instead of an incident process

Alongside the new requirements, v4 introduced the customized approach: instead of meeting a requirement exactly as written, an entity may design its own control, document how it meets the stated objective, support it with a targeted risk analysis, and have the assessor test it against that objective. It suits unusual architectures and it is heavy on documentation, so it rewards teams that already run a mature control programme rather than teams reaching for it to avoid one.

Version 4.0.1, published in June 2024, is a limited revision. It adds and removes nothing, clarifying wording and guidance instead, and it has been the only active version since v4.0 retired on 31 December 2024. In June 2026 the Council opened a request for comments on v4.0.1 to begin shaping the next release, so a programme built now should assume the current requirement set is stable for the assessment ahead of it.

FAQs

Frequently asked questions about PCI DSS compliance

38 questions taken from real search queries, acquirer onboarding checklists, PCI Security Standards Council guidance and the way assessments actually run in India.

01

Ask the acquirer which level and route apply

Your acquiring bank or payment aggregator assigns your level and states whether it expects a self-assessment questionnaire or a Report on Compliance, and by when. Those two answers fix the shape of the programme, so they are worth obtaining in writing before anything else starts.

02

Find the card data before you design anything

Run discovery across databases, file shares, application logs, backups, ticketing systems, call recordings and endpoints. Account data almost always turns up somewhere nobody designed for it, and a boundary drawn before discovery is a boundary that fails under testing.

03

Map the flows and draw the boundary

Document every path account data takes into, through and out of the business, then define the cardholder data environment: what stores, processes or transmits the data, plus everything connected to it or able to affect its security. Diagrams are assessed artefacts, not internal notes.

04

Cut the scope before you spend on controls

Redirect the payment page to a compliant provider, adopt network tokens in place of stored card numbers, retire systems holding account data for no current reason, and segment the network. Every system removed is a set of requirements you never evidence again.

05

Run the gap assessment against v4.0.1

Test the current state against the requirements that apply to your validation route, including the 51 formerly future-dated requirements that became mandatory on 31 March 2025. The output is a prioritised gap list with named owners and target dates, not a percentage score.

06

Remediate access and the payment page first

Multi-factor authentication on every path into the environment, unique credentials with no shared administrator accounts, an inventory of the scripts on the payment page with integrity checks, tamper detection on page content and headers, and logs a reviewer can search.

07

Write the policies and the targeted risk analyses

Produce the information security policy set the standard expects, then document a targeted risk analysis for every requirement whose frequency you choose yourself, recording the asset, the threat, how a failure would be detected and when the decision is reviewed.

08

Set up scanning, testing and the evidence pipeline

Schedule quarterly external scans with an Approved Scanning Vendor and internal scans on the same cadence, book annual penetration testing and the segmentation testing that protects your scope reduction, and decide where every piece of evidence lands and who owns it.

09

Complete the questionnaire or the assessor fieldwork

For a self-assessment, work through the applicable questionnaire, confirm the eligibility criteria genuinely hold, collect the evidence and sign the attestation. For the assessor-led route, brief the Qualified Security Assessor with scope, diagrams and control matrix, then support sampling.

10

Keep validation alive through the year

File the attestation with the acquirer, keep the external scans passing every quarter, re-test after significant change, review access on schedule, and re-run discovery periodically so card data does not quietly reappear outside the boundary before the next annual validation.

Find out how much of your stack is really in scope

A scoping review traces every card data flow, tells you which questionnaire you are genuinely eligible for, and gives you the gap list with owners before any assessor is engaged or any tooling is bought.

FAQs

Frequently asked questions about PCI DSS compliance

38 questions taken from real search queries, acquirer onboarding checklists, PCI Security Standards Council guidance and the way assessments actually run in India.

PCI DSS timing from first scoping review to the second annual attestation
StageTypical durationWhat is happening
Phase 1. Discovery and scoping3 to 5 weeksCard data discovery, data flow mapping, boundary definition and the scope reduction plan
Phase 2. Gap assessment2 to 4 weeksTesting the current state against v4.0.1, producing the gap list with owners and target dates
Phase 3. Remediation6 weeks to 2 quartersAccess, segmentation, payment page controls, logging, policies and the targeted risk analyses
Scanning and testingRuns alongside remediationFirst passing external scan by an Approved Scanning Vendor, internal scans, penetration testing
Self-assessment route2 to 4 weeksCompleting the questionnaire, assembling evidence and signing the Attestation of Compliance
Assessor-led route6 to 10 weeksQualified Security Assessor fieldwork, sampling, findings, remediation and the Report on Compliance
Attestation validityAnnualRevalidation each year, with the attestation filed to the acquirer or payment aggregator
External scan cadenceEvery 90 daysA passing Approved Scanning Vendor scan each quarter, plus re-scans after significant change
Penetration testingAt least annuallyExternal and internal testing, and after any significant infrastructure or application change
Segmentation testing12 months, or 6 for service providersConfirming the segmentation controls that keep systems out of scope still work as described

Plan backwards from the acquirer deadline

A merchant told in October to produce an attestation by March has roughly five months, and remediation is the only variable in that equation. Discovery and scoping take weeks; a payment page rebuild, a segmentation project or replacing a system that stores card numbers takes a quarter or more. The teams that finish comfortably start the scoping review the week the request arrives, because scope reduction decided in week two removes work that would otherwise consume months four and five.

FAQs

Frequently asked questions about PCI DSS compliance

38 questions taken from real search queries, acquirer onboarding checklists, PCI Security Standards Council guidance and the way assessments actually run in India.

Produces a clean validation

  • Discovery run before the boundary is drawn, and repeated on a schedule afterwards
  • A payment page delivered so the merchant genuinely qualifies for the questionnaire it uses
  • Segmentation designed deliberately, documented, and tested on its required cadence
  • Multi-factor authentication on every path into the environment, including vendor and break-glass access
  • An inventory of the scripts on the payment page, with an owner and integrity checking
  • A targeted risk analysis recorded for every frequency the business sets for itself
  • External scans booked as a standing quarterly commitment rather than remembered late

Produces findings

  • Card numbers sitting in application logs, ticket attachments, call recordings or an old backup
  • A flat network where every system is connected to the environment and therefore in scope
  • Shared administrator accounts, or one legacy access path still on a single factor
  • Analytics and marketing tags added to the payment page by people outside engineering
  • A questionnaire chosen for its length rather than for the architecture it describes
  • Policies that state frequencies with no risk analysis recorded behind them
  • Scans run once at the start of the year and never repeated until the next attestation is due
FAQs

Frequently asked questions about PCI DSS compliance and the privacy laws

38 questions taken from real search queries, acquirer onboarding checklists, PCI Security Standards Council guidance and the way assessments actually run in India.

PCI DSS compared with SOC 2, ISO 27001 and the privacy frameworks
DimensionPCI DSSSOC 2ISO 27001DPDP and GDPR
What it isA contractual security standard for card dataAn auditor report on controlsA certifiable management system standardStatutory obligations
Who asks for itYour acquirer and payment aggregatorEnterprise buyers in procurementEnterprise buyers, often EuropeanRegulators, and any customer whose data you hold
Who signs offYou, or a Qualified Security AssessorA licensed audit firmAn accredited certification bodyNobody: you evidence compliance yourself
OutputAn Attestation of ComplianceA restricted-use report shared under NDAA certificate valid three years with surveillanceAn evidence pack produced on demand
Scope defined byWhere card data flows and what connects to itYour system description and chosen criteriaYour management system scope statementThe personal data you actually process
Result typePass or fail against each requirementAn opinion, with exceptions disclosedCertified, with major and minor findingsContinuous, tested only when challenged
RecursAnnually, with quarterly scanning throughoutAnnually, by observation windowSurveillance yearly, recertification every three yearsContinuously, reviewed on change

The overlap is genuine but partial. One access review process, one change workflow, one logging pipeline and one evidence store can serve PCI DSS, SOC 2 and ISO 27001 at once. What none of them gives you is a lawful basis, a privacy notice or a consent record, which is why companies handling personal data run a privacy programme alongside the security work rather than in place of it.

FAQs

Frequently asked questions about PCI DSS compliance

38 questions taken from real search queries, acquirer onboarding checklists, PCI Security Standards Council guidance and the way assessments actually run in India.

Account data
The umbrella term covering both cardholder data and sensitive authentication data. Anything that stores, processes or transmits it is inside the cardholder data environment by definition.
Primary Account Number
The payment card number, abbreviated PAN throughout the standard. It is unrelated to the Permanent Account Number issued by the Income Tax Department, and it may be stored only when rendered unreadable.
Sensitive authentication data
Full track data, the card verification value and the PIN or PIN block. It may be used to authorise a transaction and must never be retained afterwards, in any form, including encrypted.
Cardholder data environment
The people, processes and technologies that store, process or transmit account data, together with every system component connected to them or able to affect their security.
Qualified Security Assessor
A company qualified by the PCI Security Standards Council to perform onsite assessments and issue a Report on Compliance, independent of the entity it assesses.
Approved Scanning Vendor
A vendor approved by the Council to run external vulnerability scans against internet-facing systems. A passing scan is required at least every 90 days.
Attestation of Compliance
The signed declaration of validation status that accompanies a questionnaire or a Report on Compliance. It is the document an acquirer, aggregator or enterprise customer actually asks to see.
Compliance Accepting Entity
The acquirer or payment brand that receives and accepts your validation. Since the August 2026 revision to FAQ 1331, it is the party that confirms how certain requirements may be reported.
Network token
A network-issued substitute for the card number used in saved-card and recurring flows. It is not account data, which is why tokenisation removes systems from scope rather than merely protecting them.
FAQs

Frequently asked questions about PCI DSS compliance

38 questions taken from real search queries, acquirer onboarding checklists, PCI Security Standards Council guidance and the way assessments actually run in India.

FAQs

Frequently asked questions about PCI DSS compliance

38 questions taken from real search queries, acquirer onboarding checklists, PCI Security Standards Council guidance and the way assessments actually run in India.

PCI DSS is the Payment Card Industry Data Security Standard, a set of 12 requirements published by the PCI Security Standards Council that every organisation storing, processing or transmitting payment card data has to meet, enforced through the contract you signed with your acquiring bank rather than through any statute.
No. PCI DSS is a contractual standard, not legislation, and no Indian regulator issues a PCI DSS certificate. It reaches Indian businesses through two routes: the merchant agreement with your acquirer or payment aggregator, and the Reserve Bank of India (Regulation of Payment Aggregators) Directions, 2025, which require a payment aggregator to ensure its merchants meet standards like PCI DSS.
PCI DSS v4.0.1, published in June 2024. It became the only active version of the standard on 1 January 2025, when v4.0 was retired, and v3.2.1 had already been retired on 31 March 2024. Every assessment signed today is against v4.0.1, and the Council opened a request for comments on it in June 2026 to start shaping the next release.
The 51 requirements that v4.0 introduced as future-dated stopped being best practice and became testable. They include multi-factor authentication for all access into the cardholder data environment, 12 character passwords, payment page script management, tamper detection on payment pages, anti-phishing controls and the targeted risk analysis that a dozen of the others depend on.
Not in the way ISO 27001 is. There is no accreditation body issuing a PCI DSS certificate to a merchant. The outputs are an Attestation of Compliance signed by your company, backed either by a self-assessment questionnaire or by a Report on Compliance written by a Qualified Security Assessor, and filed with the acquirer or payment brand that asked for it.
No, and no consultant can sign your validation for you. Where a Qualified Security Assessor is required, that firm is independent and issues the Report on Compliance; where a self-assessment applies, your own officer signs the attestation. ProTax does the scoping, remediation, documentation and evidence work behind either route, and briefs the assessor when one is engaged.
A Qualified Security Assessor is a company qualified by the PCI Security Standards Council to perform onsite assessments and issue a Report on Compliance. You need one when your acquirer or payment brand places you at Level 1, when a service provider crosses the Level 1 threshold, and often after a breach. Everyone else validates by self-assessment.
An Approved Scanning Vendor runs external vulnerability scans against your internet-facing systems from outside your network. Requirement 11.3.2 calls for a passing scan at least every three months, plus a re-scan after any significant change. Only a vendor approved by the Council can produce the scan report your acquirer will accept.

Cut the scope first, then meet the standard

Our security compliance experts map every card data flow, define the cardholder data environment, remove what does not need to be in it, close the gaps against v4.0.1 and prepare the attestation your acquirer is waiting for.

FROM THE PROTAX LIBRARY

Recent Articles & Guides

Practical reading on business records, tax filings and the decisions that come with running a company.

Newsletter

Stay ahead on compliance, tax & business updates

Get selected business and compliance updates by email. Once a month, no spam.

  • 100% privacy
  • 1 email / month
  • Unsubscribe anytime
Contact ProTax
Chosen by individuals and businesses

Get Help With Your Business

Tell us what you need help with. Our team will review your enquiry and explain the next steps.

Free Consultation No Obligations Expert Advice
FREE Consultation Get Started @ ₹299 ₹0

Talk To ProTax

Share Your Business Requirement

Instant Response 100% Confidential Expert Advice
FREE Consultation Get Started @ ₹299 ₹0

Request a Free Quote

Share Your Business Requirement

Instant Response 100% Confidential Expert Advice
Find out how much of your stack is in scope 8 to 12 weeks Scope cut