Frequently Asked Question

Can SAQ B-IP be used if cardholder data is transmitted over wireless?
SAQ B-IP is intended for merchants who use PCI PTS-approved point-of-interaction (POI) devices that communicate to the payment processor over an IP-based (Internet Protocol) network. The list of PTS-approved devices can be found here. If a POI device that uses cellular or wireless connections is PTS-approved, and the merchant meets all the eligibility criteria for SAQ B-IP, then SAQ B-IP may be appropriate for that environment. However, merchants should always consult with their acquirer (merchant bank) or the payment brands, as applicable, to determine if their environment is eligible for SAQ B-IP or any other SAQ. Contact details for the payment brands can be found in FAQ #1142.
Each SAQ contains a "Before You Begin" section that provides guidance on the type of environment each SAQ is intended for. Entities must meet all the eligibility criteria for a particular SAQ in order to be eligible to use that SAQ.
Related
-
How should PCI DSS v4.x requirements noted as superseded by another requirement be reported after 31 March 2025?
-
Are providers of third-party scripts for e-commerce environments considered third-party service providers for PCI DSS Requirements 12.8 and 12.9?
-
Why do requirements 8.3.9 and 8.3.10.1 focus on passwords/passphrases used for single-factor authentication, when multi-factor authentication is required for all access into the CDE?
Featured FAQ Articles
Featured
-
Do PCI DSS requirements for keyed cryptographic hashing apply to previously hashed PANs?
-
Is the PCI DSS Attestation of Compliance intended to be shared?
-
How does an entity report the results of a PCI DSS assessment for new requirements that are noted in PCI DSS as best practices until a future date?
-
Where do I direct questions about complying with PCI standards?
-
Can SAQ eligibility criteria be used for determining applicability of PCI DSS requirements for assessments documented in a Report on Compliance?
Most Popular
-
How should PCI DSS v4.x requirements noted as superseded by another requirement be reported after 31 March 2025?
-
Are providers of third-party scripts for e-commerce environments considered third-party service providers for PCI DSS Requirements 12.8 and 12.9?
-
Why do requirements 8.3.9 and 8.3.10.1 focus on passwords/passphrases used for single-factor authentication, when multi-factor authentication is required for all access into the CDE?
-
Do PCI DSS Requirements 8.3.9 and 8.3.10.1 apply to all system components?
-
Is the cardholder in scope for PCI DSS?
Most Recently Updated
-
How should PCI DSS v4.x requirements noted as superseded by another requirement be reported after 31 March 2025?
-
Are providers of third-party scripts for e-commerce environments considered third-party service providers for PCI DSS Requirements 12.8 and 12.9?
-
Why do requirements 8.3.9 and 8.3.10.1 focus on passwords/passphrases used for single-factor authentication, when multi-factor authentication is required for all access into the CDE?
-
Do PCI DSS Requirements 8.3.9 and 8.3.10.1 apply to all system components?
-
Is the cardholder in scope for PCI DSS?