Twilio Pay
Connect Any Compatible Payment Gateway to Twilio
Shuttle connects Twilio voice flows to 30+ payment gateways. Accept card payments during voice calls, with your PCI scope reduced.
$49/mo per live instance (one payment channel) · plus from $0.20 per transaction, falling with volume, billed through your Twilio account
Take a card on the call. Never hear the number.
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 card digits never reach your agents, your recordings, or your systems.
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 Access to Twilio, a connector passes the card details Twilio captures to your gateway for processing or tokenisation, so your systems never touch card data.
Shuttle's Twilio Pay Connector lets you connect 30+ payment gateways to Twilio, including Stripe, Adyen, Worldpay Access, Checkout.com, Authorize.net, and PayPal (PayFlow), with multi-PSP coverage, real-time reporting, and PCI DSS Level 1 certification.
New to Twilio Pay? Read the full explainer: What Is Twilio Pay? How It Works, Pricing, and Connectors.
See the Shuttle Pay Connector in Action
Product Demo
A product demo of an IVR card payment on Twilio, end to end.
Why Shuttle for Twilio Pay
Features
Built for Twilio Pay
The Shuttle connector installs from the Twilio Marketplace and is built to Twilio's Pay Connector specification.
30+ Payment Gateways
Connect Stripe, Adyen, Worldpay Access, Checkout.com, Cybersource, Global Payments, Shift4, Fortis, NMI, Moneris, Opayo, and more: 30+ gateways through one connector.
Multi-PSP Coverage
Each payment method can go to its own gateway, for example cards through Stripe and ACH through Authorize.net. No code changes. Configure it in your dashboard.
PCI DSS Level 1
Shuttle is PCI DSS Level 1. Card data never touches your infrastructure, so your PCI scope is heavily reduced. You still complete your annual self-assessment. Shuttle also holds ISO 27001 and SOC 2 Type 2.
Secure Keypad Capture
Callers key in their card on the phone keypad. The digits never reach the agent or the screen, and the call recording holds nothing usable.
Demo App Included
Install from the Twilio Marketplace, configure your gateway credentials, and start processing. A demo app and blueprint are included.
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 Access, etc.) in the Shuttle dashboard. Set up provider selection, capture modes, and tokenisation preferences.
- 3
Add Pay to your voice flow
Use Twilio's <Pay> verb in your TwiML. When the customer reaches the payment step, Twilio Pay captures the card digits securely, Shuttle sends them to your gateway, and the result comes back to your flow.
- 4
Process payments securely
Twilio Pay captures the card data and Shuttle passes it to your gateway, which processes or tokenises it. 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, including the ones below. Select yours to see how to connect it to Twilio for voice payments.
Generic, Stripe, Braintree, CardConnect or Shuttle?
Choosing a Pay Connector
Twilio's Marketplace lists several Pay Connectors. The Stripe, Braintree and CardConnect connectors each link Twilio's <Pay> verb to one gateway. 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 | Card data goes to Stripe |
| Braintree Connector | Braintree only | In-call (IVR) only | Anyone who needs visibility needs Braintree account access | Card data goes to Braintree |
| CardConnect Connector | CardConnect only | In-call (IVR) only | Anyone who needs visibility needs CardConnect account access | Card data goes to CardConnect |
| Shuttle Connector | Many gateways, one integration. Saved cards stay with the gateway that stored them | In-call (IVR), SMS payment links, REST API and webhooks | Invite teammates and manage client activity without raw gateway access | PCI DSS Level 1; your PCI scope is heavily reduced |
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 in Shuttle.
Twilio Pay Use Cases
Use Cases
Contact Centre Payments
Agents take payments during live calls, and the card digits never reach them. The agent stays on the line while Twilio Pay captures the card and Shuttle sends it to your gateway.
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 the payment step to Twilio Pay with the Shuttle connector. The AI continues the conversation while Twilio Pay captures the card via DTMF and Shuttle sends it to your gateway.
BPO & Outsourced Collections
Debt collection agencies and BPOs use Twilio Pay to collect payments during outbound calls. Card details never reach the agents, which limits PCI scope across distributed teams.
Twilio Pay Pricing
Simple Pricing
Install from Twilio Marketplace
plus from $0.20 per transaction, falling with volume, billed through your Twilio account
- An instance is one payment channel, so running phone and links is two instances
- Install from Twilio Marketplace
- Transactions billed through your Twilio account
- Card capture inside Shuttle's PCI DSS Level 1 environment
- 30+ payment gateways included
- Secure keypad capture & gateway tokenisation
- Real-time transaction reporting
- Multi-PSP coverage
- Demo app code & blueprint included
Need more than Twilio? Voice Checkout works with Twilio today, and any carrier coming soon.
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 an 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, 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 framework. You build the PSP integration yourself. Shuttle's connector has 30+ pre-built gateway integrations, PCI DSS Level 1 certification, multi-PSP coverage, tokenisation, and real-time monitoring.
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. Saved cards stay with the gateway that stored them, so switching gateways does not move them. 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 on Twilio, including Stripe, Adyen, Worldpay Access, Checkout.com, Authorize.net, PayPal (PayFlow), Global Payments, Cybersource, NMI, Moneris, Opayo, PaySafe, PayU, FreedomPay, CardConnect, USAePay, LiqPay, Shift4, Fortis, Fat Zebra, Trust Payments, BS Payone, Ecommpay, Xendit, Transbank, NAB, and ACI Speedpay.
Is Shuttle PCI compliant for Twilio payments?
Yes. Shuttle is PCI DSS Level 1 certified. Card data captured by Twilio Pay passes through Shuttle's PCI DSS Level 1 environment to your gateway and never touches your infrastructure, so your PCI scope is heavily reduced. You still complete your annual self-assessment, and your acquirer confirms which SAQ applies.
How much does Twilio Pay with Shuttle cost?
On Twilio, you pay $49 per live instance per month, plus from $0.20 per transaction, falling with volume, billed through your Twilio account. See pricing for the full model.
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 Twilio Pay with the Shuttle connector. The AI agent continues managing the conversation while Twilio Pay captures the card and Shuttle sends it to your gateway.
How do I set up Twilio Pay with Shuttle?
Install the Shuttle connector from the Twilio Marketplace, add your gateway credentials, and add the <Pay> verb to your TwiML. A demo app and setup blueprint are included.
Ready to accept payments on Twilio?
Install the Shuttle Pay Connector from the Twilio Marketplace. On Twilio, you pay $49 per live instance per month, plus from $0.20 per transaction, falling with volume, billed through your Twilio account.
Install on Twilio