Skip to content

Retail and E-commerce Cybersecurity: Securing Store and Site

Payment terminals, online stores, PCI DSS 4.0.1, gift card fraud and customer data: a practical retail cybersecurity plan for Canadian small businesses.

By the Cyber Caribou team6 min read

It's the Monday after a busy December weekend at a clothing boutique in Montréal's Mile End. Sales were strong in store and online. Then three customers call: charges they don't recognize have appeared on their credit cards. The investigation finds that a script, slipped in through a poorly maintained plugin, had been showing shoppers a fake payment form for weeks. Orders went through normally. Nobody noticed a thing.

Retail combines two worlds that fraudsters love. There's the store, with payment terminals, a point-of-sale system and Wi-Fi. And there's the online shop, with its platform, apps and admin accounts. Add the customer list from your loyalty program, and you have exactly what criminals are after: money and data.

The good news: the most effective protections are often the cheapest. Choose the right way to take payments, lock down your accounts and keep your networks apart.

TL;DR

  • The less your business touches card numbers, the simpler your PCI DSS compliance and the lower your risk.
  • In store: use terminals supplied by your payment provider, keep them off the customer Wi-Fi and give every employee their own POS login.
  • Online: require multi-factor authentication on every admin account, inventory your apps and plugins, and watch the scripts on your checkout pages.
  • Customer data is personal information, covered by Quebec's Law 25 and by privacy laws elsewhere in Canada.

Where the risks hide in a retail business

Before you buy anything, map where you're exposed. Most stores share the same weak spots.

AreaTypical threatFirst fix
Payment terminalsTampered or swapped device; terminal on the same network as everything elseProvider-supplied terminals, regular inspection, separate network
Point-of-sale (POS) systemRansomware; vendor remote access left openUpdates, on-demand remote access, MFA
Online storeMalicious script on the checkout page; vulnerable pluginProvider-hosted payment page, script inventory
Admin accountsPhishing; reused passwordsMFA, named accounts, least privilege
Customer dataForgotten export in a shared folder; data leakCollect less, restrict access
Gift cards and refundsExternal or internal fraudDual approval, report reviews

PCI DSS 4.0.1: what a merchant needs to know

PCI DSS is the security standard set by the major card brands. Version 4.0.1, published in June 2024, became the only active version when 4.0 was retired on December 31, 2024, and the "future-dated" requirements have applied since March 31, 2025.

It isn't a law; it's a contractual obligation. Your payment provider (the acquirer) or the card brand decides how you must validate compliance, and the PCI Security Standards Council tells merchants to check with them when in doubt.

For most small businesses, validation means a self-assessment questionnaire (SAQ). Which one applies depends on how you take cards:

Your setup (simplified)Likely SAQ
Online store that redirects to a payment page hosted by a compliant provider, or embeds it entirely in an iframeSAQ A
Online store whose own pages can affect the payment formSAQ A-EP
Standalone approved terminals connected over IP, linked to no other systemSAQ B-IP
Terminals that are part of a validated point-to-point encryption (P2PE) solutionSAQ P2PE
Manual entry, one transaction at a time, into a hosted virtual terminalSAQ C-VT
Anything else, including storing card numbersSAQ D

One recent change matters for online stores: since March 31, 2025, the revised SAQ A requires merchants to confirm their site isn't susceptible to script attacks that could affect their e-commerce systems.

Shrinking your scope is still the best strategy. A hardware store in the Ottawa Valley used to jot down card numbers taken over the phone, then key them in at closing. Switching to a virtual terminal and emailed payment links meant it stopped keeping card numbers altogether, and its questionnaire got simpler. Our guide to PCI DSS 4.0.1 for small businesses covers the requirements in detail.

The store: terminals, POS and Wi-Fi

Terminals. Use the ones your payment provider supplies and keep an inventory: model, serial number, location. PCI DSS requires merchants to protect them from tampering and substitution. In practice, someone checks seals, cables and appearance every week, and nobody hands a terminal to a "technician" without an appointment confirmed with the provider.

Network. The Canadian Centre for Cyber Security recommends segmenting point-of-sale terminals and putting guest Wi-Fi on a separate access point. The Wi-Fi you offer shoppers should never be able to see the till. Our article on business Wi-Fi security explains how.

