Best Compliance Software

Practical guide · November 16, 2026

SAQ A script-attack eligibility: embedded forms versus redirects

PCI SSC’s updated SAQ A guidance distinguishes an embedded payment form from a redirect for a specific eligibility criterion concerning script attacks. A merchant page containing a processor’s embedded form or iframe needs attention even when the processor handles payment collection. A redirect is treated differently under that criterion; it is not a blanket exemption from PCI obligations.

PCI SSC explains this distinction in its FAQ on SAQ A v4.0.1 r1 eligibility. The organization accepting your compliance submission should confirm which SAQ fits your implementation. PCI SSC FAQ 1588

Identify the payment journey before choosing the form

Illustrative checkout review: A merchant operates two storefronts.

Storefront What the buyer sees What the merchant should establish
Store A Payment fields appear inside the merchant’s page through a processor iframe Whether the implementation meets the script-attack eligibility criterion for embedded forms
Store B The buyer leaves the merchant page for the processor’s payment page Whether the actual flow is a redirect and whether all other SAQ A eligibility criteria are met

A checkout’s branding does not settle the question. Ask the implementer to document where payment fields are served from, what loads on the merchant page and where the buyer goes to enter payment information. Include alternative payment paths and mobile layouts in that review.

What evidence can support the embedded-form criterion?

PCI SSC describes approaches including protections using techniques such as those in PCI DSS Requirements 6.4.3 and 11.6.1, or confirmation from the compliant payment provider that its solution protects the merchant payment page against script attacks when implemented as instructed. The guidance does not mean every merchant can simply collect a generic provider compliance badge. PCI SSC’s explanation of the criterion

A useful request to the processor is:

We use your embedded checkout on these storefronts. Please identify the supported integration, the implementation conditions for your script-attack protection and the documentation we should retain for our SAQ A eligibility assessment.

That is an original request template. It is not PCI SSC’s wording or a promise that the processor will provide sufficient evidence.

Keep a short implementation record

Record the checkout version, integration instructions, responsible developer, evidence supplied by the processor and the date the implementation was checked against those instructions. Note custom scripts and integrations for the reviewer to evaluate instead of assuming they are harmless.

For the fictional Store A, “the provider is PCI compliant” leaves the implementation question unanswered. “Our developer confirmed the deployed integration matches the provider’s documented conditions, and the accepting entity reviewed our SAQ choice” is a more useful record—if those actions actually happened.

For Store B, preserve evidence of the redirect flow and assess the remaining criteria. Do not copy Store A’s conclusions across both stores merely because they use the same processor.

Before submitting an SAQ, take the documented payment flow and remaining questions to the entity accepting the submission. Revisit the assessment when the checkout integration changes.

Research basis: PCI SSC’s published FAQ, reviewed November 16, 2026. Examples and evidence-request wording are editorial aids, not an eligibility determination.