Understanding PCI DSS Service Providers: A Plain-Language Guide for Merchants

If you accept credit cards, you probably work with outside vendors. Some process payments; others run your systems or offer advice. The PCI Council’s new supplement, “Understanding PCI DSS Service Providers,” helps you determine which vendors must be PCI-compliant, what proof to request, and how to avoid responsibility gaps. This guide breaks down the main points in plain English. No fluff. No legalese. Just what you need to know to keep your business and your customers safe.

What Does “Impact Security” Mean?

The supplement says a third-party service provider (TPSP) “impacts security” if it can access or affect your PCI DSS in-scope systems or networks. That means if a vendor connects to, manages, or supports anything inside your cardholder data environment, they fall into this group. It’s not just about who handles cardholder data. If a vendor’s services can reach into your systems, you need proof they’re PCI compliant. There’s a flowchart in the supplement to help you decide if a TPSP’s services require compliance evidence. The main thing to remember: if a vendor can touch or change your PCI systems, they’re in scope.

Table 4: Vendors That May Not Impact Your Environment—But Still Might Be in Scope

Table 4 in the supplement lists examples of TPSPs that usually don’t impact your environment. Think of payment processors who never touch your systems, consultants who only give advice, or companies that sell you hardware but don’t install or manage it. But here’s the catch: if a TPSP receives, stores, processes, or transmits account data for you, even if they never access your systems, they’re still in scope for PCI DSS. So, don’t let the “may not impact” label fool you. If a vendor handles account data, you should expect them to be PCI-compliant.

Acquiring Banks and When They Become TPSPs

Not every entity is a TPSP. Acquiring banks that only process transactions for you aren’t considered TPSPs. The same applies to payment brands and card schemes that don’t provide services that affect your environment. But if an acquirer offers extra services like managing your point-of-interaction (POI) devices, tokenizing card numbers, or updating account expiry dates, they become a TPSP for those services. In those cases, you need an Attestation of Compliance (AOC) from them. Some acquirers push back on this, but the supplement is clear: extra services mean extra compliance.

Nested TPSPs: Who Needs to Give You an AOC?

Sometimes your service provider uses another service provider. This is called “nesting.” The good news is you only need an AOC from the TPSPs you contract with directly. You don’t have to chase down paperwork from their vendors. For example, if you use a tokenization provider who hosts their solution on AWS, you only need the tokenization provider’s AOC, not AWS’s. Focus on your direct relationships.

SAQ Rule: Don’t Mix Your Assessment with Your TPSP’s

If you complete a PCI DSS Self-Assessment Questionnaire (SAQ), you can’t include your TPSP’s PCI assessment in your paperwork. Each TPSP must provide its own AOC. This rule keeps things clean. It means you can’t “borrow” a vendor’s compliance for your own SAQ. Every TPSP needs to stand on its own.

Shared Responsibility Matrix: Who Does What?

PCI DSS requirements are split between you and your TPSPs. The supplement recommends using a shared responsibility matrix. This simple chart spells out which PCI DSS requirements you handle, which your TPSP handles, and which are shared. Keeping this matrix up to date helps prevent gaps. If something changes, like adding a new service or your vendor taking on more responsibility, update the matrix. It’s your map for who does what.

AOC Redaction: What Must Always Be Visible

Vendors sometimes want to hide sensitive details in their AOC. That’s fine, but four sections must always be readable:

  • Scope of assessment
  • Covered services
  • Requirements that were assessed
  • Findings from the assessment

If any of these are missing or blacked out, ask for a better copy. You need these sections to know what was actually reviewed.

Conclusion

The PCI Council’s supplement gives merchants a clear way to handle third-party service providers. Focus on whether a vendor can access or affect your PCI systems. If they can, get proof of compliance. Use a shared responsibility matrix to keep roles straight. Remember, you only need AOCs from vendors you contract with directly. Stay organized, ask for the right paperwork, and you’ll keep your PCI DSS house in order.

This article is only a summary of the document; for complete information, read the full information supplement.


Discover more from The Digital Guardian

Subscribe to get the latest posts sent to your email.

Disclaimer
The views and opinions expressed in this article are solely my own and do not necessarily reflect the views, opinions, or policies of my current or any previous employer, organization, or any other entity I may be associated with.

Similar Posts