Blog News Contact Get a proposal

PCI DSS v4.0.1 Compliance Checklist for Merchants and SaaS

Choose how you accept cards to get a preliminary SAQ type, then answer up to 44 questions on the 12 PCI DSS v4.0.1 requirements. See your readiness by requirement, the top 5 gaps and a 3-step roadmap, and get the full report as a PDF.

Runs in your browser, nothing is sent until you ask for the PDFFreeNo signup
How do you accept cards? Preliminary SAQ type

Requirements outside the selected SAQ are set to N/A. This is a preliminary choice: confirm the SAQ type with your acquirer or a QSA. You can change any answer.

Req. 1 · Network security controls

PCI DSS v4.0.1 Requirement 1

  1. Are firewall and other network security control rules documented and reviewed at least every 6 months?

    1.2.1, 1.2.7 · medium impact
  2. Do you keep a current network diagram and a data-flow diagram of card data?

    1.2.3, 1.2.4 · medium impact
  3. Is traffic into and out of the card data environment limited to what is necessary, with no direct public access?

    1.3.1, 1.3.2, 1.4.1 · high impact
Req. 2 · Secure configurations

PCI DSS v4.0.1 Requirement 2

  1. Are vendor default passwords and accounts changed or disabled on every system?

    2.2.2 · high impact
  2. Are hardening standards applied to all system components (for example CIS Benchmarks)?

    2.2.1 · medium impact
  3. Are unnecessary services disabled and is all admin access encrypted (SSH, TLS, VPN)?

    2.2.4, 2.2.7 · lower impact
Req. 3 · Protect stored account data

PCI DSS v4.0.1 Requirement 3

  1. Do you keep account data only as long as needed and securely delete it on a schedule?

    3.2.1 · medium impact
  2. Is sensitive authentication data (CVV, full track data, PIN) never stored after authorization?

    3.3.1 · high impact
  3. Is the card number (PAN) masked when displayed, showing no more than the BIN and the last 4 digits?

    3.4.1 · medium impact
  4. Is stored PAN unreadable everywhere: strong encryption, tokenization or truncation?

    3.5.1 · high impact
  5. Are encryption keys protected, with documented generation, rotation and limited custodians?

    3.6.1, 3.7.1 · medium impact
Req. 4 · Encrypt cardholder data in transit

PCI DSS v4.0.1 Requirement 4

  1. Is card data protected with strong cryptography (TLS 1.2 or higher, valid certificates) over public networks?

    4.2.1 · high impact
  2. Is PAN blocked or protected with strong cryptography whenever it is sent through email, chat or other end-user messaging?

    4.2.2 · medium impact
Req. 5 · Protection from malware

PCI DSS v4.0.1 Requirement 5

  1. Is anti-malware deployed and kept up to date on systems at risk, with periodic scans?

    5.2.1, 5.3.1, 5.3.2 · medium impact
  2. Do you have controls that detect and block phishing (email filtering, DMARC)?

    5.4.1 · medium impact
Req. 6 · Secure systems and software

PCI DSS v4.0.1 Requirement 6

  1. Do you track new security vulnerabilities and rank them by risk?

    6.3.1 · medium impact
  2. Are critical and high security patches installed within one month of release?

    6.3.3 · high impact
  3. Is software developed securely: secure coding training, code review before release, protection against common attacks?

    6.2.1–6.2.4 · medium impact
  4. Are public-facing web applications protected by a WAF or a similar automated solution?

    6.4.2 · high impact
  5. Is every script on the payment page inventoried, authorized and checked for integrity?

    6.4.3 · high impact
  6. Are changes to production tested and approved, with separate test and production environments?

    6.5.1–6.5.6 · medium impact
Req. 7 · Access by business need to know

PCI DSS v4.0.1 Requirement 7

  1. Is access to card data and systems limited to the least privileges each role needs?

    7.2.1, 7.2.2 · high impact
  2. Are user accounts and their access rights reviewed at least every 6 months?

    7.2.4 · medium impact
