Taking Card Payments Over the Phone: PCI DSS Guide
Last checked: 16 November 2026
You can take card payments over the phone and still record calls, but the card security code must never be kept in a recording, notes or any other system after the payment is authorised, even if it is encrypted. If your phone system is VoIP, the parts of it that carry card details are in scope for PCI DSS. The simplest way to stay compliant is to keep card details out of your staff's ears and recordings altogether, using DTMF masking, an automated payment line or a secure payment route from your payment provider.
This guide explains what the PCI Security Standards Council (PCI SSC) says about telephone payments, how call recording and VoIP change the picture, and the practical options for a small business taking card payments by phone.
What is PCI DSS and does it apply to phone payments?
The Payment Card Industry Data Security Standard (PCI DSS) is the security standard for any business that stores, processes or transmits payment card data. It is managed by the PCI SSC. The card brands and acquiring banks run their own compliance programmes, so it is your acquirer or payment provider that tells you how you must validate compliance, for example by a self-assessment questionnaire (SAQ).
The PCI SSC's information supplement Protecting Telephone-Based Payment Card Data (version 3.0, November 2018) explains how PCI DSS applies when card details are given over the phone. It says it does not replace any PCI DSS requirement, but it is the clearest official guidance on phone payments. PCI DSS v4.0.1 was published in June 2024 and replaced v4.0, which the PCI SSC retired on 31 December 2024; check the PCI SSC document library for the latest version.
Which card details are you not allowed to keep?
PCI DSS splits card data into two groups:
| Data | Examples | Can you keep it after the payment is authorised? |
|---|---|---|
| Cardholder data | Card number (PAN), cardholder name, expiry date | Only if necessary and protected to PCI DSS standards |
| Sensitive authentication data (SAD) | Card security code (CVV2/CVC2/CID), PINs, full magnetic stripe or chip data | No, not even encrypted |
The supplement is direct about this: "storage of sensitive authentication data after authorization is not permitted, even if the data is encrypted." If a security code is received and recorded, the business must render it unrecoverable once authorisation is complete.
That applies to anything that captures the call, not only software. The supplement notes that if a person answering the phone writes card details down, or an answering machine captures them, that counts as storage and brings your processes into scope.
PCI compliance and call recording: what are the rules?
Call recording and card payments clash because the customer reads out their card number and security code. The supplement's position is:
- Recordings that contain card data must be secured to PCI DSS standards, including encryption of stored card data, access limited to people with a business need, and logging of access.
- The security code must not stay in a recording. If a technology "cannot block the audio or video from being stored, the sensitive authentication data (SAD) MUST BE DELETED from the recording as soon as the transaction is processed."
- Prevention is better than deletion. Where possible, use processes and technology that stop card data entering the telephone environment and stop security codes being recorded at all.
- If you cannot remove security codes from recordings because of a legal or regulatory recording requirement, the supplement says to discuss this with your acquirer or payment brand.
It also warns about transcription and voice analytics. Tools that transcribe or analyse recordings "need to be carefully controlled and monitored" where card data is present. If your phone system offers AI transcription, check that card details cannot end up in the transcripts.
For the wider rules on recording calls, including telling callers and how long to keep recordings, see our guide to VoIP call recording for small business.
Is a VoIP phone system in scope for PCI DSS?
Often, yes. The supplement says that calls over a traditional public phone line (PSTN) between a business and its acquirer or payment provider are "generally considered out of scope", but that:
"Where VoIP is used for transmissions of payment card account data between a cardholder and an entity, the entity's systems and networks used for those transmissions are in scope."
The customer's own phone and network are not your responsibility; your phone system, network and anything connected to them that carries the card details are. With the PSTN switch-off moving almost every business to digital and hosted VoIP calls, it is worth assuming card details spoken on a business call will cross an IP network you are responsible for, and designing your payment process with that in mind.
If any part of the phone environment is run by a third party, such as a hosted VoIP provider or call recording service, the supplement says both sides should clearly understand and document who is responsible for securing what.
How to take card payments over the phone securely
These are the main approaches the supplement describes, from least to most effective at reducing what is in scope:
| Option | How it works | Effect on PCI scope (per PCI SSC guidance) |
|---|---|---|
| Manual pause and resume | Staff pause the call recording while card details are given | Can take call recording and storage out of scope if done properly; the agent, their desktop and other phone systems stay in scope |
| Automatic pause and resume | The system pauses recording when the payment screen opens | As above, with less reliance on staff remembering |
| IVR or automated payment line | The customer is transferred to an automated system to enter card details, then back to staff | Can reduce scope for staff and their desktops when card data genuinely bypasses them |
| DTMF masking or suppression | The customer types card details on their keypad; the tones are masked so staff and recordings do not capture them | A properly designed deployment can take the telephony, staff desktops and CRM out of scope |
What is DTMF masking?
DTMF tones are the sounds a phone makes when you press its keys. DTMF suppression removes those tones; DTMF masking replaces them with a flat or random tone. The customer types their card number and security code on their phone keypad while staying on the call, and the digits go to the payment provider rather than being heard by the member of staff or captured in the recording. The supplement says a properly designed and deployed DTMF masking solution can take "not only the telephony environment, but also the agent environment and CRM system out of scope".
Masking can be provided by a service provider before the call reaches you, or on your own premises. The supplement notes that the off-premises approach "could allow the telephony systems to be out of scope", while an on-premises one keeps some of your phone equipment in scope.
Why pause and resume is not enough on its own
Pause and resume is the most common approach, but the supplement lists its weaknesses: staff can forget to pause, so card data and security codes are captured, or forget to restart, which can break other recording obligations. It recommends checking recordings for card data regularly, "preferably weekly", where agent-initiated pause and resume is used. It also does nothing about the member of staff hearing and typing the card number.
Practical checklist for small businesses
- Ask your acquirer or payment provider how you must validate PCI DSS compliance for phone payments, and which SAQ applies.
- Map where card details go: who hears them, where they are typed, whether the call is recorded or transcribed, and which systems carry the call.
- Never write card details down. The supplement suggests restricting pens, paper and phones capable of recording in areas where card details are taken.
- Do not store the security code anywhere after authorisation: not in recordings, notes, emails, CRM fields or chat messages.
- Decide how recordings handle payments: automatic pause and resume at minimum, or DTMF masking so card data never reaches the recording.
- Restrict and log access to any recordings that could contain card data.
- Check your phone provider's role: ask your VoIP provider where calls and recordings are stored, whether they offer secure payment options, and agree responsibilities in writing.
- Train staff, and review the process when you change phone system, payment provider or call recording settings.
Worked example: a small office taking phone bookings
Picture a business with four staff who take deposits by phone. Calls are recorded for training on a hosted VoIP system, and staff type card details into the payment provider's virtual terminal.
| Issue | Risk | Change |
|---|---|---|
| Recordings | Full card numbers and security codes are in every booking call | Automatic pause and resume while the payment screen is open, with a weekly spot check of recordings |
| Transcription | AI transcripts of calls could contain card numbers | Turn transcription off for the booking line, or confirm it excludes paused sections |
| Paper notes | Staff jot numbers down when the terminal is slow | Clear-desk rule; no card details on paper |
| Scope | Staff still hear and type card details, so their computers stay in scope | Ask the VoIP and payment providers about DTMF masking or an automated payment line for the next contract |
The quick changes reduce the risk straight away; moving card entry off the call altogether is the bigger long-term win, and it is easiest to arrange when you choose or renew a phone system.
Choosing a phone system when you take card payments
When you compare VoIP providers, ask:
- Can call recording pause automatically during payments, and can paused sections be excluded from transcripts?
- Do you offer, or integrate with, DTMF masking or a secure IVR payment line?
- Where are recordings stored, who can access them and is access logged?
- Can we turn recording off for specific numbers, queues or users?
- Which parts of the PCI DSS responsibilities do you take on, and will you confirm that in writing?
How calls reach the right person also matters; a call queue or auto attendant can route payment calls to trained staff. All Compare The Networks business contracts are 24 months minimum, so settle these questions before you sign.
Frequently asked questions
Can you record calls when taking card payments?
Yes, but the card security code must not be kept in the recording after the payment is authorised, even if the recording is encrypted. Any card numbers that are recorded must be protected to PCI DSS standards. The safest approach is to stop card details being recorded at all, using automatic pause and resume or DTMF masking.
Is it legal to take card payments over the phone in the UK?
Yes. Taking card payments by phone is common and allowed. What matters is handling the card details securely in line with PCI DSS and your acquirer's requirements, and not keeping security codes after authorisation.
Is VoIP PCI compliant?
VoIP is not compliant or non-compliant on its own. The PCI SSC says that where VoIP carries card details between a customer and your business, the systems and networks you use for that are in scope for PCI DSS, so they need to be secured accordingly.
What is DTMF masking for card payments?
DTMF masking lets a customer type their card details on their phone keypad during a call while the tones are replaced or removed, so staff do not hear the digits and the recording does not capture them. A properly designed deployment can take your phone system, staff desktops and CRM out of PCI DSS scope.
Can I write down card details to process later?
No, you should not. The PCI SSC supplement treats writing card details down as storage, which brings your processes into scope, and the security code must never be kept after authorisation.
Who checks that my business is PCI compliant?
Your acquiring bank or payment provider. The card brands and acquirers run their own compliance programmes and tell you how to validate compliance, for example with a self-assessment questionnaire.
Related guides
- VoIP call recording for small business
- Hosted VoIP for business
- Hunt group vs call queue vs auto attendant
- Best business phone systems in the UK
- PSTN switch-off guide for business
- Softphone vs desk phone
- Business VoIP options
Sources
- PCI SSC: Protecting Telephone-Based Payment Card Data, information supplement v3.0 (November 2018)
- PCI SSC blog: PCI DSS v4.0.1 published
- PCI SSC blog: industry guidance on accepting telephone payments securely
Compare VoIP systems for phone payments
Tell us how many users you have, whether you record calls and how you take card payments, and we will help you compare suitable business phone systems.
Get a free business quote