Key takeaways
- The safest phone payment is one where staff never hear the full card number: a payment link texted to the guest.
- If staff must key a card, do it straight into a terminal or virtual terminal on the call; never write it down or type it into a booking note.
- Card security codes must not be stored after authorisation, whatever the customer agrees to.
- Pause call recording while card details are given, and keep only what you need for refunds and disputes.
Why phone payments need care
Phone payments cover a lot of hospitality: deposits for large tables, Christmas party bookings, takeaway orders, gift vouchers and private hire. They are convenient, but they are also the riskiest way to take a card, because the card is not present and the details pass through a person.
The sector is not well defended. In the government's 2025 Cyber Security Breaches Survey, only 25% of food or hospitality businesses had sought external cyber security information or guidance, against 42% of businesses overall[1]. Food or hospitality businesses also reported identifying fewer breaches or attacks (30% against 43%)[1], which may partly reflect less monitoring rather than less risk.
- Food or hospitality
- All businesses
Source: Department for Science, Innovation and Technology, 2025[1]
Show the data
| Item | Food or hospitality | All businesses |
|---|---|---|
| Identified a breach or attack in the last 12 months | 30% | 43% |
| Sought external cyber security guidance | 25% | 42% |
A disputed or fraudulent payment hurts more when cash is tight. In October 2026, 20% of UK accommodation and food businesses had no cash reserves and 13.2% had less than a month's worth[2]. A handful of chargebacks on a December weekend can matter.
Your options, compared
There are four common ways to take money for a phone booking or order. They differ mainly in whether card details pass through your staff.
| Method | How it works | Do staff hear the card number? | Best for |
|---|---|---|---|
| Pay-by-link | Staff text or email a secure payment link; the guest pays on the provider's page | No | Deposits, vouchers, pre-paid orders |
| Booking system deposit | The booking system asks for the deposit when the booking is confirmed online | No | Table deposits and no-show protection |
| Terminal or virtual terminal keyed on the call | Staff type the card into a card terminal or provider's web page while the guest reads it out | Yes | Occasional orders where a link is not possible |
| Pay on arrival or collection | No payment on the phone; the guest pays in person | No | Most takeaway and small bookings |
Pay-by-link and booking system deposits are the best default for a small venue. Keyed payments should be the exception, used only on a terminal or virtual terminal designed for card-not-present transactions, and never by writing details down first.
The pay-by-link script
A payment link is only as good as the way it is explained. Guests are rightly wary of links, so tell them what to expect before you send it.
Explain
"We take a deposit for tables of eight or more. I'll text you a secure payment link from our card provider now, so you can pay it yourself."
Confirm the number
Read the mobile number back before you send the link.
Send while on the call
Send the link and ask the guest to check it has arrived. Say what it will show: your venue name and the amount.
Set a deadline
"The link is valid for 24 hours. The booking is confirmed once it's paid."
Confirm in writing
When the payment comes through, send the booking confirmation with the deposit terms.
If the guest would rather not use a link, offer to take the deposit in person when they next pass, or to hold the table provisionally for a short time. Do not switch to writing down their card number to save the booking.
If you must key a card on the call
Sometimes a link is not practical: an older guest without a smartphone, or a corporate booker paying with a company card. In that case, key the card directly into a terminal or virtual terminal while the guest reads it out.
- Use a terminal or virtual terminal set up by your card provider for card-not-present payments.
- Take the call somewhere you cannot be overheard, not at a busy bar.
- Type the details as they are read out. Do not write them down, even temporarily.
- Do not repeat the full card number back aloud. Confirm the last four digits instead.
- Never type card details into a booking system note, an email, a spreadsheet or a messaging app.
- Never store the security code. The card industry standard says card verification codes must not be stored after authorisation, regardless of any permission from the customer[3].
- Give the guest the authorisation result and send a receipt.
If your phone calls are recorded, pause the recording while card details are read out, or use a system that does this automatically. A recording that contains card numbers is stored card data. Our guide to call recording in restaurants covers the wider rules.
What PCI DSS means for a small venue
PCI DSS is the card industry's data security standard. It applies to any business that accepts card payments, whatever its size. For most restaurants and pubs, it comes down to a small number of practical rules.
- Keep card data off your own systems wherever possible, by using pay-by-link, booking system deposits and provider-supplied terminals.
- Never store full card numbers on paper or in files, and never store security codes after authorisation[3].
- Limit who can take keyed payments, and make sure they are trained.
- Keep terminals physically secure, and check them for tampering.
- Complete the annual self-assessment your card provider asks for, and keep a copy.
The simpler your set-up, the shorter the self-assessment. A venue that only takes card payments in person, by link and through its booking system has far less to prove than one that keys cards into a laptop.
Data protection: keep only what you need
Card details are personal data, and so are the names, numbers and emails attached to bookings. UK GDPR requires personal data to be adequate, relevant and limited to what is necessary, and kept in identifiable form for no longer than necessary[4].
- Keep payment references and receipts, not card numbers.
- Keep what you need to handle refunds and disputes for as long as your provider's dispute window lasts, then delete or archive it.
- Restrict access to payment records to the people who need them.
- If you ever find card numbers written down or stored in a file, destroy them securely and change the process that caused it.
Example: a fictional pub found card numbers for Christmas deposits written in the back of the bookings diary from the previous year. It shredded the pages, moved all deposits to a payment link sent from its booking system, and added "never write card numbers down" to the staff handbook and the phone answer sheet.
Gift vouchers and pre-paid orders
Vouchers are one of the most common reasons guests pay over the phone, especially in the weeks before Christmas and Mother's Day. They are also attractive to fraudsters, because a voucher bought with a stolen card can be used or sold before the chargeback arrives.
- Sell phone vouchers by payment link, so the buyer enters their own card details.
- Send the voucher to the buyer's email or address, not to a different person given at the last minute, unless you have checked the order.
- Give each voucher a unique code and record its value, sale date and expiry in one place.
- State the terms on the voucher itself: expiry date, whether it can be split, and what happens if the venue closes or changes hands.
- Watch for bulk voucher orders from new callers, and call back on a number you can verify before releasing them.
Pre-paid takeaway and event orders work the same way: take payment by link, confirm the order in writing and keep the receipt with the order record.
Train the team in ten minutes
Phone payment rules only work if everyone who answers the phone knows them. Add a short section to your new starter training and repeat it before December.
The one rule
We never write card numbers down, and we never store security codes.
The default
We send a payment link from our card provider. Show staff how to send one and what the guest sees.
The exception
Only named staff key cards on the terminal, in private, while the guest reads the number out.
Recording
Pause the call recording before card details, or check it pauses automatically.
When in doubt
If a caller pushes to pay another way or something feels wrong, say a manager will call back.
Refunds, disputes and fraud warning signs
Card-not-present payments carry a higher risk of disputes. Keep clear records and watch for patterns that often signal fraud.
- Keep the booking confirmation, the terms the guest agreed to and the payment receipt together, so you can respond to a chargeback.
- Refund to the same card through the same provider. Never refund to a different card or by bank transfer at the caller's request.
- Be wary of large takeaway or voucher orders from new callers who want collection by a third party.
- Be wary of callers who offer several cards when the first is declined.
- Be wary of requests to refund an overpayment to a different account.
If something feels wrong, decline politely and offer payment in person. Our guide on storing card details for no-show charges safely covers the separate question of holding cards against bookings.
Frequently asked questions
Can we write card details down and process them later?
No. Writing a card number on a booking sheet, a notepad or a booking system note creates exactly the kind of stored card data the card industry rules are designed to stop. Key it into a terminal on the call, or better, send a payment link.
Can we keep the security code to charge a no-show later?
No. The card industry standard says card verification codes must not be stored after authorisation, even if the customer gives permission. If you want to charge no-shows, use a booking system or payment provider that holds the card securely on your behalf.
Is pay-by-link safe for deposits?
It is usually the safest option for a small venue, because the guest enters their own card details on the payment provider's page and your staff never see them. Check the link comes from your payment provider, expires after a set time and shows your venue name.
Do we need to do anything for PCI DSS as a small venue?
Yes. Every business that takes card payments is expected to follow PCI DSS, and your card provider will usually ask you to complete an annual self-assessment. Using pay-by-link and terminals that keep card data off your own systems makes that much simpler.
References
Department for Science, Innovation and Technology (2025). Cyber security breaches survey 2025 (opens in a new tab) ↑
Office for National Statistics (2026). Business insights and impact on the UK economy, wave 166 dataset (opens in a new tab) ↑
PCI Security Standards Council (2017). FAQ: Can card verification codes/values be stored for card-on-file or recurring transactions? (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) ↑