Req. 8 · User identification and authentication

PCI DSS v4.0.1 Requirement 8

  1. Does every user have a unique ID, with no shared or generic accounts?

    8.2.1, 8.2.2 · high impact
  2. Is access revoked immediately when someone leaves the company?

    8.2.5 · medium impact
  3. Are passwords at least 12 characters, with lockout after no more than 10 failed attempts?

    8.3.4, 8.3.6 · medium impact
  4. Is MFA required for all administrative access and all access into the card data environment?

    8.4.1, 8.4.2 · high impact
  5. Is MFA required for all remote network access (VPN, remote desktop)?

    8.4.3 · high impact
Req. 9 · Physical access and media

PCI DSS v4.0.1 Requirement 9

  1. Is physical access to rooms with systems that store or process card data controlled and logged?

    9.2.1 · medium impact
  2. Are paper and electronic media with card data secured, inventoried and destroyed when no longer needed?

    9.4.1–9.4.7 · medium impact
  3. Are card-reading devices (POI) inventoried and inspected for tampering, with staff trained?

    9.5.1 · medium impact
Req. 10 · Logging and monitoring

PCI DSS v4.0.1 Requirement 10

  1. Are audit logs enabled for all access to card data and all administrative actions?

    10.2.1 · high impact
  2. Are security logs reviewed every day, with automated alerting?

    10.4.1, 10.4.1.1 · medium impact
  3. Are logs kept for at least 12 months, with the last 3 months immediately available?

    10.5.1 · medium impact
Req. 11 · Regular security testing

PCI DSS v4.0.1 Requirement 11

  1. Do you pass external vulnerability scans by an ASV every quarter and after significant changes?

    11.3.2 · high impact
  2. Do you run internal vulnerability scans every quarter, using authenticated scanning?

    11.3.1, 11.3.1.2 · medium impact
  3. Is a penetration test done every year and after significant changes, including segmentation tests?

    11.4.1–11.4.5 · high impact
  4. Do you detect unauthorized changes to the payment page and its HTTP headers?

    11.6.1 · high impact
  5. Is intrusion detection or prevention in place to monitor traffic in the card data environment?

    11.5.1 · medium impact
Req. 12 · Security policies and programs

PCI DSS v4.0.1 Requirement 12

  1. Is there an information security policy, reviewed every year, with assigned security roles?

    12.1.1–12.1.3 · medium impact
  2. Do you confirm your PCI DSS scope and run targeted risk analyses at least every year?

    12.3.1, 12.5.2 · medium impact
  3. Does staff take security awareness training when hired and every year, including phishing?

    12.6.1–12.6.3 · medium impact
  4. Do you keep a list of payment and service providers, with written agreements and their PCI status checked every year?

    12.8.1–12.8.5 · high impact
  5. Do you have an incident response plan for a card data breach, reviewed and tested every year?

    12.10.1, 12.10.2 · high impact

This checklist is not a QSA assessment, not a Report on Compliance or an official SAQ, and not legal advice. It helps you find gaps before your assessment. Your answers stay in your browser until you request the PDF.

Full gap report to your inbox

PDF with readiness by requirement, every gap with its PCI DSS reference and a recommendation, a 3-step roadmap and the next step. We send it once, no newsletter.

Need help closing the PCI DSS gaps?

We build PCI DSS-ready payment software and run security audits: scope reduction, tokenization, payment page script control, MFA and logging. Send us your report or a short brief and we will reply within one business day.

TL;DR: PCI DSS v4.0.1 applies to every business that accepts, processes, stores or transmits payment card data. How much of it you must cover depends on how you take payments: a fully hosted payment page or iframe usually means SAQ A, a payment form that your own page controls means SAQ A-EP, and card data on your own systems means SAQ D. The checklist above picks a preliminary SAQ type, scores your readiness across the 12 requirements and lists the five gaps to close first. It is a self-check, not an official assessment.

