PCI DSS for Small Business: Where to Start

By Bug Circuit Security Team
PCI DSS for Small Business: Where to Start

Is your own website affected? Check it free in 2 minutes.

Passive outside check only. Nothing is attacked, no signup.

PCI DSS is the card industry's security rulebook, and as a small business you meet it by working out how card data touches your business, filling in the matching self-assessment questionnaire (SAQ A, A-EP or D), and keeping card data away from your own systems wherever you can.

This guide is for owners of shops, WordPress and Shopify sites, small SaaS products and local businesses that take cards. You will learn what PCI DSS actually asks of you, how to pick the right SAQ in about ten minutes, and what to ask your payment provider. This is general information, not legal advice, and it does not cover penetration testing.

What PCI DSS is, in plain English

PCI DSS stands for Payment Card Industry Data Security Standard. The major card brands created it, and the PCI Security Standards Council maintains it. The current version is 4.0.1, so check the Council's site for updates.

It is mainly a contract rule set by the card brands, not a general law. A few places, such as some US states, refer to it in their own rules, so ask a qualified adviser if you need legal certainty. Your bank or payment provider (the "acquirer" or "processor") passes it on to you in your merchant agreement. That applies to small businesses in the UK, the US and most other places where cards are accepted. Your provider will usually ask you to confirm compliance each year, and some charge a fee if you don't.

The idea is simple: the less card data you touch, the less you have to protect.

Step 1: Work out how you take payments

Your SAQ depends on how card details travel. Here is a quick way to check your website checkout.

  1. Open your checkout page in a browser.
  2. Right-click the card number field and choose Inspect.
  3. Look at what surrounds the field.

If the card field sits inside an <iframe> whose src points to your provider's domain (for example js.stripe.com), it is a hosted field. If clicking Pay sends you to a different address, such as a PayPal or Stripe-hosted page, you use a redirect. If the card field is a normal <input> on your own page, card details are typed into a page you control, even if they go straight to the provider, which usually means SAQ A-EP or SAQ D rather than SAQ A. That changes your answer a lot.

The Inspect check is a quick hint, not proof. An iframe alone does not guarantee that SAQ A applies, so confirm your setup with your payment provider.

If you take card payments by phone, by terminal or by typing cards into a virtual terminal, you have different questionnaires (see below).

Step 2: Pick your SAQ

A Self-Assessment Questionnaire (SAQ) is a yes/no form about your security. The PCI Council publishes each one in its document library. Each has strict eligibility rules, so read them before you start.

SAQWho it fitsTypical setupEffort
SAQ AOnline sellers who fully outsource card handlingRedirect to a hosted payment page, or a provider-hosted iframe or hosted fields. Shopify Payments checkout, Stripe Checkout, PayPal buttonsShortest
SAQ A-EPOnline sellers who outsource payment processing, but whose own website can affect how card data is sentDirect Post or a JavaScript form on your page that sends card data straight to the providerMedium. Many more requirements
SAQ DEveryone who doesn't fit another formCard data stored or passing through your own servers, or custom checkout codeLongest. Covers the full standard

There are also shorter forms for other setups. SAQ B and B-IP cover imprint machines and standalone terminals. SAQ C-VT covers virtual terminals typed in by hand. SAQ P2PE covers validated point-to-point encrypted terminals. Ask your provider which applies to your card machine.

SAQ A: the goal for most small sites

If your checkout is fully handled by your provider's hosted page or iframe, and card data never touches your servers, you probably fit SAQ A. Current versions also ask you to confirm your site is not open to known script attacks, because a tampered page that frames a payment form is still a risk. Keep plugins and themes updated. A free check of your security headers is a useful starting point.

Some common matches:

  • Shopify with Shopify Payments or another hosted checkout
  • WooCommerce using the Stripe or PayPal plugin with hosted fields or redirect
  • Squarespace or Wix stores using their built-in checkout

Check your own provider's guide, because settings matter. Stripe, for example, explains which integration leads to which SAQ.

SAQ A-EP: the middle ground

You land here when your page collects card details but sends them straight to the provider without them being stored. Because your page code controls that step, an attacker who edits your site could skim cards. That is why this form has far more questions than SAQ A. Often the best fix is a small change: switch to hosted fields or a redirect, and you may drop to SAQ A.

SAQ D: the heavy one

Choose SAQ D if you store card numbers, capture them on your own server, or run a custom checkout that doesn't qualify for the others. It covers the whole standard. For most small businesses, the smart move is to redesign checkout so you never need it.

Step 3: Do the basics that apply to everyone

