A2P 10DLC Campaign Vetting Delays: Twilio cannot approve 10DLC Campaigns ourselves, and must rely on third parties who control our connections to carriers to sign off. These external processes are creating several week delays for our customers. We continue to escalate these issues and are working to reduce delays wherever possible. Further details will be shared in the Campaign Vetting Changes article as they become available.

PCI Compliant Twilio Workflows

The Payment Card Industry Data Security Standard (PCI DSS) is a set of security standards designed to ensure that ALL companies that accept, process, store or transmit credit card information maintain a secure environment. The PCI standard requires a continuous validation process in order to remain compliant, and dictates that all businesses that store, process or transmit payment cardholder data must be PCI Compliant.

Twilio's <Pay> TwiML verb allows you to quickly and easily build a PCI Compliant workflow for securely capturing payments over the phone. With <Pay>, Twilio developers can capture end customer credit card information, and then pass this information along to your payment provider of choice through Twilio’s newly created <Pay> Connectors for processing. Best of all, <Pay> handles all of the PCI infrastructure and auditing requirements, so you can focus on building your payment workflows without the hassle.

For more details and code samples, please see Getting Started with the Twilio Programmable Voice <Pay> TwiML Verb (Beta).

Additional Resources

Have more questions? Submit a request
Powered by Zendesk