Most teams that run this checklist sell online, build a checkout for a client or run a SaaS product that takes subscription payments. If you are building or reworking a payment flow and want it designed for PCI DSS from the start, see our PCI DSS compliant software development service. The questions follow PCI DSS v4.0.1, the version published by the PCI Security Standards Council in June 2024, and each one shows the requirement numbers it checks.

Who needs PCI DSS compliance?

PCI DSS applies to merchants of any size that accept Visa, Mastercard, American Express, Discover or JCB cards, and to service providers that store, process or transmit card data for them or can affect its security. That includes payment gateways, hosting and cloud providers, and development agencies with access to a production checkout. PCI DSS is not a law. Card brands make it mandatory through the contract between a merchant and its acquiring bank, and the acquirer decides how you validate: with a Self-Assessment Questionnaire (SAQ) or a Report on Compliance from a Qualified Security Assessor (QSA). The choice depends on your merchant level, which card brands set by yearly transaction volume.

Which SAQ type applies to my business?

Your SAQ type depends on where card data is entered and which systems can touch it. The table covers the three types this checklist supports. Other SAQs exist for card terminals and phone orders, and service providers always use SAQ D or a full assessment.

SAQ typeTypical payment setupWhat is in scope
SAQ ARedirect to a provider page, or a provider-hosted payment page or iframe; no card data on your systemsDefault passwords, patching, user accounts, paper media, quarterly ASV scans, providers and an incident plan
SAQ A-EPYour own page sends card data to the provider, for example a direct post or a JavaScript payment formMost technical controls for the web server and the checkout page, including payment page scripts (6.4.3) and change detection (11.6.1)
SAQ DCard data is stored, processed or transmitted on your systems; all service providersAll applicable PCI DSS requirements, including stored data protection, key management and card terminals

Since the January 2025 revision of SAQ A, requirements 6.4.3 and 11.6.1 are no longer in its questionnaire. Instead, the merchant must confirm that its site is not susceptible to script attacks that could affect the payment process. Your acquirer confirms the final SAQ type.

What changed in PCI DSS v4.0 and v4.0.1?

PCI DSS v4.0 replaced v3.2.1, which was retired on 31 March 2024. Version 4.0.1 clarified the text without adding new requirements, and v4.0 itself was retired at the end of 2024. The future-dated requirements of v4.0 became mandatory on 31 March 2025. For online businesses, the most visible changes are:

  • MFA for all access into the cardholder data environment, not only for admins (8.4.2).
  • Passwords of at least 12 characters (8.3.6).
  • Authenticated internal vulnerability scans (11.3.1.2).
  • A targeted risk analysis for every requirement where you choose the frequency (12.3.1).
  • An inventory and authorization of every script on the payment page (6.4.3) and detection of unauthorized changes to the page and its HTTP headers (11.6.1).
  • An automated technical solution, such as a WAF, in front of public-facing web applications (6.4.2).

What does the example result look like?

Press "Load an example" above. It fills the answers of a typical online store with a JavaScript payment form (SAQ A-EP): TLS, unique logins and quarterly ASV scans are in place, but there is no inventory of payment page scripts, no change detection on the checkout and no yearly penetration test. The overall score lands at about 60%, and the roadmap puts payment page security and testing first.

How is the readiness score calculated?

Each of the 44 questions has a weight from 1 to 3 based on its impact. "Yes" counts in full, "Partly" counts as half and "No" counts as zero. "N/A" answers and questions outside the selected SAQ type are left out, so they do not lower the score. The requirement score is the weighted share of met items. Gaps are sorted by weight, so high-impact items land in the first 30 days of the roadmap. The score shows where you stand against the checklist; it is not an Attestation of Compliance.

Which PCI DSS gaps are the most common?

