Series: Secure flows in Architect

Secure call flows overview


前提条件
  • PureCloud 2 or PureCloud 3

The following permissions:

  • Architect > Flow > Add
  • Architect > Flow > Edit
  • Architect > FlowView

Use a secure call flow to temporarily prevent system recording or agent access to a caller’s entry of sensitive information, such as payment processing. Secure flows mask the audio paths and sensitive data captured through an automated IVR call flow.

The concept of secure IVR bundles multiple tools that the system currently offers. Enable secure interactions with a customer by either an automated system or by an agent. The provided tools help the system effectively manage the security of the data collected while still providing flexibility in the defined experience for the end caller.


When processing credit and debit card payments by phone, IVR technology is more secure than live phone support. Users don’t have to hand over sensitive financial data to an actual person. PureCloud’s secure IVR technology is designed to make it easy for PureCloud customers to handle any sensitive information safely. When used with credit cards, it allows PureCloud customers to comply with the Payment Card Industry Data Security Standard (PCI DSS). This standard provides guidelines for protecting consumers’ credit card information from unauthorized use.

For example, a caller speaking to an agent wants to make a payment toward a bill. Use a secure flow for a secure payment option that prompts customers to enter sensitive data, such as credit card or bank account information. The secure flow handles the payment processing and if configured, when it reaches the end flow action it returns the caller to the agent.

Implementing secure call flows can improve performance and reduce costs in many ways:

  • Reduce exposure to PCI compliance issues due to manual handling of credit card payments
  • Reduce agent-assisted processing
  • Improve the accuracy and efficiency of payments by phone
  • Improve customer satisfaction


PureCloud allows you to retrieve a trunk’s diagnostics logs to help diagnose call issues. When you enable protocol and media diagnostic captures for troubleshooting purposes, the system does not encrypt data.

Enabling media capture and protocol capture logs all data entered in the system, including data entered via secure call flows. This process can include sensitive data that the system should not expose or capture. It is recommended practice to avoid enabling these settings when using secure call flows.

If you are a PCI-compliant PureCloud organization and have the PCI DSS setting enabled, the PureCloud disables the Media Capture and Protocol Capture settings. For more information, see Enable media capture and Enable protocol capture.



:Previous Suggested Article Next Suggested Article: Secure flow scenarios