Skip to content
SwipeSeal
Menu

PCI Merchant Level Calculator

There is no single PCI level. Each card brand sets its own, from how many of its transactions you take in a year. Enter your counts per brand to see the level each one publishes, why you land there and what it asks you to send. Where a brand publishes no thresholds, the answer is to ask your acquirer.

Key figures

Brands with published thresholds3 of 4

Dithered print of three receipt stacks of different heights beside a card terminal

What a PCI merchant level is

A merchant level is a card brand's label for how much of its card traffic you handle, and it decides how you prove PCI compliance each year. The PCI Security Standards Council writes the standard, but each card brand runs its own program: “which entities need to validate compliance, validation levels, whether an entity is eligible to complete a Self-Assessment Questionnaire (SAQ) or must complete a Report on Compliance (ROC), and any fines or penalties.”

Your acquirer assigns your merchant level from your yearly card volume for each card brand. Visa, Mastercard and Discover set their own thresholds; ask your acquirer which level you are. Of the 4 brands here, 3 print their thresholds on their own sites, and those are the only ones this calculator applies. Visa's page says your total Visa volume over 12 months sets your level and publishes no numbers, so its line always reads “ask your acquirer”.

How to use the calculator

  1. Pull 12 months of processor statements or your gateway's report, split by card brand. Count transactions, not money: every level threshold here is a number of transactions.
  2. Enter each brand's yearly total across every channel. For Visa and Mastercard, also enter how many of those were e-commerce; Mastercard's Level 3 is counted on e-commerce alone.
  3. Read each brand's level, why it landed there, and what that brand asks you to send.
  4. Copy or print the receipt and take it to your acquirer. Then find your questionnaire with the SAQ type finder.

Worked example: a shop with a till and a web store

The calculator opens on this shop. Its counts are made up for the example; the thresholds are the brands' own. The shop lands on the same level number with every brand that publishes one, each for its own reason, and Visa gives no number at all.

Swipe sideways for the result

The example shop walked through each brand's table
BrandShop's yearly countLine it meetsResult
Visa180,000 total, 60,000 onlineNo thresholds publishedAsk your acquirer
Mastercard90,000 total, 30,000 onlineTotal under 1 million; online over 20,000Level 3
American Express12,00010,000 to fewer than 50,000Level 3
Discover4,000All other merchantsLevel 3

Strictest published levelLevel 3

Mastercard is the one to watch: this shop's Mastercard total is far below one million, but its online sales alone pass 20,000, and that is Mastercard's Level 3 test. A shop with the same total and fewer web orders would be Level 4.

What your level means for validation

Depending on the card brands' programs, an entity either has a detailed assessment documented in a Report on Compliance or self-assesses with an SAQ. An AOC goes with either one, and “Quarterly submission of an ASV scan report … may also be required.” In practice, Level 1 with a brand that publishes levels means a ROC; the lower levels mean an SAQ, sometimes only when the brand asks.

“PCI SSC does not define compliance requirements for any organization or set compliance validation responsibilities … Compliance validation requirements are set by brands, acquirers, payment facilitators, etc.” Before you start an SAQ, confirm with the organization you submit it to (usually your acquirer, the merchant bank) that you are eligible for it.

Programs that can lighten the paperwork

Visa's Technology Innovation Program can remove the requirement to verify PCI DSS compliance “when at least 75% of yearly transactions originate through EMV chip-enabled terminals, a validated point-to-point encryption solution or integrated industry-standard tokenization solution meeting EMVCo Tokenization Specification.” Eligibility is Visa's and the acquirer's call.

Discover runs a similar Security Compliance Innovation Program for merchants that, among other criteria, have “met at least 75% of merchant’s transactions originated from using security technologies” such as chip terminals, a validated P2PE solution or EMVCo tokenization. Merchants with an outside acquirer ask that acquirer whether they qualify.

Where each brand says so

Each brand's table, in its own terms, as read on its own site. Mastercard also puts a merchant at Visa's level when it meets Visa's criteria, and Discover puts any merchant another brand or acquirer treats as Level 1 at its own Level 1; the calculator applies the second rule when your Mastercard or American Express count makes you Level 1.

Swipe sideways for every level

Merchant level thresholds as each card brand publishes them
BrandLevel 1Level 2Level 3Level 4
VisaVisa transactions over 12 months (credit, debit and prepaid)Ask your acquirerAsk your acquirerAsk your acquirerAsk your acquirer
MastercardCombined Mastercard and Maestro transactions a year; Level 3 counts e-commerce onlyMore than 6 million totalMore than 1 million, up to 6 million totalMore than 20,000, up to 1 million e-commerceAll other merchants
American ExpressAnnual American Express card transactions2.5 million or more50,000 to fewer than 2.5 million10,000 to fewer than 50,000Fewer than 10,000
DiscoverCard transactions a year on Discover Network6 million or moreBetween 1 million and 6 millionAll other merchantsNo Level 4

Visa's own rulebook says acquirers report their merchants' PCI DSS status to Visa “at least every 6 months” and that “The criteria for each Merchant’s level is set out in the Account Information Security (AIS) Program Guide,” which is not linked from Visa's compliance page. That is why the Visa line asks your acquirer.

After you know your level

Your level tells you what to send; your SAQ type tells you what to answer. The yearly PCI compliance loop puts the two in order, and if a ROC or an assessor is now on the cards, the PCI compliance cost calculator adds up what that year costs you. A PCI non-compliance fee on a merchant statement comes from the acquirer or processor under its card-brand program, never from the PCI Security Standards Council; PCI compliance fees explained covers who bills what.

Sources

  1. Mastercard: Site Data Protection program and PCI (What merchants need to know) (mastercard.com), read on 2026-10-22
  2. American Express: Data Security Operating Policy, U.S. (October 2026), Tables 2-1 and 2-2 (americanexpress.com), read on 2026-10-22
  3. Discover Global Network: Determining your merchant level, validation and reporting requirements (discoverglobalnetwork.com), read on 2026-10-22
  4. Visa: Security and compliance (corporate.visa.com), read on 2026-10-22
  5. Visa Core Rules and Visa Product and Service Rules (April 2026), section 12.5.1.2 (corporate.visa.com), read on 2026-10-22
  6. PCI DSS v4.x Quick Reference Guide (Jan 2025) (docs-prv.pcisecuritystandards.org), read on 2026-10-22
  7. PCI SSC blog: updates for merchants validating to SAQ A (30 Jan 2025) (blog.pcisecuritystandards.org), read on 2026-10-22
  8. SAQ Instructions and Guidelines v4.0.1 r1 (Apr 2025) (docs-prv.pcisecuritystandards.org), read on 2026-10-22
  9. PCI SSC glossary (pcisecuritystandards.org), read on 2026-10-22
  10. PCI SSC: At a Glance, Role of the PCI Security Standards Council (listings.pcisecuritystandards.org), read on 2026-10-22