Pausing call recording for card payments

Most teams record calls for quality and training. Then someone on the phone says "I would like to pay by card", reads sixteen digits and a security code aloud, and those details are now stored in an audio file that a dozen people can open. This is a well-known problem with an equally well-known fix: stop the recording while the payment is taken.

Why card details should not be in recordings

The Payment Card Industry Data Security Standard, PCI DSS, is the rulebook the card brands expect businesses to follow when they handle card data. Among other things, it does not allow a business to keep the card security code after a payment has been authorized, and it expects any stored card number to be protected. An audio recording that captures both is a copy of data you are not meant to keep, in a format that is hard to search, redact or delete.

Whether your own situation requires compliance, and to what level, depends on how you take payments and who your acquiring bank is. Treat this post as general background and ask your payment provider or a qualified assessor what applies to you. Nothing here is a statement about any company's certification.

How pause and resume works

The idea is simple. When the agent reaches the payment step, the recording stops. The call continues as normal, so the customer and agent can still talk, but nothing from the payment is written to the recording. When the details are taken, the recording starts again.

There are two ways to trigger it. Manual pause relies on the agent pressing a button, which is easy to forget. Automatic pause starts when the agent opens the payment screen or enters the payment step, so the pause cannot be skipped. Tizbo pauses recording while a payment is taken and resumes it on its own, so a distracted agent does not leave the rest of the call unrecorded.

Whichever method you use, check what it covers. A pause should apply to the whole call, both sides of the conversation, and to any other copies, such as a live transcript or notes generated from the call.

The agent workflow

1. The agent confirms what the customer is buying and the amount.
2. The agent says what is about to happen: "I am going to pause the recording while you read me the card details. It will start again as soon as we are done."
3. The payment step begins and recording pauses. The agent sees a clear indicator that it is paused.
4. The customer reads the number, the expiration date and the security code. The agent types them directly into the payment form and does not write them down anywhere else.
5. The agent confirms the payment went through and the recording resumes. The agent checks the indicator before carrying on.
6. The agent confirms the outcome with the customer and closes the call as normal.

Agents should never repeat the numbers back aloud once the recording has resumed, and should never ask a customer to read details out while the indicator shows recording. If something goes wrong in the middle, stop and start the step again.

Telling the customer

Customers often feel reassured when they hear why the pause is happening. A short sentence is enough. If you have a recorded-call announcement at the start, you can add a line that card details are not recorded. Write the wording once, with your legal advisor, and give agents that script so each call sounds the same.

A worked example

Halcyon Dental takes payments for deposits and overdue balances on a billing line. The office manager, Dana, finds three old recordings in which patients read out their cards. She does not know who has accessed them. She works with the payment provider to delete the recordings that include card details, then switches on automatic pause for the billing queue. She walks the four billing agents through the script above and calls the line herself twice, once with a test card number provided by the payment provider and once without a payment, then listens to both recordings. The first has a silent gap that matches the payment step. The second is whole.

She adds a monthly check: listen to five recordings from the billing queue, and confirm that no recording includes a card number. If one does, she looks for the cause and tells the team the same day.

Common mistakes

• Relying on agents to press a pause button on every call.
• Pausing the call recording but leaving a transcript or an AI summary running that includes the numbers.
• Taking card details by chat or email, which sends the numbers to places that were never meant to store them.
• Letting agents write numbers on paper or in a notes field.
• Skipping the test after a change to the payment screen or the call flow.

What to ask a provider

• Does the recording pause automatically with the payment step, or only by manual button?
• Does the pause cover transcripts and summaries as well as audio?
• Does the agent see when recording is paused and when it resumes?
• How can I check, after the fact, that a pause happened on a given call?

Pausing the recording will not make a business compliant on its own, and it does not replace a proper payment page or tokenized payment flow. It is one control that closes one real gap, and it is cheap to get right.