News

PCI DSS 4.0: What Small Online Shops With Hosted Checkout Should Know

October 22, 2026 4 min read
PCI DSS 4.0: What Small Online Shops With Hosted Checkout Should Know

If you take card payments online, you have almost certainly agreed, somewhere in your payment provider's terms, to follow a security standard called PCI DSS. Most small shop owners never think about it again. But the standard was updated, version 4.0 is now the only version in use, and the questionnaire your provider may ask you to complete has changed. Here is what that means in plain terms for a small shop that uses a hosted checkout.

What PCI DSS Is

PCI DSS stands for Payment Card Industry Data Security Standard. It is a set of security requirements created by the major card brands and maintained by the PCI Security Standards Council. It is not a government law. You are bound by it through your agreement with the company that processes your card payments.

It applies to any business that stores, processes or transmits card data, and to systems that can affect the security of that data. That second part matters: even if card numbers never touch your server, your website can still affect payment security because it is where customers start the checkout.

What Changed

Version 4.0 was published in 2022. The previous version, 3.2.1, was retired at the end of March 2024. Many of the new requirements in version 4.0 were future-dated, meaning they were best practice at first and became mandatory at the end of March 2025. A minor revision, 4.0.1, followed in 2024 to clarify wording.

The main themes of the update include:

  • Stronger authentication. Wider use of multi-factor authentication and stricter password rules for access to payment systems.
  • More attention to payment pages. Attacks that inject malicious code into checkout pages to steal card details led to new requirements about scripts on payment pages.
  • Risk-based decisions. More requirements ask businesses to assess their own risks and decide how often to perform certain tasks.
  • More flexibility for larger organizations in how they meet the security goals.

What It Means for a Shop With Hosted Checkout

A hosted checkout means customers type their card details on a page or into payment fields that are run entirely by your payment provider. Your site sends them to the provider, or displays the provider's fields, but never handles the card number itself. This greatly reduces your responsibilities.

Many merchants with a fully outsourced checkout qualify for the shortest self-assessment questionnaire, called SAQ A. Under version 4, that questionnaire includes some items it did not have before, and the Council has issued updates to it since. If your provider asks you to complete one, make sure you are answering the current version.

If your website collects card numbers directly in its own form, your responsibilities are much larger, and a different, longer questionnaire applies. If you are unsure which setup you have, ask your provider.

Common Gaps in Small Shops

  • Never completing the questionnaire the provider requested, or not knowing which one applies
  • Shared logins and no multi-factor authentication on the store admin
  • Outdated themes, plugins or extensions that leave the site open to attack
  • Card numbers received by email, chat or phone and written down
  • Many third-party scripts on the pages leading up to checkout
  • Former staff or agencies still holding admin access

What to Do

  1. Confirm your checkout type. Ask your provider whether card data is entered entirely on their hosted page or fields.
  2. Find out what your provider requires. Some ask small merchants to complete a questionnaire every year through an online portal. Others handle validation differently.
  3. Answer the current questionnaire honestly. If a question is unclear, ask your provider rather than guessing.
  4. Turn on multi-factor authentication for your store admin, payment provider dashboard, domain account and hosting account.
  5. Keep software updated. Update your platform, theme and plugins, and remove any you no longer use.
  6. Trim scripts. Remove trackers, widgets and tools you do not need, especially on cart and checkout pages.
  7. Never take card numbers by message. If a customer sends one, delete it and ask them to pay through the checkout.
  8. Keep your provider's compliance evidence on file. Payment providers can supply documentation showing they meet the standard.

Quick Checklist

  • Checkout is fully hosted by your payment provider
  • You know which questionnaire applies and when it is due
  • Multi-factor authentication is on for every key account
  • Platform, theme and plugins are current
  • Unneeded scripts are removed from shopping pages
  • Card numbers are never collected by email or chat