Even SAQ A has a short list of hygiene rules. This checklist covers the ground that most small sites need.

  • [ ] Never store full card numbers or the card security code (CVV, the 3 or 4 digit code on the card). The standard bans storing the security code after payment authorisation.
  • [ ] Never take card details by email, chat, social media DM or paper notes.
  • [ ] Use unique logins for every person who can access your shop, hosting and payment dashboard. No shared passwords.
  • [ ] Turn on multi-factor authentication (MFA) on your payment provider, hosting, domain registrar and website admin.
  • [ ] Update your CMS, plugins and themes. Remove any you don't use.
  • [ ] Serve every page over HTTPS, especially checkout.
  • [ ] Keep a list of the payment pages, scripts and providers you rely on.
  • [ ] Write a one-page policy saying who is responsible for security and what to do if something goes wrong.
  • [ ] Complete your SAQ and Attestation of Compliance (AOC) and send it to your provider each year.

Some SAQs, including in some cases SAQ A, may also require quarterly external vulnerability scans from an Approved Scanning Vendor (ASV). Check the requirements list on your form and ask your provider whether they require scans or include them.

Step 4: Ask your payment provider these questions

Your provider knows how you are set up better than any article does. Copy and send these:

  1. Which SAQ do you expect me to complete, given my integration?
  2. Do you have a PCI portal, and what is the deadline?
  3. Is my checkout a redirect, hosted iframe, hosted fields or direct post?
  4. Are there fees if I don't validate compliance?
  5. Do I need ASV scans, and do you include them?
  6. What do I do if I suspect card data has been exposed?
  7. Can you send your own PCI Attestation of Compliance for my records?

Keep the written answers. They show you did your homework if a bank or client asks.

Common mistakes to avoid

  • Assuming the provider's compliance covers you. Stripe, Shopify and PayPal are validated service providers, but that does not automatically cover your own setup. Ask your provider whether you must complete an SAQ. Some platforms, such as Shopify, handle much of the validation for hosted stores, while others expect you to file an SAQ yourself.
  • Picking SAQ A because it is easiest. Pick the one that matches your real setup. Answering incorrectly can fall apart in a breach investigation.
  • Forgetting other places cards turn up. Check old order emails, support tickets, spreadsheets and backups for stray card numbers.
  • Leaving the form until a deadline. Your provider's reminder is often the first you hear of it.

Where a human check fits in

PCI DSS is about proving you follow a standard. It does not tell you whether your site has holes. A small site can pass an SAQ and still run an outdated plugin or an exposed admin page. Start with the free website security check, and read is my website hackable for the common weak spots.

Key takeaways

  • PCI DSS is a card-industry rule passed on by your bank or provider, and it applies to every business that takes cards.
  • Work out how card data flows. A redirect or hosted iframe usually means SAQ A. A card form on your own page means A-EP or D. Storing or handling cards yourself means SAQ D.
  • Outsourcing card handling to a hosted checkout is the easiest way to cut your workload.
  • Use MFA, unique logins, updates and HTTPS, and never keep card numbers or CVVs.
  • Ask your provider which SAQ they expect, and keep their answers in writing.

A simple next step

A Bug Circuit audit is not a PCI certification, and it does not replace your SAQ. It is a manual security test of one website by a real person, with a written report that explains each issue and how to fix it. Essential is $49 one-time, and you can see the plans and prices before you decide.

Want certainty, not guesswork?

A real human security engineer audits your whole site by hand and sends a full report: every issue, its severity, and the exact fix. From $49, with a 14-day money-back guarantee.

See pricing

Frequently asked questions

What does PCI compliance require for a small business?
You must protect card data in line with PCI DSS, which in practice means completing the right self-assessment questionnaire (SAQ) each year and following its rules. For most small businesses that means using a hosted checkout, using MFA and unique logins, keeping software updated and never storing card numbers or security codes. Your payment provider tells you how to submit your results.
Which SAQ should a small business use?
It depends on how you take payments. SAQ A fits a fully outsourced online checkout (redirect or hosted iframe). SAQ A-EP fits sites whose own page sends card data to the provider. SAQ D is for everyone else, including businesses that store or process card data themselves. Check the eligibility rules on each form and confirm with your provider.
Is PCI compliance required for small businesses in the UK?
PCI DSS is mainly a contract rule set by the card brands, not a general UK law. It is enforced through your bank or payment provider's contract, so it applies to UK small businesses that take cards. Your provider will tell you which SAQ to complete and when. For legal questions, speak to a qualified adviser.
Does using Stripe, PayPal or Shopify make me PCI compliant?
Not automatically. These providers handle card data securely and make compliance much easier, often letting you use SAQ A. You still have to confirm how your checkout is set up, ask your provider whether you must complete a questionnaire and keep your own site and accounts secure.
What happens if a small business is not PCI compliant?
The consequences come from your contract. Your provider may charge non-compliance fees, ask for corrective action or, in serious cases, limit or end your ability to take cards. If card data is stolen from a non-compliant business, costs can be higher. Ask your provider what applies to you.

Keep reading

See what attackers see, for free

Run the free passive check on your website. No login, no impact on your site, results in seconds.

Ready for the full manual audit? See pricing

Published by Bug Circuit. Written with AI assistance and reviewed for accuracy before publishing.