Merchant Levels and PCI Validation Requirements | Redscan
Contact Us

Contact Us

Please get in touch using the form below

1000 characters left
View our privacy policy

Overview

Understand your route to PCI DSS compliance

To understand how the PCI DSS applies to your organisation, it’s important to refer to each card payment brand’s PCI validation requirements.

As a general rule, merchants and service providers will fall into one of four levels, based on the annual volume of card data transacted. Categorisation will affect the minimum standards expected and the requirement to complete either a Self-Assessment-Questionnaire (SAQ) or Reports on Compliance (ROC). All level one merchants and service providers – organisations that process millions of transactions annually – are required to undergo an onsite assessment.

The SAQ varies and it is important to choose the most appropriate version for the payment scenario.

PCI SAQs

Which PCI SAQ is right for your organisation?

Merchants are encouraged to contact their merchant bank (acquirer) or the applicable payment brand(s) to identify the appropriate SAQ based on their eligibility. The main PCI SAQ types are listed below:

PCI SAQ A

Card-not-present merchants (e-commerce or mail/telephone-order) that have fully outsourced all cardholder data functions to PCI DSS-validated third-party service providers and do not store, process or transmit cardholder data on in-house systems or premises.

PCI SAQ A-EP

E-commerce merchants who outsource all payment processing to PCI DSS-validated third parties, and who have a website(s) that doesn’t directly receive cardholder data but that can impact the security of the payment transaction. No electronic storage, processing, or transmission of any cardholder data on the merchant’s systems or premises.

PCI SAQ B

Merchants using imprint machines with no electronic cardholder data storage; and/or standalone, dial-out terminals with no electronic cardholder data storage.

PCI SAQ B-IP

Merchants using only standalone, PTS-approved payment terminals with an IP connection to the payment processor, with no electronic cardholder data storage. Not applicable to e-commerce channels.

PCI SAQ C

Merchants with payment application systems connected to the internet that electronically store cardholder data.

PCI SAQ C-VT

Merchants who manually enter a single transaction at a time via a keyboard into an Internet-based virtual terminal solution that is provided and hosted by a PCI DSS-validated third-party service provider. No electronic cardholder data storage.

PCI SAQ P2PE-HW

Merchants using only hardware payment terminals that are included in and managed via a validated, PCI SSC-listed P2PE solution, with no electronic cardholder data storage.

PCI SAQ D

Includes merchants not covered by any other SAQ types as well as service providers defined by a payment brand as eligible to complete a SAQ.

More

More about PCI DSS compliance

For more information about PCI DSS compliance:

Get in touch

Complete the form for a prompt response from our team.

Two Redscan team members analysing cyber security intelligence

1000 characters left
View our privacy policy

Resources

Discover our latest content and resources

From the blog
From the blog Case studies Latest news
UK finance sector exposed by third-party risk management gaps
A new report has identified significant gaps in financial services third-party risk management strategies, with almost half of these organizations only assessing third-party risk at the initial supplier onboarding stage.  
58% of ransomware victims forced to shut down operations
A new report by the Ponemon Institute has revealed that more than half of organisations affected by ransomware in 2024 had to shut down operations to recover, representing a significant increase from its previous report in 2021.  
73% of UK education sector impacted by cyber-attacks in past five years
New research confirms that the UK education sector continues to be a key target for cyber-attacks, with 73% of institutions having experienced at least one cyber-attack or breach in the past five years.  
DORA compliance costs exceed €1m for many UK and EU companies
New research has shown that compliance with the EU's new Digital Operational Resilience Act (DORA) has cost many businesses more than €1m over the last 24 months.