What 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 (Payment Card Industry Data Security Standard) is the security standard for any business that stores, processes or transmits payment card data. The PCI Security Standards Council writes it, and card brands and acquirers enforce it through contracts. As of November 2026 the only active version is 4.0.1, and your merchant level and questionnaire decide what you must prove.
This guide covers who must comply, the levels, the questionnaires, ways to shrink scope and a 10 step checklist, as of November 2026. It pairs with a card payment step by step, with fees and declines, chargeback ratios and Visa and Mastercard thresholds, KYC and KYB in payments and payment fraud prevention.
Key takeaways
- PCI DSS 4.0.1 is the only active version. The council published it on 11 June 2024 as a limited revision with no additional or deleted requirements.
- Everyone who touches card data must comply. How much you must prove depends on volume (level) and on how much card data your systems can reach (scope).
- Hosted fields, redirects and tokenization shrink scope, and SAQ A is the lightest form.
- Card brands and acquirers enforce PCI DSS by contract. The council itself does not fine anyone.
- Bank transfers are outside the card standard, but they carry their own rules.
What is PCI DSS?
PCI DSS is a set of technical and operational requirements for protecting cardholder data. It covers network security, access control, encryption, monitoring, testing and policy.
The standard exists because card data is valuable to criminals and merchants are many. The PCI Security Standards Council (PCI SSC) maintains it, but compliance is mainly a contractual duty to your acquirer and the card brands rather than a statute. Version 4.0.1 was published on 11 June 2024 as a limited revision that fixes typos and clarifies wording, according to the PCI SSC announcement. Version 4.0 was retired on 31 December 2024, and the future-dated requirements that 4.0 introduced took effect on 31 March 2025. No newer version appeared in the council's document library as of November 2026.
Who must comply with PCI DSS?
Any entity that stores, processes or transmits cardholder data, or can affect the security of that data, must comply. That includes merchants, payment service providers, gateways and processors.
Three roles matter:
- Merchants accept cards. They validate yearly against their level.
- Service providers handle card data for others. For them, SAQ D for service providers is the only questionnaire option.
- Acquirers require their merchants to comply and report to the card brands.
Outsourcing does not remove the duty. It reduces how much you must prove, because a validated provider carries most controls. You still own the controls that remain, such as protecting your website and managing your vendors.
What are the PCI merchant levels?
Merchant levels group businesses by yearly card volume. Visa's published levels, from its regional compliance page, are in the table below. Other card brands publish their own levels, and the acquirer decides how you are classified.
| Level | Visa transaction volume (12 months) | What you validate |
|---|---|---|
| Level 1 | Over 6 million Visa transactions across all channels, or designated by Visa | Annual Report on Compliance by a Qualified Security Assessor, quarterly scan by an Approved Scanning Vendor, Attestation of Compliance |
| Level 2 | 1 million to 6 million | Annual self-assessment questionnaire, plus scans |
| Level 3 | 20,000 to 1 million e-commerce transactions | Annual self-assessment questionnaire, plus scans |
| Level 4 | Under 20,000 e-commerce transactions, and other merchants up to 1 million | Self-assessment recommended, acquirer decides |
Source: Visa Caribbean, compliance validation, a regional page checked in November 2026. Some sources say Visa merged Levels 3 and 4 in 2024, and we could not confirm that on a primary page, so ask your acquirer which levels it applies.
Which self-assessment questionnaire applies?
The self-assessment questionnaire (SAQ) depends on how you accept cards. The council published the SAQs for version 4.0.1 on 15 October 2024.
| SAQ | Who it fits | Notes |
|---|---|---|
| A | Card-not-present merchants that fully outsource all account data functions to validated third parties | The lightest e-commerce form |
| A-EP | E-commerce merchants whose site does not receive card data but can affect the security of the payment page | Heavier, because your page code matters |
| B | Imprint machines or standalone dial-out terminals, with no electronic storage | In-person |
| B-IP | Standalone approved terminals connected by IP, no e-commerce | In-person |
| C | Payment application systems connected to the internet, with no electronic storage | |
| C-VT | Staff keying one transaction at a time into a third-party virtual terminal on an isolated device | |
| P2PE | Only a validated point-to-point encryption solution, no e-commerce | |
| D | Everything else. For service providers, the only option | The longest form |
The one-line descriptions summarize PCI SSC documents. Read the current form before you self-select.
How can you reduce PCI scope?
You reduce scope by making sure card data never reaches your systems. The less data your servers, code and staff see, the fewer requirements apply.
- Redirect the shopper to a payment page hosted by a validated provider.
- Embed hosted fields or an iframe so card entry happens in the provider's frame, not your page.
- Tokenize, so you store a single-use or reusable token instead of the card number.
- Use validated point-to-point encryption for in-person terminals.
- Segment your network so any system that does touch card data is isolated.
- Never write card numbers to logs, emails or support tools.
A caveat applies to embedded pages. The council's FAQ on revised SAQ A eligibility says merchants that embed a third-party payment page or iframe, as opposed to a full redirect, must confirm their site is not susceptible to script attacks. It points to techniques in requirements 6.4.3 and 11.6.1, or a confirmation from the processor. That took effect on 1 April 2025.
What changed in PCI DSS 4.0.1?
PCI DSS 4.0.1 changed no requirements. It corrected typos, clarified wording and aligned guidance, and it is the only version in force as of November 2026.
The bigger change for most teams came from 4.0, whose future-dated requirements became mandatory on 31 March 2025. The practical ones for e-commerce are the script controls in requirements 6.4.3 and 11.6.1, which protect payment pages from tampering. If you embed a payment frame, you either implement them or get the processor's confirmation that the frame is covered.
A 10 step PCI DSS compliance checklist
Use this order for a first pass. Your acquirer and assessor will refine it.
- Ask your acquirer your merchant level and which SAQ or report it expects.
- Map every place card data enters, moves through or rests in your business.
- Remove what you do not need. Stop storing card numbers you do not use.
- Move card entry to a hosted page or hosted fields from a validated provider.
- Tokenize anything you must keep.
- Confirm your payment page is protected against script tampering (requirements 6.4.3 and 11.6.1) or get the provider's confirmation.
- Keep systems patched, restrict access by role and require multi-factor authentication for administrators.
- Collect each provider's current Attestation of Compliance and record who owns which requirement.
- Complete the questionnaire or report, sign the Attestation of Compliance and run required scans through an Approved Scanning Vendor.
- Put validation on a yearly calendar and re-check scope whenever you change checkout, vendors or systems.
What happens if you are not compliant?
Non-compliance is enforced through your contracts, not by the council. Your acquirer can charge program fees, raise your rates, require remediation or end the agreement.
The larger risk is a breach. If card data is compromised while you are out of compliance, you can face forensic investigation costs, brand assessments, and chargebacks and fraud losses (see chargeback ratios and Visa and Mastercard thresholds). Terms differ by acquirer, so read your merchant agreement. No public source gives a single fine figure, and quoting one would mislead.
What about bank transfer and payout flows?
PCI DSS protects payment card account data, so a flow that moves money only over bank rails does not put card data in scope. That does not make it unregulated.
If you add payouts or bank transfers next to cards, keep two points in mind. First, a bank-rail product has its own obligations, such as Nacha rules for ACH. Nacha's fraud monitoring rules took effect in two phases in 2026, on 20 March and 19 June (22 June in practice, because 19 June is a federal holiday), per its Phase 2 page. See ACH payments explained. Second, if any part of your product touches card data, even by a card-on-file feature, that part is in scope. Confirm scope with a Qualified Security Assessor.
Where BlindPay fits
BlindPay is not a card acquirer and not a merchant of record. Its payouts and collections run over bank rails and stablecoins, and its compliance layer handles KYC, KYB, sanctions screening and Travel Rule checks inside the payment flow, which sits alongside, not inside, your card program. BlindPay does offer card payins: card fields render in an isolated frame on pay.blindpay.com, 3-D Secure is required, and the card payins docs say this keeps your PCI scope at the lowest level, SAQ A. Confirm your own eligibility with your acquirer or assessor.
Methodology and sources
Checked in November 2026. Card brand levels come from a Visa regional page. SAQ descriptions are summaries of PCI SSC documents.
- PCI SSC, PCI DSS v4.0.1 published
- PCI SSC, SAQs for PCI DSS v4.0.1 bulletin
- PCI SSC, revised SAQ A eligibility FAQ
- Visa Caribbean, compliance validation
- Nacha, fraud monitoring Phase 2
- BlindPay docs: card payins, KYC requirements
This article is for general information only and is not legal, tax, or compliance advice.
FAQ
More compliance articles
See all compliance articlesPCI 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 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.
High-risk merchant accounts: what they are, which industries, and how to get approved
What makes a merchant high risk, which industries providers flag, what it costs, how to prepare for approval and what to do if you are declined.