Evidence tier Source Confirmed · 4 captures on record
What the publisher says
As described on AWS Marketplace.
Data security matters more than ever to your customers and to your brands reputation. When your customers use their credit cards to make a payment over the phone, they trust you with their personal authentication data. It is stipulated in the PCI DSS guidelines that all sensitive card data is removed from call recordings automatically, without the need for an agent or other members of staff to intervene.
If calls are being recorded and payments are taken over the phone this can present a compliance issue. The best strategy for protecting your customers and ensuring compliance is to never record or store this confidential information, even if encrypted or redaction is attempted after the event.
Show the rest of the publisher’s description (2 more lines)
Pauseable achieves compliant recording by automatically pausing recording during the payment process when confidential information is being exchanged. This ensures sensitive card data is never recorded, helping to enable PCI DSS compliance for contact centers and other businesses that process card payments.
Pauseable is recognized by Security Assessors and QSAs, and is used by dozens of financial services, Healthcare, Retail, BPO and Government customers across tens of thousands of agent positions worldwide.
Highlights
Highlighted by the publisher on AWS Marketplace.
Rapid, easy deployment in hours. Pauseable handles all integration in-app, meaning whether you use the latest web-based CRM systems or legacy Green-Screen Emulators, internal development teams aren't required.
Seamless and automatic for both agents and customers. Your people stay focused on providing an exceptional service and do not have to worry about additional steps or buttons.
Customer data stays out of the recording estate, in real time, thus reducing risk, simplifying compliance and lowering your costs.
Agent build and provenance
See the full provenance
The layer-by-layer build, the evidence behind each claim, the risk basis and the cross-marketplace links are open to any account. Some rows are disclosed, some the source leaves Unknown; a free account shows you which.
Compliance
- FedRAMPConfirmedNot listed90%, registry-checkedNo FedRAMP Marketplace entry matched this vendor's domain, checked 2026-08-27registry recordas observed 2026-08-27
Confirmed means matched to a public authoritative registry. Claimed means the vendor or its listing states it, not yet cross-checked. A framework not shown was not found in any source we hold, which is not evidence against it. Not listed means a scoped registry check found no match for this vendor's domain: a No is a scoped registry check, not a compliance judgment. Confidence bands: 95% domain-verified, 90% registry-checked, 80% self-attested, 70% weak signal. Self-attested items marked “vendor's site” are gathered from the vendor's own website and are not verified by us.
Vendor
External enrichment
Plans and pricing as listed
6 listed- UserHrs
- UserHrs
- Users
- Users
- Users
- Users
Refund terms
As stated by the publisher on AWS Marketplace.
Refunds are not available
Sources
Linked repositories
Unknown means this listing does not publish a repository. It is not a statement that the code is closed, and a linked repository is not a claim that the publisher wrote it: the registry computes that relationship privately and does not publish it.
Evidence risk is the share of the build you cannot see before you deploy, not a security rating. Sign in to see the layer-by-layer basis for this band.