PCI DSS 4.0.1 compliance guide for merchants and fintechs: requirements, levels, and how to reduce scope
PCI compliance under PCI DSS 4.0.1: who must comply, merchant levels, SAQ types, what card data you can store, and how to cut your scope to SAQ A.
PCI compliance means meeting PCI DSS, the security standard for any business that stores, processes or transmits cardholder data. The current version is 4.0.1. Your validation level depends on transaction volume, and you can cut your scope sharply with hosted payment fields, tokenization or point-to-point encryption, so that card numbers never touch your systems.
This guide covers who must comply, what changed in version 4, the merchant levels, the questionnaire types, the data storage rules and a checklist. It reflects PCI Security Standards Council publications and Visa's public pages as of November 2026. It is not a substitute for your acquirer or a qualified assessor.
Key takeaways
- PCI DSS applies to anyone who handles card data, including merchants, processors and fintechs.
- Version 4.0.1 is current. Version 4.0 was retired on December 31, 2024, and 51 future-dated requirements took effect on March 31, 2025.
- The card brands set merchant levels, and your acquirer confirms yours.
- You may never store the security code, full track data or PIN after authorization, even encrypted.
- Scope is the lever. If card numbers never reach your systems, most requirements fall away.
What is PCI DSS and who must comply?
PCI DSS is the Payment Card Industry Data Security Standard. It is a set of technical and operational requirements for protecting card data. The PCI Security Standards Council (PCI SSC), a body founded by the major card brands, maintains it.
The standard applies to every entity that stores, processes or transmits cardholder data. That includes merchants of any size, payment processors, gateways and service providers whose systems could affect the security of card data. The roles are explained in issuer, acquirer, network, processor, gateway and PSP.
Three terms come up throughout.
- Primary account number (PAN): the card number.
- Sensitive authentication data (SAD): the full magnetic stripe or chip track data, the card security code, and the PIN or PIN block.
- Cardholder data environment (CDE): the people, processes and systems that store, process or transmit card data, plus anything connected to them.
Your scope is the size of your CDE. A smaller CDE means fewer requirements apply to you.
Is PCI DSS a law?
No. The PCI SSC writes the standard but does not enforce it. Its FAQ 1004 says the participating payment brands decide which entities must comply and run their own enforcement programs. In practice, your acquirer requires compliance in your merchant agreement.
Some state laws overlap with it. Washington's RCW 19.255.020 gives businesses a safe harbor from certain liability to financial institutions after a breach if they were certified compliant with the standard. Minnesota's Statute 325E.64 does not mention PCI, but it bars retaining the card security code, the PIN verification code number or full track data after authorization. Ask counsel which laws apply to you.
What changed in version 4.0 and 4.0.1?
Version 4.0 rewrote much of the standard, and version 4.0.1 tidied it up. The main dates are below.
| Date | What happened | Source |
|---|---|---|
| June 11, 2024 | PCI DSS v4.0.1 published, with no requirements added or deleted | PCI SSC blog |
| December 31, 2024 | PCI DSS v4.0 retired | PCI SSC blog |
| January 30, 2025 | SAQ A updated for e-commerce merchants | PCI SSC blog |
| March 31, 2025 | 51 future-dated requirements became effective | PCI SSC blog |
The PCI SSC counted 64 new requirements in version 4, of which 51 were future-dated to March 31, 2025. Four of them affect most merchants.
- Multi-factor authentication (MFA) for the CDE. Requirement 8.4.2 says MFA is implemented for all access into the cardholder data environment, not only for administrators.
- Longer passwords. Requirement 8.3.6 sets a minimum length of 12 characters, or eight if a system cannot support 12, with both letters and numbers.
- Payment page script control. Requirement 6.4.3 requires a method to confirm that each script on a payment page is authorized and to assure its integrity.
- Tamper detection. Requirement 11.6.1 requires a mechanism that detects changes to payment pages and their HTTP headers.
The last two target attacks where criminals inject code into a checkout page to copy card numbers as customers type them. Planet's 2026 payment security guide (August 2026) describes these as safeguards against Magecart-style attacks, alongside MFA, tighter passwords and ongoing compliance.
The requirement wording above comes from the PCI SSC's SAQ D for Merchants for version 4.0.
What changed for SAQ A merchants?
On January 30, 2025, the PCI SSC removed requirements 6.4.3, 11.6.1 and 12.3.1 from SAQ A. Requirement 12.3.1 is the targeted risk analysis that supports 11.6.1. In their place, it added an eligibility criterion: the merchant must confirm that its site is not susceptible to attacks from scripts that could affect its e-commerce systems.
A follow-up FAQ (February 28, 2025) clarified that the criterion applies to merchants that embed a third-party provider's payment page or form, such as an iframe. It does not apply to merchants that fully redirect customers to the provider.
What are the merchant levels and SAQ types?
Merchant levels decide how you validate. The card brands set them, not the PCI SSC, and each brand counts its own transactions. Your acquirer tells you your level.
The table shows Visa's commonly published thresholds. The only Visa page we could find that lists them is an older regional page, so treat them as a guide. Visa's current security compliance page says only that the level is based on Visa transaction volume over 12 months and that acquirers must make sure merchants validate at the right level.
| Level | Typical volume trigger (confirm with your acquirer) | Validation required |
|---|---|---|
| 1 | More than 6 million Visa transactions a year | Annual Report on Compliance (ROC) by a Qualified Security Assessor (QSA), quarterly scan by an Approved Scanning Vendor (ASV), Attestation of Compliance |
| 2 | 1 million to 6 million Visa transactions a year | Annual Self-Assessment Questionnaire (SAQ), quarterly ASV scan |
| 3 | 20,000 to 1 million Visa e-commerce transactions a year | Annual SAQ, quarterly ASV scan |
| 4 | Fewer than 20,000 Visa e-commerce transactions a year, and all other merchants up to 1 million Visa transactions | SAQ recommended, ASV scan if applicable. The acquirer sets the validation |
Merchants that validate by questionnaire choose the SAQ that matches how they accept cards. The PCI SSC's rule is that all the eligibility criteria for a given SAQ must be met.
| SAQ | Who it is for |
|---|---|
| A | E-commerce or mail and telephone order merchants that have fully outsourced all account data functions to validated third parties. Not for face-to-face sales |
| A-EP | E-commerce merchants whose website does not receive account data but controls how customers are redirected to the processor |
| B | Merchants using only imprint machines or standalone dial-out terminals. Not for e-commerce |
| B-IP | Merchants using only standalone, approved point-of-interaction devices with an IP connection |
| C | Merchants with payment applications or point-of-sale systems connected to the internet and no stored account data. Not for e-commerce |
| C-VT | Merchants that key in one payment at a time on a third-party virtual terminal from an isolated device |
| P2PE | Merchants using only a validated, PCI-listed point-to-point encryption solution. Not for e-commerce |
| D | Merchants that fit none of the above, and service providers eligible to self-assess |
How a sale is taken changes which SAQ fits. Card-present vs card-not-present payments explains the two channels.
What data can and cannot be stored?
You may store the card number only if it is protected, and you may never store sensitive authentication data after authorization. These are the two rules most often broken by accident, usually in logs, call recordings or spreadsheets.
| Data | Can you store it after authorization? | Rule |
|---|---|---|
| Primary account number | Yes, if rendered unreadable wherever it is stored | Requirement 3.5.1 |
| Cardholder name and expiry date | Yes, with protection when stored with the card number | Requirement 3 |
| Full track data from the stripe or chip | No | Requirement 3.3.1.1 |
| Card security code (the three or four digits) | No | Requirement 3.3.1.2 |
| PIN and PIN block | No | Requirement 3.3.1.3 |
Requirement 3.3.1 is blunt: sensitive authentication data is not retained after authorization, even if encrypted. Requirement 3.5.1 lists the accepted ways to make a stored card number unreadable, including one-way hashes and truncation.
The simplest way to follow both rules is to store nothing. Card tokenization replaces the card number with a token that has no value if stolen.
How do you reduce PCI scope?
You reduce scope by keeping card data out of your systems. Each method below moves the sensitive step to a validated provider.
- Use a hosted payment page. The customer is redirected to the provider to pay. Your site never sees the card.
- Use hosted fields or an embedded frame. The card fields load from the provider inside your page. The PCI SSC's iframe FAQ explains when this qualifies for SAQ A.
- Tokenize stored cards. Keep a token for repeat billing and let the provider hold the card number.
- Use point-to-point encryption in stores. A validated solution encrypts the card at the reader, so your network carries no readable card data.
- Segment your network. Isolate anything that does touch card data, so the rest of your systems stay out of scope.
- Stop collecting card data in other channels. Remove card numbers from email, chat, tickets and call recordings.
Payment methods that do not use cards carry no cardholder data at all. Stablecoin and bank-transfer flows, such as the ones BlindPay runs, sit outside the cardholder data environment. When a business uses BlindPay card payins, the card fields render in BlindPay's hosted frame, so card data never touches the business's servers, which keeps its scope at SAQ A per the card payins docs. Confirm your own scope with your assessor or acquirer.
What does a PCI compliance checklist look like?
Use this list to prepare for your first validation. It follows the order most small teams work in.
- Ask your acquirer for your merchant level and the validation it expects.
- Map every place card data enters, moves through or leaves your business.
- Remove card data you do not need, starting with stored security codes and logs.
- Move card entry to a hosted page, hosted fields or a validated terminal.
- Pick the SAQ whose eligibility criteria you fully meet.
- Turn on MFA for all access into the CDE and set 12-character passwords.
- Inventory the scripts on any payment page you host, and add tamper detection.
- Schedule quarterly ASV scans if your SAQ requires them.
- Collect the Attestation of Compliance from each service provider you rely on.
- Complete the SAQ and your own attestation, and send both to your acquirer.
- Set a calendar for the annual revalidation and for reviewing changes to your checkout.
Sources
- PCI Security Standards Council, "Just published: PCI DSS v4.0.1" (June 2024): blog.pcisecuritystandards.org
- PCI Security Standards Council, future-dated requirements of PCI DSS v4.x (2025): blog.pcisecuritystandards.org
- PCI Security Standards Council, SAQ A updates (January 2025) and eligibility FAQ (February 2025): blog.pcisecuritystandards.org
- PCI Security Standards Council, SAQ D for Merchants, PCI DSS v4.0 (2022): listings.pcisecuritystandards.org
- PCI Security Standards Council, FAQ 1004 on enforcement (2012): pcisecuritystandards.org
- Visa, security compliance overview (2026): corporate.visa.com
- Visa, compliance validation levels, regional page (undated): visa.com.tt
- Washington State Legislature, RCW 19.255.020 (2026): app.leg.wa.gov
- Minnesota Revisor of Statutes, Section 325E.64 (2026): revisor.mn.gov
- Planet, "Payment security for merchants in 2026" (August 2026): weareplanet.com
What to do next
Start with the data map: you cannot shrink a scope you have not drawn. Then read card tokenization explained for the storage side and how card payments work for where card data travels. If your customers buy stablecoins by card, how to buy stablecoins with a credit card in 2026 shows how a hosted card frame keeps that flow at SAQ A.
This article is general information, not legal, tax, or financial advice.
FAQ
More compliance articles
See all compliance articlesWhat is PCI DSS compliance? Levels, SAQs, 4.0.1 and how to shrink your scope
PCI DSS is the card industry's security standard. See who must comply, merchant levels, SAQ A vs D, what 4.0.1 changed and how hosted fields cut scope.
PCI DSS for merchants: which level and SAQ applies to you
PCI DSS compliance for merchants: Visa's current levels, which SAQ (A, A-EP, B, C, D) fits how you take cards, what v4.0.1 changed, and a checklist.
Merchant onboarding and underwriting: what acquirers check before approving you
Acquirers verify your business, owners and history, then set approval, pricing, limits and reserves. See the documents to prepare and how to get approved.