PCI Compliance and ASV Scans with Stripe
If you take payments on your own website with Stripe, you need a quarterly ASV scan of that website, whichever Stripe integration you use. The PCI Security Standards Council says so plainly for sites that redirect to a payment provider or embed its payment form. What your Stripe integration does decide is which SAQ you fill out, and how much of your payment page security falls on you. Here is how each option works out.
Stripe Checkout: a redirect to Stripe's page
With Stripe Checkout, or a Payment Link, your customer leaves your site and types their card into a page Stripe hosts. That usually means SAQ A, the shortest questionnaire. Your website is still in scope for the quarterly ASV scan, because it is the page that sends customers to Stripe, and a hacked site could send them somewhere else instead. The SAQ A rule about scripts on your page does not apply to a redirect. If you use embedded Checkout, which shows Stripe's form inside your own page, treat it like Elements below.
Stripe Elements and the Payment Element: Stripe's fields on your page
Elements puts Stripe's card fields into your own checkout page, inside frames that Stripe hosts. Stripe maps this to SAQ A as well, because the card is typed into Stripe's frames rather than your form. There is one extra step. SAQ A asks merchants whose page embeds a payment provider's frame to confirm the page is not open to attacks from scripts. The Council's guidance gives two ways. One is the techniques in requirements 6.4.3 and 11.6.1: know which scripts run on your checkout page and notice when they change. The other is confirmation from the payment provider. The quarterly ASV scan of your site applies here too.
Your own card form: SAQ A-EP or SAQ D
If your page builds its own card fields and sends the details to Stripe from the browser, as older Stripe.js integrations did, you are usually under SAQ A-EP. If card numbers pass through your server at all, for example by posting them to Stripe's API from your own code, you are in SAQ D, the full questionnaire. Both include the quarterly ASV scan, and both put the payment page scripts squarely on you.
What to scan
Scan the public domain and IP address of every server that delivers your checkout page or the page that links to it. If your site sits behind Cloudflare or another CDN, scan the real server too, and read our note on ASV scans behind Cloudflare. Our guide to which IP addresses to scan covers staging sites, subdomains and shared hosting.
Confirming your SAQ with Stripe
Stripe asks each account to confirm its PCI DSS compliance in the Dashboard, and it suggests the SAQ that fits your integration. Use that as your starting point, check it against our SAQ guide, and keep the result with your passing scan reports. If someone other than Stripe processes some of your payments, they may ask for the same paperwork.
Common questions
Does Stripe make me PCI compliant?
No. Stripe is a PCI DSS Level 1 service provider and keeps its own systems compliant, which makes your part much smaller. You still confirm your own compliance, usually with an SAQ each year and, for a website that takes payments, a passing ASV scan every quarter.
Do I need an ASV scan if I only use Stripe Checkout?
Yes. SAQ A includes requirement 11.3.2, and the PCI Security Standards Council says that covers merchant websites that redirect customers to a payment provider. The scan covers your site, not Stripe's.
Is the Payment Element SAQ A or SAQ A-EP?
Stripe maps Elements, including the Payment Element, to SAQ A, because the card fields are frames Stripe hosts. You also have to confirm your checkout page is not open to attacks from scripts. If you are unsure, check the SAQ Stripe suggests in your Dashboard and ask your bank.
What about Stripe on Shopify, Wix or Squarespace?
Then the platform's checkout decides your SAQ, not Stripe. See our guides for Shopify, Wix and Squarespace. For WooCommerce with a Stripe plugin, see PCI scanning for WooCommerce.
Do I need payment page monitoring with Stripe Elements?
Not necessarily, but you need some way to stand behind it. You have to confirm your checkout page is not open to script attacks, and Stripe's Dashboard asks you to confirm you have set up a Content Security Policy following Stripe's guidance. Keeping track of the scripts on the page, and noticing when they change, is how you know that policy still holds. You can do that by hand or with a tool. Our payment page monitoring checks the page every day and keeps a dated record of every script.
Scanning a Stripe site with ServerScan
ServerScan scans each IP address or domain for $59 a quarter or $188 a year. That includes unlimited rescans while you fix things, help reading the report, SAQ forms with guidance on choosing one, and the Attestation of Scan Compliance your bank asks for. Most sites can run their first scan the same day they sign up.