Skip to content

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.

PCI DSS is the security standard for handling payment card data. Your merchant level depends on your annual card transaction volume, and your SAQ, the self-assessment questionnaire you complete, depends on how you accept cards. Hosted payment pages and tokenization, which swaps card numbers for placeholder values, shrink your scope the most.

This guide covers Visa's current merchant levels, the SAQ types, what the current PCI DSS version changed and a small-business checklist, as of November 2026. Standards and card brand rules change, so check the PCI Security Standards Council (PCI SSC) and your acquirer before you file anything.

Key takeaways

  • PCI DSS v4.0.1 is the current version on the PCI SSC document library. It was published on 11 June 2024 as a limited revision with no new or deleted requirements.
  • Visa now has three merchant levels. On 25 April 2024 it merged its old Levels 3 and 4 into one Level 3, which covers 1 to 1,000,000 Visa transactions a year.
  • Your SAQ type follows how you take cards: A for fully outsourced card-not-present, A-EP, B, B-IP, C-VT, C, P2PE for specific setups, and D when nothing else fits.
  • A compliant payment provider lowers your scope but does not make you compliant.

What is PCI DSS and who must comply?

PCI DSS, the Payment Card Industry Data Security Standard, is a set of security requirements for any business that stores, processes or transmits payment card data. It is maintained by the PCI SSC and enforced through the card brands and acquirers, the banks or providers that process your card payments.

It is not a law in the usual sense. Visa's compliance page states that acquirers must ensure their merchants validate at the appropriate level, and that merchants must always maintain full compliance. So the practical rule is simple: if you accept cards, you are in scope, and your acquirer will ask you to prove it.

Scope means every system that touches card data, plus systems connected to them. The smaller that footprint, the shorter your paperwork. That is why most small merchants try to keep card data off their own servers.

What are the merchant levels?

Visa has three merchant levels, set by your Visa transaction volume over 12 months. Level 1 is more than 6,000,000 transactions, Level 2 is 1,000,001 to 6,000,000, and Level 3 is 1 to 1,000,000.

Older guides, and some other sources, still describe four levels. Visa's current document footnote says that effective 25 April 2024 Visa consolidated merchant levels 3 and 4 into a unified Level 3, and that this does not change the existing PCI DSS compliance requirements. The table uses the current scheme.

Visa merchant levelAnnual Visa transactionsNotes
Level 1More than 6,000,000Highest volume
Level 21,000,001 to 6,000,000
Level 31 to 1,000,000Merged from former Levels 3 and 4 on 25 April 2024

The figures come from Visa's "What To Do If Compromised" guide, version 10.0, effective 25 June 2026. Visa's security compliance page says a merchant's total Visa transaction volume over a 12-month period determines the level.

Here is a worked example. It is illustrative and the inputs are stated: a merchant with 18,000 Visa transactions in the last 12 months is Level 3. A merchant with 950,000 is also Level 3. One with 2,400,000 is Level 2, and one with 7,200,000 is Level 1.

Mastercard runs its own program, with its own level definitions, and other networks set theirs. Ask your acquirer which levels apply to you and what it expects you to submit. Visa's page also says merchants that meet its Technology Innovation Program criteria, such as at least 75% of transactions through EMV chip terminals, validated point-to-point encryption or EMVCo-compliant tokenization, do not have to verify PCI DSS compliance.

Which SAQ applies to me (A, A-EP, B, C, D)?

Pick the SAQ that matches how you take cards, not how big you are. The PCI SSC publishes a separate SAQ for each setup, and each one lists eligibility criteria you must meet in full.

The descriptions below come from the PCI SSC's SAQ documents (version 4.0, April 2022). The SAQs for v4.0.1, published 15 October 2024, clarified eligibility in SAQs A, A-EP and C-VT, so read the current document before you choose.

