If your own website takes payments through PayPal, you need a quarterly ASV scan of that website, whichever PayPal option you use. The PCI Security Standards Council says that covers sites that send customers to a payment provider or embed its payment form. What your PayPal setup changes is which SAQ you fill out, and whether the scripts on your checkout page become your responsibility. Here is how each common setup works out.

PayPal buttons: the customer pays on PayPal

With the standard PayPal buttons, the customer usually clicks through to PayPal, in a pop-up window or a new page, and logs in or types their card there. If customers only ever pay in PayPal's window or on PayPal's site, that counts as a redirect, and it usually means SAQ A. Your website is still in scope for the quarterly ASV scan, because it is the page that sends customers to PayPal. Some setups also let customers type a card into a form that opens on your own page under the buttons. If yours does, treat it like the card fields below.

PayPal card fields on your own checkout

PayPal also offers card fields that appear inside your checkout page but are hosted by PayPal, so the card number is typed into PayPal's frames, not your form. Under the Council's rules, fields a provider hosts in frames on your page can qualify for SAQ A, with one extra step: you must confirm the page is not open to attacks from scripts, either with the techniques in requirements 6.4.3 and 11.6.1 or with the provider's confirmation. PayPal's own developer guide mentions SAQ A-EP for these fields, though, so confirm with PayPal or your bank which one they expect. The quarterly scan of your site applies either way.

A card form of your own

If your site collects the card number in its own form and passes it to PayPal from your page or your server, your SAQ grows. A form on your page that sends the card straight from the browser usually means SAQ A-EP. Card data that touches your server means SAQ D. Both include the quarterly ASV scan, and both make the scripts on your payment page your responsibility.

What to scan

Scan the public domain and IP address of every server that delivers your checkout page or the page with the PayPal button. If your site sits behind Cloudflare or another CDN, scan the real server as well, and read our note on ASV scans behind Cloudflare. Our guide to which IP addresses to scan covers subdomains, staging sites and shared hosting.

Confirming your SAQ

If PayPal processes your card payments, PayPal or its acquiring bank is who asks for your compliance paperwork. Work out which of the setups above you use, check it against our SAQ guide, and confirm with whoever asks. Keep your SAQ and your four quarterly passing scans together.

Common questions

Does PayPal make me PCI compliant?

No. PayPal keeps its own systems compliant, which shrinks your part a lot. 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 a scan if customers only pay through the PayPal button?

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 PayPal's.

I use PayPal and Stripe together. Which SAQ is it?

The SAQ follows the riskiest way your site collects cards. If both send customers to the provider's page, it is usually SAQ A. If either one puts its card fields in your page, you also need to confirm your page is safe from script attacks. If either one uses a form of your own, plan for SAQ A-EP, or SAQ D if card numbers reach your server. Some banks ask for a separate SAQ for each way you take cards.

What about PayPal on Shopify, Wix, Squarespace or WooCommerce?

On a hosted platform, the platform's checkout decides your SAQ. See our guides for Shopify, Wix and Squarespace. On WooCommerce your own server delivers the checkout, so see PCI scanning for WooCommerce.

Do I need payment page monitoring with PayPal card fields?

Not necessarily, but you need some way to stand behind it. If you are on SAQ A, you confirm your checkout page is not open to script attacks, and if PayPal or your bank puts you on SAQ A-EP, requirements 6.4.3 and 11.6.1 apply in full. Either way, keeping track of the scripts on the page and noticing when they change is the usual way to show it. 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 PayPal 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.