Every business that accepts a card already has a PCI-DSS level, whether it has looked it up or not. The level is not something you choose; it is set by how many transactions you process and confirmed by your acquiring bank, and the costliest compliance mistakes come from companies that simply guessed wrong.
As the FinTech Engineering Lead at Acquaint Softtech, a software product development partner, I help teams find their real level and build payment applications that can prove it.
Short answer: there are four PCI-DSS merchant levels, from Level 1, over 6 million transactions a year and the most scrutiny, down to Level 4, the smallest merchants. Your level decides how you must prove compliance, from a self-assessment questionnaire at the lower levels to a full on-site audit at Level 1. This guide explains all four and how to find yours.
The rules here follow the PCI Security Standards Council and the card brands’ published programs. This guide draws on secure, regulated platforms Acquaint Softtech has built as an Official Laravel Partner, with 1,300+ projects, 70+ in-house engineers, and clients across the USA, UK, Europe, and Australia who deploy dedicated teams within 48 hours of a brief.
What PCI-DSS compliance levels are
PCI-DSS, the Payment Card Industry Data Security Standard, is the mandatory security standard for any business that stores, processes, or transmits card data. The four compliance levels sort merchants by annual card volume, from the largest at Level 1 to the smallest at Level 4.
The important nuance is that the level does not change what security you must have; every merchant must meet the same standard. The level changes how you prove it. The current version is PCI-DSS v4.0.1, whose once future-dated requirements have been mandatory since 31 March 2025, so 2026 is the first full assessment cycle on the complete standard.
The four merchant levels, side by side
The table below is the fastest way to place yourself. Levels are based on annual transactions across all channels, and the validation each requires steps up sharply from Level 4 to Level 1.
| Level | Annual card transactions | How you validate |
| Level 1 | Over 6 million (or after a breach) | On-site audit, ROC by a QSA, quarterly ASV scan, AOC |
| Level 2 | 1 million to 6 million | Annual SAQ, quarterly ASV scan, AOC |
| Level 3 | 20,000 to 1 million e-commerce | Annual SAQ, quarterly ASV scan |
| Level 4 | Under 20,000 e-commerce (up to 1M total) | Annual SAQ, ASV scan as the acquirer requires |
Two quotable facts anchor the tiers. Level 1 begins at more than 6 million transactions a year, and a data breach escalates any merchant to Level 1 regardless of size, which is why small merchants are not as low-risk as they assume.
How your level is actually decided
Your acquiring bank assigns your level, per card brand, based on a rolling twelve months of transactions across every channel. The card brands, not the PCI Council, define the thresholds, and your acquirer can escalate you above them for a high-risk profile or after an incident.
A current nuance trips up many guides: effective April 2024, Visa consolidated Levels 3 and 4 into a single Level 3, while Mastercard kept all four. The same small merchant can therefore be a Visa Level 3 and a Mastercard Level 4 at the same time. American Express, meanwhile, sets its Level 1 at 2.5 million transactions rather than 6 million, so you should confirm your level separately for each brand you accept.
See also: How Flat Roof Coatings Can Help Prevent Leaks and Extend the Life of Commercial Roofing Systems
SAQ types: the validation path for your app
A Self-Assessment Questionnaire (SAQ) is how lower-level merchants validate compliance, and which one you use depends entirely on how your application handles card data. Choosing the wrong SAQ is one of the most common and costly compliance errors.
| SAQ type | When it applies |
| SAQ A | Fully outsourced e-commerce; a hosted page or redirect, no card data on your systems |
| SAQ A-EP | E-commerce where your page affects the payment but you do not store card data |
| SAQ C-VT | Manual entry through a virtual terminal, one transaction at a time |
| SAQ C | A payment application connected to the internet, with no card data storage |
| SAQ D | You store card data, or you are a service provider; the most demanding |
Here is the classic trap. A merchant signs SAQ A because its website redirects to a hosted payment page, but staff also key phone orders into a virtual terminal. That second channel is really SAQ C-VT, so the easy self-assessment was never valid, and a single missed channel can undo the whole attestation.
Payment applications and the Secure Software Framework
If you build or sell payment software, the old standard for it is gone, and most level guides never mention this. PA-DSS, the Payment Application Data Security Standard, was retired on 28 October 2022 and replaced by the PCI Software Security Framework (SSF).
The SSF is made up of two standards, the Secure Software Standard and the Secure Software Lifecycle (Secure SLC) Standard. It is outcome-based rather than checklist-based, which lets it support modern, frequently updated software instead of the slow release cycles PA-DSS assumed. If your product processes payments, this framework, not the retired PA-DSS, is what a validated listing now comes from.
How to reduce your PCI scope and cost
The cheapest compliance is the smallest cardholder data environment, so the goal is to touch as little card data as possible. Every system that sees a raw card number is in scope, so keeping that data out of your servers can move you from the heavy SAQ D toward the light SAQ A.
- Tokenize and outsource capture: use hosted fields or a redirect so card data never reaches your backend.
- Segment the network: isolate any system that does touch card data from the rest of your platform.
- Store nothing sensitive: never keep the full card number or the security code, ever.
This scope reduction is architectural, which makes it disciplined backend development work rather than a paperwork exercise, and it is the single highest-leverage decision for lowering both audit effort and breach risk.
How to get compliant and stay that way
Compliance is a continuous state, not a once-a-year certificate. The path is to confirm your level with your acquirer, choose the correct SAQ or engage a QSA, close the gaps, run quarterly ASV scans, and keep evidence current all year rather than scrambling before the assessment.
Deciding your scope, your validation path, and your target architecture is a strategic call as much as a technical one, which is where a virtual CTO earns its place, mapping the cheapest compliant route before a single control is built. Getting that plan right up front is what turns an annual audit into a formality instead of a fire drill.
Proof: secure engineering for a bank
Acquaint Softtech embedded an engineering squad inside Ameriabank CJSC, a leading financial and technology company in Armenia, to strengthen its customer-facing platforms and transaction monitoring. This account is drawn from the client’s verified Clutch review, which rated the work 5.0 for quality, schedule, and cost.
A specialist group moved the bank’s transaction monitoring from static rules to a behavior-based scoring system, built data pipelines that turned transaction streams into risk signals, and gave compliance teams internal dashboards to review flagged activity with real context. The team also hardened the API layers that carried data between services.
All of it landed inside a live banking system that customers used daily, with no disruption to service. The client highlighted the balance of performance, security, and usability, which is exactly the discipline PCI-DSS is meant to enforce: strong security that does not break the product it protects.
Short answers to common questions
How do I know which PCI-DSS level I am?
A: Count your card transactions per brand over a rolling twelve months across all channels, then confirm with your acquiring bank, which makes the final call. Over 6 million is Level 1; under 20,000 e-commerce is the lowest tier.
What is the difference between the levels?
A: All levels must meet the same PCI-DSS standard; the level only changes how you prove it. Level 1 needs an on-site audit by a QSA, while Levels 2 to 4 can validate with a self-assessment questionnaire and ASV scans.
Which SAQ should a payment application use?
A: It depends on how you handle card data. Fully outsourced checkout uses SAQ A, a virtual terminal uses SAQ C-VT, and storing card data or being a service provider means SAQ D. Match the SAQ to every payment channel you run.
Does a small business really need to comply?
A: Yes. Every merchant that accepts cards must comply in full, whatever its level. Small merchants are targeted precisely because controls are assumed to be weak, and a breach escalates any business to Level 1.
Is PA-DSS still the standard for payment software?
A: No. PA-DSS was retired on 28 October 2022 and replaced by the PCI Software Security Framework, made up of the Secure Software Standard and the Secure Software Lifecycle Standard. New payment software validates against the SSF.
How can I lower my PCI compliance burden?
A: Reduce scope by touching less card data. Use tokenization and a hosted payment page so card data never hits your servers, and segment any system that does. This can move you from the demanding SAQ D toward the simple SAQ A.



