Twilio Pay
Connect Any Payment Gateway to Twilio
Shuttle connects Twilio voice and chat flows to 30 payment gateways. Accept PCI-compliant card payments during voice calls. Connect your existing payment gateway to Twilio in minutes, not months.
$0.20 per transaction · No setup fees · Billed via Twilio
Take a card on the call. Never hear the number. 54 seconds.
What Is Twilio Pay?
Twilio Pay lets contact centres, IVR systems, and AI voice agents accept secure card payments during phone calls. When a customer needs to pay, they enter their card details via the telephone keypad (DTMF). The tones are stripped from the audio so agents never hear sensitive data.
To process a payment on Twilio, you need a Pay Connector that bridges Twilio's voice platform to your payment gateway. Whether you need to connect Stripe to Twilio, connect Adyen to Twilio, or connect Worldpay to Twilio, a connector handles tokenisation, gateway routing, and PCI compliance so your systems never touch card data.
Shuttle's Twilio Pay Connector lets you connect any of 30 payment gateways to Twilio out of the box (including Stripe, Adyen, Worldpay, Checkout.com, Authorize.net, and PayPal) with multi-PSP routing, real-time reporting, and PCI DSS Level 1 certification.
See the Shuttle Pay Connector in Action
Full Demo
The full 13-minute walkthrough: install from the Twilio Marketplace, connect your gateway, add the <Pay> verb, and take a test payment.
Why Shuttle for Twilio Pay
Features
Built for Twilio Pay
The Shuttle connector installs from the Twilio Marketplace, is built to Twilio's Pay Connector specification, and is optimised for production-grade voice payment flows.
30 Payment Gateways
Connect Stripe, Adyen, Worldpay, Checkout.com, Cybersource, Global Payments, QuickBooks Payments, Shift4, Mollie, Fortis, NMI, Moneris, Opayo, and more: 30 gateways through one connector.
Multi-PSP Routing
Route transactions to different gateways based on card type, currency, region, or business rules. No code changes. Configure routing in your dashboard.
PCI DSS Level 1
Highest level of payment card security. Card data never touches your infrastructure, reducing your PCI scope to SAQ-A. Also ISO 27001 and SOC 2 certified.
DTMF Masking
Card digits entered via keypad are intercepted and masked in real time. Agents hear a flat tone, never the actual card number. Call recordings are clean.
Go Live in Hours
Install from the Twilio Marketplace, configure your gateway credentials, and start processing. Demo app and blueprint included. No lengthy onboarding.
How to Set Up Twilio Pay with Shuttle
Four Steps
- 1
Install from Twilio Marketplace
Find the Shuttle Pay Connector on the Twilio Marketplace and install it to your Twilio account. No infrastructure to provision.
- 2
Configure your payment gateway
Add your gateway credentials (Stripe, Adyen, Worldpay, etc.) in the Shuttle dashboard. Set up routing rules, capture modes, and tokenisation preferences.
- 3
Add Pay to your voice flow
Use Twilio's <Pay> verb in your TwiML or Studio flow. When the customer reaches the payment step, Shuttle handles secure DTMF capture, gateway processing, and returns the result.
- 4
Process payments securely
Card data is captured within Shuttle's PCI-compliant environment, tokenised, and routed to your gateway. Your Twilio application receives a payment token, never raw card data.
Connect Your Payment Gateway to Twilio
Supported Gateways
Shuttle's Twilio Pay Connector supports 30 payment gateways. Select your gateway below to see how to connect it to Twilio for voice payments.
Generic, Stripe, Braintree, CardConnect or Shuttle?
Choosing a Pay Connector
As of July 2026, Twilio's Marketplace lists several Pay Connectors. The Stripe, Braintree and CardConnect connectors each link Twilio's <Pay> verb to one gateway (Twilio bills per transaction for Stripe since January 2024 and CardConnect since October 2025). The Generic Connector reaches any gateway, but you build and maintain the integration yourself and your endpoint receives full card data, which puts it in PCI scope. Shuttle is not an alternative to your gateway. It sits over it: one connector that reaches many gateways and adds team and client management on top. See the full comparisons: Stripe Pay Connector vs Shuttle and the Generic Pay Connector and your PCI scope.
| Connector | Gateways you can use | Channels | Team & client access | PCI |
|---|---|---|---|---|
| Generic Connector | Any gateway, but you build and maintain the integration yourself | In-call (IVR) only | Manage payments inside your own gateway account | Your responsibility to build to spec |
| Stripe Connector | Stripe only | In-call (IVR) only | Anyone who needs visibility needs Stripe account access | Handled by Stripe |
| Braintree Connector | Braintree only | In-call (IVR) only | Anyone who needs visibility needs Braintree account access | Handled by Braintree |
| CardConnect Connector | CardConnect only | In-call (IVR) only | Anyone who needs visibility needs CardConnect account access | Handled by CardConnect |
| Shuttle Connector | Many gateways, one integration, switch anytime | In-call (IVR), SMS payment links, REST API and webhooks | Invite teammates and manage client activity without raw gateway access | PCI DSS Level 1, SAQ-A scope for IVR |
What the Shuttle connector adds
For platforms, BPOs and teams
Team access without gateway logins
Invite teammates to view and manage payments across voice and links inside Shuttle, without giving anyone access to the raw gateway account.
Manage payments for every client
Platforms and BPOs see and manage each client's payment activity through Shuttle, without being handed credentials to every client's gateway account.
Voice and payment links together
Take payment in the call with Twilio's Pay verb, or send an SMS payment link to finish online or after the call. Both managed from one Shuttle console.
Twilio Pay Use Cases
Use Cases
Contact Centre Payments
Agents take payments during live calls without hearing card details. DTMF masking keeps the conversation flowing while Shuttle captures payment securely in the background.
IVR Payment Automation
Fully automated phone payment flows. Customers call in, navigate your IVR menu, and pay by entering card details on their keypad. No agent required.
AI Voice Agent Payments
AI voice agents built on Twilio can hand off to Shuttle for the payment step. The AI continues the conversation while Shuttle handles PCI-compliant card capture via DTMF.
BPO & Outsourced Collections
Debt collection agencies and BPOs use Twilio Pay to collect payments during outbound calls. Shuttle ensures PCI compliance across distributed agent teams.
Twilio Pay Pricing
Simple Pricing
Install from Twilio Marketplace
Billed via your Twilio account
- Install from Twilio Marketplace
- Billed through your Twilio account
- PCI-compliant voice payment capture
- 30 payment gateways included
- DTMF masking & tokenisation
- Real-time transaction reporting
- Multi-PSP routing
- Demo app code & blueprint included
Need more than Twilio? Voice Checkout is adding carrier-agnostic support (any carrier via SIP) later this year, alongside AI voice agent support, multi-currency, and regional telephony deployment.
Twilio Pay Guides & Resources
Learn More
Twilio Pay FAQ
FAQ
What is Twilio Pay?
Twilio Pay is Twilio's built-in capability for accepting payments during voice calls. It uses the <Pay> TwiML verb to capture card details via DTMF (keypad entry) during a call. A Pay Connector (like the Shuttle connector) bridges Twilio to your payment gateway to actually process the transaction.
What is a Twilio Pay Connector?
A Twilio Pay Connector is a certified integration that connects Twilio's payment capture to a specific payment gateway. Without a connector, Twilio can capture DTMF input but cannot process payments. Shuttle's connector supports 30 gateways out of the box, so you don't need to build and maintain your own.
How is Shuttle different from the Twilio Generic Connector?
The Twilio Generic Connector is a lightweight, open framework. You build the PSP integration yourself. Shuttle's connector is a fully managed, production-ready solution with 30 pre-built gateway integrations, PCI DSS Level 1 certification, multi-PSP routing, tokenisation, and real-time monitoring. You go live in hours instead of weeks.
Should I use the Generic, Stripe, Braintree, CardConnect, or Shuttle connector?
If you only ever want one specific gateway and a single in-call payment flow, a single-gateway connector (Stripe, Braintree, or CardConnect) is the simplest path, and the Generic Connector lets you build your own integration to any gateway. Choose Shuttle when you want one connector that reaches many gateways and can switch between them, take payments over both voice and SMS payment links, and let your team or your clients manage payments without handing out raw gateway-account access. Shuttle sits over your gateway rather than replacing it.
Can my team manage payments without access to the gateway account?
Yes. With Shuttle you invite teammates into Shuttle to view and manage payments across voice and links. They never need a login to the underlying gateway account. A single-gateway connector leaves you managing payments inside the raw gateway console, so anyone who needs visibility needs full account access.
I run payments for multiple client merchants. Can Shuttle handle that?
Yes. Platforms and BPOs use Shuttle to see and manage each client's payment activity in one place, without being given access to every client's gateway account. Connecting a gateway directly would mean holding credentials for each client's account.
What payment gateways does Shuttle support on Twilio?
Shuttle supports 30 gateways including Stripe, Adyen, Worldpay, Checkout.com, Authorize.net, PayPal, Cybersource, Global Payments, QuickBooks Payments, Shift4, Mollie, Fortis, Fat Zebra, Trust Payments, BS Payone, Ecommpay, Xendit, Transbank, NAB, ACI Speedpay, NMI, Moneris, Opayo, PaySafe, PayU, FreedomPay, CardConnect, USAePay, and LiqPay. New gateways are added regularly.
Is Shuttle PCI compliant for Twilio payments?
Yes. Shuttle is PCI DSS Level 1 certified, the highest level of payment card security. Card data captured during Twilio calls is processed within Shuttle's PCI-compliant environment and never touches your infrastructure. This reduces your PCI scope to SAQ-A.
How much does Twilio Pay with Shuttle cost?
Shuttle's Twilio Pay Connector costs $0.20 per transaction, billed through your Twilio account. No setup fees, no monthly minimums, no hidden costs. You only pay for transactions you process.
Can I use Twilio Pay with AI voice agents?
Yes. AI voice agents built on Twilio (including those powered by PolyAI, Retell, and other platforms) can hand off the payment step to Shuttle. The AI agent continues managing the conversation while Shuttle handles PCI-compliant DTMF capture in the background.
How long does it take to set up Twilio Pay with Shuttle?
Most teams go live within hours. Install the Shuttle connector from the Twilio Marketplace, add your gateway credentials, and add the <Pay> verb to your TwiML or Studio flow. A demo app and setup blueprint are included.
Ready to accept payments on Twilio?
Install the Shuttle Pay Connector from the Twilio Marketplace and start processing voice payments today. $0.20 per transaction, no setup fees.
Install on Twilio