The most common PCI DSS gap is an unclear scope: nobody can say which systems, people and vendors touch card data. Other frequent findings in assessments:

  • Third-party scripts on the checkout page that nobody inventoried or monitors. This is how web skimming attacks steal card numbers.
  • Shared admin accounts and no MFA on cloud consoles or the CMS admin.
  • Critical and high patches installed later than one month after release.
  • Logs that are collected but not reviewed every day.
  • No list of service providers with their Attestation of Compliance and a clear split of responsibilities.
  • An incident response plan that has never been tested.

How do I reduce my PCI DSS scope?

Keep card data off your systems. Use a hosted payment page or an iframe from your payment provider, replace stored card numbers with provider tokens and never log card data. Segment the few systems that still touch card data from the rest of the network, and test that segmentation. A smaller scope means a shorter SAQ, fewer controls to run every day and a cheaper assessment.

What should you fix in the first 30, 90 and 180 days?

Start with scope and the controls attackers use most: access, patching and the payment page. A practical order for an online merchant or a small SaaS team:

  1. Days 1–30. Confirm your SAQ type with the acquirer, map the systems and vendors in scope, turn on MFA, remove shared accounts and install overdue critical patches.
  2. Days 31–90. Inventory the payment page scripts, set up change detection on the checkout, centralize logs with daily review and book quarterly ASV scans.
  3. Days 91–180. Write the security policy and the incident response plan, train the team, collect your providers' AOCs and run the penetration test that your SAQ type requires.

If you need the test itself, our penetration testing and security audits team covers external, internal and segmentation testing.

This checklist is an educational self-assessment based on PCI DSS v4.0.1. It is not an official SAQ, a QSA assessment or legal advice. Use the official forms from the PCI Security Standards Council and confirm your validation requirements with your acquirer.

PCI DSS compliance checklist: common questions

Is PCI DSS compliance mandatory?

PCI DSS is not a law, but card brands require it through the merchant agreement with your acquirer. Non-compliance can lead to fines passed on by the acquirer, higher processing fees, liability for fraud losses after a breach and, in the worst case, the loss of the ability to accept cards.

Which SAQ do I need if I use Stripe, Adyen or PayPal?

It depends on the integration, not on the provider. A redirect or a provider-hosted page or iframe usually qualifies for SAQ A. If your own page loads the payment fields with JavaScript or posts card data directly, it is usually SAQ A-EP. Confirm the type with your acquirer.

What changed for SAQ A in 2025?

In January 2025 the PCI Security Standards Council removed requirements 6.4.3 and 11.6.1 from SAQ A. In their place, merchants must confirm that their site is not susceptible to script attacks that could affect the payment process. Quarterly ASV scans remain in SAQ A.

Do I need a penetration test for PCI DSS?

For SAQ A-EP and SAQ D, yes: a penetration test every year and after significant changes, plus segmentation testing if you use segmentation to reduce scope. SAQ D also requires an internal test. SAQ A merchants need quarterly ASV scans but no penetration test.

How long does it take to become PCI DSS compliant?

For SAQ A, a few weeks is usually enough. For SAQ A-EP and SAQ D, expect several months for scoping, closing technical gaps, collecting evidence and the assessment. Reducing scope first is the fastest way to shorten the timeline.

What does "N/A" mean in the checklist?

Choose N/A when a requirement does not apply to you, for example card terminals if you only sell online. Questions outside the selected SAQ type are set to N/A automatically. N/A answers are excluded from the score, so they do not lower it.

Is this checklist an official SAQ?

No. It is a self-check based on PCI DSS v4.0.1 that helps you find gaps before you fill in the official Self-Assessment Questionnaire or meet a QSA. The official SAQ forms are published by the PCI Security Standards Council.

Is my data sent anywhere when I use the checklist?

No. The checklist runs in your browser, and your answers stay on your device. Data is sent only if you ask for the PDF report by email, and then only the details you enter in that form.

Related tools