Frequently Asked Question
How is the payment page determined for SAQ A merchants using iframe?
To be eligible for SAQ A, all elements of the payment page delivered to the consumer's (cardholder's) browser must originate only and directly from a PCI DSS validated third-party service provider(s). The term "payment page" refers to a collection of web elements used to collect and/or process payment card data. Payment pages can exist as a standalone web page or be embedded into another web page using iframe.
An iframe can appear as a section within a larger web page or it could be sized to encompass the entire web page. Where an iframe encompasses the entire web page, all content is typically delivered via the iframe. Where an iframe appears as a section of a larger web page, content is delivered via the iframe and also via the web page on which the iframe resides.
Payment pages can be as simple as input fields collecting payment information, or they could also be used to display additional information, such as the list of items being purchased, shipping information, and promotional materials. All web elements located within the same iframe as elements associated with payment card data are considered part of the payment page.
Where the payment page is embedded within an iframe on a page on the merchant's website, all fields and web elements associated with capturing payment card data must be contained within the iframe to be eligible for SAQ A. If any element involved in the collection or processing of payment card data is present on or provided by the merchant website, the merchant is not eligible for SAQ A.
Web page elements that are unrelated to the capture of payment card data, and that exist on the merchant website outside of the iframe, are not considered part of the payment page. SAQ A may therefore be used where the merchant website delivers content unrelated to the payment process, as long as all elements of the payment page originate from a compliant service provider via an embedded iframe, and all other SAQ eligibility criteria are met.
An iframe can appear as a section within a larger web page or it could be sized to encompass the entire web page. Where an iframe encompasses the entire web page, all content is typically delivered via the iframe. Where an iframe appears as a section of a larger web page, content is delivered via the iframe and also via the web page on which the iframe resides.
Payment pages can be as simple as input fields collecting payment information, or they could also be used to display additional information, such as the list of items being purchased, shipping information, and promotional materials. All web elements located within the same iframe as elements associated with payment card data are considered part of the payment page.
Where the payment page is embedded within an iframe on a page on the merchant's website, all fields and web elements associated with capturing payment card data must be contained within the iframe to be eligible for SAQ A. If any element involved in the collection or processing of payment card data is present on or provided by the merchant website, the merchant is not eligible for SAQ A.
Web page elements that are unrelated to the capture of payment card data, and that exist on the merchant website outside of the iframe, are not considered part of the payment page. SAQ A may therefore be used where the merchant website delivers content unrelated to the payment process, as long as all elements of the payment page originate from a compliant service provider via an embedded iframe, and all other SAQ eligibility criteria are met.
Originally published: September 2016
Article Number: 1438
Related
-
What evidence is a TPSP expected to provide to customers to demonstrate PCI DSS compliance?
-
Does PCI SSC consider guidance from other standards organizations when making updates to PCI standards?
-
If an organization provides software or functionality that runs on a consumer's device (for example, smartphones, tablets, or laptops) and is used to accept payment account data, can the organization store card verification codes for those consumers?
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
-
What evidence is a TPSP expected to provide to customers to demonstrate PCI DSS compliance?
-
Does PCI SSC consider guidance from other standards organizations when making updates to PCI standards?
-
If an organization provides software or functionality that runs on a consumer's device (for example, smartphones, tablets, or laptops) and is used to accept payment account data, can the organization store card verification codes for those consumers?
-
Do PCI DSS requirements for keyed cryptographic hashing apply to previously hashed PANs?
-
Can a compensating control be used for requirements with a periodic or defined frequency, where an entity did not perform the activity within the required timeframe?
Most Recently Updated
-
How does encrypted cardholder data impact PCI DSS scope for third-party service providers?
-
Does PCI SSC provide a list of PCI DSS-compliant third-party service providers?
-
How does encrypted cardholder data impact PCI DSS scope?
-
What effect does the use of a PCI-listed P2PE solution have on a merchant's PCI DSS validation?
-
Are Mobile Payments on COTS (MPoC)™ solutions, Software-based PIN Entry on COTS (SPoC)™ solutions, or Contactless Payments on COTS (CPoC™) solutions eligible for a P2PE Solution approval?