The short answer
The cheapest PCI DSS control is the one you don't need. Keep card numbers out of your systems with hosted payment fields or redirects, replace stored card numbers with tokens, use P2PE terminals in stores, and segment whatever card data remains. Each step removes systems from PCI DSS 4.0.1 scope, which lowers assessment cost and the damage of any breach.
What makes a system "in scope"
A system is in scope if it stores, processes or transmits cardholder data, or if it is connected to or can affect the security of those systems. In a flat network, that can mean almost everything: web servers, databases, admin laptops, logging tools and CI pipelines.
Scope reduction methods compared
| Method | What it removes from scope | Typical fit |
|---|---|---|
| Redirect or hosted fields (iframe) | Your web servers never receive card data | eCommerce, SaaS billing |
| Tokenization | Systems that only store tokens | Subscriptions, card-on-file |
| P2PE terminals | Store networks and POS software | Retail, hospitality |
| Network segmentation | Systems outside the cardholder data environment | Payment platforms, large merchants |
| Outsourcing to a PCI-compliant provider | Card handling, if responsibilities are clearly split | Most merchants |
The 2025 change to remember
Since 31 March 2025, PCI DSS 4.0's future-dated requirements are mandatory, including payment page script controls (6.4.3 and 11.6.1) and MFA into the cardholder data environment. Moving to hosted fields and simpler SAQs reduces how much of this applies to you.
How to reduce your PCI scope: 6 steps
1. Draw your card data flows
Map every path card data takes: web, mobile, phone, store, refunds, chargebacks and support. Include where staff might write card numbers down or paste them into tickets.
2. Remove card entry from your own pages
Use your payment provider's hosted fields, iframe or redirect so card numbers go straight to the provider. This can move you from SAQ A-EP or SAQ D towards SAQ A.
3. Tokenize stored cards
Replace stored card numbers with provider tokens. Delete legacy card data you don't need; search databases, logs and backups for stray card numbers.
4. Segment what's left
If you must handle card data, isolate the cardholder data environment with firewalls and strict access, and test segmentation with penetration testing.
5. Clarify responsibilities
Get your providers' attestation of compliance and a responsibility matrix showing which requirements they cover and which remain yours.
6. Validate and keep it small
Complete the right SAQ or a QSA assessment, then review data flows every time you add a payment method, app or vendor.
How Zuroth helps
- PCI DSS scoping and gap assessment against PCI DSS 4.0.1.
- Payment integration engineering: hosted fields, tokenization and secure APIs.
- Penetration testing from $499, including segmentation testing.
- Script monitoring for payment pages to meet 6.4.3 and 11.6.1.
Our retailer case study shows how a 1,100-store retailer met PCI DSS 4.0 and cut card-testing attempts by 97%.
Next step: read the PCI DSS 4.0 guide or book a free scoping call.
Related reading
- FinTech & Financial Services
- PCI DSS 4.0 guide
- DORA explained
- Penetration testing
- API development & integration
Frequently asked questions
What does PCI DSS scope mean?
PCI DSS scope is every system, person and process that stores, processes or transmits cardholder data, plus anything connected to or able to affect the security of those systems. Everything in scope must meet the relevant PCI DSS requirements, so smaller scope means fewer controls to run and assess.
Does tokenization remove systems from PCI scope?
Systems that only ever see tokens, never the real card number, and cannot reach the tokenization service to turn tokens back into card numbers, can usually be taken out of scope. The tokenization system itself, and anything that can detokenize, stays in scope.
What is the difference between SAQ A and SAQ A-EP?
SAQ A applies when all card data entry is fully outsourced, for example through a redirect or iframe hosted by a PCI-compliant provider. SAQ A-EP applies when your website controls the payment page that sends card data to the provider. SAQ A-EP has far more requirements.
Do payment page script rules apply if we use an iframe?
PCI DSS 4.0.1 kept requirements 6.4.3 and 11.6.1 for payment pages, but merchants eligible for SAQ A can meet the related eligibility criterion by confirming their site is not susceptible to script attacks or by using provider techniques. Check the current SAQ A and your provider's guidance.
Does network segmentation reduce PCI scope?
Yes. PCI DSS does not require segmentation, but properly isolating the cardholder data environment from other networks can take the rest of your systems out of scope. Segmentation controls must be tested by penetration testing, yearly for merchants and every six months for service providers.