Skip to content

PCI DSS Requirements for Merchants: A Complete Guide

Accepting card payments brings commercial opportunity, but it also places merchants within a framework of security obligations. The PCI DSS requirements for merchants govern how payment data is collected, transmitted, stored, and protected throughout the acquiring process.

Compliance depends on more than installing security tools. Merchants must determine their cardholder-data environment, address applicable controls, document validation, and coordinate responsibilities with acquirers and payment service providers. Recognizing these obligations is essential to reducing fraud risk and maintaining reliable payment acceptance.

What PCI DSS Requires from Merchants in Card Payment Acceptance

PCI DSS requires merchants that store, process, or transmit payment card data to protect that data throughout the payment lifecycle. The obligations apply whether transactions occur in physical stores, online, through mobile applications, or by mail and telephone order.

Merchants must establish controls covering secure systems, access management, vulnerability protection, monitoring, testing, and incident response. They must also restrict access to cardholder data based on business need and prevent the storage of sensitive authentication data after authorization, where prohibited by the standard.

The specific validation method depends on factors such as transaction volume, payment channels, and the acquiring bank’s requirements. Merchants may need to complete a Self-Assessment Questionnaire, submit an Attestation of Compliance, or undergo a formal assessment by a Qualified Security Assessor.

The PCI DSS requirements for merchants also extend to outsourced payment arrangements. Using a payment service provider may reduce the systems within scope, but the merchant remains responsible for selecting compliant providers, understanding shared responsibilities, and maintaining appropriate oversight.

Determining a Merchant’s PCI DSS Scope

A merchant’s PCI DSS scope includes every system, process, person, and payment channel that stores, processes, transmits, or can affect the security of cardholder data. The assessment should cover in-store terminals, e-commerce platforms, mobile payments, call centres, networks, and connected administrative systems.

Merchants must identify cardholder data, such as the primary account number, and distinguish it from sensitive authentication data, including full track data, card verification codes, and PIN information. Sensitive authentication data generally must not be stored after authorization, even when encrypted.

Scope also depends on technology relationships and access. A hosted payment page or payment service provider may reduce the merchant’s environment, but it does not automatically remove responsibilities. Any systems that redirect, connect to, or influence payment security may remain in scope.

Merchants should document data flows and confirm boundaries with their acquirer, qualified security assessor, or payment service provider. Under the PCI DSS requirements for merchants, scope decisions must be supported by evidence rather than based solely on assumptions about outsourcing.

Identifying Cardholder Data and Sensitive Authentication Data

Merchants must identify all cardholder data (CHD) they store, process, or transmit. This includes the primary account number (PAN), cardholder name, expiration date, and service code. The PAN is the defining element; other data becomes cardholder data when stored or transmitted with it.

Sensitive authentication data (SAD) includes full track data, card verification codes or values, and personal identification numbers (PINs) or PIN blocks. PCI DSS generally prohibits retaining SAD after authorization, even when encrypted, so merchants should verify whether payment systems collect or retain it.

See also  Multi-Currency Merchant Accounts: A Guide for Global Banking

The review should cover payment terminals, e-commerce platforms, mobile applications, call-centre processes, receipts, databases, logs, backups, and paper records. Data-flow mapping can reveal unexpected storage or transmission points and establish the boundaries of PCI DSS requirements for merchants.

Merchants should distinguish payment data handled directly from data processed by an acquirer or payment service provider. Outsourcing may reduce the merchant’s exposure, but it does not remove responsibility for confirming what data enters merchant systems and how providers protect it.

Assessing In-Scope Systems, People, and Payment Channels

Merchants must map every environment involved in payment processing, including point-of-sale terminals, e-commerce platforms, mobile applications, databases, networks, and administrative systems. Systems that store, process, or transmit cardholder data are generally within PCI DSS scope.

The assessment should also include people with access to payment environments or cardholder data. This may cover employees, contractors, support personnel, and third-party administrators. Access privileges, responsibilities, remote connections, and security procedures should be documented and reviewed.

Each payment channel requires separate consideration. Card-present transactions, card-not-present orders, telephone payments, recurring billing, and mobile transactions may use different technologies and controls. The merchant should document how card data enters, moves through, and leaves each channel.

Network diagrams, data-flow diagrams, asset inventories, and payment-process records help establish the scope accurately. For merchants evaluating PCI DSS requirements for merchants, overlooked systems or personnel can result in incomplete assessments and compliance gaps.

Using Payment Service Providers to Reduce, Not Eliminate, Scope

A payment service provider (PSP) can reduce PCI DSS scope by handling card data through hosted checkout pages, tokenization, or validated payment applications. When merchants do not store, process, or transmit cardholder data directly, fewer internal systems and processes may fall within the assessment.

