keepcalculator

06 Numbers and Powers

PCI Compliance for WooCommerce Stores: A Practical Guide

Card No. 06·70832 · Updated · Standard formula, shown below

PCI compliance for WooCommerce stores means meeting the Payment Card Industry Data Security Standard (PCI DSS) requirements that apply to how you handle cardholder data. This guide explains what you actually need to do, how to assess your risk level, and how to achieve compliance without unnecessary expense or complexity.

What PCI DSS Actually Requires

The PCI DSS is a set of security controls created by the major card brands (Visa, Mastercard, American Express, Discover, JCB) to reduce credit card fraud. The standard has 12 core requirements grouped into six objectives: build and maintain a secure network, protect cardholder data, maintain a vulnerability management program, implement strong access control measures, regularly monitor and test networks, and maintain an information security policy. For a WooCommerce store, the most relevant requirements usually involve securing your server, encrypting data transmissions, limiting access to admin areas, and regularly updating your software.

Importantly, PCI DSS is not a law. It is a contractual obligation imposed by the card brands through your payment processor or acquiring bank. If you fail to comply, you can face fines, higher transaction fees, or even losing the ability to accept credit cards.

How WooCommerce Stores Fit Into PCI Compliance

Your compliance level depends on how you process, transmit, or store cardholder data. WooCommerce itself does not store full credit card numbers unless you use a plugin that saves them, which is almost never a good idea. The real question is whether card data touches your server at all.

  • Direct post: If your checkout form sends card data to your own server before passing it to a payment gateway, your server is in scope. This is the riskiest setup and requires the most work.
  • Redirect: If the customer is redirected to a payment page hosted by the gateway (like PayPal or Stripe), your server never sees the card data. This dramatically reduces your compliance burden.
  • Embedded iframe or JavaScript: Many modern gateways use a hosted field or iframe approach where the card form is rendered by the gateway on your page, but the data goes directly to them. This also keeps your server out of scope.

Most WooCommerce stores use the redirect or embedded approach, which means they are typically considered SAQ A or SAQ A-EP merchants. SAQ stands for Self-Assessment Questionnaire, and the version you fill out depends on how you handle data.

Choosing the Right SAQ for Your Store

The SAQ is a series of yes/no questions that assess your compliance. Using the wrong SAQ can lead to wasted effort or false confidence. Here are the most common ones for WooCommerce:

  • SAQ A: For merchants who fully outsource cardholder data to a third-party and have no direct storage or processing. This applies if you use a redirect to PayPal, Stripe, or similar, and your website never receives card data.
  • SAQ A-EP: For merchants who use an embedded checkout form (like Stripe Elements or Square) but do not store card data. Your site may be in scope for some requirements because the form is on your domain.
  • SAQ D: For merchants who process or store card data on their own servers. This is the most comprehensive SAQ and involves hundreds of questions, on-site audits, and quarterly network scans.

If you are unsure which SAQ applies, ask your payment processor or acquiring bank. They are the ones who ultimately determine your compliance level, and they will guide you to the correct form.

Steps to Achieve PCI Compliance in WooCommerce

Here is a practical, step-by-step approach to becoming compliant, assuming you use a hosted payment gateway:

  1. Use a PCI-compliant payment gateway. Choose a well-known provider like Stripe, PayPal, Square, or Braintree. These companies handle the heavy lifting of securing card data. Enable their hosted or embedded checkout features.
  2. Disable any plugins that store card data. If you have a subscription plugin or a “save card” feature, make sure it is configured to use the gateway’s tokenization, not to store raw card numbers on your server.
  3. Complete the relevant SAQ. Download the SAQ A or A-EP from the PCI Security Standards Council website and answer honestly. Most questions will be about your hosting environment, access controls, and security policies.
  4. Pass a vulnerability scan (if required). SAQ A-EP and SAQ D require quarterly scans by an Approved Scanning Vendor (ASV). Your hosting provider or security plugin may offer this service.
  5. Fill out the Attestation of Compliance (AOC). This is a form that certifies you have completed the SAQ. Your payment processor may have a portal where you submit it.
  6. Maintain compliance. PCI DSS is not a one-time event. You must review your security policies annually, update software regularly, and re-assess if you change your payment setup.

