Site icon RSI Security

PCI DSS by Business Type: E-Commerce, Retail, Phone, and Providers

PCI DSS v4.0.1 is one standard, and your payment channel shapes how it applies. E-commerce merchants focus on payment page scripts, retailers on terminals, phone-based businesses on spoken and recorded card data, and service providers on added requirements.

If you are unsure PCI DSS applies at all, start with who needs it.

E-commerce merchants

Is compliance mandatory?

PCI DSS applies to any business that accepts participating brands’ payment cards, including online. Payment brands and acquirers decide whether a specific entity must comply or validate. Outsourcing checkout does not end your responsibility, so ask your acquirer what it expects.

SAQ A vs SAQ A-EP

Your website’s role in the payment decides which Self-Assessment Questionnaire (SAQ) may fit.

Question SAQ A SAQ A-EP
Outsourcing All account data functions All processing except the payment page
Your website No electronic account data on merchant systems Receives no account data, but affects transaction security
Payment page elements Only and directly from a compliant provider From your website or a compliant provider
6.4.3 and 11.6.1 Not included Included

Merchants that accept account data on their own website may need SAQ D for Merchants. Your acquirer or payment brand makes the final call.

Requirements 6.4.3 and 11.6.1

Both became mandatory after 31 March 2025. Requirement 6.4.3 covers payment page scripts in the consumer’s browser. Confirm each is authorized, assure its integrity, and keep a justified inventory.

Requirement 11.6.1 calls for a change- and tamper-detection mechanism. It alerts personnel to unauthorized changes in security-impacting HTTP headers and script contents. It runs at least weekly or at a frequency set by a targeted risk analysis under Requirement 12.3.1.

With an iframe, you manage scripts on your page, and the provider manages scripts inside its iframe. With a redirect, you manage scripts on the page that includes the redirect. In a single-page application, both requirements apply to all views.

SAQ A eligibility changes

SAQ A changed in January 2025. PCI SSC removed Requirements 6.4.3, 11.6.1, and 12.3.1 from the questionnaire. It added an eligibility criterion for e-commerce merchants. You confirm your site is not susceptible to attacks from scripts that could affect your e-commerce systems.

If you cannot make that confirmation, SAQ A does not fit.

Retail and card-present merchants

SAQ A does not apply to face-to-face channels. Options depend on your equipment:

Requirement 9.5.1 covers physical devices. Keep a list, inspect them periodically for tampering or substitution, and train staff to report suspicious behavior.

Phone-based businesses

No SAQ is specific to phone orders. SAQ A can fit completely outsourced mail and telephone orders. SAQs B, B-IP, C, C-VT, and P2PE can also cover telephone orders when their criteria are met.

Watch for card data in audio recordings, which PCI DSS names as an often-overlooked storage location. Requirement 3.3.1 prohibits storing sensitive authentication data after authorization, even if encrypted. Outsourced contact centers belong on your provider list under Requirement 12.8.1.

Service providers

Some requirements apply only to service providers:

Multi-tenant providers also have Appendix A1. SAQ D for Service Providers is the only SAQ option, and only for those a payment brand defines as eligible.

Find a starting point

If you are or use… Likely starting point Why
Service provider handling account data for others SAQ D for Service Providers Only for service providers a payment brand defines as eligible. Others report through a ROC, so confirm with the payment brand or your acquirer.
Merchant that stores account data electronically SAQ D for Merchants The other merchant SAQs exclude electronic storage of account data. SAQ D covers all applicable requirements.
E-commerce: site redirects to, or embeds, a provider page or iframe SAQ A For merchants that fully outsource all account data functions, where every element of the payment page comes only and directly from a compliant provider. SAQ A also has an eligibility criterion about script attacks, so check it closely.
E-commerce: your site hosts the form, but the browser sends card data directly to the provider SAQ A-EP Your website doesn’t receive account data but controls how it reaches the provider, so it can affect the security of the transaction.
E-commerce: card data reaches your server, and you pass it on SAQ D for Merchants Merchants that accept account data on their website don’t meet the SAQ A or SAQ A-EP criteria.
Mail or phone orders, fully outsourced to a provider SAQ A For card-not-present merchants that fully outsource all account data functions to PCI DSS compliant providers.
Terminal on the PCI-listed validated P2PE list SAQ P2PE All payment processing runs through a validated, PCI-listed P2PE solution. Phone or mail orders may qualify when keyed directly and only into those terminals.
Phone or tablet with a PCI-listed SPoC solution (in person only) SAQ SPoC Card-present only, using a validated software-based PIN entry solution with a secure card reader. Excludes phone and mail orders, e-commerce, and unattended payments.
Standalone, PCI-listed terminal with its own IP connection SAQ B-IP Only standalone, PCI-listed PTS devices with their own IP connection to the processor, not connected to other merchant systems. Card readers that pair with a phone or computer don’t qualify.
Imprint machines or a dial-out terminal SAQ B Only imprint machines or standalone dial-out terminals, with no electronic storage.
Typing cards into a provider website (virtual terminal) on an isolated computer SAQ C-VT Only keying single transactions into a third-party virtual terminal on an isolated computing device, with no attached card readers.
Payment application on an internet-connected system SAQ C A single location with payment application systems connected to the internet, isolated from other merchant systems, and no electronic account data storage. If locations connect to each other, SAQ D may apply.
Integrated or networked terminals, or not sure SAQ C or SAQ D Ask your acquirer which applies.
More than one of these channels Ask your acquirer Many SAQs require that channel to be your only one. SAQ D applies if you meet no other SAQ criteria.

This is a starting point only. Each SAQ has its own eligibility criteria, and your acquirer or payment brand has the final say on how you validate.

Frequently asked questions

Is PCI compliance mandatory for e-commerce merchants?
PCI DSS applies to merchants that accept payment cards bearing participating brand logos. Whether a specific entity must comply or validate is set by payment brands and acquirers, so confirm your obligations with your acquirer.
What is the difference between SAQ A and SAQ A-EP?
SAQ A fits merchants that completely outsource account data functions, with every payment page element coming directly from a compliant provider. SAQ A-EP fits e-commerce merchants whose websites do not receive account data but do affect transaction security.
Do Requirements 6.4.3 and 11.6.1 apply if we use an iframe?
They apply to scripts on your page that includes the provider’s iframe. The provider manages scripts inside its iframe, and your SAQ type affects how you report this.
Can a service provider complete an SAQ?
Only if a payment brand defines it as eligible. SAQ D for Service Providers is the only SAQ option for service providers.

Work with RSI Security

RSI Security is a PCI Qualified Security Assessor (QSA) company and an Approved Scanning Vendor (ASV). It performs PCI DSS assessments and quarterly ASV scans. Organizations that need help with scoping or readiness can work with RSI Security through a separate advisory engagement. RSI Security provides either advisory or assessment to a given client, never both.

Schedule a PCI DSS assessment · Talk to an advisor about readiness

Sources

Request a consultation

Exit mobile version