What PCI DSS is
PCI DSS (Payment Card Industry Data Security Standard) is the security standard set by the card brands, such as Visa and Mastercard, through the PCI Security Standards Council. It applies to any business that accepts, processes, stores or transmits card data.
It is not a law, but it is a contractual obligation: your bank or the payment gateway you use requires it. If there is a breach and you are not compliant, the consequences can range from penalties to losing the ability to accept cards.
What your platform covers and what it doesn't
Certified SaaS platforms and payment gateways handle the heaviest part: processing and storing card data in their systems. Shopify, for example, is certified as a PCI DSS Level 1 service provider.
What remains yours is everything around the payment: who logs in to the shop's admin, which apps or scripts have access to the checkout pages, how the gateway is integrated if the shop is self-hosted, and what you do if something goes wrong.
Which questionnaire (SAQ) applies to you
Most online shops comply by completing a self-assessment questionnaire, the SAQ. There are several, and the one that applies to you depends on how payment is integrated.
If the card form is served entirely by the gateway, with its own payment page or an iframe it hosts, SAQ A usually applies, the shortest one. If your website affects the payment page, for example with your own form that sends the data to the gateway via JavaScript, it is usually SAQ A-EP, which is far more demanding.
Your bank or your gateway will tell you which one to submit. It is worth confirming this every time you change platform or integration method.
What you should check in your shop
These are the checks that remove the most risk in an ecommerce business, whatever the platform:
- No card data passes through your servers or is stored in your database, your logs or your emails.
- The payment form is served by the gateway (hosted page or iframe) whenever possible.
- An inventory of the scripts loaded on checkout pages: analytics, pixels, chats. Only those that are needed, and from known sources.
- Two-factor authentication and least-privilege permissions for everyone with access to the admin.
- Platform, modules and apps kept up to date, especially on PrestaShop, Magento and WooCommerce.
- A written plan for what to do and who to notify if you suspect a breach.
The most common risk: malicious code in the checkout
One of the most common attacks on online shops is web skimming: someone manages to inject a script into the payment page that copies card data while the customer types it. It usually gets in through an outdated module, an admin account without two-factor authentication or a compromised third-party script.
That is why recent versions of PCI DSS focus on controlling the scripts on payment pages. Knowing what is loaded and why is the first line of defence.
Frequently asked questions
If I sell on Shopify, am I already PCI DSS compliant?
Shopify is PCI DSS compliant as a provider, and that covers payment processing in its checkout. The shop is still responsible for its access, for the apps and scripts it installs and for submitting the questionnaire its payment provider asks for.
What is SAQ A?
SAQ A is the shortest PCI DSS self-assessment questionnaire. It usually applies to online merchants that fully delegate the payment form to a certified gateway, through a payment page or an iframe hosted by the gateway.
Can I store card numbers for recurring payments?
Not in your own systems. For subscriptions and recurring payments, the gateway's tokenisation is used: the gateway stores the card and your shop only keeps an identifier that is worthless to an attacker.
We’ll tell you what we would do in your case, no strings attached. A real person from the team replies.