SAQWho it fitsNot for
ACard-not-present merchants (e-commerce or mail and telephone order) that fully outsource account data to PCI DSS compliant third parties; keep only paper reports or receiptsFace-to-face channels
A-EPE-commerce merchants that partially outsource, whose website does not receive account data but does affect the security of the payment transaction or the integrity of the pageNon-e-commerce channels
BMerchants using only imprint machines or standalone dial-out terminals, with no account data stored on any computerE-commerce channels
B-IPMerchants using only standalone, PCI-listed PTS point-of-interaction terminals with an IP connection to the processorSecure card readers (SCR, SCRP)
C-VTMerchants that key transactions one at a time into a third-party virtual payment terminal from an isolated computerOther setups
CMerchants with payment application systems, such as point-of-sale systems, connected to the Internet that do not store electronic account dataE-commerce channels
P2PEMerchants that process account data only through a validated, PCI-listed point-to-point encryption solutionE-commerce channels
D (merchants)Everyone who is SAQ-eligible but does not meet another SAQ, including sites that take card data directly or store it electronicallyService providers

Use this selector as a starting point, then confirm eligibility in the document.

  1. Do you send customers to a provider's hosted page or embed a provider's payment form, and never touch card data? Look at SAQ A.
  2. Does your site control how customers reach the provider, or could it affect the payment page, without receiving card data? Look at SAQ A-EP.
  3. Do you take cards only on a standalone terminal? SAQ B (dial-out), B-IP (IP-connected) or P2PE (validated encryption).
  4. Do you key cards into a provider's virtual terminal? SAQ C-VT.
  5. Does your point-of-sale system connect to the Internet? SAQ C.
  6. Does none of that fit, or do you store card data? SAQ D.

SAQ A has an extra e-commerce condition for sites that embed a provider's form. A PCI SSC blog post dated 28 February 2025 explains that the merchant must confirm its site is not susceptible to script attacks, either with script-protection techniques of its own or by obtaining confirmation from its compliant provider. The post says the criterion does not apply to merchants that redirect customers or fully outsource payment functions.

What changed in the current PCI DSS version?

The current version is PCI DSS v4.0.1, a limited revision published on 11 June 2024 that fixed formatting and typographical errors and clarified some requirements. It added no new requirements and deleted none.

The PCI SSC retired v4.0 on 31 December 2024, so v4.0.1 is the only active version. The future-dated requirements that v4.0 introduced became mandatory on 31 March 2025, and v4.0.1 did not move that date. The PCI SSC also published updated SAQs for v4.0.1 on 15 October 2024, including a requirement added to SAQ A and one removed from SAQ C.

Check the document library for the current version on the day you read this. The library showed v4.0.1 as the featured document when this guide was written.

How do hosted fields and tokenization reduce scope?

They keep card numbers off your systems. With a hosted payment page, the customer types the card number on the provider's page or in a form the provider delivers, so your servers never see it, and the provider stores or tokenizes it.

Tokenization replaces the card number with a placeholder value, a token, that is useless outside the provider's system. You keep the token for repeat billing and refunds and never store the number itself. That is the logic behind the SAQ A criteria, which require that all payment page elements originate only and directly from a compliant provider, and that you do not electronically store, process or transmit account data.

Scope reduction checklist:

  • Use a redirect, a hosted page or a provider-delivered embedded form, not a form you build and post yourself.
  • Never log, email, screenshot or store full card numbers or security codes.
  • Store tokens and the last four digits only.
  • Review the provider's Attestation of Compliance each year, and keep it with your records.
  • Keep payment pages free of scripts you do not need, and approve every script that does run on them.
  • Use validated point-to-point encryption terminals in stores.

What happens if I am not compliant?

The consequences come mostly through your acquirer and the card brands. Visa's compliance page says Visa may assess non-compliance penalties to the issuer or acquirer, and your contract decides what is passed on to you.

After a data breach, the cost rises. Visa's "What To Do If Compromised" guide says that if a PCI forensic investigation is not finished within four full calendar months of Visa's notice, Visa may charge fees: USD 3,000 flat for Level 3 merchants, or USD 10,000 per month for Level 1 and 2 merchants until the investigation is complete. That is separate from the cost of the investigation, fraud losses, remediation and customer notices.

Non-compliance can also complicate your acquiring relationship, including holds on funds or termination, depending on your contract. Read the merchant agreement for the clauses on data security.

What is a PCI compliance checklist for a small business?

