PCI DSS merchant levels are often described as if they were four universal compliance tiers. They are not. The PCI Security Standards Council publishes and maintains the PCI Data Security Standard, but payment brands and acquiring banks determine how merchants must validate and report compliance.
Table of Contents

That distinction matters because a Level 1 merchant, a Level 3 merchant, and a Level 4 merchant are all still expected to protect payment-account data under PCI DSS when the standard applies. The level mainly changes the validation route, reporting expectations, and who may be required to assess the environment.
For most merchants, the practical question is therefore not simply, “What PCI level am I?” It is, “Which payment brand or acquirer is classifying me, how many relevant transactions do I process, and what validation documents will that organization accept?”
What Are PCI DSS Merchant Levels?
Merchant levels are classifications used by payment-brand compliance programs to determine how a merchant demonstrates PCI DSS compliance. Transaction volume is usually the starting point, but it is not always the final word. A payment brand or acquirer may impose a higher validation level because of risk, a previous account-data compromise, contractual requirements, or another program rule.
The PCI Security Standards Council’s merchant guidance makes an important point that is easy to miss: PCI DSS applies regardless of merchant size when the merchant is within scope, while individual payment brands decide the validation and reporting requirements. The Council also explains that compliance-accepting entities such as payment brands and acquirers determine whether evidence should take the form of a Self-Assessment Questionnaire, Report on Compliance, or another accepted validation method.
This means “Level 4” does not mean “PCI DSS does not apply,” and “Level 1” does not describe a stronger version of PCI DSS. The underlying security standard is the same standard. What changes is principally how compliance is demonstrated and reported.
PCI DSS Level 1, 2, 3, and 4 at a Glance
The four-level table below illustrates Mastercard’s merchant framework, not a universal classification for all brands. Visa now uses a consolidated lower tier; American Express uses different thresholds, and Discover uses three levels. Read the relevant brand section before applying any number.
| Level | Common transaction-volume pattern | Typical validation direction |
|---|---|---|
| Level 1 | Mastercard illustration: more than 6 million combined Mastercard and Maestro transactions, or another Level 1 criterion | ROC-based annual validation is generally expected |
| Level 2 | Mastercard illustration: more than 1 million and up to 6 million combined transactions, or another Level 2 criterion | Annual SAQ-based validation is common, subject to brand-specific assessor rules |
| Level 3 | Often applies to merchants below 1 million transactions with an e-commerce threshold | Annual SAQ commonly used where eligible |
| Level 4 | Other smaller merchants falling below higher-level thresholds | SAQ or another acquirer-defined validation path may apply |
Treat that table as an orientation map, not as a self-classification form. American Express and Discover use different thresholds, and even Visa and Mastercard rules include brand-specific details that matter once you move from explanation to actual compliance reporting.
PCI DSS Level 1 Explained
Level 1 is generally the highest merchant validation category. Under Visa’s current public compliance program, merchants processing more than 6 million Visa transactions annually across all channels are Level 1. Visa can also treat certain global merchants as Level 1.
Mastercard similarly places merchants with more than 6 million combined Mastercard and Maestro transactions annually into Level 1. Mastercard may also classify a merchant as Level 1 if it satisfies Visa’s Level 1 criteria or if Mastercard determines that Level 1 treatment is appropriate to reduce risk.
Level 1 normally leads to a Report on Compliance rather than an ordinary self-assessment route. But be careful with the popular statement that “every Level 1 merchant must hire a QSA.” Brand rules are more nuanced. Visa’s current program permits its merchant ROC to be completed by a Qualified Security Assessor or, in defined circumstances, internal resources with the required officer sign-off. Mastercard likewise specifies permitted signing and assessment arrangements within its program.
For procurement purposes, the important question is not whether someone online calls your company “Level 1.” Ask the organization receiving your validation exactly who may perform the assessment, which ROC and AOC documents are required, and whether additional scanning, testing, or program-specific evidence must accompany them.
If you are budgeting for that process, the difference between self-assessment and formal ROC work can be substantial. Our guide to PCI DSS assessment costs for SAQ and ROC engagements explains the cost drivers separately from the merchant-level thresholds.
PCI DSS Level 2 Explained
Level 2 commonly covers a merchant processing more than 1 million but no more than 6 million annual transactions under the relevant payment-brand program. Visa uses a 1-million-to-6-million annual Visa transaction range, while Mastercard currently places merchants with more than 1 million and no more than 6 million combined Mastercard and Maestro transactions into Level 2.
Annual SAQ validation is common at this level, but “Level 2 equals DIY SAQ” is too simplistic. Mastercard, for example, currently requires additional QSA or Internal Security Assessor involvement when a Level 2 merchant completes certain questionnaires, including SAQ A, SAQ A-EP, or SAQ D. Mastercard also allows a Level 2 merchant to choose a ROC instead of an SAQ.
This illustrates why two merchants processing almost identical volumes can receive different compliance instructions. Transaction count gets you into the neighborhood. Payment architecture, SAQ eligibility, brand rules, and your acquirer’s requirements tell you which door to knock on.
PCI DSS Level 3 Explained
Level 3 is frequently associated with e-commerce. Mastercard’s current Site Data Protection program includes merchants with more than 20,000 and no more than 1 million combined Mastercard and Maestro e-commerce transactions in Level 3, subject to higher-level and cross-brand criteria. Do not apply the old Visa 20,000-transaction split as a current universal rule: Visa consolidated its former Levels 3 and 4.
An annual SAQ is generally the validation direction for Mastercard Level 3 merchants. Mastercard currently does not require Level 3 merchants to report validation directly to Mastercard in the same way it does for higher tiers, although the merchant must still comply and the acquiring bank manages its merchant-risk program.
E-commerce merchants should be especially careful about assuming that lower transaction volume automatically means an easy assessment. PCI DSS v4.0.1 changed the practical workload for many online merchants, particularly around payment-page security and current SAQ eligibility.
A merchant that redirects payment to a third-party processor can have a very different PCI footprint from a merchant whose own webpage controls payment fields, scripts, or data flows. If the architecture is the bigger question, see our PCI DSS compliance cost guide for e-commerce stores for a payment-flow-based explanation.

