Key takeaways
- The safest way to store card details is not to: let a payment or booking provider hold the card and give you a token.
- Card security codes must never be kept once the transaction is authorised, and card-on-file charges do not need them.
- Card numbers in booking notes, emails, paper diaries, photos and chat groups are the most common real-world risk.
- Small teams should pick a provider that does the heavy lifting, then check their own habits with a one-hour audit.
The rule: never hold card numbers yourself
To charge a no-show fee you need permission to take a payment later, not a copy of the guest's card. Modern booking and payment providers store the card details in their own secure systems and give your booking a reference, called a token, that lets you charge the card under the terms the guest agreed. You never see or keep the full number.
If any part of your process involves a person writing down, typing into a spreadsheet, photographing or reading back a full card number, that is the part to change first. It is where the real risk sits, far more than in the provider's systems.
How a tokenised card hold works
The guest enters their card
On your booking page or a secure payment link, the card details go straight to the provider. Your website and staff never handle them.
The provider checks and stores it
The card may be verified, and the provider stores it securely against the booking.
You receive a token
Your booking system holds a reference and perhaps the last four digits, enough to recognise the card but useless to a thief.
You charge only under the terms
If the guest does not arrive, you trigger the stated charge through the provider, which uses the stored card.
The stored card is removed
After the booking, the provider should delete or stop using the stored card according to its retention rules.
What PCI DSS says about security codes
The three- or four-digit security code on a card is treated as sensitive authentication data. The PCI Security Standards Council says it is not permitted to retain card verification codes once the specific transaction they were collected for has been authorised, and that they are not needed for card-on-file transactions[1]. A booking process that asks staff to note the security code "for later" is not compliant, whatever else it does well.
PCI DSS is the card industry's security standard, enforced through your contract with your card acquirer rather than by statute. The practical effect is the same: if card data leaks from your venue, you can face costs and lose the ability to take cards.
Where card data leaks in real venues
| Practice | Why it is risky | Safer alternative |
|---|---|---|
| Card number in the booking notes field | Visible to anyone with system access, and often exported | Card entered only on the provider's secure form |
| Paper booking diary with card details | Left on the bar, photographed, never shredded | No card data on paper, ever |
| Guests emailing or messaging card details | Sits in inboxes and chat history indefinitely | Reply with a secure payment link and delete the message |
| Staff reading numbers back on the phone | Overheard at the bar or recorded | Secure link, or key directly into the provider's terminal |
| Call recordings with card details | Recordings kept for months | Pause recording or use the provider's phone payment flow |
| Photos of cards for large bookings | Stored on personal phones | Never accept them; send a link instead |
Phone bookings without the risk
Phone bookings are where most venues slip. The safest approach is to take the booking by phone and send a secure payment link by text or email while the guest is still on the line, so they can enter their own card. If staff must take a card over the phone, they should key it directly into the provider's virtual terminal, never write it down and never repeat it aloud. If you record calls, pause the recording while card details are given or use a provider service designed for phone payments.
For the full process, including what to say, see taking card payments over the phone securely.
When a guest will not give card details
Some guests refuse, often for good reasons, having been caught by fraud before. Do not argue or pressure them into reading a number over the phone. Offer the secure link, explain that you never see the full number, and if they still prefer not to, offer a time or night where no card is needed, or a deposit by another method your provider supports. A guest treated patiently over this is a guest who trusts you with the rest of the booking.
UK GDPR applies too
Card details linked to a named guest are personal data. UK GDPR requires personal data to be processed with appropriate security, including protection against unauthorised processing and accidental loss, and kept in an identifiable form for no longer than necessary[2]. An old spreadsheet of card numbers from last year's Christmas parties fails both tests at once.
Your privacy notice should say that card details for bookings are collected and held by your payment provider, for what purpose and for how long. If a breach does happen, you may need to report it to the ICO and tell affected guests, so it is worth knowing in advance who in the business would handle that.
Hospitality's security picture
The sector is not as well prepared as it might be. In the government's 2025 survey, 30% of food and hospitality businesses had identified a cyber breach or attack in the previous 12 months, only 12% had a board member responsible for cyber security, and 25% had sought external cyber security guidance, against 42% of businesses overall[3].
Most venues are also small. About 53% of restaurant and mobile food enterprises have four or fewer employees[4], which usually means nobody whose job is security. That is a strong argument for letting the provider carry the card data and keeping your own processes simple.
Questions to ask your provider
- Do card details go directly to you, without passing through our website or staff?
- Can our staff ever see a full card number? If so, can that be switched off?
- Do you keep security codes after authorisation? (The answer must be no.)
- How long do you keep stored cards after the booking date, and can we shorten it?
- Can we send secure payment links by text or email for phone bookings?
- Who do we contact if we suspect a breach, and what will you do?
A one-hour audit for your venue
- Search the booking system's notes fields for long strings of digits and remove any card numbers.
- Check the bookings inbox and social media messages for card details sent by guests; delete them and reply with a link.
- Look at the paper diary, the bar and the office for written card details; shred them.
- Ask staff, without blame, how they take card details for phone bookings, and fix any workaround.
- Check whether calls are recorded and how card details are handled on those calls.
- Confirm who can export booking data and remove access for people who have left.
Example: a two-site restaurant group runs the audit and finds card numbers in 14 booking notes, all entered by one long-serving manager who had never been shown the payment-link option. The notes are cleared, the link is set up, and the manager trains the rest of the team on it the following week.
Train the team in ten minutes
Card-data mistakes are almost always habits, not malice. A long-serving manager who started when bookings were taken in a paper diary, a new host trying to be helpful, a busy bartender who jots a number on a pad: each is solved by a short, clear rule that everyone hears in the same words.
- We never write down, type into notes, photograph or read back a card number.
- Guests enter their own card details on our secure page or link.
- If a guest sends card details by email or message, we delete them and send the link instead.
- If a guest insists on giving a card over the phone, we key it straight into the payment terminal and nowhere else.
- If you find card details anywhere, tell the manager on duty the same day.
Put the five rules on the inside cover of the bookings folder or pinned beside the phone, and repeat them at the start of each busy season.
Keep the charge side clean too
Safe storage is half the job. The other half is charging fairly: stating the exact amount at booking, sending a reminder before the deadline and keeping the evidence. See winning disputes on no-show fees and card holds vs deposits vs prepayment.
Frequently asked questions
Can a restaurant store customers' card details for no-show fees?
Use a payment or booking provider that stores the card and gives you a token. You should not keep card numbers in your own notes, spreadsheets, emails or paper records.
Can we keep the card security code to charge no-shows later?
No. PCI DSS does not allow card verification codes to be kept after the transaction is authorised, and card-on-file charges do not need them.
Is it safe to take card details over the phone?
It can be, if staff key the details directly into the provider's secure terminal or send a payment link, never write them down and do not record them. A secure link is usually the simplest option.
What should we do if card details were written in our booking notes?
Remove them, check who had access, and tell your payment provider. If you think the data was exposed, take advice on whether you need to report a personal data breach.
References
PCI Security Standards Council (2015). Can card verification codes/values be stored for card-on-file or recurring transactions? (FAQ 1280) (opens in a new tab) ↑
legislation.gov.uk (The National Archives) (2016). UK GDPR, Article 5: principles relating to processing of personal data (opens in a new tab) ↑
Department for Science, Innovation and Technology (2025). Cyber security breaches survey 2025 (opens in a new tab) ↑
Office for National Statistics (2026). UK business: activity, size and location, 2026 (workbook) (opens in a new tab) ↑