Start by finding out how card data flows through your business, then choose the smallest scope that fits. The list below gives the order of operations.

  1. Map how you accept cards: website, terminal, phone, virtual terminal, marketplace.
  2. Ask your acquirer what level they assign you, which SAQ they expect and what dates and forms they need.
  3. Choose the smallest eligible SAQ by outsourcing card handling, then confirm every eligibility criterion.
  4. Collect your providers' Attestations of Compliance and confirm they cover the services you use.
  5. Fix the gaps the questionnaire reveals: passwords, patching, access control, logging.
  6. Complete the SAQ and the attestation, and submit them the way your acquirer asks.
  7. Set a calendar reminder to revalidate, and rerun the process whenever you change a payment page, provider or terminal.
  8. Write an incident plan that names who calls your acquirer if card data is exposed.

For how acquirers fit into the wider picture, see what merchant acquiring is. Where PSPs and gateways sit, read acquirer vs processor vs gateway vs PSP. Underwriters also ask about security, as covered in merchant underwriting and onboarding, and a breach can turn into disputes, covered in chargebacks explained.

For the requirements in more depth, see the PCI DSS 4.0.1 compliance guide and PCI DSS for payment processing.

Methodology and sources

Merchant levels, the 25 April 2024 consolidation and the forensic fee amounts come from Visa's What To Do If Compromised guide, version 10.0, effective 25 June 2026. Level determination, acquirer responsibility and the Technology Innovation Program come from Visa's security and compliance page, which is undated and was read in November 2026. The current standard version was checked on the PCI SSC document library in November 2026, and its release details come from the PCI SSC post Just Published: PCI DSS v4.0.1, 11 June 2024.

The v4.0.1 SAQ changes come from the PCI SSC bulletin on SAQs for v4.0.1, 15 October 2024, and the SAQ A script criterion from the PCI SSC FAQ post, 28 February 2025. SAQ eligibility wording is from the PCI SSC's version 4.0 SAQ documents, April 2022, which were read in full; the v4.0.1 editions could not be read, so check them. Mastercard's level definitions were not readable, so none are stated here. Levels, thresholds and requirements change, so confirm everything with your acquirer.

Next, read chargebacks explained to see how card disputes are counted, or how merchant underwriting works to see what an acquirer asks before it approves you.

This article is general information, not legal, tax, or financial advice.

FAQ

One API.
Multiple payment rails.

Blind Pay, Inc. (“BlindPay”) is a United States-based financial technology and payments infrastructure company, incorporated in the State of Delaware on May 2, 2024. BlindPay is duly registered as a Money Services Business (“MSB”) with the Financial Crimes Enforcement Network (“FinCEN”) under registration number 31000277566153. BlindPay is not a state-licensed money transmitter and does not, in its own capacity, engage in regulated money transmission services. All such regulated activities are conducted exclusively through, and under the licenses of, duly authorized financial institution partners. BlindPay's role is limited to providing financial technology, virtual account management, payment processing, and related payments infrastructure services that facilitate payment flows and account functionalities. These services are provided in coordination with its licensed partners and in compliance with applicable federal MSB requirements and relevant state regulatory frameworks.

Blind Pay, LLC (“BlindPay”) is a Delaware limited liability company formed on June 24, 2025. BlindPay is duly registered as a Money Services Business (“MSB”) with the Financial Crimes Enforcement Network (“FinCEN”) under registration number 31000318334247 and is listed in the Nationwide Multistate Licensing System (“NMLS”) under NMLS ID #2745309.

BLIND PAY SOCIEDADE PRESTADORA DE SERVIÇOS DE ATIVOS VIRTUAIS LTDA. (“BlindPay”) is a Virtual Asset Service Provider (“VASP”) operating in Brazil. The company is presently completing the regulatory adaptation process required of Virtual Asset Service Provider Companies (SPSAV) under Central Bank of Brazil Resolution No. 520/2025, and remains subject to the transitional regime set forth in Article 88 of that Resolution. Registered address: Avenida Princesa Isabel, nº 15, Sala 1405, Edifício Martinho de Freitas, Centro, Vitória/ES, 29010-361.

BlindPay is a stablecoin API that enables individuals and businesses to move money worldwide.