// Security compliance
PCI-DSS for SaaS that touches payments
What PCI-DSS is
PCI-DSS is the card data security standard (maintained by the PCI SSC), required for anyone who stores, processes or transmits card data. Compliance is validated by a QSA (qualified assessor) or by self-assessment (SAQ), depending on volume and how you touch the data. The current version is 4.0.1.
The good news for SaaS: if you tokenize via a certified provider (Stripe, for example) and never store the card number (PAN), your PCI scope drops a lot. Even so, the flows that touch payments must be secure.
RET runs this test: a 25-hour Sprint for R$9,500, within 7 business days. See price and timeline for my case
What it requires technically
Several PCI requirements can only be proven with real technical testing, not policy.
- Requirement 6: secure development and remediation of code vulnerabilities.
- Requirement 11: regular security testing, including internal and external pentests.
- Requirements 7 and 8: least-privilege access and strong authentication for whoever touches the card environment.
- Payment webhook with signature verification and idempotency (no double credit).
Where RET fits (and where it does not)
RET is NOT a QSA and does not issue the Attestation of Compliance (AoC). What RET does is the technical testing Requirement 11 asks for and the QSA expects to see: a manual pentest of the flows that touch payments and the isolation around them, with reproducible evidence. It is the technical input to your PCI, not the formal validation.
Where to start
First, cut scope: tokenize via a certified provider and do not store the PAN. Then use a Risk Review to map the flows that still touch payments and a Manual Pentest to prove Requirement 11. AuditMySaaS helps keep the webhook and checkout under monitoring.
Frequently asked questions
Does RET make me PCI compliant?
RET covers the technical part (Requirement 11 testing, security of payment flows). Formal validation (AoC, ROC, SAQ) is a QSA’s or self-assessment’s job. RET is not a QSA.
Do I need PCI if I use Stripe?
You still have PCI obligations, but tokenizing via a certified provider and not storing the PAN greatly reduces scope (usually to a simpler SAQ). The flows that touch payments still need to be secure.
Does PCI require a pentest?
Yes. Requirement 11 asks for regular security testing, including internal and external pentests of the card data environment. It is mandatory evidence, not optional.
Who runs the pentest at RET?
Gabriel Lima Ferreira, founder and lead pentester, with an authorized scope and reproducible evidence.