telvox
ComplianceNovember 20, 2026· 6 min read

Can you record a call while a customer reads out a card number?

Recording every call is good practice until a customer starts reading out their card. Here is what the card rules say, and how pause and resume keeps card data out of your archive.

The short answer

You can record the call, but you should not record the card details. PCI DSS forbids keeping the security code after a payment is authorized, so the usual fix is to pause the recording while the customer reads out the card and resume it straight after.

tvThe TelVox team
Close-up of hands dialing on a white smartphone
Photo: Unsplash

An agent on a collections floor gets a yes. The customer wants to clear the balance now, on this call. They pull out their card and start reading: sixteen digits, the expiry date, the three numbers on the back. The call is being recorded, as every call on that campaign is.

That recording now holds everything a fraudster needs. It will sit in your archive for months or years. Anyone with access to recordings can play it back. And under the card industry's own rules, part of what it holds is something you are not allowed to keep at all.

So can you record a call while a customer reads out a card number? You can record the call. You should not record the card. Here is why, and how to do both on the same call.

What PCI DSS says about card data in call recordings

If you take card payments, you are expected to follow the Payment Card Industry Data Security Standard, or PCI DSS. It is set by the card brands through the PCI Security Standards Council, and your bank or payment provider is usually the one asking you to prove you meet it.

PCI DSS splits card data into two kinds, and treats them very differently:

  • The card number, expiry date and cardholder name. You may store these, but only if you protect them properly. Any system that holds them falls inside the scope of your card security assessment.
  • Sensitive authentication data, which includes the three or four digit security code on the card. This must not be stored after the payment is authorized. Encrypting it does not make it allowed.

A call recording does not care which kind of data it captures. If the customer reads out the security code, the recording now stores it. The PCI Council has published guidance on telephone payments for exactly this reason, and the safest answer it points to is the obvious one: do not let card data reach the recording in the first place.

Scope is the hidden cost

Even if you only captured the card number, every place that recording travels becomes part of your card security footprint: storage, backups, the QA tool, any export. Keeping card data out of recordings keeps all of those out of scope.

Why not just stop recording payment calls?

Some teams solve this by turning recording off on any campaign that takes payments. It works for PCI, but it costs you elsewhere. Payment calls are often the ones you most want on tape. A customer who later says they never agreed to a payment plan, or that the agent pushed them, is a dispute you settle with the recording.

Payment calls also carry the disclosures your compliance team cares about: who the agent said they were, what the customer agreed to, what amount and date were confirmed. Losing all of that to keep out a few seconds of card digits is a bad trade.

What you want is the whole call on tape except the card details. That is what pause and resume is for.

How pause and resume works on a live call

The idea is simple. When the conversation reaches the card, the agent pauses the recording. The customer reads out the details. The agent enters them into the payment system, then resumes the recording and carries on. The stored file has the agreement before the pause and the confirmation after it, with nothing in between.

In TelVox, recording is set for your organisation as always, on demand or never, and each campaign can override that. Pause and resume sits on top. It is gated by its own permission, separate from recording, so only the roles you choose can use it. The paused segment is never written to disk, so there is no hidden copy waiting in a temp folder. Since a transcript is made from the recording, a paused card number never turns up in transcripts either.

A good habit is to say it out loud. "I'm pausing the recording while you give me your card details." Then, after: "Thanks, the recording is back on." The customer knows what happened, and anyone listening to the call later hears the gap explained in the agent's own words.

The safest way to hold card data is not to hold it. A recording that never captured the card has nothing to leak.

Where manual pause goes wrong

Pause and resume depends on a person pressing a button at the right moment. That is its weakness, and it is worth planning for. The common misses are:

  1. 01The customer starts reading the card before the agent pauses. Some people are quick. Train agents to ask for the card only after they have paused, not before.
  2. 02The agent forgets to resume. The rest of the call, including the confirmation and closing disclosures, is lost. Check payment calls in QA for recordings that end early.
  3. 03Pause gets used for the wrong reasons. If anyone can pause any call, it becomes a way to keep awkward moments off tape. Limit the permission to roles that take payments.
  4. 04Card details end up somewhere else. A paused recording does not help if the agent types the card number into a notes field. Payments belong in the payment system and nowhere else.

Pause is not the only option

Manual pause is the most common approach because it needs no change to how payments are taken. Larger payment operations sometimes go further and keep card details away from the agent entirely. Two patterns you will see in the industry:

  • The customer keys the card number on their phone keypad, and the tones are captured by a payment service and masked from both the agent and the recording.
  • The agent sends a secure payment link by text or email, and the customer pays on their own device while still on the call.

Both reduce human error, and both need a payment provider that supports them. Whatever you choose, ask your payment provider and your assessor which approach they expect. The answer shapes how much of your setup is in scope.

Consent is a separate question

Pausing for card data does not change your recording consent obligations. Some US states require every party on a call to agree to recording, and many countries have their own rules. You still need the usual notice at the start of the call. Pause solves a card data problem, not a consent problem.

Get both right and you end up with a recording you can actually use: the whole conversation, the agreement in the customer's own words, and no card number for anyone to find.

Common questions

Is it legal to record a call when a customer gives card details?
Recording the call itself is a question of consent law where you and the customer are. The card rules are a separate problem. PCI DSS says the card security code must not be stored after the payment is authorized, even encrypted, so a recording that holds it breaks the standard.
What is PCI pause in a call center?
PCI pause means stopping the call recording while the customer reads out card details, then resuming it once the payment part is done. The card number and security code never make it into the stored recording, so the archive holds no card data to protect or leak.
Can a call recording store the CVV if it is encrypted?
No. Under PCI DSS, sensitive authentication data such as the CVV must not be kept after authorization, and encryption does not change that. The card number itself can be stored only if it is properly protected, which pulls your recording system into the scope of your card security assessment.
Who should be allowed to pause a call recording?
Only the people whose calls take payments. If every agent can pause any call, pausing becomes a way to hide parts of conversations from QA. In TelVox, PCI pause is a separate permission from recording itself, so you decide which roles can use it.
What happens if an agent forgets to pause the recording?
Then the card details are in the recording and you have a cleanup job. Find the call, decide with your security team how to handle the file, and treat the miss as a process problem. Train agents on the moment to pause and spot check payment calls in QA.