PCI DSS is intended for any organization that stores, processes, or transmits account data, or that could affect its security. That covers merchants, processors, acquirers, issuers, and other service providers. Payment brands and acquirers decide who must formally validate compliance, and how.
A quick self-check
Start with how your business relates to card data. PCI DSS is likely relevant if you can answer yes to any of these questions:
- Does your business accept payment cards for goods or services?
- Do your systems store, process, or transmit account data, even briefly?
- Do you handle account data on behalf of another business?
- Could your services affect the security of someone else’s account data, such as by hosting or managing their systems?
- Do you keep card data on paper, such as forms or printed reports?
Answering yes doesn’t mean every requirement applies. The applicable requirements depend on your environment. Your acquirer or a payment brand can confirm any added criteria for your business.
Merchants
PCI DSS defines a merchant as any entity that accepts cards bearing a participating payment brand’s logo for goods or services. The definition has no size threshold. A business that takes a handful of card payments is still a merchant.
One company can hold both roles. PCI DSS gives the example of an internet service provider that accepts cards for monthly billing. It’s also a service provider if it hosts merchants as customers.
Service providers
A service provider is a non-brand business directly involved in processing, storing, or transmitting account data for another entity. Payment gateways, payment service providers, and independent sales organizations all fit. So do companies whose services control or could affect that data’s security, such as managed firewall and hosting providers.
A company offering only public network access, such as a telecommunications link, isn’t a service provider for that service. Payment software vendors may be service providers if they handle account data or can access their customers’ account data. Software as a service and cloud payment offerings can fall into this group.
Service providers have some additional obligations. For example, Requirement 12.5.2.1 calls for confirming scope at least once every six months. Requirement 12.9.2 calls for giving customers compliance status and responsibility information on request.
Service providers can validate for customers in two ways. They can complete an annual assessment and share evidence, or they can undergo assessments on request or join each customer’s assessment.
If you outsource payments
Outsourcing can shrink your compliance work, but some of it remains. A business that uses a third-party service provider stays responsible for confirming its own compliance when compliance programs ask. Requirement 12.8 applies, covering provider due diligence, written agreements, and monitoring.
Other situations can trigger specific requirements even without PAN on your systems:
- Your website controls a payment form or page: Some requirements apply because your infrastructure can affect how cardholder data is processed.
- Card data exists only on paper: Requirement 9 applies to the security and disposal of physical media.
- You have any PCI DSS role: Incident response plan requirements apply to all entities.
Merchant levels vary by payment brand
Many people assume that one universal table of merchant levels exists. Each payment brand independently defines its own merchant and service provider levels, along with who must validate. Those decisions can shape how you validate, such as through a self-assessment or a Report on Compliance.
If you are a merchant, your acquirer is a good first contact. Ask which level applies to you and what they expect you to submit. If you accept several card brands, check whether different programs affect your obligations.
Find your SAQ starting point
A Self-Assessment Questionnaire (SAQ) is a reporting tool for documenting self-assessment results. Several versions exist because payment setups differ. This table suggests where to start, based on how you accept cards.
| If you are or use… | Likely starting point | Why |
|---|---|---|
| Service provider handling account data for others | SAQ D for Service Providers | Only for service providers a payment brand defines as eligible. Others report through a ROC, so confirm with the payment brand or your acquirer. |
| Merchant that stores account data electronically | SAQ D for Merchants | The other merchant SAQs exclude electronic storage of account data. SAQ D covers all applicable requirements. |
| E-commerce: site redirects to, or embeds, a provider page or iframe | SAQ A | For merchants that fully outsource all account data functions, where every element of the payment page comes only and directly from a compliant provider. SAQ A also has an eligibility criterion about script attacks, so check it closely. |
| E-commerce: your site hosts the form, but the browser sends card data directly to the provider | SAQ A-EP | Your website doesn’t receive account data but controls how it reaches the provider, so it can affect the security of the transaction. |
| E-commerce: card data reaches your server, and you pass it on | SAQ D for Merchants | Merchants that accept account data on their website don’t meet the SAQ A or SAQ A-EP criteria. |
| Mail or phone orders, fully outsourced to a provider | SAQ A | For card-not-present merchants that fully outsource all account data functions to PCI DSS compliant providers. |
| Terminal on the PCI-listed validated P2PE list | SAQ P2PE | All payment processing runs through a validated, PCI-listed P2PE solution. Phone or mail orders may qualify when keyed directly and only into those terminals. |
| Phone or tablet with a PCI-listed SPoC solution (in person only) | SAQ SPoC | Card-present only, using a validated software-based PIN entry solution with a secure card reader. Excludes phone and mail orders, e-commerce, and unattended payments. |
| Standalone, PCI-listed terminal with its own IP connection | SAQ B-IP | Only standalone, PCI-listed PTS devices with their own IP connection to the processor, not connected to other merchant systems. Card readers that pair with a phone or computer don’t qualify. |
| Imprint machines or a dial-out terminal | SAQ B | Only imprint machines or standalone dial-out terminals, with no electronic storage. |
| Typing cards into a provider website (virtual terminal) on an isolated computer | SAQ C-VT | Only keying single transactions into a third-party virtual terminal on an isolated computing device, with no attached card readers. |
| Payment application on an internet-connected system | SAQ C | A single location with payment application systems connected to the internet, isolated from other merchant systems, and no electronic account data storage. If locations connect to each other, SAQ D may apply. |
| Integrated or networked terminals, or not sure | SAQ C or SAQ D | Ask your acquirer which applies. |
| More than one of these channels | Ask your acquirer | Many SAQs require that channel to be your only one. SAQ D applies if you meet no other SAQ criteria. |
This is a starting point only. Each SAQ has its own eligibility criteria, and your acquirer or payment brand has the final say on how you validate.
Treat it as a first look. Each SAQ has its own eligibility criteria that you should confirm. For example, SAQ A covers card-not-present merchants that fully outsource account data functions, and it doesn’t apply to face-to-face channels. SAQ D for Service Providers applies to providers that a payment brand defines as eligible for self-assessment.
Situations that often cause doubt
These cases come up often when businesses try to decide whether they are in scope.
Encrypted card data
Encryption is an accepted way to make stored cardholder data unreadable, but it generally doesn’t take that data out of scope. Systems performing encryption, decryption, or key management remain in scope. A provider that only holds customer-encrypted data and can’t decrypt it may be able to exclude that data if certain conditions are met.
Telephone and VoIP payments
Mail and telephone orders are card-not-present channels that need evaluation under PCI DSS. VoIP network devices appear among the system components the standard lists. Review them if they carry account data or could affect its security.
Payment terminals with P2PE
A PCI-listed point-to-point encryption solution can significantly reduce the requirements that apply to a merchant. It doesn’t remove PCI DSS from the merchant environment entirely.
Where to go from here
If PCI DSS applies to you, learn how the process works from scope through reporting. You can also check how requirements differ by segment or review warning signs worth a closer look.
Frequently asked questions
Work with RSI Security
RSI Security is a PCI Qualified Security Assessor (QSA) company and an Approved Scanning Vendor (ASV). It performs PCI DSS assessments and quarterly ASV scans. Organizations that need help with scoping or readiness can work with RSI Security through a separate advisory engagement. RSI Security provides either advisory or assessment to a given client, never both.
Schedule a PCI DSS assessment · Talk to an advisor about readiness
Sources
- PCI DSS v4.0.1 (Section 2, PCI DSS Applicability Information)
- PCI DSS v4.0.1 (Section 3, Applicability of PCI DSS to Payment Software Vendors)
- PCI DSS v4.0.1 (Section 4, Scope of PCI DSS Requirements, Encrypted Cardholder Data, and Use of Third-Party Service Providers)
- PCI DSS v4.0.1 (Appendix G, Glossary, definitions of Merchant and Service Provider)
- PCI DSS v4.0.1 (Requirements 1.2.3, 1.2.4, 12.5.2.1, 12.8, and 12.9.2)
- PCI DSS v4.0.1 SAQ A r1 (Completing the SAQ, eligibility criteria)
- PCI DSS v4.0.1 SAQ D for Service Providers r2 (Completing the SAQ, applicability statement)
- PCI QSA Program Guide v4.1 (Section 2.1, Participating Payment Brands)
