Whether PCI DSS obliges you to buy a penetration test comes down to one question, and it isn't how much you process or how many staff you have. It's who builds the card form on your payment page.
Two small companies can use the same payment processor, take the same volume, and land on different sides of this. One has no PCI penetration testing obligation at all. The other has an annual one. The difference is how the card fields get onto the page.
This is general information, not legal or compliance advice, and the final call on which form applies to you belongs to your acquiring bank.
The thing that decides it: which SAQ you qualify for
Most small merchants validate PCI compliance by filling in a Self-Assessment Questionnaire rather than hiring a Qualified Security Assessor. There are several SAQ types, and each one is a different subset of the full standard. The form you qualify for determines which requirements you actually have to answer for.
Requirement 11.4 is the penetration testing requirement in PCI DSS v4. It isn't on every form, and that's the whole ballgame.
- SAQ A is for e-commerce merchants who outsource all card data handling, where every element of the payment page comes directly from a PCI DSS compliant third party, either by redirect or in an iframe. SAQ A doesn't carry the Requirement 11.4 rows, so it brings no penetration testing obligation.
- SAQ A-EP is for e-commerce merchants whose own website doesn't receive card data but does affect the security of the payment transaction, typically because the merchant's page builds the card form and posts it to the processor. This form carries the external penetration testing part of 11.4, at least every 12 months and after significant changes.
- SAQ D is the long one, for everyone who doesn't fit a shorter form, including anyone whose servers see card numbers. Internal and external testing both apply.
Exactly which 11.4 sub-requirements land on SAQ A-EP is something published commentary doesn't fully agree on, especially around segmentation testing. The solid parts: SAQ A has no penetration testing, and SAQ A-EP has the external test. The forms get revised, so check the current ones in the PCI SSC document library against your own setup.
Where founders get this wrong
“We use Stripe, so we're SAQ A.” For Stripe's standard integrations that's usually right. It stops being right the moment card numbers go into fields your own code renders, or touch your server. Roughly, and your acquirer has the final word:
- Redirect to a hosted checkout or a Payment Link. The customer leaves your domain, the payment page is served entirely by Stripe, and your site never touches card data or the page it's typed into. This is the SAQ A shape.
- Stripe Elements or embedded Checkout. The card fields sit on your page, but inside iframes served by Stripe. Stripe says these integrations qualify for SAQ A. The catch is that your page hosts the iframe, so since the January 2025 revision SAQ A also asks you to confirm your site isn't open to script attacks that could affect your e-commerce systems.
- Card fields your own page renders. Your HTML collects the number and your JavaScript sends it straight to the processor, so it never hits your server. This is the A-EP shape, and it's where the external penetration test obligation shows up. Stripe steers people away from it, but older integrations and other processors still work this way.
- Card numbers reach your server. Even briefly, even just to forward them on. That's SAQ D, or a full assessment.
The logic is simple. If an attacker can change a script on your page, they can skim card data on its way to a perfectly compliant processor. Your site is in the security path even though no card number is ever stored on it, and the standard treats you that way.
For what it's worth, our own checkout is the boring version: fastpentests.com sends you to a Stripe Payment Link. Card details are never entered on a page we serve.
A pen test is not an ASV scan, and we are not an ASV
This trips up more people than the SAQ question, and it's the one place where buying from us would be the wrong move.
PCI has two separate kinds of technical testing. Quarterly external vulnerability scans (Requirement 11.3.2) have to be run by an Approved Scanning Vendor, which is a specific PCI SSC qualification. Penetration testing under 11.4 is a different requirement, with different expectations about method and human effort.
They aren't interchangeable in either direction. An ASV scan doesn't satisfy a penetration testing requirement, and a pen test, ours included, doesn't satisfy an ASV scanning requirement. We're not an Approved Scanning Vendor. If your form requires ASV scans, buy those from an ASV on the PCI SSC list.
What to do this week
- Open your checkout in a browser and watch the address bar. If the domain changes before card entry, you are probably in redirect territory. If it stays on your domain, look at whether your page is loading the provider's fields into your own markup.
- List every script that loads on the page where payment begins: analytics, tag managers, chat widgets, A/B testing tools. Each one is third-party code running on that page.
- Ask your acquirer, in writing, which SAQ they expect from you. They decide, not you and not a blog post. Get the answer on record.
- If the answer is A-EP, budget for an annual external penetration test and find out whether ASV scanning applies too.
- If the answer is A, you may still want testing for your customers or your own peace of mind. Just be clear with yourself that PCI isn't what's making you do it.
One cheap structural fix: if you're on A-EP only because of a hand-built card form, moving to a hosted redirect or Stripe's iframe fields can shrink your scope more than any amount of testing. Price that against what A-EP compliance costs you every year.