Payment fraud prevention for smaller online businesses
Card-not-present fraud, chargebacks, SCA and 3-D Secure, fraud screening and PCI DSS v4.0.1 scope explained for small online merchants, with a checklist.
Data minimisation, access control, patching, backups, admin MFA, logging, vendor risk and breach response for small online shops, with a 30-day checklist.
A small online retailer holds more sensitive data than it might think: customer names and addresses, order histories, email lists, staff details, supplier contracts and the keys to payment, marketplace and advertising accounts. Most of the incidents that hurt small shops are not sophisticated. They come from a reused password on an admin account, an unpatched plugin, an old agency login nobody removed, or a backup that turned out not to work. This guide covers the basics that prevent most of them, and closes with a checklist for the first 30 days.
The guidance draws on free government material written for small organisations: the UK National Cyber Security Centre’s Small organisations guide to cyber security, ENISA’s cybersecurity guide for SMEs and CISA’s cyber guidance for small businesses. All three are worth reading in full.
You cannot protect what you have not listed. Spend an hour writing down:
This list becomes your record for access reviews and incident response, and it overlaps heavily with the record-keeping the GDPR expects. Our guide to GDPR obligations for online businesses covers that side.
Data minimisation is a legal principle under Article 5 of the GDPR and also the cheapest security control available. Data that was never collected cannot leak.
In practice:
Illustrative example: a ceramics shop selling on its own site and a marketplace exports all orders every month to a spreadsheet for bookkeeping. After three years, the shared drive holds 36 files with every customer’s name, address and phone number. Replacing the exports with a direct integration to the accounting tool, and deleting the old files once retention needs are met, removes a large and entirely avoidable exposure.
Give each person the lowest level of access that lets them do their job, and give every person their own login. Shared accounts make it impossible to see who did what or to remove one person’s access cleanly.
Review access at least quarterly and immediately when someone leaves.
Turn on multi-factor authentication (MFA) for the ecommerce admin, marketplace seller accounts, email (especially the address used for password resets), domain registrar, hosting, payment provider and accounting. Email and the domain registrar matter as much as the shop itself: whoever controls them can reset almost everything else.
Prefer phishing-resistant methods, passkeys or hardware security keys, for owner and admin accounts. Authenticator apps are a reasonable second choice. Avoid SMS for admin access where anything better is available. The reasons are explained in our guide to protecting ecommerce customer accounts.
Third-party extensions are the main way small shops’ attack surface grows. Each plugin, theme or app is code written by someone else, running with access to your store.
If you run a self-hosted platform, also consider whether a managed hosting provider or a hosted platform would remove patching work you are not equipped to do. That is a legitimate security decision, not just a cost one.
A widely used rule of thumb is 3-2-1: three copies of your data, on two different types of storage, with one copy off-site. Because ransomware and account compromise can delete or encrypt connected backups, make sure at least one copy is offline, immutable or held in a separate account that day-to-day credentials cannot reach.
Hosted platforms back up their own infrastructure, but that does not necessarily let you restore your product catalogue, content or settings to last Tuesday after a mistake or malicious change. Check what your platform offers and consider exporting key data or using an app built for store backups.
Most importantly, test a restore. A backup you have never restored is an assumption, not a control. The NCSC’s small organisations guide puts backups first for good reason.
You do not need a security operations centre, but you do need to be able to answer “what happened?” Turn on and retain the logs your platforms already provide: admin activity, staff logins, app installations, payout and bank-detail changes, and email-account sign-ins. Enable alerts for new admin users, changes to payout details, new email forwarding rules and logins from new countries. A forwarding rule silently copying your inbox to an outside address is a classic sign of a compromised email account.
Your security depends on the providers you use. For each important vendor, ask: Does it support MFA and named user accounts? Where is data stored and who can access it? Does it offer a data processing agreement, as the GDPR requires for processors? How will it tell you about a breach? Is there an exit route that lets you export your data?
Keep the answers with your inventory. The NCSC’s supply chain security guidance goes further for businesses with more complex supplier relationships.
A one-page incident plan should name who decides, who to call (hosting, platform support, payment provider, IT help, insurer if you have cyber cover), where your inventory and contact list live offline, and how to communicate with customers. The NCSC’s incident management collection and its free exercise materials help small teams rehearse.
Under Article 33 of the GDPR, and the equivalent in the UK GDPR, a controller must notify the supervisory authority of a personal data breach without undue delay and, where feasible, within 72 hours of becoming aware of it, unless the breach is unlikely to result in a risk to individuals. Where the risk to individuals is high, Article 34 also requires telling the people affected. You must document every breach, including those you decide not to report. The EDPB’s Guidelines 9/2022 explain how to assess risk and what “becoming aware” means. In the UK, reports go to the Information Commissioner’s Office; in the EU, to the relevant national data protection authority.
At the time of writing, the European Commission’s digital omnibus proposals, published in November 2025, would change breach notification, including a longer deadline and a higher threshold for notifying regulators. These remained proposals in November 2026, so the 72-hour rule continues to apply. Check for updates before relying on any change.
A breach is a security incident and possibly a crime. In the UK, cyber crime against businesses can be reported to Report Fraud; elsewhere, to national police or cyber agencies.
For UK businesses, Cyber Essentials is a government-backed certification covering five technical controls: firewalls, secure configuration, security update management, user access control and malware protection. Cyber Essentials Plus adds independent technical testing. The requirements were updated to version 3.3 from April 2026, including making clear that cloud services cannot be excluded from scope. Even if you never certify, the requirements make a sensible baseline. EU businesses can use ENISA’s SME guide in the same way.
| When | Actions |
|---|---|
| Days 1–3 | Turn on MFA for admin, email, domain registrar, hosting, payment provider and marketplace accounts. Remove shared logins. |
| Days 4–7 | Build your systems, data and access inventory. Remove ex-staff, old agency accounts and unused apps. |
| Days 8–14 | Update platform, plugins, themes and devices; enable automatic updates where safe. Delete old exports and unnecessary data. |
| Days 15–21 | Set up 3-2-1 backups with one copy isolated, and test a restore. Enable admin, login and payout-change alerts. |
| Days 22–30 | Write a one-page incident plan, including the 72-hour breach process. Check key vendors’ MFA and data processing terms. Read the Cyber Essentials requirements and note the gaps. |
In our assessment, a small retailer that completes these 30 days will have closed off most of the routes behind real-world incidents: stolen admin passwords, abandoned accounts, unpatched extensions and unrecoverable data. None of it requires specialist staff. It requires an owner who treats security as a recurring operational task, like stocktaking, rather than a one-off project.
This article is general information, not legal advice. For specific obligations under data protection law, consult the relevant regulator’s guidance or a qualified adviser.
Card-not-present fraud, chargebacks, SCA and 3-D Secure, fraud screening and PCI DSS v4.0.1 scope explained for small online merchants, with a checklist.
A practical guide to defending online-shop customer accounts against credential stuffing and takeover, based on NIST SP 800-63B-4 and OWASP guidance.
How the most common scams against marketplace buyers and sellers work, the red flags that give them away, and where to report them in the UK, EU and US.