Join our Newsletter — 33% off our NHI Course
Home› Guides› Card Payments Security for Small Merchants Guide: Terminals,…
Guide Security Policies & Awareness

Card Payments Security for Small Merchants Guide: Terminals, Online Checkout and PCI SAQs

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 27 October 2026 14 min read
On this page

A small shop can be breached through a tampered card terminal, a skimming script on its checkout page or a supplier's remote access login, and it is still responsible for the cards it takes. Most small merchants do not need a security team to accept cards safely, but they do need to choose the right payment set-up, know which PCI DSS Self-Assessment Questionnaire (SAQ) applies, and keep a short list of controls running. This guide explains how payment set-ups differ in risk and PCI scope, how the 2025 changes to SAQ A affect online shops, how to protect terminals and checkout pages, what to ask payment providers, and what to do if card data may have been stolen. It is written for owners and managers of small shops, restaurants, trades and online stores, and the IT providers who support them. For a step-by-step compliance list, see the PCI DSS Readiness Checklist.

Key takeaways

  • Your payment set-up decides most of your risk. A standalone terminal or a fully hosted payment page leaves far less to secure than a till system connected to everything else or a checkout built on your own site.
  • Your acquirer decides what you must validate. The PCI Security Standards Council (PCI SSC) says payment brands set validation rules and directs merchants to their acquirer (merchant bank) to confirm which SAQ to complete.
  • SAQ A changed in 2025. From 31 March 2025, online shops that embed a provider's payment form must confirm their site is not susceptible to script attacks, either with their own script controls or the provider's written confirmation.
  • Terminals need a routine. Keep an inventory with photos, inspect devices for tampering, control who repairs them and keep payment devices off the customer Wi-Fi.
  • Do not keep card data you do not need. Never take card numbers by email, shred paper records, and let a PCI DSS compliant provider hold card data wherever possible.

Payment set-ups and their risk

PCI SSC's small merchant guidance groups payment systems by complexity: the more connected systems involved, the more there is to secure. The table compares the common set-ups and the SAQ each usually maps to. SAQ names are PCI SSC's; eligibility criteria are detailed in each questionnaire, and only your acquirer can confirm which one you should use.

Set-upHow it worksRelative riskUsual SAQ
Fully hosted or redirect checkoutCustomer is sent to the provider's page, or receives a payment link; your site never handles card dataLowSAQ A
Embedded payment form (iframe)Provider's form sits inside your checkout pageLow to medium: your page can still be attacked by scriptsSAQ A, with the new script criterion
Direct post or JavaScript formYour page builds the form or sends data straight to the providerMedium to high: your site affects card data securitySAQ A-EP
Standalone terminal (phone line or cellular)Terminal connects only to the processorLowerSAQ B or B-IP (IP-connected)
Terminal integrated with a till or EPOS systemCard data passes through or alongside the merchant's network and systemsHigher: every connected system needs securingSAQ C, or SAQ D
Virtual terminal in a browserStaff key card details into the provider's web page for phone ordersMedium: the PC used must be secured and isolatedSAQ C-VT
PCI-listed P2PE solutionCard data encrypted in a validated device and decrypted only by the providerLowSAQ P2PE
Software-based PIN entry on a phone or tabletPIN entered on a commercial device using a validated solutionLow to mediumSAQ SPoC
Own payment system, stores card dataYou process or keep card numbers yourselfHighSAQ D

Two points from PCI SSC's merchant pages are often misunderstood. Encrypting card data is acceptable under Requirement 3.5.1, but encryption alone generally does not take an environment out of scope. A PCI-listed point-to-point encryption (P2PE) solution can significantly reduce the number of applicable requirements, but it does not remove PCI DSS from the merchant altogether. For scoping detail, see the PCI DSS Scoping and Segmentation Guide.

Choosing a set-up: decision guidance

  • New online shop: use a fully hosted page, redirect or payment link where the customer experience allows it. It gives the smallest scope, and the SAQ A script criterion does not apply to redirects or fully outsourced payments.
  • Online shop wanting an embedded checkout: choose a provider that will confirm in writing that its embedded solution protects your page from script attacks when you follow its instructions, and keep that confirmation for your SAQ.
  • Shop or restaurant: a standalone, PCI-approved PIN Transaction Security (PTS) terminal or a listed P2PE solution is simpler to secure than a terminal integrated into a till on the shop network.
  • Phone orders: use a virtual terminal on a dedicated device, or a phone payment service that takes card details by keypad, so staff never write or hear card numbers.
  • Growing business: each new integration (loyalty, booking, stock system) can pull more systems into scope. Ask your provider how each change affects your SAQ before you connect it.

Online checkout and the 2025 SAQ A change

