PCI DSS, the Payment Card Industry Data Security Standard, is a set of technical and operational requirements for protecting payment card data. It applies to organizations that store, process or transmit cardholder data or sensitive authentication data, and to those that can affect the security of that data. If your store accepts card payments, it applies to you in some form.
How much of it applies depends mostly on how card details travel from the buyer to the payment provider. A store whose own servers handle card numbers takes on far more of the standard than one that uses hosted payment fields from a provider such as Stripe.
Who sets PCI DSS
The standard is published by the PCI Security Standards Council (PCI SSC). The Council says it was founded in 2006 by American Express, Discover, JCB International, Mastercard and Visa. It develops and maintains the standards, trains and qualifies security assessors, and publishes guidance.
The Council does not enforce the standard itself. It states that it does not monitor how standards are implemented, and that the organizations running compliance programs, such as the card brands and acquirers, decide who must comply and how they prove it. For more on how network rules reach a merchant, see card network rules merchants should know.
How compliance is checked
Formal assessments are carried out by Qualified Security Assessors, and external vulnerability scans by Approved Scanning Vendors. Many smaller merchants confirm compliance with a Self-Assessment Questionnaire (SAQ). There are several SAQ types, and the right one depends on how your checkout handles card data.
How Stripe's hosted payment fields affect your scope
Stripe describes PCI compliance as a shared responsibility. Stripe says it is certified each year by an independent Qualified Security Assessor as a PCI Level 1 Service Provider, and that a business accepting payments must still meet its own PCI obligations and attest to its compliance each year.
What changes is how much of the standard falls on you. According to Stripe's PCI guide:
- With Stripe Checkout or Elements, card data is sent to Stripe and never touches your servers. Stripe maps these integrations to SAQ A.
- With an older integration that builds the card form on your own page, which Stripe names as Stripe.js v2, Stripe maps the integration to SAQ A-EP.
- If your servers pass card numbers to Stripe's API, your integration is handling card data directly. Stripe maps this to SAQ D, the most demanding questionnaire, and its security guide says a business handling card data directly might need to meet more than 300 security controls.
Stripe also says that the non-sensitive card details it returns, such as card type, the last four digits and the expiry date, are not subject to PCI compliance and can be stored.
What stays with you
Hosted payment fields reduce your share of the standard. They do not remove it. Stripe's guidance leaves these with the merchant:
- Validating compliance every year, and revalidating when your business changes.
- Serving payment pages over TLS 1.2 or above, with every resource on the page also served over HTTPS.
- Keeping third-party JavaScript on payment pages to a minimum, because a compromised script could run code on your page.
- Avoiding custom code that handles card data, which Stripe says can add requirements and make you ineligible for SAQ A.
If you are unsure which questionnaire fits your setup, Stripe suggests asking a Qualified Security Assessor.
Where PCI DSS fits
PCI DSS is about protecting card data. It is a separate question from whether a processor will support your type of business, which is covered in how payment processors review a merchant. Meeting one does not settle the other.
With Claddr, payments are processed by Stripe on your own Stripe account, and Claddr never holds funds. Our security page covers how Claddr approaches security.
Sources
- 01PCI Security Standards Council: PCI DSSwww.pcisecuritystandards.org/standards/pci-dss/
- 02PCI Security Standards Council: About Uswww.pcisecuritystandards.org/about_us/
- 03Stripe Docs: Integration security guidedocs.stripe.com/security/guide
- 04Stripe: A guide to PCI compliancestripe.com/guides/pci-compliance