Scope is not eliminated, however. Merchant websites, networks, devices, and personnel connected to the payment process may still affect transaction security. For example, a compromised website could redirect customers to a fraudulent payment page, even when the PSP processes the card details.

Under the PCI DSS requirements for merchants, the merchant must confirm that the PSP is appropriately compliant and that its services operate as described. The merchant should review the provider’s Attestation of Compliance, maintain required agreements, and document the payment-flow design.

Merchants also remain responsible for securing their own systems, restricting administrative access, managing vulnerabilities, and protecting payment-page integrity. Eligibility for a particular Self-Assessment Questionnaire depends on the actual implementation and the acquiring institution’s requirements.

The 12 PCI DSS Requirements Merchants Must Address

PCI DSS requirements for merchants are organized into 12 controls covering the full card-payment environment. They address network security, secure configuration, protection against malware, vulnerability management, access control, authentication, and physical security.

The framework also requires merchants to monitor access, test security systems regularly, and maintain information-security policies. Requirements for logging, detecting suspicious activity, and responding to incidents help support ongoing oversight rather than one-time compliance.

Merchants must protect stored account data and encrypt cardholder data during transmission across public networks. They must also avoid retaining sensitive authentication data after authorization, except where PCI DSS explicitly permits limited handling.

The applicable controls depend on the merchant’s payment channels, technologies, and relationships with service providers. Validation activities, such as completing the appropriate Self-Assessment Questionnaire or undergoing a Report on Compliance, provide evidence that these requirements are being addressed.

Protecting Cardholder Data Across Merchant Payment Channels

Merchants must protect cardholder data consistently across in-store, e-commerce, mail-order, telephone-order, and mobile payment channels. Controls should cover payment applications, point-of-sale devices, networks, administrative access, and any systems that store, process, or transmit account data.

See also  Card Payment Acceptance: A Guide for Modern Banking Businesses

Cardholder data should be collected only when necessary, transmitted through strong cryptographic protocols, and stored securely when retention is permitted. Sensitive authentication data, such as full track data, security codes, and PIN data, must not be retained after authorization, even if encrypted.

In card-present environments, merchants should secure terminals against tampering, restrict physical access, and inspect devices for unauthorized modifications. Online merchants should protect checkout pages, payment integrations, and administrative accounts against unauthorized changes and malicious scripts.

Tokenization or hosted payment pages can reduce exposure by keeping payment data outside merchant systems, but they do not remove all PCI DSS requirements for merchants. Merchants remain responsible for secure configurations, access controls, employee practices, incident response, and verifying that payment providers operate as represented.

Merchant Responsibilities When Working with Acquirers and Service Providers

Merchants remain responsible for understanding how acquirers, payment processors, gateways, and other service providers handle cardholder data. Outsourcing payment functions may reduce PCI DSS scope, but it does not transfer the merchant’s accountability for selecting, overseeing, and using compliant providers.

Merchants should establish written agreements that define security responsibilities, breach-notification procedures, data handling requirements, and compliance evidence. Agreements should identify which party manages each relevant PCI DSS control and specify how responsibilities are reviewed when payment processes change.

Practical oversight should include:

  • Confirming providers appear on applicable PCI SSC lists or supply current compliance documentation.
  • Reviewing relevant Attestations of Compliance and service descriptions.
  • Restricting provider access to necessary systems and data.
  • Maintaining records of due diligence and periodic reviews.

Acquirers may set additional validation or reporting requirements under their programs. Merchants should therefore coordinate with the acquiring bank, respond to requests for evidence, and monitor providers throughout the relationship rather than relying solely on a contract signed at onboarding.

Shared PCI DSS Responsibilities

PCI DSS responsibilities are divided among the merchant, acquiring bank, payment processor, and other service providers according to the services each party provides. The merchant remains accountable for securing its own systems, payment processes, employees, and cardholder data, even when transaction processing is outsourced.

An acquirer or processor may operate payment infrastructure, apply security controls, monitor transactions, or support compliance reporting. These activities do not automatically transfer the merchant’s obligations. The merchant must understand which PCI DSS requirements each provider covers and which controls remain within its environment.

Responsibility boundaries should be documented through contracts, service descriptions, and compliance evidence. Agreements should identify applicable controls, incident-notification duties, data-handling practices, and the provider’s PCI DSS validation status.

For merchants, this documented allocation supports accurate scoping and prevents gaps caused by assuming another party is responsible. The PCI DSS requirements for merchants still apply to all payment channels and systems under the merchant’s control.

Written Agreements and Compliance Evidence

Written agreements should clearly define each party’s PCI DSS responsibilities, including requirements for payment processing, security controls, incident reporting, and compliance validation. A merchant should understand which activities remain under its control and which are performed by the acquirer or service provider.