Common Mistakes and Misconceptions

One common misconception is that using WooCommerce automatically makes you non-compliant. That is false. WooCommerce itself is a platform; compliance depends on how you configure it. Another mistake is thinking that SSL alone makes you compliant. SSL encrypts data in transit, but PCI DSS also requires secure storage, access controls, and monitoring.

Another frequent error is ignoring the “self” in Self-Assessment Questionnaire. Some merchants simply click “yes” to every question without actually implementing the controls. That is dangerous because if a breach occurs, you will be held accountable for the answers you gave.

Also, many store owners forget about third-party plugins. A vulnerable plugin that allows an attacker to inject malicious code could compromise your entire site, even if the card data goes directly to the gateway. PCI DSS requires you to keep all software updated and remove unused plugins.

Costs and Tools for Compliance

The cost of PCI compliance varies widely. If you use SAQ A, the main cost is your time to fill out the form. If you need SAQ A-EP, you may need to pay for a quarterly vulnerability scan, which typically costs between $100 and $300 per year. SAQ D can cost thousands of dollars due to the need for a Qualified Security Assessor (QSA) and extensive remediation.

Many hosting providers offer PCI-compliant managed WordPress hosting, which includes security hardening, malware scanning, and sometimes free vulnerability scans. These plans can cost more than standard shared hosting, but they reduce your compliance burden significantly.

You can also use security plugins like Wordfence or Sucuri to add firewalls and malware scanning, but note that these do not automatically make you compliant. They are tools that help you meet the technical requirements.

Alternatives to Reduce Compliance Burden

If you find PCI compliance overwhelming, consider these alternatives:

  • Use a payment gateway with a fully hosted checkout. For example, PayPal Standard or Stripe Checkout redirects customers to the gateway’s domain, which puts you in SAQ A, the simplest category.
  • Use a platform that handles everything. Services like Shopify or BigCommerce host your store and are PCI Level 1 compliant themselves. You still have some responsibilities, but they are much lighter than self-hosted WooCommerce.
  • Hire a managed WooCommerce provider. Some agencies offer PCI-compliant hosting and maintenance as a package, so you don’t have to worry about the technical details.

Remember, choosing a simpler payment method does not mean you can ignore security altogether. You still need basic protections like strong passwords, two-factor authentication, and regular backups.

Frequently Asked Questions

Is WooCommerce itself PCI compliant?

No platform is “PCI compliant” on its own. Compliance is about the entire environment, including your hosting, plugins, and how you handle card data. WooCommerce can be used in a compliant way, but it is up to you to configure it correctly.

Do I need a vulnerability scan if I use Stripe or PayPal?

If you use a redirect to the gateway’s site (SAQ A), you do not need a scan. If you use Stripe’s embedded elements or PayPal’s Advanced Checkout on your own domain (SAQ A-EP), you likely do need quarterly scans. Check with your processor to confirm.

Can I store credit card numbers in WooCommerce?

Technically you can, but it is a terrible idea. Storing card data puts you in SAQ D, which requires the highest level of security and is very difficult for small stores. Always use tokenization provided by your gateway instead.

What happens if I don’t become PCI compliant?

If you are not compliant, your acquiring bank may fine you, increase your transaction fees, or terminate your ability to accept credit cards. In the event of a breach, you could also be liable for fraud losses and legal costs.

How often do I need to re-certify?

PCI DSS requires annual validation. You must complete the SAQ and submit the AOC once a year, and if you require scans, they must be done quarterly. You should also re-assess whenever you make significant changes to your payment processing.

Does using a security plugin like Wordfence make me compliant?

No, a security plugin is only one piece of the puzzle. PCI DSS has 12 requirements covering network security, access control, monitoring, and policies. A plugin can help with some of these, but you still need to address the others, like having a written security policy and restricting admin access.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.

More cards in this drawer

The whole Numbers and Powers drawer →