Web skimming, where malicious JavaScript on a checkout page copies card details as customers type, is the main threat to small online shops. PCI DSS v4.0.1 added Requirements 6.4.3 (authorise and check the integrity of every script on the payment page, and keep an inventory with a justification for each) and 11.6.1 (detect unauthorised changes to payment page scripts and security-impacting HTTP headers as the browser receives them). Both became mandatory after 31 March 2025.

On 30 January 2025 PCI SSC removed 6.4.3, 11.6.1 and the related targeted risk analysis (12.3.1) from SAQ A, replacing them with an eligibility criterion: the merchant must confirm its site is "not susceptible to attacks from scripts that could affect the merchant's e-commerce system(s)". PCI SSC stressed that the underlying requirements still apply. FAQ 1588, published on 28 February 2025, explains two ways to meet the criterion:

  1. Protect the page yourself: use techniques such as those in 6.4.3 and 11.6.1, deployed by you or a third party.
  2. Rely on your provider: obtain confirmation from a PCI DSS compliant payment provider that its embedded solution, implemented according to its instructions, includes protection against script attacks.

The criterion applies to pages that embed a provider's payment form, for example in an iframe. It does not apply where customers are redirected to the provider (HTTP 30x, meta refresh or JavaScript redirect) or where payments are fully outsourced, such as an emailed payment link.

Practical steps for a small online shop, whatever the SAQ:

  • Remove unneeded scripts from checkout pages: chat widgets, analytics and marketing tags are common entry points.
  • Lock down the site admin: MFA on the content management system, hosting control panel and any cloud storage or CDN account, and remove old admin users. See the Small Business Website Security Guide.
  • Keep the platform patched: core, theme and plug-ins, with automatic updates where your platform supports them. See the PHP and WordPress Security Guide.
  • Use TLS everywhere: the FTC's web host guidance stresses encrypting customers' card numbers in transit.
  • Watch for change: a script monitoring service or your provider's tooling should alert you when checkout page scripts change. See the PCI DSS Payment Page Script Requirements Guide.

Card terminals and in-store payments

PCI SSC's Guide to Safe Payments for small merchants sets out terminal basics that remain sound:

ControlWhat to doWhy
Approved devicesUse PCI-approved PTS terminals that support EMV chip, validated payment applications, and qualified integrators and resellers (QIRs) for installationReduces device and installation weaknesses
Inventory and photosRecord every terminal's make, model and serial number, with photos of how it should lookMakes swaps and add-ons easier to spot
Tamper inspectionCheck for broken seals, unfamiliar cabling or extra devices; stop using and report a suspect terminal at onceSkimming overlays and swapped devices
Controlled repairsVerify the identity of anyone claiming to service terminals; supervise third parties with physical accessFake engineers swap or bug devices
Network isolationDo not use payment devices for browsing, email or social media; keep payment systems on a separate network from customer Wi-FiStops malware and other users reaching payment systems
EncryptionPrefer listed P2PE solutions and terminals with secure reading and exchange of data (SRED)Card data is useless if intercepted

PCI DSS v4.0.1 Requirement 9.5.1 formalises this: point-of-interaction devices must be inventoried, periodically inspected and staff trained to recognise tampering. Train staff to refuse a "technician" who arrives without notice, and to tell a manager if a terminal looks or feels different.

Suppliers, remote access and passwords

Many small merchant breaches start with a supplier: the till vendor's remote support tool, the web developer's admin login or the hosting account. The PCI SSC guide and the FTC's vendor security advice agree on the essentials.

  • Know your providers: list your acquirer, terminal vendor, integrator, web host and payment gateway, with contact numbers, and confirm each is PCI DSS compliant. PCI SSC publishes a Questions to Ask Your Vendors tool for this.
  • Remote access off by default: ask vendors whether they use remote access; keep it disabled unless needed, enable it only on request, require MFA and unique credentials per provider.
  • Put security in contracts: the FTC advises making specific standards non-negotiable, defining how vendors may use and delete data, verifying compliance rather than relying on assurances, and limiting access to what is needed for as long as needed.
  • Change default passwords on terminals, routers and tills before use, give every employee a unique login, and never share credentials. PCI DSS v4.0.1 sets a 12-character minimum for passwords in scope (Requirement 8.3.6).
  • Scan what faces the internet: if your SAQ requires it, use a PCI Approved Scanning Vendor (ASV) for external vulnerability scans and fix what it finds.

Where identity fits

The logins that matter most in a small merchant are rarely the owner's: they are the shared till PIN, the developer's hosting account, the vendor's remote support account and the API keys that connect a website to its payment gateway or cloud storage. In the AI agent retail card theft campaign, an AWS key with write access to the bucket behind one retailer's CDN let attackers serve a skimmer from the shop's own infrastructure, and database passwords in a configuration file helped them move between hosts. Treat these as identities: one per person or system, removed when no longer needed, with the least access that works. See the PCI DSS Requirements for Service Accounts and NHIs Guide (8.6).

