Keeping Card Details Off Your Calls: Phone Payment Basics
How to take phone payments without card numbers passing through agents or recordings: the main options, a simple process and a rollout checklist.
A customer says, "I'd like to pay now," and reads sixteen digits aloud. In one sentence the card number has landed in an agent's ears, possibly a call recording, perhaps an automatic transcript and, if the agent is in a hurry, a note field. Each of those places is now something you have to protect.

This guide explains why card data on calls is a problem, what the card industry's standard asks of you in broad terms, and the practical ways to take phone payments without card details ever touching your agents or your recordings. If you are working out what to record in the first place, also read Call Recording Notices.
Why card data on calls is a problem
The Payment Card Industry Data Security Standard (PCI DSS) sets security requirements for organisations that store, process or transmit payment card data. The more systems that card data reaches, the more of your environment falls within that scope, and the more you must secure, test and document.
Phone calls make this awkward in three ways. Speech is captured by recordings and transcripts. Agents' desktops, headsets and notes become part of the picture. And one particular rule is worth remembering: sensitive authentication data, such as the card's security code, must not be kept after authorisation, even if encrypted. A recording that contains a spoken security code is a stored security code.
Where spoken card data tends to end up
- Call recordingsThe full audio, kept for as long as your retention rules say.
- TranscriptsSearchable text that can be copied, exported or shared.
- Agent notesTyped into a free-text field for "just in case".
- Memory and paperWritten on a sticky note or remembered for a repeat order.
Four ways to take phone payments safely
The aim is the same in each case: the card details go straight from the customer to the payment provider, and your agents hear nothing sensitive.
| Option | How it works | Watch out for |
|---|---|---|
| Payment link | The agent sends the customer a link to a hosted payment page; the customer enters the card on their own device | Needs a way to send the link, such as email or a message, and a customer who can use it on a phone or laptop |
| Automated payment line | The agent transfers the caller to an automated payment flow run by a payment provider, then the caller returns to the agent | Transfers must be smooth, and the caller needs a way back to a person if something fails |
| Keypad tone masking | The caller types the digits on the keypad; the tones are masked so the agent cannot hear or record them | Requires specialist tooling from a payment provider; test that recordings are clean |
| Pause and resume recording | The agent pauses recording while the caller speaks the card details | Still exposes the agent to the details and depends on a person remembering; the weakest option |
Options that remove the agent from the card details are generally preferred over options that ask the agent to behave perfectly. Your payment provider will know what it supports and what its own requirements are.
What not to do
- Do not let agents write card details on paper or in notes, even briefly.
- Do not accept card details by chat or email as a shortcut.
- Do not rely on an instruction like "please don't read it out too loud" as a control.
- Do not keep spoken security codes in recordings or transcripts.
A simple process to follow
Taking a payment without hearing the card
- Confirm the amountThe agent states what is being paid for and the amount, and checks the customer is happy to go ahead.
- Move the customer to the payment stepSend a payment link or transfer to the automated payment flow.
- Customer enters the cardThey type or tap the details themselves. The agent does not see or hear them.
- Wait for confirmationThe payment provider reports success or failure; the agent reads the result, not the card.
- Close and noteThe agent records the outcome, such as "paid", without card data, and ends the call.
Practise the failure paths as well. What happens when the link does not arrive, the transfer drops or the card is declined? Agents should have a script that never falls back to "just read it to me".
Why a smaller footprint wins
Many small businesses discover that the cheapest route to meeting the standard is to have less to meet it with. If card details never enter your phones, your recordings, your agents' desktops or your CRM, there is simply less to secure, less to document and less to explain when your payment provider asks how you handle card data. That is the reasoning behind hosted pages and automated payment flows: they move the sensitive step to a specialist.
It also changes the conversation with agents. Instead of training people to handle card data with perfect care, you train them on a short process that never involves it. Fewer exceptions means fewer mistakes, and it makes quality reviews easier because reviewers do not have to avoid sensitive audio. See Quality Management for Phone Calls for how reviews work in general.
AI agents and payments
A voice agent can take a request such as "I'd like to pay my invoice," but it should hand the actual card entry to a payment provider's flow, exactly as a human agent would. Do not design an AI agent to ask for a spoken card number. Remember too that AI agents create transcripts and summaries automatically, which are further places spoken digits can end up. See Handling Personal Information on Calls for more on what to collect.
Recording and retention choices
Not every call needs recording. If a queue exists only for payments, consider whether you need to record it at all. If you record, keep the retention period as short as your purposes allow, as discussed in How Long to Keep Call Recordings and Data.
Phone payment readiness checklist
- Decide which payment option you will use and confirm it with your payment provider
- Remove any instruction that asks agents to take card numbers verbally
- Test that recordings and transcripts of payment calls contain no card digits
- Write a script for failed links, dropped transfers and declined cards
- Train agents on what to say when a customer offers to read the card out
- Decide whether payment queues need recording at all
- Review the process whenever your payment provider or telephony setup changes
Doing it in Call
Call does not take payments. It does not store card numbers for you, so a payment step has to happen with a payment provider you choose. Within Call, an operator can set what gets recorded: record always, never or a sample, applying to every call, a queue, a campaign or an agent, with the most specific rule winning. A queue that exists only for payment follow-up could therefore be set not to record. Callers can also be moved between queues, and agents can note outcomes in the call record. Keep card data out of those notes, and speak to your payment provider about how its flow fits with your phone setup.
Frequently asked questions
Is it against the rules to hear a card number on a call?
Hearing it is not the core problem; storing and spreading it is. The more of your environment the card data touches, the more you must protect. Taking card entry out of the agent's hands is the simplest way to reduce that.
Is pausing the recording enough?
It helps, but it relies on a person pausing at the right moment every time, and the agent still hears the details. Options that keep the details away from the agent altogether are usually stronger.
Can we keep spoken security codes if the recording is encrypted?
The card industry's standard says sensitive authentication data, including the security code, must not be stored after authorisation. Encryption does not change that, so such codes should not be in recordings or transcripts.
Does Call take card payments?
No. Call does not take payments. You can use it for the conversation, and pass the customer to a payment provider's page or flow for the card step.
What about taking payments through an AI voice agent?
Design the agent so it never asks for a spoken card number. It can take a request and direct the caller to a payment link or an automated payment flow run by your provider.
Who decides what we must do?
Your payment provider, your acquiring bank and the card brands set the requirements that apply to you. Ask them, and consider a qualified assessor for anything complex.