Email security for retail stores: protect your shops, staff and payments
Retail stores are targeted by email because managers pay suppliers, sell gift cards and rely on card processor and POS accounts. Protect them with personal logins and MFA, a phone call-back for supplier bank changes, a rule that nobody buys gift cards on an email request, no card numbers by email, and DMARC on your domain.
On this page 9 sections
A retail store runs on more email than most owners realize. Supplier orders and invoices, card processor alerts, gift card and loyalty programs, messages from head office and customer complaints all land in a handful of inboxes, often shared between managers and shifts. This guide covers the email scams that target physical stores and small retail chains, the card data rules that apply, and a checklist you can work through before your next busy season.
If you also sell online, read email security for ecommerce stores for order notification and platform issues. This page focuses on the shop floor and the back office.
Why do retail stores need email security?
Retail stores need email security because their inboxes control payments to suppliers, access to card processing and point-of-sale (POS) accounts, and the authority to buy gift cards, all handled by busy staff who switch between the counter and the back office. A point-of-sale system is the register software and card terminal you use to take payments, usually managed through an online account that's reached by email sign-in and password reset.
Three things make retail different from an office business:
- Many people, few accounts. Stores often share one mailbox per location, so a password ends up on a sticky note and nobody knows who signed in.
- High staff turnover and seasonal hiring. New staff don't know what normal looks like, and old staff keep access after they leave.
- Managers can spend money immediately. A manager can buy gift cards from the register or pay a supplier from the store account without waiting for anyone.
The losses that follow are real. The FBI's 2025 IC3 Annual Report recorded 24,768 business email compromise complaints and $3,046,598,558 in reported losses in 2025 across all industries. Business email compromise (BEC) is fraud where a criminal impersonates or takes over a trusted email account to get money sent to them.
What email scams target retail stores?
Retail stores face seven common email scams. The table shows who gets the email and the habit that stops each one.
| Scam | What arrives | Who it targets | What stops it |
|---|---|---|---|
| Fake supplier invoice or bank change | An invoice or "new bank details" from a regular supplier | Owner, bookkeeper | Call the supplier on a known number |
| Gift card request from "the boss" | "Buy six $200 gift cards for a customer, send me the codes" | Store managers | A written rule: no gift cards on email requests |
| Fake card processor or POS alert | "Your account is locked," "payout on hold" | Owner, managers | Open the processor's site or app yourself |
| Fake customer complaint or receipt | An attachment or link "showing" a bad purchase | Store inboxes | Don't open unexpected attachments; report them |
| Fake shipping or delivery notice | "Your stock delivery failed, reschedule here" | Receiving staff | Check the carrier's site directly |
| Ransomware via email | A malicious attachment or download link | Anyone | Filtering, updates, offline backups |
| Fake email in your store's name | Promotions or "refund" messages to your customers | Your customers | DMARC and lookalike monitoring |
Fake supplier invoices and bank detail changes
The scam with the biggest price tag is a supplier "changing banks." The email may come from a lookalike of the supplier's domain or from the supplier's own hacked mailbox, so it can arrive inside a real thread. The FTC's Cybersecurity for Small Business guidance gives the fix: "require your employees to call and confirm wire transfer requests that they receive through email." Use a number from an old invoice or contract. Our guides to vendor invoice fraud and fake invoice and payment emails cover the full procedure.
Gift card requests sent to store managers
Retail is a natural target for the boss gift card scam, because managers can buy cards at their own registers. The email looks like it's from the owner or a district manager and asks for cards "for a customer" or "for staff awards," with the codes sent back by email. Here's an example of the kind of message to treat as fraud:
Example: "Hi Sam, are you on shift? I need you to grab 6 x $200 gift cards from the register for a client gift. Scratch the backs and email me photos of the codes. I'm in meetings all day so don't call. Thanks, Laura (Regional Manager)."
The FTC's gift card guidance is direct: "No real business or government agency will ever tell you to buy a gift card to pay them." If codes have already been sent, the FTC says to report the scam to the gift card company right away, keep the cards and receipts, and report it at ReportFraud.ftc.gov.
Fake card processor and POS alerts
Criminals copy the emails your payment processor sends: payouts on hold, accounts suspended, a new device signed in. The link goes to a fake sign-in page that steals the password to the account that controls your payouts. Square's phishing help page is a good model of what real processors say: it will never ask for "sensitive information" such as full bank account details or card numbers by email, phone or text; you should check that the browser shows https://squareup.com/login before signing in; and suspicious mail can be forwarded to spoof@squareup.com. Whatever processor you use, find its equivalent page and pin it in the back office.
Fake customer complaints, receipts and deliveries
A store inbox accepts mail from anyone, which makes "customer complaint" emails an easy lure. They carry an attachment or link said to show a receipt, a photo of a faulty product or a refund form. The FTC notes that "Most ransomware attacks start with phishing or scam emails." Staff should never enable macros or open archives from strangers; read dangerous email attachment types and fake delivery notification emails for the common forms.
Can a retail store take card payments by email?
No. Don't ask customers to email card numbers, and don't send card numbers by email yourself. The PCI Security Standards Council's FAQ 1085 says "PCI DSS Requirement 4.2.2. prohibits the sending of unprotected primary account numbers (PANs)" via "end-user messaging technologies, whether sent internally or over public networks." A PAN (primary account number) is the long number on a payment card, and PCI DSS is the card industry's data security standard that merchants agree to follow.
For phone or special orders, send a payment link from your processor or take the card through your terminal. If a customer emails a card number anyway, don't reply with it or forward it. Follow your processor's guidance on deleting it, and tell the customer how to pay safely.
How should store staff handle a payment or gift card request by email?
Store staff should never buy gift cards, change supplier bank details or send money because of an email alone, and should confirm any such request by calling the person on a number they already have. Write this down as a store policy and post it in the back office.
- Stop. Urgency, secrecy and "don't call me" are the signs of a scam, not of a busy boss. CISA lists "urgent or emotionally appealing language" first among its phishing signs.
- Check the full sender address, not just the display name. On a phone, tap the name to see it. See display name spoofing.
- Call the person on a number from the staff list or the supplier's file. Don't use any number in the email.
- Get a second approval for any supplier bank change or any purchase of gift cards for business use.
- Report the email using your mail app's report button, then tell the owner or IT contact so other stores can be warned. Our guide to reporting phishing emails shows where the buttons are.
- If money or codes have gone, call the bank or gift card company at once and file at ic3.gov and ReportFraud.ftc.gov.
How should a store with several locations set up email?
Give every manager and staff member who needs email their own account with multi-factor authentication (MFA), and use shared mailboxes for each location rather than shared passwords. MFA means a sign-in needs a second factor, such as an authenticator app, as well as the password. A shared mailbox is an inbox that several named users can open with their own logins, so access can be granted and removed per person.
- Personal accounts with MFA. Turn on MFA everywhere; start with Microsoft 365 Security Defaults or Google Workspace 2-Step Verification.
- Shared location mailboxes, such as
store12@, opened by named users. See shared mailbox spam protection. - Limit company-wide lists. Stop outsiders from mailing
allstores@; see restricting who can email distribution lists. - A start and finish routine for seasonal staff. Follow our new employee onboarding and offboarding checklists, and switch access off on the last day.
- Separate POS and processor logins from everyday email where your provider allows it, with MFA on the processor account itself.
How do you stop criminals sending email as your store?
Publish SPF, DKIM and DMARC for your domain and move DMARC to enforcement, so mail faking your exact domain is rejected by your customers' mail providers. SPF lists the servers allowed to send your mail, DKIM signs each message, and DMARC tells receivers what to do when both checks fail. Include every service that emails customers in your name: your POS system's digital receipts, loyalty program, email marketing tool and booking system. A record at enforcement looks like this example:
_dmarc.example-store.com TXT "v=DMARC1; p=reject; rua=mailto:dmarc-reports@example-store.com"
Start at p=none, check the reports, then tighten. The DMARC from none to reject guide has the steps, and the FTC's small business guidance says the same thing in plain terms: with email authentication, "Emails from imposters are either blocked or sent to a quarantine folder for further review." DMARC can't stop lookalike domains, so check yours with the Lookalike Domain Generator.
Is Microsoft 365 or Google Workspace protection enough for a retailer?
For a single shop, Microsoft 365 or Google Workspace configured properly is a reasonable start. Both filter spam and malware, support MFA and can tag external senders. Review the settings in Microsoft 365 preset security policies or Gmail spam settings in Google Workspace.
An MX-level filter adds a checkpoint before mail reaches your stores. MX-level filtering means your domain's MX records point to a filtering service that checks mail before your platform delivers it. It helps when phishing keeps reaching store inboxes, when managers need to release a held supplier email from a quarantine digest themselves, and when you run several store or brand domains. iBlockSpam prices per domain with unlimited mailboxes, so adding seasonal staff doesn't change the bill; see email security for small businesses.
Retail store email security checklist
- Give every staff member who needs email their own login, with MFA on.
- Replace shared store passwords with shared mailboxes opened by named users.
- Put MFA on your card processor, POS, bank and supplier portal accounts.
- Post a written rule: no gift card purchases or supplier bank changes on an email request.
- Call suppliers on a known number before any bank change, with a second approver.
- Never request or send card numbers by email; use processor payment links.
- Publish SPF, DKIM and DMARC, including POS receipt and marketing senders.
- Keep POS computers and office PCs updated, and keep offline backups.
- Train every new and seasonal hire on phishing in their first week.
- Remove email and POS access on each leaver's last day.
Next steps
- Run the free Email Health Check on your store's domain to see your MX, SPF and DMARC setup.
- Print the gift card rule and the supplier call-back rule for every back office before the holiday season.
- Read business email compromise prevention for the wider set of payment controls.
- If you want inbound filtering that each manager can handle from a digest email, see email security for small businesses. Pricing is per domain, not per mailbox.
More threat guides are in our phishing and threats topic.
Frequently asked questions
Why do scammers email store managers asking them to buy gift cards?
Store managers can buy gift cards on the spot, often from their own registers, and they're used to quick requests from head office. A criminal poses as the owner or a district manager and asks for cards for a customer or staff reward. The FTC says no real business will ever tell you to buy a gift card to pay them.
Is an email from my card processor about a locked account real?
Assume it isn't until you check. Don't use the email's links. Open your processor's site or app yourself and look for alerts. Square, for example, says it will never ask for sensitive information such as full bank details or card numbers by email, and asks sellers to forward suspected phishing to spoof@squareup.com.
Should seasonal retail staff get their own email accounts?
Yes, if they need email at all. A personal account with MFA lets you see who did what and remove access the day they leave. A shared store password is copied, written down and rarely changed. Give seasonal staff only the access they need, and switch it off at the end of the season.
Can a retail store take card payments over email?
Don't ask customers to email card numbers, and don't email them yourself. PCI DSS Requirement 4.2.2 prohibits sending unprotected card numbers by end-user messaging such as email, chat and SMS. Send a payment link from your processor instead, or take the card in store or over the phone through your terminal.
What should a store do when a supplier emails new bank details?
Hold the payment and call the supplier on a number from an old invoice, a contract or their official website, never one in the email. Ask a second person to approve the change. The FTC advises businesses to require staff to call and confirm wire transfer requests that arrive by email.
Sources
- FTC: Cybersecurity for Small Business (September 2025)
- FTC Consumer Advice: Avoiding and Reporting Gift Card Scams
- PCI Security Standards Council FAQ 1085: Can unencrypted PANs be sent over e-mail, instant messaging, SMS, or chat?
- Square Support: Recognize and report phishing scams
- CISA: Recognize and Report Phishing
- FBI IC3: 2025 IC3 Annual Report
See how your domain measures up
Run a free Email Health Check: MX, SPF, DKIM, DMARC and transport security in one scan, with the raw records shown. No sign-up.
Keep reading
What is display name spoofing, and how do you stop it?
Why email showing your CEO's name from a free account passes every check, how it differs from domain spoofing, and the Microsoft 365 and Gmail settings to use.
9 min read Phishing & threatsHow to prevent business email compromise (BEC)
What business email compromise is, what the FBI's 2025 IC3 figures show, and the payment checks and technical controls that stop BEC fraud at small firms.
9 min read Phishing & threatsFake invoice and payment emails: how to spot them
How to spot fake invoice emails: bogus renewal notices, domain and SEO bills, overdue invoices and refund call scams, plus an invoice check for staff.
9 min read