Storing less card data

  • Never by email or chat: do not accept card numbers by email, messaging apps or social media, and tell customers so on your site.
  • Paper: if you must take details on paper for phone orders, process them promptly and shred them; never record the security code.
  • No sensitive authentication data: card security codes, full track data and PINs must not be kept after authorisation under PCI DSS.
  • Tokenisation: use your provider's tokens for repeat billing, so a stolen database contains nothing usable. See the Tokenisation and Data Masking Guide.

A phased plan for a small merchant

  1. Week 1, map: list every way you take cards (terminals, website, phone, invoices, payment links) and every provider involved. Ask your acquirer which SAQ applies.
  2. Week 2, quick wins: change default passwords, turn on MFA for the payment gateway, hosting and website admin, remove old users, and stop taking cards by email.
  3. Weeks 3 to 4, terminals: build the terminal inventory with photos, start a weekly inspection, and move payment devices to their own network.
  4. Month 2, online checkout: remove unnecessary checkout scripts, get your provider's written script-protection confirmation or deploy script monitoring, and confirm automatic updates.
  5. Month 3, validate: complete the SAQ with your acquirer's tools, keep the evidence, and set a calendar for annual validation and any quarterly scans.
  6. Ongoing: review the plan whenever you add a payment method, change website platform or change provider.

Test before you change: try a new checkout or provider set-up on a staging site or with low-value test transactions, and keep the old configuration documented so you can roll back if payments fail.

Detection, measurement and what to do if cards are stolen

Signs of compromise include customers reporting fraud after shopping with you, your acquirer or card brand notifying you of a common point of purchase, unexpected script or file changes on the website, and a terminal that looks different. Useful measures:

  • Terminal inspections completed on schedule (target 100%).
  • Checkout page scripts without a documented reason (target zero).
  • Accounts with access to the payment gateway, website admin or hosting that lack MFA (target zero).
  • Days since the last review of supplier access.
  • Days from SAQ due date to submission.

If you suspect a breach, contact your acquirer first; it will explain the card brands' process, which may require a PCI Forensic Investigator. Do not wipe or rebuild affected systems before you have taken advice, and take infected devices off the network. The FTC's ransomware advice is to disconnect without powering down, since that may destroy evidence. Report crime to the police (in the UK, Report Fraud; in the US, the FBI) and consider data protection notification duties. See the Web Skimming Incident Playbook and the Small Business Incident Response Guide.

Framework mapping

ThreatMITRE ATT&CK v20ControlNIST CSF 2.0 / SP 800-53 Rev. 5
Skimming script on checkoutT1059.007 JavaScript, T1185 Browser Session HijackingScript inventory, integrity and change detection (PCI DSS 6.4.3, 11.6.1)PR.PS-01, SI-7, CM-3
Compromised supplier or plug-inT1195.002 Compromise Software Supply ChainVendor compliance checks and contractsGV.SC-07, SA-9
Tampered or added terminal hardwareT1200 Hardware AdditionsInventory and inspection (PCI DSS 9.5.1)PE-6
Card data stored or sent insecurelyStore less, tokenise, TLSPR.DS-01, PR.DS-02
Unpatched internet-facing systemsUpdates and ASV scansRA-5

Common failure patterns

  • Assuming the provider covers everything: an embedded payment form is safe only if the page around it is; the SAQ A criterion exists because scripts on the merchant page can still capture data.
  • Custom checkout code on an unmaintained site: the AI agent card theft campaign filtered targets to shops running custom code, at a cost of about $25 per target.
  • Cloud and hosting keys with write access to checkout files: one leaked key let attackers modify what every customer's browser loaded.
  • Vendor remote access left on permanently with a shared password across that vendor's customers.
  • Payment terminal on the customer Wi-Fi, or a till PC used for email and browsing.
  • Card numbers in the email inbox from customers or staff taking phone orders.

Practitioner checklist

  • Ask your acquirer, in writing, which SAQ applies to each way you take cards.
  • Prefer hosted, redirect, P2PE or standalone terminal set-ups that minimise scope.
  • For embedded checkouts, keep the provider's script-protection confirmation or deploy script monitoring.
  • Turn on MFA for payment gateway, website admin, hosting, cloud storage and vendor remote access.
  • Keep a terminal inventory with photos and inspect terminals on a fixed schedule.
  • Put payment devices on a separate network from customer Wi-Fi and office browsing.
  • Stop accepting card data by email or chat, and shred paper records after processing.
  • Confirm every payment supplier is PCI DSS compliant and list their contact numbers.
  • Know who to call first if a breach is suspected: your acquirer.

Standards and references

Related NHI Mgmt Group resources: PCI DSS Readiness Checklist · PCI DSS 4.0 Guide · Cybersecurity for Retail and Ecommerce Guide · Small Business Cybersecurity Basics Guide

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 27 October 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.