Key takeaways
- PCI DSS is the card industry's security standard; your acquirer or payment brand tells you how to validate[1].
- Most small restaurants validate with a self-assessment questionnaire (SAQ) chosen by how they take cards.
- The fewer places card data can touch your systems, the shorter and easier your SAQ.
- Common gaps: card numbers in notes, shared logins, guest Wi-Fi on the POS network and an SAQ never filed.
What PCI compliance means for a restaurant
The Payment Card Industry Data Security Standard, PCI DSS, is a set of security requirements created by the major card brands and maintained by the PCI Security Standards Council. The current standard is PCI DSS version 4.x[2]. It is not a federal law; it applies to you through your merchant agreement with your card processor, which is why the processor, not a government agency, asks you to prove compliance each year.
For most independent restaurants, proving compliance means completing a self-assessment questionnaire, or SAQ, and sometimes running quarterly network scans. The PCI Council encourages merchants to contact their merchant bank (acquirer) or the payment brands to identify the right SAQ based on their eligibility[1]. If you never file it, many processors add a monthly non-compliance fee to your statement, which is often the first sign an owner sees that PCI exists at all.
Why it matters more as payments move to the table and online
Restaurants now take cards in more places than the old counter terminal. Mobile ordering is mainstream: 57 percent of adults have recently used it, including 74 percent of millennials and 65 percent of Gen Z adults[3]. Sixty-five percent of adults would be comfortable paying at a full-service restaurant with a tablet at the table[4]. Each new way of taking cards, from handhelds to QR payment to phone orders, changes where card data flows and can change which SAQ applies.
Source: National Restaurant Association, 2025[3]
Show the data
| Item | Value |
|---|---|
| All adults | 57% |
| Millennials | 74% |
| Gen Z adults | 65% |
The cost of getting it wrong is not only a monthly fee. A breach can bring card brand assessments, forensic investigation costs, higher processing rates and lost guest trust. Swipe fees are already a significant challenge for more than 9 in 10 operators[5]; a breach makes them worse.
Which SAQ fits your setup
The SAQ you complete depends on how cards are accepted. These are the main merchant SAQ types as the PCI Council described them in its information supplement on the questionnaires[1]. Eligibility criteria are updated with each version of the standard, so confirm details against the current SAQ and with your acquirer.
| SAQ | Who it is for (PCI Council description, summarized) | Typical restaurant situation |
|---|---|---|
| A | Card-not-present merchants that have fully outsourced all cardholder data functions to validated third parties, with no electronic storage, processing or transmission of card data on their systems | Online ordering where the payment page is fully hosted by the provider, if that is the only channel being assessed |
| A-EP | E-commerce merchants whose website does not receive card data but can affect the security of the payment transaction | Your own website that loads the payment form in a way that does not qualify for SAQ A |
| B-IP | Merchants using only standalone, PTS-approved payment terminals with an IP connection to the processor, with no electronic card data storage | A counter or bar using standalone card terminals separate from the POS |
| C-VT | Merchants manually entering one transaction at a time into a virtual terminal hosted by a validated provider | Phone catering deposits keyed into a web-based virtual terminal |
| C | Merchants with payment application systems connected to the internet, with no electronic card data storage | A traditional POS where the payment application runs on internet-connected systems |
| P2PE-HW | Merchants using only hardware terminals included in a validated, PCI Council-listed point-to-point encryption solution | Terminals from a listed P2PE solution, which usually means the shortest SAQ |
| D | All merchants not included in the descriptions above | Restaurants that store card data electronically or have complex setups |
Restaurants usually accept cards in more than one way. If you take cards in the dining room, online and by phone, ask your acquirer whether you need one SAQ that covers everything or a separate one for each channel. Get the answer in writing.
Shrink your scope first
PCI work grows with the number of systems that can see card numbers. The most effective compliance step is reducing that number before you fill in a single form. Every system you take out of the card-data path is a set of questions you no longer need to answer, a set of controls you no longer need to maintain and one less place a breach can start.
- Use terminals that encrypt the card at the point of entry, ideally from a validated point-to-point encryption solution if your processor offers one.
- Use hosted payment pages for online ordering, so card numbers never pass through your website.
- Replace keyed phone payments with a secure payment link sent by text or email.
- Never write card numbers on paper for catering deposits or phone orders, and never type them into reservation notes or emails.
- Keep the POS and payment devices on their own network, separate from guest Wi-Fi, staff phones and cameras.
If a guest emails or texts a card number, do not use it. Delete the message, empty the deleted folder and send a payment link instead.
Handhelds, kiosks, QR payments and delivery apps
Newer ways of taking cards each raise their own PCI questions. Ask about each one before you add it, not after the processor's portal flags it.
- Handhelds at the table: confirm they use the same encrypted card reader as your counter terminals and connect only to the POS network.
- Self-order kiosks: ask whether the card reader is part of a validated encryption solution and who is responsible for inspecting it for tampering.
- QR code payment at the table: usually a hosted payment page run by the provider; ask the provider for its own PCI attestation.
- Delivery apps: the app takes the guest's card, not you, so these orders are normally outside your card-data scope. Keep the tablet on a separate network anyway.
- Gift cards and stored value: ask whether your gift card provider is in scope, especially if staff can look up balances by card number.
For every provider that touches card data on your behalf, ask for its current attestation of compliance and keep a copy. Providers that cannot produce one are a risk you inherit.
Working with your POS vendor and processor
You are responsible for compliance, but your POS vendor and processor hold most of the answers. They know whether your terminals encrypt at the point of entry, whether their software is validated, and which SAQ their other restaurant customers usually complete. Use them.
- Ask the POS vendor for its PCI documentation and an implementation guide for your setup.
- Ask who manages updates to terminals and the payment application, and how often.
- Ask how vendor support connects remotely, and require that access be turned on only when you request it.
- Ask the processor whether quarterly external network scans are required for your SAQ, and whether they provide a scanning service.
Keep a compliance folder with the completed SAQ, the attestation, scan reports if required, provider attestations, your network diagram, the list of payment devices with serial numbers and the dates you inspected them. If a breach ever happens, this folder is the first thing an investigator will ask for.
The gaps most restaurants have
| Gap | Why it matters | Fix |
|---|---|---|
| Card numbers in notes, emails or paper | Stored card data expands scope and is what thieves look for | Payment links; shred existing paper; search and delete old emails |
| Shared or default passwords | Anyone who learns one login can reach the system | Individual logins and PINs; change all vendor defaults |
| Guest Wi-Fi on the POS network | Guest devices can reach payment systems | Separate networks, set up by your installer |
| Vendor remote access left open | A permanent door into your POS | Enable remote access only when needed, with MFA |
| No terminal inspection | Skimmers on terminals go unnoticed | Check terminals for tampering on a schedule and keep a device list |
| SAQ never filed | Monthly non-compliance fees and no clear picture of risk | Ask the processor which SAQ applies and complete it |
Most of these are habits, not technology. The same rules appear in good general security practice, so fixing them lowers your risk well beyond card data.
How to complete the SAQ
Ask the processor
Log in to the processor's compliance portal or call them. Ask which SAQ applies to each way you take cards, and whether quarterly network scans are required.
Map how cards flow
Write down every way a card is accepted: terminals, handhelds, kiosks, online ordering, phone orders, delivery apps and catering deposits.
Fix the easy gaps first
Change default passwords, separate networks, stop storing card numbers and turn on MFA for remote access.
Answer honestly
Work through the questionnaire with your POS vendor's documentation. Mark "no" where you are not compliant and write down the fix and a date.
Sign and submit
Submit the SAQ and its attestation of compliance through the portal and save a copy.
Put it in the calendar
Set a reminder for next year, and repeat the process whenever you change POS, processor or add a new way to take cards.
Example: removing the monthly fee
Example: a fictional pizzeria notices a PCI non-compliance fee on every statement. The owner calls the processor and learns the SAQ was never filed. Mapping card flows shows a counter terminal, online ordering on a hosted page, and phone orders where staff write card numbers on tickets and key them in later.
Example: the owner switches phone orders to a payment link, shreds the old tickets, moves the guest Wi-Fi to its own network and changes the router's default password. The processor confirms which SAQ applies, the owner completes it in an afternoon with the POS vendor's help, and the fee disappears from the next statement.
Frequently asked questions
Is PCI compliance required by law?
PCI DSS is an industry standard, not a federal law. It applies to restaurants through their merchant agreements, and processors can charge fees or penalties for non-compliance.
Which PCI SAQ does a restaurant need?
It depends on how you accept cards. Your acquirer or payment brand decides; the PCI Council encourages merchants to contact them to identify the right SAQ[1].
Why is there a PCI fee on my processing statement?
Often because the annual SAQ has not been filed. Ask your processor which SAQ applies, complete it and ask them to remove the non-compliance fee.
Can I take card numbers over the phone?
You can accept phone payments, but a secure payment link is safer than writing or keying numbers, and it keeps card data off your systems.
References
PCI Security Standards Council (2015). Understanding the SAQs for PCI DSS version 3 (information supplement) (opens in a new tab) ↑
PCI Security Standards Council (2026). PCI Data Security Standard (PCI DSS) (opens in a new tab) ↑
National Restaurant Association (2025). From Trend to Transformation: Off-Premises Dining Now Essential for Restaurant Consumers, Operators (opens in a new tab) ↑
National Restaurant Association (2024). Serving Up Technology: New Data Shows How Tech Integration is Transforming the Restaurant Experience (Restaurant Technology Landscape Report 2024) (opens in a new tab) ↑
National Restaurant Association (2026). Persistent Cost Increases and Enduring Demand Will Shape the Restaurant Industry in 2026 (opens in a new tab) ↑