POS system. One login per employee, not a shared code taped under the cash drawer. Keep the POS software patched, and switch on the vendor's remote access only when needed, with multi-factor authentication.

The online store: accounts, plugins and scripts

Whether your store runs on a hosted platform or your own server, four habits matter.

  1. Protect admin accounts. Require MFA for the owner, staff and your web agency. Everyone gets their own account, with only the permissions they need.
  2. Clean up your apps and plugins. Every add-on is someone else's code running on your site. Remove what you no longer use and install updates promptly.
  3. Watch your scripts. The Mile End attack relied on an unwanted script. Keep a list of the scripts allowed on your checkout pages and use a Content Security Policy (CSP). Our security headers checker shows in seconds whether your site has one.
  4. Block card testing. Bots try stolen cards through bursts of small purchases. Turn on your payment provider's fraud filters, rate-limit attempts and add bot protection at checkout.

If your store is custom-built, a web application penetration test finds the holes before fraudsters do. Like any penetration test, it requires written authorization (Criminal Code, s. 342.1), including your host's where applicable.

Fraud: gift cards, refunds and fake suppliers

Not all retail fraud goes through IT. Three scenarios come up again and again:

  • Gift cards. A fake "district manager" calls the store and asks staff to activate cards for a VIP customer. Simple rule: no activation without real payment, no matter who's calling.
  • Refunds. Set a threshold above which a second employee must approve, and review the refunds and voids report every week.
  • Fake suppliers. An email announces that a wholesaler's banking details have changed. Always confirm by phone, using the number you already had on file.

Customer data and privacy law

Loyalty programs, newsletters, customer accounts, deliveries: your business holds more personal information than you might think. In Quebec, Law 25 requires you to protect it, keep a register of every confidentiality incident and, if an incident presents a risk of serious injury, promptly notify the Commission d'accès à l'information and the people affected. Retailers in other provinces have comparable obligations under federal or provincial privacy law.

In practice: collect only what you use, limit who can export the customer list, and delete old exports sitting in shared folders. Run your approach past your legal counsel.

Your retail security checklist

  • Know which PCI DSS questionnaire applies to you, and complete it every year.
  • No card numbers kept on paper, in spreadsheets or in email.
  • Terminal inventory and weekly inspection.
  • Terminals and POS on a network separate from customer Wi-Fi.
  • One login per employee on the POS and the online platform.
  • MFA on every admin account and on email.
  • A list of approved apps, plugins and scripts on the online store.
  • Payment provider fraud filters switched on.
  • Dual approval for large refunds and gift card activations.
  • An up-to-date incident register.

Want to know where your real gaps are, from the till to the checkout page? Our team can test your online store through a well-scoped penetration test and hand you a prioritized action plan.

Frequently asked questions

Does a small shop really need to be PCI DSS compliant?+

Yes, as soon as it accepts credit cards. PCI DSS isn't a law; it's a requirement built into your agreement with your payment provider. Most small merchants prove compliance with an annual self-assessment questionnaire (SAQ), and its length depends on how you accept payments.

If my online store runs on a hosted platform like Shopify, is security handled for me?+

Not entirely. The platform secures its own infrastructure, but you remain responsible for your admin accounts, the apps and scripts you add, the access you give staff and agencies, and any customer data you export. Taking over the owner account is enough for a criminal to alter the store or steal the customer list.

Is our loyalty program data covered by privacy law?+

Yes. Names, email addresses, phone numbers and purchase histories are personal information. In Quebec, Law 25 requires you to protect them, restrict access and log every confidentiality incident; other provinces have comparable rules under federal or provincial privacy legislation. Check edge cases with your legal counsel.

What should we do if customers report fraudulent charges after shopping with us?+

Take it seriously, especially if it happens more than once. Notify your payment provider, check your terminals and your website's checkout pages, and document what you find. Several similar reports can point to a tampered terminal or a malicious script on your online store.

Sources

  1. 1.PCI Security Standards Council: Just Published: PCI DSS v4.0.1
  2. 2.PCI Security Standards Council: Important Updates Announced for Merchants Validating to Self-Assessment Questionnaire A
  3. 3.PCI Security Standards Council: Merchant Resources
  4. 4.Canadian Centre for Cyber Security: Protecting your organization while using Wi-Fi (ITSAP.80.009)
  5. 5.LégisQuébec: Act respecting the protection of personal information in the private sector (P-39.1)