PCI DSS Level 4 Explained
Level 4 remains a category in Mastercard and American Express programs, but it is not a current universal label across card brands. Mastercard describes Level 4 as other merchants outside its higher categories. Visa’s former Level 4 was consolidated into Level 3, so an older Visa Level 4 label needs to be reconciled with the current program.
This is the level where one of the most persistent PCI myths appears: “We’re Level 4, so PCI is optional.” It is not. Mastercard explicitly states that Level 4 merchants are required to comply with PCI DSS even though validation to Mastercard itself is generally not required unless another applicable requirement says otherwise.
The practical validation process for a small merchant may instead be managed by its acquiring bank, processor, payment facilitator, or merchant-services provider. That organization may require a particular SAQ, Attestation of Compliance, external vulnerability scan where applicable, or completion through a compliance portal.
Small merchants should therefore read their processor’s request rather than treating “Level 4” as a free pass. If cost is the concern, our PCI DSS compliance cost guide for small businesses explains where the real expense tends to appear, including staff time, security remediation, scanning, and professional assistance.
Visa Merchant Levels: Former Levels 3 and 4 Were Consolidated
Visa’s current AIS compliance page presents three merchant levels. Its June 2026 What To Do If Compromised supplement expressly records that former Levels 3 and 4 were consolidated into Level 3 effective April 25, 2024. The consolidation did not remove PCI DSS obligations.
| Visa category | Current public AIS summary |
|---|---|
| Level 1 | Over 6 million annual Visa transactions, or global Level 1 designation. |
| Level 2 | 1–6 million annual Visa transactions. |
| Level 3 | Lower-volume category; the AIS page describes fewer than 1 million Visa e-commerce transactions. Former Level 4 is consolidated here. |
Use the applicable Visa program and acquirer’s written classification, particularly at exactly 1 million transactions or with mixed channels. Visa’s public AIS and incident supplement summaries use differing boundary wording. Do not resolve that difference by guessing. Visa’s counting guidance also considers corporate entities, countries and acquirers; independently operated locations may receive different treatment.
Mastercard Merchant Levels
Mastercard publishes particularly clear current thresholds through its Site Data Protection Program.
| Mastercard level | Current criteria in summary | General validation path |
|---|---|---|
| Level 1 | More than 6 million combined Mastercard and Maestro transactions annually, certain merchants meeting Visa Level 1 criteria, or merchants Mastercard assigns Level 1 | Annual PCI DSS assessment resulting in a ROC |
| Level 2 | More than 1 million and no more than 6 million combined transactions, or certain merchants meeting Visa Level 2 criteria | Annual SAQ, with additional validation rules for specified SAQ types |
| Level 3 | More than 20,000 qualifying e-commerce transactions and no more than 1 million, unless a higher level applies | Annual SAQ |
| Level 4 | All other merchants | Annual SAQ is available; Mastercard does not generally require direct validation to Mastercard |
Notice how the Mastercard program also refers to Visa classifications. Merchant levels are therefore not isolated labels living inside the PCI DSS document. They sit inside payment-network compliance programs.
American Express Merchant Levels Are Different
American Express is a good demonstration of why a generic “PCI Level 1 to 4” table should never be treated as universal. Its October 2026 U.S. Data Security Operating Policy uses four merchant levels with the transaction thresholds below. The document was published October 23 and took effect October 24, 2026, except where it specifies a later date.
| American Express level | Annual American Express transactions |
|---|---|
| Level 1 | 2.5 million or more, or a merchant American Express otherwise assigns Level 1 |
| Level 2 | 50,000 to fewer than 2.5 million |
| Level 3 | 10,000 to fewer than 50,000 |
| Level 4 | Fewer than 10,000 |
American Express’ current U.S. Data Security Operating Policy then maps those levels to its own validation-document requirements. This table summarizes the U.S. policy. Merchants in other markets should use their applicable policy rather than assuming regional documents are interchangeable.
This produces a useful example. A merchant processing 100,000 American Express transactions annually would sit in American Express Level 2 even though 100,000 transactions would not approach Level 2 under the familiar Visa or Mastercard volume model.
Discover Uses Three Merchant Levels
Discover provides another reminder that four tiers are not a PCI DSS law of nature. Its current merchant-level program uses three merchant levels.
- Discover Level 1: 6 million or more Discover Network transactions annually, certain merchants assigned Level 1 by Discover, or merchants required by another payment brand or acquirer to validate as Level 1.
- Discover Level 2: between 1 million and 6 million Discover Network transactions annually.
- Discover Level 3: all other merchants.
Discover also states that an actual or suspected cardholder-data compromise can lead to a merchant being required to validate at a higher level. So transaction count is a classification input, not an absolute shield against additional validation.