Agreements should also specify the evidence each party must provide, such as:

  • Current Attestation of Compliance (AOC)
  • Relevant Report on Compliance (ROC) or Self-Assessment Questionnaire (SAQ)
  • Documentation of applicable service-provider responsibilities
  • Notice of changes affecting payment security or PCI DSS scope

A merchant should retain these records with contracts, service descriptions, and correspondence concerning compliance. The documents should identify the service provider’s role accurately; an AOC does not transfer the merchant’s own obligations or prove that every merchant process is compliant.

See also  Merchant Onboarding Process: A Guide for Banks and Fintechs

Acquirers may impose validation requirements beyond the PCI DSS baseline, so merchants should confirm submission deadlines, approved assessment methods, and evidence formats in writing. Maintaining an evidence register helps support audits, demonstrate oversight, and manage the PCI DSS requirements for merchants throughout the business relationship.

Monitoring Third-Party Service Provider Compliance

Merchants should maintain an up-to-date register of third-party service providers that store, process, or transmit cardholder data, or could affect the security of the cardholder data environment. The register should identify each provider’s services, responsibilities, and PCI DSS status.

Compliance monitoring should be documented through a risk-based process that may include:

  • Reviewing the provider’s current Attestation of Compliance (AOC)
  • Confirming the scope and services covered by its validation
  • Checking relevant contractual security obligations
  • Recording remediation actions and review dates

A provider’s PCI DSS validation does not transfer the merchant’s responsibilities. Merchants must verify that the provider’s documented scope matches the services being used and that required security controls remain effective throughout the relationship. An expired or incomplete AOC should trigger follow-up with the provider.

Monitoring should also account for material changes, such as new payment channels, subcontractors, data flows, or security incidents. These changes may affect the merchant’s PCI DSS requirements for merchants and should be assessed promptly with the acquirer or qualified security personnel where appropriate.

PCI DSS Validation: SAQs, ROC, and AOC

Merchants demonstrate compliance through documentation determined by their transaction volume, payment channels, and acquirer requirements. The applicable validation method may include:

  • Self-Assessment Questionnaire (SAQ)
  • Report on Compliance (ROC)
  • Attestation of Compliance (AOC)

An SAQ is a structured questionnaire that allows eligible merchants to assess their controls against relevant PCI DSS requirements. The correct SAQ depends on how payment data is captured, transmitted, processed, and stored. Merchants should confirm eligibility with their acquiring bank or payment brand.

A ROC is a detailed assessment report prepared by a Qualified Security Assessor or, where permitted, an Internal Security Assessor. It documents testing procedures, findings, and evidence supporting compliance. Large or higher-risk merchants commonly require this level of validation.

The AOC formally records the merchant’s compliance status and identifies the assessment method used. Acquirers may request an SAQ, ROC, AOC, or supporting evidence. Completing these documents does not replace ongoing controls required under PCI DSS requirements for merchants.

Common PCI DSS Compliance Gaps for Merchants

Merchants often underestimate their PCI DSS scope, excluding systems, staff, or payment channels that can affect cardholder data security. Misclassified e-commerce platforms, point-of-sale devices, call-centre processes, and remote-access tools can create undocumented compliance exposure.

Weak access controls are another frequent gap. Shared accounts, excessive privileges, unchanged default passwords, and insufficient multi-factor authentication may allow unauthorised access to payment environments. Inadequate logging, alert monitoring, and delayed vulnerability remediation can also leave suspicious activity undetected.

Some merchants retain cardholder data unnecessarily or store it without appropriate encryption, masking, or retention controls. Paper records, email messages, payment terminals, and backup systems are often overlooked during data-flow reviews. Sensitive authentication data must not be stored after authorisation, even when encrypted.

Incomplete vendor oversight can undermine PCI DSS requirements for merchants. Missing written responsibilities, expired compliance evidence, and unmonitored payment service providers may create accountability gaps. Staff training, incident-response testing, and recurring security assessments are also commonly treated as one-time tasks rather than ongoing controls.

Maintaining Continuous PCI DSS Compliance in Merchant Operations

Continuous PCI DSS compliance requires merchants to integrate security controls into daily operations rather than treating compliance as an annual exercise. They should review payment processes, system changes, access permissions, and cardholder-data flows whenever business operations or technologies change.

Routine activities should include vulnerability scanning, timely patching, malware protection, log review, and monitoring for unauthorised access. Employees and contractors with relevant responsibilities should receive security training, while access rights should be removed or adjusted promptly when roles change.

Merchants should maintain evidence of policies, technical tests, training, incident-response exercises, and service-provider reviews. Documented procedures make it easier to demonstrate that PCI DSS requirements for merchants remain active and consistently applied.

Incident-response plans should be tested and updated based on operational lessons. Changes involving payment applications, terminals, e-commerce platforms, or acquiring partners should trigger a review of PCI DSS scope and validation obligations.