Requirement 3.3.1: card security codes and recorded calls
By Sam Rivera, Founder, SentinelPanda · October 7, 2026 · 3 min read · PCI DSS
The payment system can be spotless and the business still non-compliant, because the breach lives in a call archive nobody thought of as a card system.
What 3.3.1 actually prohibits
Requirement 3.3.1 says sensitive authentication data must not be retained after authorisation, even where it is encrypted. That is a stricter rule than the one governing card numbers: a PAN may be stored if it is rendered unreadable and the storage is justified. Sensitive authentication data may not be stored at all once the transaction is authorised.
The category covers the full track data on the magnetic stripe or chip, the card verification code printed on the card, and PINs or PIN blocks. The security code is the one that catches businesses, because it is the only part of a card a customer routinely says out loud.
Why call recording breaks it
Most contact centre platforms record by default, for quality, training or dispute resolution. Retention is typically measured in years and the recordings are searchable.
If an agent takes a payment during a recorded call, the customer reads the long number, the expiry and the three digits on the back, and all three are now in an audio file that will be retained for as long as the policy says. The payment system behind it may be beyond reproach. The requirement is still being broken, in a system most organisations do not think of as a card system at all.
The same applies to voicemail, to screen recording, and to any transcription service running over the top of the call.
The three workable approaches
- <strong>Pause and resume</strong> — the recording stops before the card is read and restarts afterwards, ideally triggered automatically by the agent opening the payment screen rather than by remembering to press a button.
- <strong>Take the card out of the call</strong> — the agent sends a payment link, or uses dual-tone keypad entry where the customer types the digits and the tones are suppressed, so the number never enters the audio.
- <strong>Do not record payment calls</strong> — viable where payment calls are a distinct queue, less so where any call can turn into a payment.
Why the manual approach fails
Agent-triggered pausing works until it is busy. The weakness is not laziness; it is that a payment often arrives in the middle of a conversation about something else, and the pause depends on someone recognising the moment and acting on it while also talking.
Automated pausing tied to the payment screen removes the judgement call. If your platform supports it, use it — and then test it, because the configuration failing silently looks exactly like it working.
What to do about the archive you already have
If recordings containing security codes already exist, the position is uncomfortable but not unusual. The requirement is clear that the data should not be there, and the practical response is to establish how far back it goes, stop the ongoing capture first, and then deal with the existing archive — in that order, because an archive cleaned while the recording continues simply refills.
Targeted deletion is difficult in most platforms, which is why organisations in this position often shorten retention on the affected queue and let it age out while the new control holds. Document the decision and the reasoning. An assessor will accept a deliberate remediation plan far more readily than a surprised silence.