Merchant Level Is Not the Same Thing as SAQ Type
This is probably the most important distinction after the payment-brand issue.
A merchant level describes where you fall within a payment brand’s compliance-validation program. An SAQ type describes the payment environment for which a particular self-assessment questionnaire is designed.
Those are two different axes. “Level 3” does not automatically mean SAQ A. “Level 4” does not automatically mean SAQ D. A Level 2 merchant may use one SAQ while another Level 2 merchant uses a different questionnaire because their payment architectures are different.
| Question | Merchant level | SAQ type |
|---|---|---|
| What mainly determines it? | Payment-brand program, transaction volume, and risk rules | How payment data is accepted, processed, stored, transmitted, or outsourced |
| Examples | Level 1, 2, 3, or 4 | SAQ A, A-EP, B, B-IP, C, C-VT, D and other applicable forms |
| Who controls the framework? | Payment brands and compliance-accepting entities | PCI SSC publishes the questionnaires; eligibility still has to be accepted by the relevant compliance program |
| Does one determine the other automatically? | No | |
The PCI SSC Document Library contains the current PCI DSS v4.0.1 questionnaires and supporting documents. Before starting an SAQ, check every eligibility condition for that questionnaire rather than selecting whichever form contains the fewest questions.
Merchant Level Is Also Not Your PCI DSS Scope
A 50,000-transaction merchant can have a technically complicated cardholder data environment. A merchant processing millions of transactions can sometimes have a tightly designed payment architecture with much of the payment function outsourced.
Merchant level alone does not tell you which systems, networks, applications, people, service providers, or security controls are in scope. It also does not tell you which SAQ you qualify for.
That is why payment-flow mapping comes before questionnaire shopping. Document where customers enter card details, whether cardholder data ever reaches a system you control, where data is stored, which third parties participate in processing, and which systems can affect the security of the payment environment.
Can a Data Breach Change Your Merchant Level?
Yes, depending on the payment brand and compliance program. Merchant-level rules commonly preserve discretion to impose higher validation requirements when risk changes.
Discover expressly notes that a merchant involved in an actual or suspected compromise of Discover cardholder data may be required to validate at a higher level. Mastercard can designate a merchant Level 1 to minimize risk. American Express can assign merchants to Level 1 in its discretion.
That is one reason a business should not build its entire compliance plan around the sentence, “Our transaction count says Level 4.” The organization that accepts your compliance evidence may have more information than the raw transaction number.
What If You Accept More Than One Card Brand?
Most merchants do. That means you should not necessarily add every card transaction together and apply the total to one generic merchant-level table.
Payment brands generally define their classifications using transactions relevant to their own programs. Visa looks at Visa transaction volume. Mastercard uses combined Mastercard and Maestro volume for its thresholds. American Express uses American Express Card transactions.
It is therefore possible for the same business to fall into different numerical levels under different brands. Cross-brand rules can also matter: Mastercard and Discover, for example, include circumstances in which another payment brand’s Level 1 treatment can affect their classification.
Your acquiring bank or payment processor is often the practical coordinator. Ask it which classification governs the compliance submission it expects from you rather than trying to reconcile several brand charts by intuition.
Does Level 1 Mean Compliant and Level 4 Mean Less Secure?
No. Merchant level is not a security grade.
A Level 1 merchant can be non-compliant. A Level 4 merchant can maintain an excellent security program. The number reflects the compliance-validation category assigned under a payment-brand program, not a score for cybersecurity quality.
Think of the merchant level as determining the size and formality of the inspection lane, not the quality of the vehicle arriving for inspection.
Do Level 4 Merchants Have to Comply With PCI DSS?
Yes, when PCI DSS applies to their payment environment. Lower validation volume does not remove the underlying obligation to protect account data.
The confusion comes from mixing up compliance with validation. A payment brand may not require the smallest merchant to send the same documentation directly to the brand that a very large merchant submits. An acquiring bank may instead define how the smaller merchant demonstrates compliance.
The PCI SSC itself says PCI DSS is intended for merchants regardless of size or transaction volume. What varies is how individual payment brands require compliance to be validated and reported.
Threshold Boundaries: Why “About One Million” Is Not Enough
Classification thresholds use exact counts and program-specific language. Rounding a report before comparing it with a threshold can hide the very transaction that changes the result. Preserve the original aggregate totals and ask for confirmation where source summaries overlap or the accepted counting method is unclear.
| Example count | What the published wording tells you | What still needs confirmation |
|---|---|---|
| Mastercard: exactly 6,000,000 total combined transactions | The volume-only Level 2 band includes this endpoint; Level 1 starts above it. | Any cross-brand or discretionary Level 1 assignment. |
| Mastercard: exactly 20,000 e-commerce transactions | The e-commerce limb of Level 3 says more than 20,000, not 20,000 or more. | Total volume, other criteria and acquirer classification. |
| American Express U.S.: exactly 50,000 transactions | The volume band is Level 2, not Level 3. | Applicable account aggregation and any override. |
| Discover: exactly 6,000,000 transactions | The explicit Level 1 rule includes 6 million. Its adjacent Level 2 description is less precise. | Obtain the assigned level rather than treating overlapping wording as permission to select Level 2. |
| Visa: exactly 1,000,000 transactions | Public summaries use differing endpoint language. | Ask the acquirer to identify the governing rule and assigned category. |
These are reading examples, not classifications of a real merchant. They assume the named count has already been calculated using the correct brand, period, channel and entity rules. A threshold example cannot establish whether those inputs are correct.
Build a Merchant-Level Counting Worksheet
Before requesting an assessment quote, ask finance or payment operations for one aggregate record per brand and reporting population. Keep raw cardholder data out of this worksheet. Its purpose is to make the classification inputs traceable, not to create another payment-data store.
Review date / owner: Payment brand / applicable program and market: Merchant role confirmed (not service-provider classification): Entity, merchant accounts and locations included: Reporting period start / end / counting rule: All-channel transaction total for this brand: E-commerce subset where relevant: Source report / export reference / preparer: Treatment of refunds, reversals, retries and duplicate records: Multiple processors / overlap reconciliation: Previous assigned level / current written request: Potential cross-brand or discretionary override: Assigned level confirmed by / date / reference: Required document / assessor or signatory / recipient / deadline: Separate SAQ eligibility and scope decision: Unresolved issue / owner / next review trigger:
Do not assume how authorizations, reversals, refunds or retries count. Record the definition your compliance contact accepts and ask the report owner to reconcile the data to that definition. If two processors supplied overlapping migration-period reports, explain how overlap was handled before adding their totals.
An unresolved counting issue should have a named owner and a due date. “The portal says Level 4” is evidence of a request or label, not proof that the current program rules and your transaction population match. Ask whether the label reflects an acquirer-specific process, an older chart or a current brand assignment.
Worked Example: Seven Million Total Card Transactions
Consider a fictional business with 7 million total card transactions spread across several brands. A combined sales dashboard does not tell you how many were Visa, combined Mastercard/Maestro, American Express or Discover. The total is enough to trigger a review, but it is insufficient to assign a volume-based level for any one brand.
The first useful action is to split the aggregate by brand using the required counting period and population. Then check channel-specific criteria and possible cross-brand overrides. Do not conclude that the business cannot be Level 1 merely because each initial brand subtotal is below a familiar headline threshold; the applicable program can include other designation criteria.
A reviewable internal note might say: “Our sales dashboard shows 7 million transactions across all cards. Brand-specific counts and reporting periods have not yet been reconciled. Finance owns the worksheet; our acquirer will confirm the assigned level and required evidence. SAQ eligibility will be reviewed separately against the payment flow.” This is a fictional example, not a compliance determination.
Repeat the review when growth, acquisitions, entity changes, new payment channels or processor migrations change the inputs. The related payment-provider migration checklist helps document integration changes without confusing a new processor with a new exemption.
How to Determine Your PCI DSS Merchant Level
You can narrow the answer quickly, but the final classification should come from the organization managing your compliance program.
- Confirm that you are being classified as a merchant. Service providers have separate PCI validation categories and should not use merchant-level thresholds.
- Identify each payment brand you accept. Record Visa, Mastercard, American Express, Discover, and any other relevant brand separately.
- Calculate the transaction volumes for each program’s required period. Visa describes a 12-month period; Mastercard specifies the most recent 52 weeks. Follow the applicable rule rather than substituting company revenue, order count or an assumed calendar year.
- Separate e-commerce from other channels where required. Some level definitions specifically depend on e-commerce volume.
- Ask your acquirer or processor for your assigned merchant level. Do this before buying an assessment or compliance package.
- Ask exactly what validation evidence is required. Get the expected SAQ, ROC, AOC, scan, or other deliverable in writing where possible.
- Determine the correct PCI scope and SAQ eligibility separately. Merchant level alone cannot answer those questions.
Five Questions to Send Your Acquirer
If your compliance portal simply says “PCI required” and leaves you staring into the alphabet soup, send these questions to the organization managing your merchant account:
- Which PCI DSS merchant level have you assigned to our business?
- Which payment-brand rules were used to determine that level?
- What PCI DSS validation document must we submit for this reporting period?
- Are we permitted to self-assess, or is QSA, ISA, or other independent validation required?
- Do you require ASV scanning, additional testing, or other evidence beyond the questionnaire or ROC?
Those five answers are more useful than a generic online calculator because they identify the actual compliance-accepting entity, classification, and deliverable.
Common Merchant-Level Mistakes
Mistake 1: Treating the Visa Levels as the PCI SSC Levels
PCI SSC does not publish one universal merchant-level table that overrides every payment brand. The Council publishes the standard and validation tools. The payment brands and acquirers run compliance-validation programs.
Mistake 2: Assuming Level 4 Means Exempt
A lower merchant level usually changes validation expectations, not whether payment data needs protection.
Mistake 3: Choosing an SAQ From Transaction Volume
SAQ eligibility depends heavily on payment architecture. Transaction count and merchant level do not by themselves tell you whether SAQ A, SAQ A-EP, SAQ C, SAQ D, or another questionnaire applies.
Mistake 4: Assuming Level 1 Always Means a QSA Must Perform Everything
Many Level 1 programs involve a formal ROC, but the permitted assessor and signatory arrangements depend on the payment-brand program. Check the rule that actually governs your submission.
Mistake 5: Adding Every Brand’s Transactions Together
Brand-specific transaction volume is often what matters. A company with 7 million total card transactions is not automatically processing more than 6 million Visa transactions or more than 6 million Mastercard and Maestro transactions.
Mistake 6: Using Last Year’s Classification Without Checking
Transaction volumes change, payment architecture changes, contracts change, and brand programs evolve. Treat merchant-level determination as part of the recurring PCI process rather than a permanent label attached to the company.
Which PCI DSS Version Applies Now?
As checked on November 16, 2026, the PCI SSC document library lists PCI DSS v4.0.1. PCI DSS v4.0 was retired at the end of 2024, and the requirements that had future effective dates through March 2025 are now in effect.
That matters because an old merchant-level chart may still show roughly familiar volume thresholds while pointing readers toward outdated questionnaires, outdated technical requirements, or outdated e-commerce assumptions. Use current merchant-level rules and current PCI DSS validation documents together.
Your Next Merchant-Level Review
PCI DSS merchant levels are best understood as validation categories, not four versions of PCI DSS.
Level 1 usually brings the most formal validation process. Levels 2 and 3 commonly use SAQ-based validation where permitted. Level 4 generally captures smaller merchants, but those merchants are not automatically exempt from PCI DSS. And none of those descriptions can replace the rules of the payment brand and acquirer that actually receive your compliance evidence.
Start with three facts: your transaction volume by payment brand, your payment architecture, and the validation document requested by your acquirer or processor. Once those are known, “What PCI level are we?” stops being a foggy compliance question and becomes a much more manageable administrative one.
If there is one action to take today, ask your acquirer this exact question: “What PCI DSS validation documentation do you require from our merchant account for the current reporting period?” That answer is the bridge between a merchant-level chart and the work your business actually needs to complete.
Sources, Review Date and Limits
- Visa AIS program: counting and validation overview.
- Visa June 2026 supplement: the April 25, 2024 consolidation note.
- Mastercard SDP program: current merchant criteria, 52-week period and assessor notes.
- American Express U.S. DSOP: October 2026 policy, Tables 2-1 and 2-2.
- Discover merchant program: classification and reporting guidance.
Editorial review: November 16, 2026. Rechecked the linked primary sources, corrected the Visa tier description and updated the American Express policy edition. Boundary examples, the worksheet and the fictional business scenario are editorial aids. No merchant account, transaction export or actual classification was accessed or verified. Confirm the assigned level, scope and submission requirements with the organization accepting your compliance evidence.