PCI DSS Vendor Compliance: Third-Party Requirements Guide

Understand PCI DSS requirements for third-party service providers and learn how to build a compliant vendor management program.

On this page

What is PCI DSS?

The Payment Card Industry Data Security Standard (PCI DSS) is a set of security standards designed to ensure that all companies that accept, process, store, or transmit credit card information maintain a secure environment. It was developed by the Payment Card Industry Security Standards Council (PCI SSC), founded by major card brands including Visa, Mastercard, American Express, Discover, and JCB.

PCI DSS compliance is mandatory for any organization handling cardholder data. Critically, it also requires organizations to ensure their third-party service providers are compliant, making vendor due diligence a core PCI DSS requirement.

PCI DSS 4.0 Now Effective

PCI DSS v4.0 became mandatory in March 2024, with additional requirements phased in through 2025. The new version strengthens third-party risk management requirements, including more prescriptive due diligence and ongoing monitoring obligations.

Service Provider Requirements

Requirements 12.8 and 12.9 specifically address service provider (vendor) management:

Requirement 12.8

Service Provider Management

Maintain policies and procedures to manage service providers with whom cardholder data is shared or that could affect security.

  • Maintain a list of all service providers
  • Maintain written agreements with acknowledgment of responsibilities
  • Establish a process for engaging service providers including due diligence
  • Monitor service providers' PCI DSS compliance status annually

Requirement 12.9

Service Provider Acknowledgment

Service providers must acknowledge their responsibility for cardholder data security.

  • Written acknowledgment from service provider
  • Clearly documented responsibilities for PCI DSS requirements
  • Defined security obligations in contracts

Vendor Categorization

Not all vendors require the same level of PCI DSS due diligence. Categorize vendors based on their access to cardholder data:

CategoryExamplesPCI DSS Requirement
Direct Card Data AccessPayment processors, acquiring banks, payment gateways, POS providersRequired - Must be PCI DSS compliant
Indirect Access (Could Impact Security)Hosting providers, managed security services, IT supportRequired for relevant systems and services
No Card Data AccessMarketing agencies, office supplies, unrelated SaaSNot required but may need general security review

Vendor Due Diligence Process

Follow this process for vendors that handle or could impact cardholder data:

1

Identify Cardholder Data Touchpoints

Map where the vendor will interact with cardholder data or systems that process, store, or transmit card data.

2

Request PCI DSS Compliance Documentation

Obtain the vendor's Attestation of Compliance (AOC) or Self-Assessment Questionnaire (SAQ) appropriate to their service type.

3

Verify Compliance Scope

Ensure the vendor's PCI DSS scope covers the specific services you'll be using. Scope limitations in their AOC may exclude your use case.

4

Document Responsibility Matrix

Create a clear matrix showing which PCI DSS requirements are the vendor's responsibility and which remain yours.

5

Establish Contractual Requirements

Include PCI DSS compliance obligations, breach notification requirements, and audit rights in vendor agreements.

6

Implement Ongoing Monitoring

Establish annual compliance verification process and mechanisms to be notified of compliance status changes.

Responsibility Matrix

A responsibility matrix clarifies which PCI DSS requirements are your responsibility vs. the service provider's. This is especially important for cloud and managed services:

Shared Responsibility Warning

Many PCI DSS requirements involve shared responsibility between you and service providers. For example, a cloud provider may manage physical security while you're responsible for data encryption and access controls. Document these clearly and verify both parties are meeting their obligations.

Documentation Requirements

  • Maintain a current list of all service providers with access to cardholder data
  • Document which PCI DSS requirements apply to each service provider
  • Keep copies of service provider AOCs and/or SAQs
  • Retain signed agreements with PCI DSS acknowledgments
  • Document the annual compliance verification process and results
  • Maintain evidence of due diligence performed before engagement

Frequently Asked Questions

What is an Attestation of Compliance (AOC)?

An AOC is a formal document signed by a Qualified Security Assessor (QSA) or the organization itself (for self-assessment) attesting to PCI DSS compliance. It confirms the assessment was completed and details the scope, compliance status, and any noted exceptions. Request the AOC rather than just accepting a vendor's claim of compliance.

What SAQ type should my vendor have?

SAQ type depends on how the vendor handles card data. SAQ A is for e-commerce merchants using only iframe/redirect solutions. SAQ A-EP is for e-commerce merchants with payment pages. SAQ D is the most comprehensive, for vendors that store, process, or transmit cardholder data. Ensure the SAQ type matches the services they provide to you.

Are we responsible for our vendor's PCI DSS compliance?

You're responsible for ensuring your vendors are compliant with PCI DSS requirements relevant to the services they provide. You must perform due diligence, maintain written agreements, and monitor their compliance status annually. A vendor breach can still result in liability for your organization.

How often should vendor PCI compliance be verified?

At minimum, verify vendor PCI DSS compliance annually. Best practice is to also verify when: renewing contracts, changing service scope, after any security incident, when notified of compliance status changes, or when the vendor undergoes significant changes (ownership, infrastructure).

What if a vendor is not PCI DSS compliant?

If a vendor handling cardholder data is not PCI DSS compliant, you have several options: require them to achieve compliance within a defined timeline, implement compensating controls to protect data, limit their access to non-card systems, or find an alternative compliant vendor. Continuing to use a non-compliant vendor for card data services puts your own compliance at risk.

Conclusion

PCI DSS compliance extends beyond your own systems to include every service provider that handles or could impact cardholder data. A robust vendor management program, with clear due diligence processes, documented responsibilities, and ongoing monitoring, is essential for maintaining compliance and protecting payment data.

Remember that your organization remains responsible for ensuring vendor compliance. Build strong processes, document everything, and verify compliance annually to avoid gaps that could lead to data breaches or compliance failures.

Check the vendor. Keep the evidence.

Start free