Moving calls from Twilio to Telnyx? If you take payments through Shuttle, they can come with you: same account, same gateway, and saved cards stay put.
Shuttle works as the payment connector on both carriers. You can move one call flow at a time, or keep some calls on each. Calls that stay on Twilio carry on exactly as they are.
This guide covers what moves, what stays, and the few things to change in your payment step.
What Moves and What Stays
Your numbers and call flows. Telnyx publishes its own guides for moving numbers and TwiML call flows, and says TeXML is built to run existing TwiML code. Use those for the rest of your call flow. The payment step is covered below.
The payment step. On Twilio, <Pay> sends the card to a Pay Connector installed from the Twilio Marketplace. On Telnyx, <Pay> in TeXML sends it to a payment connector you configure in your Telnyx account, as set out in Telnyx's Pay documentation. Shuttle works as the connector on both, so the payment step moves with a few changes, listed below.
Calls that stay on Twilio. Nothing changes. Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways. Your Twilio setup keeps working as it does today.
If You Take Payments Through Shuttle Today
One Shuttle instance, both carriers. Your Twilio connector and your Telnyx connector sit on the same Shuttle instance and run independently. Setting up Telnyx does not touch your Twilio configuration, so you can run both side by side, and move call flows when you're ready.
The same gateway. Shuttle's Telnyx connector works with the same voice gateways as its Twilio connector. If your gateway takes phone payments through Shuttle on Twilio today, it works with the Telnyx connector too. Telnyx describes Voice Payments as USD, so see the currency step below if you charge in anything else.
Your saved cards stay put. A card saved through Shuttle stays with your gateway, which holds it and issues the token. Shuttle has no vault, and nothing about the saved card is tied to Twilio. Moving carrier doesn't change that. After the move you can still charge those cards through Shuttle's API or a payment link. Neither connector charges a saved card inside the call itself.
What to Change in Your Payment Flow
Create the Telnyx connector. In the Shuttle Merchant Portal, the Telnyx Pay Configuration page gives you an endpoint URL and credentials. In the Telnyx portal, create a payment connector with them. The steps are in our Telnyx payments guide.
Point the Pay verb at it. In your TeXML
<Pay>, setpaymentConnectorto the name you gave the Telnyx connector.Read the result differently. Twilio posts the connector's result fields to your action URL. Telnyx sends back the charge or token ID and the last four digits. If your flow reads other result fields, look them up in Shuttle's API using the ID instead.
ACH: pass the account details yourself. Telnyx does not ask the caller for their bank account type, so pass it as a
<Parameter>in your TeXML, along with the account holder's name.Check the currency. Telnyx describes Voice Payments as USD. If a flow charges in another currency, talk to us before you move it.
Test before you switch numbers over. Talk to us about testing against your gateway's sandbox.
If You Use a Different Pay Connector on Twilio
Your Twilio setup keeps working for any calls that stay there. Other Pay Connectors on Twilio are installed from the Twilio Marketplace and work with Twilio's <Pay>. If you also run calls on Telnyx, <Pay> there needs a connector you configure in Telnyx, and Shuttle can be that connector, with 30+ payment providers that support voice.
Cards saved by another connector do not carry over to Shuttle on their own. They will need to be migrated, so talk to us before you plan around them.
Twilio Pay and Telnyx Voice Payments Side by Side
Twilio Pay | Telnyx Voice Payments | |
|---|---|---|
How the card is taken | Keyed in during the call, through | Keyed in during the call. Shuttle's connector is built for |
Where the card goes | A Pay Connector from the Twilio Marketplace, such as Shuttle | A payment connector you configure in Telnyx, such as Shuttle |
What comes back to your flow | Twilio's standard result fields, plus the connector's own fields | The charge or token ID and the masked card, but not the connector's own fields |
Telnyx Voice Payments is in beta as of September 2026. Shuttle's Telnyx connector is built for <Pay> in TeXML. If you plan to start payments from the Voice API or an AI Assistant's Pay tool, talk to us before you build.
PCI When You Move
Moving carrier doesn't change what Shuttle does with the card. It passes through Shuttle's PCI DSS Level 1 environment to your gateway, which issues the token. Shuttle has no vault and does not store the card. The card never touches your platform.
What changes is who captures it. On Telnyx, Telnyx takes the keypad entry, so ask Telnyx for its PCI evidence for that step.
Shuttle limits your PCI scope. It does not remove it. Merchants complete SAQ-A, the lightest PCI self-assessment; platforms complete SAQ-D. Everyone taking card payments has to be PCI compliant, and your acquirer confirms which form applies to you.
Twilio to Telnyx FAQ
Can I move from Twilio to Telnyx and keep taking payments through Shuttle? Yes. Shuttle works as the payment connector on both. Set up the Telnyx connector on your existing Shuttle instance, point <Pay> in your TeXML at it, and update how your flow reads the result, passes ACH details and sets the currency. Telnyx describes Voice Payments as USD.
What happens to my saved cards when I move from Twilio to Telnyx? They don't need to move. A card saved through Shuttle's Twilio connector stays with your gateway, which holds it, and nothing about it is tied to Twilio. After the move you can charge it through Shuttle's API or a payment link, but not inside the call. Cards saved by a different Pay Connector will need to be migrated.
Can I run Twilio and Telnyx at the same time? Yes. Both connectors run on the same Shuttle instance, independently, so you can move one call flow at a time.
Do I need to change my payment gateway? No. Shuttle's Telnyx connector works with the same voice gateways as its Twilio connector. Telnyx describes Voice Payments as USD, so if you charge in another currency, talk to us before you move.
Will my TwiML payment flow run on Telnyx unchanged? No. The payment step needs a few changes: point <Pay> at your Telnyx connector, look up result details in Shuttle's API instead of reading the connector's fields from your action URL, pass the ACH account type and holder name as parameters, and check the currency, since Telnyx describes Voice Payments as USD.
Do I have to move everything at once? No. You can move one call flow at a time, or keep some calls on each carrier.
Related Reading
Moving carriers and want to keep payments running? Talk to us.