Before you can answer any PCI question, you need to know which role you play. Get it wrong and you end up filling in the wrong questionnaire, or leaving a customer exposed without realizing it. This is general information, not advice for your situation.
Use the current version
PCI DSS v4.0.1, published as a limited revision in June 2024, is the version to work from. It added and removed no requirements, and v4.0 was retired on 31 December 2024. The newer requirements that had been marked as future-dated became mandatory on 31 March 2025. If a guide you are reading talks about the “new” requirements as upcoming, it predates all of this.
Two questions that settle most cases
Do you take cards in exchange for what you sell? If you hold a merchant account with an acquiring bank and accept payment cards for goods or services, you are a merchant. Size does not matter. A corner shop and a hospital group are both merchants.
Do you touch other people’s card data, or their ability to protect it? The PCI glossary describes a service provider as a business that is not a payment brand but is directly involved in processing, storing or transmitting cardholder data for another entity, or that can affect the security of that data. A payment gateway is the obvious example. A managed firewall provider, a hosting company or a remote-support vendor fits too, even if no card number ever crosses their own servers.
If both answers are yes, you are both. A web host that also bills its own customers by card is a service provider for the hosting and a merchant for the billing. Treat the two roles as separate assessments.
Why the role matters
- The questionnaires and attestation forms differ for each role. Handing a customer the merchant version when they need the service provider version is a common and avoidable mistake.
- A service provider is judged on the services it delivers to others, so the scope is defined service by service.
- Customers will rely on your paperwork when they assess their own scope. If it is vague, their assessment gets harder.
Where organizations go wrong
- Treating it as either/or. Decide for each service you offer and each way you take payments.
- Forgetting outsourced pieces. A call center that takes card details by phone for you, or a payment page hosted by someone else, still shapes your scope.
- Trusting a badge. The useful document is the Attestation of Compliance, and for a service provider it should name the services that were assessed. A service that is not listed is probably not covered.
- Leaving it out of the contract. If you depend on a provider to meet PCI requirements, put that in writing and ask for their current attestation every year.
Ask your providers
1. Which of your services were in your last assessment?
2. Can I see your current Attestation of Compliance, service provider version?
3. Which requirements do you handle for us, and which stay with us?
4. How will you tell us if your status or scope changes?
Reporting rules for service providers, including when a full Report on Compliance is expected, are set by the card brands and acquirers and can change. Check the current position with your acquirer instead of relying on a figure from an old article.
See how we help with incident response and security services.
Sources
- PCI SSC blog: Just Published, PCI DSS v4.0.1
- PCI SSC blog: Just Published, PCI DSS v4.0.1
- PCI SSC blog: Just Published, PCI DSS v4.0.1
Related
Discover more from Core-Infosec
Subscribe to get the latest posts sent to your email.