# PCI Compliance Basics for Small Online Stores

Source: https://hostreta.com/2026/11/pci-compliance-small-stores/

The moment your store accepts card payments, a set of security rules applies to you — even if you’re a one-person business working from a kitchen table. The good news is that for most small stores, PCI compliance comes down to a handful of sensible habits plus letting your payment provider do the heavy lifting. You don’t need a security team; you need the right setup and a little discipline.

This guide is updated for PCI DSS v4.0.1, the current version of the standard, including the January 2025 changes to the simplest self-assessment questionnaire that took effect on March 31, 2025. It explains what PCI DSS is, who needs to comply, how hosted gateways reduce your responsibility, what changed recently, the everyday habits that count, how self-assessment works, and what to do before the holiday rush. It is a general overview, not legal or compliance advice — your payment provider has the final word on your obligations.

Table of Contents

[Toggle](#)

- [What PCI compliance means in plain words](#What_PCI_compliance_means_in_plain_words)
- [Why small stores are targets](#Why_small_stores_are_targets)

- [Who needs PCI compliance](#Who_needs_PCI_compliance)
- [How hosted gateways reduce your PCI compliance scope](#How_hosted_gateways_reduce_your_PCI_compliance_scope)
- [What changed in PCI DSS v4.0.1](#What_changed_in_PCI_DSS_v401)
- [How to show your site resists script attacks](#How_to_show_your_site_resists_script_attacks)

- [Everyday security habits that count](#Everyday_security_habits_that_count)
- [Choosing hosting that supports PCI compliance](#Choosing_hosting_that_supports_PCI_compliance)
- [Completing a PCI compliance self-assessment](#Completing_a_PCI_compliance_self-assessment)
- [Write a simple security policy](#Write_a_simple_security_policy)

- [PCI compliance checks before Black Friday 2026](#PCI_compliance_checks_before_Black_Friday_2026)
- [What to do if you suspect a breach](#What_to_do_if_you_suspect_a_breach)
- [The 12 PCI DSS requirements in brief](#The_12_PCI_DSS_requirements_in_brief)
- [PCI compliance for different payment setups](#PCI_compliance_for_different_payment_setups)
- [Subscriptions and saved cards](#Subscriptions_and_saved_cards)

- [Common PCI compliance mistakes](#Common_PCI_compliance_mistakes)
- [Team training and access](#Team_training_and_access)
- [A yearly PCI compliance routine for small stores](#A_yearly_PCI_compliance_routine_for_small_stores)
- [Keeping PCI compliance evidence](#Keeping_PCI_compliance_evidence)

- [Frequently asked questions](#Frequently_asked_questions)
- [Do I need PCI compliance if I use Stripe or PayPal?](#Do_I_need_PCI_compliance_if_I_use_Stripe_or_PayPal)
- [Is PCI compliance a one-time task?](#Is_PCI_compliance_a_one-time_task)
- [Can I store the last four digits of a card?](#Can_I_store_the_last_four_digits_of_a_card)
- [Does SSL make my store PCI compliant?](#Does_SSL_make_my_store_PCI_compliant)
- [What happens if I ignore PCI compliance?](#What_happens_if_I_ignore_PCI_compliance)
- [Do digital product stores need PCI compliance?](#Do_digital_product_stores_need_PCI_compliance)
- [Who can help me with PCI compliance questions?](#Who_can_help_me_with_PCI_compliance_questions)

- [Key takeaways](#Key_takeaways)

## What PCI compliance means in plain words

PCI DSS (Payment Card Industry Data Security Standard) is a set of security requirements created by the major card networks and maintained by the [PCI Security Standards Council](https://www.pcisecuritystandards.org/). It covers how card data is handled, stored, and transmitted, and exists to reduce fraud and data breaches.

It isn’t a law, but it’s part of your agreement with your payment provider. Serious failures can mean fines, higher fees, or losing the ability to take cards. PCI compliance is also simply good security: the same steps that satisfy the standard protect your customers and your reputation.

### Why small stores are targets

Attackers know small stores often have fewer defences than large retailers. Common attacks include injecting skimming scripts into checkout pages (so-called Magecart attacks), card testing with stolen numbers, and taking over admin accounts with reused passwords. Most of these attacks are automated, so being small doesn’t make you invisible. Good PCI compliance habits block the majority of them.

## Who needs PCI compliance

Any business that accepts, processes, stores, or transmits card data — regardless of size. Requirements scale by transaction volume, and the vast majority of small online stores fall into the smallest merchant level, with a short self-assessment rather than a full audit by a qualified assessor.

Your acquirer or payment provider tells you which self-assessment questionnaire (SAQ) applies. Many providers, such as Stripe and PayPal, guide you through this inside your account dashboard, and some complete much of it for you based on how you integrate.

## How hosted gateways reduce your PCI compliance scope

The single biggest factor is where card details are entered:

- Redirect or fully hosted payment page: the customer leaves your site to pay on the provider’s page (for example PayPal or a hosted checkout). Card data never touches your website.

- Embedded hosted fields or iframes (such as Stripe Elements or WooPayments): card fields appear on your checkout but are served from the provider, so card data goes straight to them. These setups usually qualify for the simplest questionnaire, SAQ A.

- Direct post or JavaScript forms that your page controls before sending data on: these typically fall under SAQ A-EP, with many more requirements.

- Card fields processed by your own server: a far heavier set of requirements (often SAQ D), and rarely worth it for a small store.

Practical rule: use a reputable gateway’s hosted fields or hosted page, keep the payment plugin updated, and never build your own card form. Payment options are compared in [Payment Gateways Explained: Stripe, PayPal and More](https://hostreta.com/2026/10/payment-gateways-guide/).

## What changed in PCI DSS v4.0.1

Version 4.0 introduced two requirements aimed at checkout skimming: 6.4.3, which requires an inventory and authorisation of scripts on payment pages, and 11.6.1, which requires detecting unauthorised changes to those pages. They became mandatory on March 31, 2025.

In January 2025, the Council revised SAQ A. Requirements 6.4.3 and 11.6.1 (and the related risk analysis in 12.3.1) were removed from the questionnaire, and a new eligibility criterion was added: merchants must confirm their site is not susceptible to attacks from scripts that could affect their e-commerce systems. In practice, that means you still need to protect your website against malicious scripts — the questionnaire is shorter, but the responsibility remains. Merchants on SAQ A-EP or SAQ D must still meet 6.4.3 and 11.6.1 in full.

### How to show your site resists script attacks

- Keep checkout pages lean: remove chat widgets, heatmaps, and marketing tags that don’t need to run there.

- Update everything promptly: WordPress, WooCommerce, plugins, themes, and PHP.

- Scan for malware and file changes automatically.

- Use a web application firewall to block common attacks — see [Web Application Firewalls (WAF) Explained](https://hostreta.com/2026/10/waf-guide/).

- Consider a Content Security Policy that limits which domains can load scripts on your site.

- Protect admin access with strong passwords and two-factor authentication.

## Everyday security habits that count

- Never store card numbers — not in your database, not in order notes, not in email, not in spreadsheets.

- HTTPS everywhere with a valid certificate — see [What Is SSL? How to Get HTTPS for Free](https://hostreta.com/2026/09/what-is-ssl-how-to-get-https-for-free/). An [SSL certificate from Kawedma](https://kawedma.com/ssl-certificates.php) is an option if your host doesn’t include one.

- Keep software updated: WordPress, WooCommerce, payment extensions, themes, and PHP — see [How to Safely Update WordPress, Themes and Plugins](https://hostreta.com/2026/10/wordpress-updates/).

- Strong unique passwords and two-factor authentication for every admin — see [Best Password Managers for Teams and Freelancers](https://hostreta.com/2026/10/password-manager-guide/).

- Least-privilege roles and prompt removal of old accounts — see [WordPress User Roles and Permissions Explained](https://hostreta.com/2026/10/wordpress-user-roles/).

- Limit scripts on checkout — every third-party script is a risk — see [WooCommerce Checkout Security: 7 Essential Checks](https://hostreta.com/2026/11/woocommerce-checkout-security/).

- Monitor file changes and scan for malware — see [How to Scan Your Website for Malware](https://hostreta.com/2026/10/malware-scan/). [SiteLock](https://kawedma.com/sitelock.php) automates daily scans.

- Keep an activity log — see Activity Log Plugins: 7 Essential Checks.

- Use a secure connection on public Wi-Fi when managing your store remotely; a VPN such as [NordVPN](https://kawedma.com/store/nordvpn) encrypts your traffic.

## Choosing hosting that supports PCI compliance

If card data never touches your server, your host isn’t processing payments. But your website still has to be secure enough to resist script attacks, which depends heavily on hosting. Look for account isolation, current PHP versions, a firewall, malware scanning, automatic backups, and responsive security support — see [Is Your Hosting Secure? 12 Features to Check](https://hostreta.com/2026/10/hosting-security-checks/).

[Kawedma WordPress hosting](https://kawedma.com/wordpress-hosting.php) and [managed WordPress hosting powered by Rocket.net](https://my.hosting.com/aff/08a016e41d3100e5460ff6ebee1b5e0a91e643d6) handle updates and security layers for you. Larger stores that want isolated resources can choose a [Kawedma VPS server](https://kawedma.com/vps-server.php) or a [managed VPS from Hosting.com](https://my.hosting.com/aff/a4acdd3ba5260a0812f3b4249da227e940d132e7). Keep off-site backups with a service such as [CodeGuard](https://kawedma.com/codeguard.php) so you can recover quickly from any incident.

## Completing a PCI compliance self-assessment

- Ask your provider which SAQ applies to your setup.

- Confirm how payments are captured — hosted page, embedded hosted fields, or on your server.

- Work through the questionnaire, which covers areas such as secure configuration, access control, updates, and policies.

- Confirm the script-attack eligibility criterion if you use SAQ A, and keep notes on how you protect your site.

- Run any required vulnerability scan, if your questionnaire needs one.

- Keep records of your answers and evidence.

- Review annually and whenever you change gateways, checkout plugins, or themes.

### Write a simple security policy

Even small businesses benefit from a one-page policy: who has admin access, how passwords and two-factor authentication are managed, how often software is updated, how backups are kept, and what to do in an incident. It helps with PCI compliance questions and makes sure nothing is forgotten when you’re busy.

## PCI compliance checks before Black Friday 2026

With Black Friday on November 27 and Cyber Monday on November 30, 2026, run these checks before your code freeze:

- Confirm your payment plugin and gateway settings are current.

- Review every script that loads on cart and checkout pages, and remove anything unnecessary.

- Remove old admin and shop manager accounts.

- Check that fraud rules and bot protection are active — see [Card Testing: 7 Essential Checks](https://hostreta.com/2026/11/card-testing-fraud/) and How to Add reCAPTCHA to WooCommerce Checkout.

- Run a full malware scan and confirm backups are working.

- Test checkout end to end — see [How to Test Your Checkout End to End](https://hostreta.com/2026/11/checkout-testing/).

## What to do if you suspect a breach

- Don’t panic or delete evidence. Take screenshots and note what you saw.

- Contact your payment provider immediately; they have procedures for suspected card data exposure.

- Contact your host and ask for help identifying modified files.

- Change all passwords and revoke unknown accounts and API keys.

- Clean the site or restore a known-good backup — see [How to Fix a Hacked WordPress Site Step by Step](https://hostreta.com/2026/10/how-to-fix-a-hacked-wordpress-site-step-by-step/).

- Follow legal requirements for notifying customers in your region.

## The 12 PCI DSS requirements in brief

PCI compliance is built on twelve high-level requirements grouped into six goals. As a small store using hosted payments, many will be handled by your provider, but it helps to know what they cover:

- Install and maintain network security controls such as firewalls.

- Apply secure configurations and change default passwords and settings.

- Protect stored account data — or better, don’t store it at all.

- Protect card data with strong encryption when it travels over networks.

- Protect systems from malicious software with anti-malware and scanning.

- Develop and maintain secure systems and software, including timely updates.

- Restrict access to card data on a need-to-know basis.

- Identify users and authenticate access, including multi-factor authentication.

- Restrict physical access to card data.

- Log and monitor access to systems and data.

- Test security regularly, including vulnerability scans where required.

- Support security with policies and programmes across the business.

For a store on SAQ A, the questionnaire covers only a small subset of these. Still, treating the twelve as a checklist for your whole website is a practical way to strengthen PCI compliance and general security together.

## PCI compliance for different payment setups

- WooPayments or Stripe with hosted fields: card fields are served by the provider. Keep the plugin updated, keep checkout scripts lean, and complete the questionnaire your provider recommends.

- PayPal and other redirect methods: the customer pays on PayPal’s site. Your PCI compliance work focuses on keeping your own site secure so the redirect can’t be tampered with.

- Express wallets such as Apple Pay and Google Pay: these add security through tokenisation, but they still run through your gateway’s integration, so the same rules apply.

- Phone and manual orders: if staff take card details by phone, never write them down or type them into order notes. Use your provider’s virtual terminal and limit who can access it.

- In-person sales: card readers from your provider handle encryption, but keep devices secure and updated.

### Subscriptions and saved cards

Stores that offer subscriptions or saved payment methods don’t store card numbers themselves. Instead, the gateway stores the card and gives your store a token. This keeps PCI compliance manageable even for recurring billing, as long as you never capture raw card data in custom forms or plugins.

## Common PCI compliance mistakes

- Asking customers to email card details for manual orders.

- Storing card numbers in order notes or support tickets.

- Running outdated payment plugins or abandoned extensions.

- Loading dozens of marketing scripts on the checkout page.

- Sharing one admin login between several people.

- Forgetting the annual review after the first questionnaire.

- Assuming the gateway covers everything, when your website security is still your responsibility.

Avoiding these mistakes takes little time and does more for PCI compliance than any expensive tool.

## Team training and access

People are often the weakest link. Make sure everyone who works on your store knows the basics: never ask for or record card details, spot phishing emails, use a password manager, and turn on two-factor authentication — see [Phishing Emails: How to Spot Them in 5 Seconds](https://hostreta.com/2026/10/phishing-emails-how-to-spot-them-in-5-seconds/) and [Two-Factor Authentication Apps Compared](https://hostreta.com/2026/10/two-factor-authentication-apps-compared/). Review user accounts every quarter and remove anyone who no longer needs access. These habits strengthen PCI compliance and protect against the most common attacks on small businesses.

## A yearly PCI compliance routine for small stores

Turn PCI compliance into a simple annual routine instead of a stressful one-off project:

- January: review the self-assessment questionnaire, confirm your SAQ type with your provider, and update your security policy. Start the year with PCI compliance confirmed.

- Every month: apply updates, check malware scan results, review new admin accounts, and confirm backups ran successfully.

- Every quarter: audit the scripts on checkout pages, remove unused plugins, and run any vulnerability scans your questionnaire requires.

- Before peak season: repeat the checkout script review, test payments end to end, and confirm fraud rules — the steps in the Black Friday section above.

- After any change: new gateway, new theme, or new checkout plugin means reviewing PCI compliance again before going live.

Put these dates in your calendar. A few minutes each month keeps PCI compliance current, and it means you’re always ready if your payment provider asks for evidence.

### Keeping PCI compliance evidence

Store a simple folder with your completed questionnaire, scan reports, your security policy, a list of admin users, and notes on how you protect checkout from script attacks. Date every document. If you ever face questions from your provider after an incident, organised records show you took PCI compliance seriously.

## Frequently asked questions

### Do I need PCI compliance if I use Stripe or PayPal?

Yes, but using their hosted fields or hosted pages greatly reduces your responsibility, usually to the short SAQ A questionnaire plus keeping your website secure.

### Is PCI compliance a one-time task?

No. Self-assessments are typically completed annually, and you should review your setup whenever you change your checkout, theme, or payment provider.

### Can I store the last four digits of a card?

Gateways usually provide a masked card reference for your records. Never store full card numbers or security codes yourself.

### Does SSL make my store PCI compliant?

SSL is required, but it’s only one part. PCI compliance also covers updates, access control, script security, and policies.

### What happens if I ignore PCI compliance?

Nothing may happen at first, but if a breach occurs, your provider can apply penalties, raise fees, or stop you accepting cards. You may also face costs for investigation, customer notification, and lost trust.

### Do digital product stores need PCI compliance?

Yes. Any store that accepts card payments needs it, whether it sells physical goods, digital downloads, or services. The same hosted-payment approach keeps the workload small.

### Who can help me with PCI compliance questions?

Start with your payment provider’s support and documentation. For complex setups or larger volumes, a qualified security assessor or consultant can review your systems.

For most small stores, the path is clear: choose a trusted gateway with hosted fields, keep your website clean and updated, protect admin access, and review your setup once a year. Do that consistently and you will meet your obligations while giving customers a checkout they can trust, during the holiday rush and every other day of the year.

Start today with one step: check which questionnaire your provider says applies to you.

## Key takeaways

- Let your gateway handle card data through hosted fields or a hosted page.

- Never store card numbers anywhere on your server.

- Under PCI DSS v4.0.1, SAQ A merchants must still protect their site from script attacks.

- Keep software, SSL, and admin access locked down.

- Ask your provider which self-assessment applies and review it yearly.
