Retail Payment Security and It
Cardholder Data Never Enters Your Environment, Including Your AI Stack.
PCI Pal is the independent trust layer that descopes retail contact centers by design. DTMF masking, secure IVR, tokenization, and secure payment links across voice, digital, and AI channels; across any CCaaS, with any payment gateway, whether a person or an AI agent is taking the payment.
PCI Pal: The Trusted Transaction Layer, powering secure human and AI-driven experiences for business communications environments across the globe
Trusted by leading retailers:


Two questions, two answers. Start wherever you sit.
Security and Compliance
Reduce PCI scope. Survive the assessment. Keep card data out of your stack.
IT and Architecture
One control point across every platform, region, and channel. Certified once, not at every migration.
What the Standard Actually Says
Most retailers running assisted payments rely on a compensating control their QSA has signed off on. The question isn’t whether it was accepted. It’s whether it will hold.
The Council’s first-choice control is suppression at the point of entry. Pause-and-resume is what it recommends when you can’t do that. PCI Pal is built on the first choice: suppression at the point of entry, built in rather than bolted on, on every channel and for every agent, human or AI.

The AI Logging Paradox
PCI DSS Requirement 10 pushes you to log what your AI systems receive and how they reason, while Requirement 3 forbids storing sensitive authentication data.
If a customer speaks their card number to an AI voice agent, you cannot satisfy both. The PAN lands in the transcript, the prompt log, the conversation summary, the vector store, and—depending on your architecture—a third-party model provider’s retention policy.
There is only one resolution to this problem: the card data never enters the AI’s input stream. The agent orchestrates the conversation. A separate, PCI DSS Level 1 certified path takes the payment. The model receives a status and the last four digits.
AI powers the conversation. PCI Pal secures the engagement.

“Use of AI does not remove or bypass the need to meet the requirements of any applicable PCI SSC standard.”
PCI SSC, AI Principles, September 2025
The Help Desk Is Now the Front Door. Yours Also Takes Card Numbers.
Two of Britain’s largest retailers were breached through social-engineered support desks in 2025. Neither was a cardholder-data breach.
But, that’s the point. The same human layer that failed on identity verification is the layer hearing PANs today. Third parties were involved in 68% of retail breaches, compared to just 48% across all industries—and card data your outsourcer never receives is one row you never have to defend in your 12.8.5 matrix.

Certified Once, Not at Every Migration
Nearly 40% of retail contact centers are still on-premises. Nearly half of those on cloud platforms are changing, planning to change, or evaluating a switch.
A payment control embedded in one platform is a control you re-scope, re-integrate, and re-certify at every migration, every acquisition, and every region you add. A decoupled layer is the consolidation answer, not the exception to it: one payment security control across voice, chat, SMS, email, IVR, and AI agents, on whatever platform each part of your estate happens to run.
- Platform-independent – the control doesn’t belong to your CCaaS vendor, so it survives the decision to change them
- Channel-complete – platform-native masking is a voice feature and does nothing for chat, SMS, email, or AI agents
- Region-consistent – one control and one certification across a multi-platform, multi-region estate
- AI-agnostic – the same control sits in front of whichever LLM, voice bot, or AI agent platform you adopt next, so new AI doesn’t mean a new payment integration.

Your Gateway Relationship Doesn’t Change
PCI Pal boasts 130+ payment gateway integrations. That means multi-acquirer routing, interchange optimization, settlement terms, fraud rules, and PSP relationships stay exactly as they are.
Payment success rate is among the metrics merchants rate most important. A security layer that forces a single PSP is a tax on it. PCI Pal doesn’t touch it.


The Three Pillars of Seamless Security & Compliance
Assurance
PCI DSS Level 1 Service Provider. SOC 2 Type II. Available under NDA, not on request.
Architecture
Card data is captured outside your environment and tokenized at the point of entry. There is no point in the flow at which an agent, a desktop, a recording, a CRM, or a model can access it. Security built in, not bolted on.
Operational reality
99.999% uptime. Cloud-native from the start. Trusted by 750+ enterprise customers and proven through even the busiest Black Friday and Christmas peaks at retail scale.
Questions You Should Ask Every Vendor, Including Us
If you’re evaluating more than one option, these are the questions that separate them. Ask us the same ones.
Which of the twelve PCI DSS requirements come off our scope, and which stay ours? Show it as a responsibility matrix, not a claim.
What does your AI or agent-assisted integration receive during a payment—and what is retained, where, and for how long?
Where is cardholder data captured, and does it ever traverse our network or sit in our environment?
Which payment gateways do you support, and does using you constrain our acquirer routing?
Does your control cover chat, SMS, email, and IVR, or only voice?
If we change CCaaS platforms next year, what has to be rebuilt and re-certified?
Who are your subprocessors, and in which regions is data processed?
What Leaves Your Scope
Every system that touches cardholder data brings MFA enrollment, password policy, logging, vulnerability scanning, a targeted risk analysis, and a line in your assessment. Descoping the assisted payment channel removes the systems—and everything that attaches to them.
Your QSA will tell you what that’s worth in your environment. We’ll tell you exactly what comes out of scope.

Frequently Asked Questions
Yes, both under NDA, along with our SOC 2 Type II report. The matrix is our standard responsibility mapping across the services and deployment models we support—which PCI DSS requirements sit with us, which stay with you, and which are shared. We tailor it to your specific deployment at implementation, but the version you evaluate us on is the one you can take straight into a scoping conversation with your QSA.
Because sign-off records that a control was accepted, not that it descopes you. The Council is explicit that pause-and-resume doesn’t reduce PCI DSS applicability to the agent, the desktop, or the surrounding telephony systems—and its stated preference is suppression at the point of entry where the technology exists.
A status and the last four digits. The PAN never enters the model’s input stream, so there’s nothing in the transcript, the prompt log, the conversation summary, or the vector store to redact later. It’s the same whether the payment is handled by an AI agent, a human agent, or a hand-off between the two.
Either. Most retailers run PCI Pal as the single control across all channels, so security follows the customer rather than the channel, instead of maintaining a voice-only platform feature alongside separate handling for chat, SMS, email, and AI agents.
Card data is captured and tokenized outside your environment, in the region you specify. Processing locations and subprocessors are documented in the diligence pack.
The control moves with you. Because PCI Pal is a separate, cloud-native layer rather than a feature of one platform, it doesn’t get rebuilt and re-certified every time your contact center platform changes.



