WooCommerce · Explainer
Is WooCommerce PCI Compliant? Who Is Responsible for What
Short answer
No, WooCommerce on its own is not PCI compliant, because the plugin does not store, process or transmit card numbers. Your store meets PCI DSS when card data goes through a compliant payment gateway, such as WooPayments or Stripe, and you keep WordPress, your hosting and your checkout secure. You still complete a yearly Self-Assessment Questionnaire, usually SAQ A, and run quarterly security scans.
Key takeaways
- WooCommerce itself holds no card numbers, so it cannot be PCI certified on its own.
- WooPayments is a PCI DSS Level 1 service provider, but that does not make your whole store compliant.
- Hosted payment fields and tokenization keep card numbers and CVC codes off your server.
- Most small stores validate with SAQ A each year and run quarterly scans from an approved vendor.
- SSL alone does not make a store PCI compliant, though most gateways still require it.
What does PCI compliant mean for a WooCommerce store?
A PCI compliant WooCommerce store meets the Payment Card Industry Data Security Standard, the set of rules for handling card payments safely.
PCI DSS is the global security standard for any business that stores, processes or transmits cardholder data. It applies to every business that takes card payments, whatever its size or sales volume.
The standard is run by the Payment Card Industry Security Standards Council, known as the PCI SSC. Visa, Mastercard, American Express, Discover and JCB formed the council in 2006, according to Stripe. The card brands enforce the rules through your merchant agreement.
For a WooCommerce store, compliance is not a badge you buy or a plugin you install. It is the way your checkout, gateway, hosting and upkeep work together.
Is WooCommerce itself PCI compliant?
No, WooCommerce itself is not PCI compliant, because the core plugin does not handle card data or process payments.
WooCommerce is a free, open source plugin that runs your shop on WordPress. It builds the cart, the checkout page and the order records. When a customer pays, WooCommerce hands the payment to a gateway.
That split is the key point. A store can meet PCI DSS even though WooCommerce alone holds no certificate.
The certificate sits with the gateway and the other services that touch card data. Your job is to pick a compliant gateway and to run the rest of the store in a secure way.
WooCommerce states this in its own PCI guidance. The store owner carries the final duty, and the payment processor may ask for proof, such as a completed questionnaire or a security scan.
Who is responsible for what in a WooCommerce store?
Responsibility is shared, and each party covers only the part it controls.
The gateway collects and processes card data in its own validated system. The host keeps the server patched and guarded. You keep WordPress, WooCommerce, your theme and your plugins updated, and you control who can log in.
| Party | What it handles | What it does not cover |
|---|---|---|
| Payment gateway | Card data, tokenization, payment processing | Your WordPress updates and admin accounts |
| Hosting provider | Server patching, network guards, backups if offered | Your plugins, theme and checkout scripts |
| Store owner | Updates, strong logins, SSL, yearly SAQ | The gateway's own card systems |
| WooCommerce plugin | Cart, checkout page, order records | Card numbers, which it never sees |
WooCommerce stores customer details such as name, address and country in your WordPress database, while card numbers and CVC codes never reach it with a hosted gateway.
If you use WooPayments, it acts as a PCI DSS Level 1 service provider. That covers its own payment systems, not your site. You still have duties around the checkout page and site security.
What is PCI DSS v4.0.1 and which version applies now?
PCI DSS v4.0.1 is the version in force as of November 2026, and all of its requirements became mandatory on 31 March 2025.
The standard has 12 requirements grouped under six goals, covering network guards, safe setup, stored account data, encryption in transit, malware defence, secure software, access control, logging, testing and security policy.
Version 4.0.1 was published in June 2024 as a small revision of version 4.0. The 51 requirements that version 4.0 had marked as future dated all became mandatory on 31 March 2025.
Two newer rules matter most for WooCommerce checkouts. Stores must list the scripts on payment pages, check that each one is allowed, and spot changes to those pages. That is why a checkout loaded with extra scripts needs more care than a plain one.
Which SAQ does a WooCommerce store complete?
Most WooCommerce stores complete SAQ A, the shortest questionnaire, when card data never touches their server.
SAQ stands for Self-Assessment Questionnaire, the form a merchant fills in each year to show it meets the PCI DSS rules for its setup. The right SAQ depends on how card data reaches your gateway, not on how big your store is.
| SAQ | Who it fits | When it applies to WooCommerce |
|---|---|---|
| SAQ A | Stores that fully outsource card handling | Hosted fields, iframe checkout or redirect to the gateway |
| SAQ A-EP | Stores whose own site serves the payment page | Card form hosted on your site, data sent to the gateway |
| SAQ D | Stores that handle card data direct | Card numbers passed to the gateway API by your own code |
Stripe's PCI guide gives the same split for its own tools. Stripe Checkout and Stripe Elements use a hosted field from Stripe's servers, so they fit SAQ A. Passing card data direct to Stripe's API needs SAQ D, the longest and hardest form.
PayPal works the same way. Its Hosted Fields show the card number, CVV and expiry date inside iframes served by PayPal, and the data goes straight to PayPal without touching your server. That keeps a merchant eligible for SAQ A.
How does tokenization keep card numbers off your server?
Tokenization swaps a real card number for a random reference code, called a token, that is useless to a thief on its own.
When a customer types a card number into a hosted payment field, the number goes direct to the gateway. The gateway stores it in its own secure system and sends your store a token instead.
WooPayments works this way. Its hosted payment fields are served from its payment partner's PCI DSS validated system, so card details never pass through your site. A saved card or subscription is charged again later with a token.
The token is stored by the payment partner and reached through your site's link to WordPress.com. The card number and CVC are never stored on your site.
A side by side look at WooCommerce Payments vs Stripe can help you weigh the two hosted options. Both use hosted fields and tokens, so the PCI picture is much the same either way.
What are the four PCI merchant levels?
Your merchant level comes from how many card transactions you process in a year, and it sets how you prove compliance.
Stripe's PCI guide lists four levels. Level 1 covers over 6 million Visa transactions, over 6 million Mastercard transactions or over 2.5 million American Express transactions in a year. Level 2 covers 1 million to 6 million a year.
Level 3 covers 20,000 to 1 million online transactions a year, and Level 4 covers under 20,000 online transactions a year. Most WooCommerce stores sit in Level 3 or Level 4.
Visa does not use Level 4, and it treats any store under 1 million transactions a year as Level 3.
Level 1 stores cannot use an SAQ. They need a yearly on site check by a Qualified Security Assessor, called a QSA, which ends in a Report on Compliance.
Levels 2 to 4 can use an SAQ, though a Level 2 store using SAQ A, SAQ A-EP or SAQ D may still need a QSA to sign it off.
Every level also needs a quarterly network scan by an Approved Scanning Vendor, called an ASV. The scan looks for known holes in your server and site. Your gateway or acquirer can tell you which scan service to use.
What must you do on your own site?
You must keep the site patched, guarded and watched, because the gateway cannot do that part for you.
Start with SSL, also called TLS. Most payment gateways require it, and WooCommerce strongly recommends running the whole store over https, not just the checkout page.
Its SSL guide notes that an SSL certificate is needed whenever customer details travel over the web. You can read the steps in the WooCommerce SSL guide.
Next, keep everything updated. WooCommerce server guidance as of November 2026 calls for WordPress 6.9 or newer, PHP 8.3 or newer, MySQL 8.0 or newer or MariaDB 10.6 or newer, HTTPS support and a WordPress memory limit of 256 MB or more.
Old versions of WordPress, WooCommerce or a plugin are a common way in for attackers.
Limit who can reach your admin area. Give each staff member only the access they need, and use a strong, unique password for each account. Remove old admin accounts and plugins.
Watch the checkout page in particular. Card testing bots probe WooCommerce checkouts with small stolen card charges, and the guide to stopping card testing attacks shows the signs to look for.
Keep the scripts on the checkout page to a minimum, since each extra script is one more thing that could be changed without you noticing.
How do you check PCI compliance on your WooCommerce site?
You check it in three steps: confirm your gateway setup, run the ASV scan, and fill in the SAQ.
First, open your gateway settings and confirm how card data is collected. With WooPayments, the card fields should be hosted fields from its partner's system.
With Stripe, look for Checkout or Elements. With PayPal, look for Hosted Fields or the Drop-in form. If your own code sends card numbers to an API, your SAQ changes to SAQ D.
Second, run the quarterly ASV scan. Your acquirer or gateway usually names an approved vendor or offers a scan tool.
Fix any failures it reports, then re-run the scan until it passes. Keep the pass report with your records.
Third, complete the SAQ that matches your setup, most often SAQ A, and sign the Attestation of Compliance that goes with it. Send both to your acquirer or gateway when they ask.
If you need proof of your gateway's own compliance, ask its support team for a copy of its Attestation of Compliance.
WordPress security basics still matter here, and the guide on whether WordPress is secure covers the settings and habits that support the PCI work. A store with a clean update routine and tight logins will find the SAQ far easier than one that has let updates slide.
What are common myths about WooCommerce PCI compliance?
The most common myth is that a compliant gateway makes the whole store compliant on its own.
WooCommerce says this is not so for WooPayments. The gateway is a PCI DSS Level 1 service provider, yet the store owner still has duties around the checkout page and site security.
A second myth is that SSL alone is enough. WooCommerce states in its SSL FAQ that SSL alone does not make a site PCI compliant. SSL guards data in transit, but it does nothing for outdated plugins, weak passwords or card data stored in the wrong place.
A third myth is that small stores are exempt. Stripe states that all businesses that accept card payments must comply with PCI DSS, whatever their volume or integration type. A small store may have a lighter SAQ, but it still has one to complete.
A fourth myth is that WooCommerce stores card numbers for you. With a hosted gateway it does not.
WooCommerce stores only the order and customer details in your database, and the gateway holds the card data behind a token. Storing card numbers yourself, in a note field or a spreadsheet, would break that setup and push you into SAQ D.
Customer details such as names and addresses still need care under privacy law, even though they are not card data. The guide to making WooCommerce GDPR compliant covers that side of the job.
Frequently asked questions
Do I need PCI compliance if I only sell a few items a month?
Yes. Every business that accepts card payments must meet PCI DSS, whatever its sales volume. A small store usually has a lighter job, often SAQ A plus a quarterly scan, but there is no exemption for low volume. Your gateway or acquirer will tell you which form to complete and when to send it.
Does using WooPayments mean I can skip the SAQ?
No. WooPayments is a PCI DSS Level 1 service provider, but that covers its own payment systems, not your whole store. You still complete a yearly Self-Assessment Questionnaire, usually SAQ A, and run quarterly scans. Ask WooPayments support for a copy of its Attestation of Compliance if your acquirer wants proof.
Can I store card numbers in WooCommerce to charge customers later?
No, never store card numbers or CVC codes on your own site, in a note field, a spreadsheet or an order note. Use the gateway's saved payment method instead, which stores a token and keeps the real card number on the gateway's servers. Storing card data yourself would move your store to SAQ D, the hardest form.
What happens if my store is not PCI compliant?
Your acquirer can fine you, raise your processing fees or close your merchant account, and the card brands enforce the rules through the acquirer. A breach can also bring forensic costs, card replacement costs and lost customer trust. Keeping the SAQ and scans up to date is far cheaper than dealing with a breach after the fact.
Is PayPal checkout enough for PCI compliance on its own?
PayPal handles the card data when you use its hosted checkout, and that keeps most stores eligible for SAQ A. It does not cover the rest of your site. You still need SSL, prompt updates, tight admin logins and a yearly SAQ, plus quarterly scans from an approved vendor.
How often must I renew PCI compliance?
Validation is yearly. Complete the SAQ and sign the Attestation of Compliance once a year, and run the Approved Scanning Vendor scan every three months. Update the SAQ sooner if you change gateway, checkout setup or hosting, since a new setup can change which form applies.
Sources
- Is WooPayments PCI Compliant? WooCommerce
- What is PCI DSS compliance? Stripe
- SSL, HTTPS, and WooCommerce WooCommerce
- Hosted Fields PayPal Developer
- PCI DSS Self-Assessment Questionnaire Instructions and Guidelines PCI Security Standards Council
- PCI compliance PayPal
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
