Take card payments over the phone on Telnyx. The caller keys their card, Telnyx captures it, and Shuttle charges it through your own gateway.
Your calls stay on Telnyx. Shuttle works as the payment connector for Telnyx's <Pay> verb, and connects to 30+ payment providers that support voice, including Stripe, Adyen, PayPal, Authorize.net, Cybersource and Worldpay Access. Telnyx keeps the card away from your agents and recordings, and the card never touches your platform.
Looking to pay your own Telnyx bill? That is in Telnyx's billing guide. This guide is about taking payments from your callers.
What Telnyx Voice Payments Does
Telnyx Voice Payments takes card payments during a live call. It is in beta as of September 2026, and Telnyx says the beta is open to existing Telnyx customers. Per Telnyx's documentation:
The caller keys their card on the phone keypad. Nobody reads it out.
The digits stay out of the conversation. Telnyx keeps them away from your agent, human or AI, and out of your recording and transcript.
No transfer. The caller stays on the same call, and your flow picks up when the payment step ends.
Charge or tokenise. Take the payment now, or get a token for the card from your gateway.
Cards and ACH debit, in USD.
Three ways to start it: the
<Pay>verb in TeXML, the pay action in the Voice API, or the Pay tool on a Telnyx AI Assistant. Shuttle's connector is built for the TeXML<Pay>route, as covered below.
Telnyx sends the captured card to a payment connector you configure. In Telnyx's words, it works with "any processor you can reach through an HTTPS endpoint, using the generic connector."
The Connector Is the Part You Decide
Something has to sit at that HTTPS endpoint. It receives the card details in Telnyx's request format, charges your gateway, and replies in the format Telnyx expects.
Two common options:
Build it yourself. You write and run the endpoint, and connect it to each gateway you use. The card details then land on your own servers, which brings those systems into PCI scope.
Use Shuttle as the connector. You don't write or run the endpoint. Shuttle already connects to 30+ gateways that support voice, so if yours is one of them, you keep it and your merchant account. And the card stays off your servers: it passes through Shuttle's PCI DSS Level 1 environment to your gateway, which issues the token. Shuttle stores nothing.
How Phone Payments Work on Telnyx
The call runs on Telnyx, as it does now.
At the payment step, your TeXML flow runs
<Pay>, with Shuttle's connector named inpaymentConnector.The caller keys their card. Telnyx captures it and sends it to Shuttle.
Shuttle charges the card through your gateway, or tokenises it with your gateway.
The result comes back to your flow: the charge or token ID and the last four digits. The call carries on.
For the full transaction record, look up the charge or token ID in Shuttle's API. Shuttle does not store the card.
Setting It Up
In the Shuttle Merchant Portal, open your instance's Telnyx Pay Configuration page. It shows the endpoint URL and the credentials to give Telnyx. You need an admin login.
In the Telnyx portal, go to Voice API, then Applications, then Payment Connectors, and create a connector. Use Shuttle's endpoint URL and basic authentication with the credentials from step 1.
Add the Pay verb to your TeXML: use
<Pay>withpaymentConnectorset to the name you gave the connector.
Telnyx connectors have a test mode. Talk to us about testing against your gateway's sandbox before you go live.
Telnyx Pay Configuration is switched on by the same feature as Twilio Pay Configuration, so there is no new app to install. If you already take voice payments through Shuttle on Twilio, you use the same instance and the same gateways. See Twilio to Telnyx for what changes in the payment step.
Shuttle's connector is built for the <Pay> verb in TeXML. If you plan to start payments from the Voice API or from an AI Assistant's Pay tool, talk to us before you build.
Gateways and Payment Methods
Gateways. Shuttle connects to 30+ payment providers that support voice. Braintree, Square, QuickBooks Payments and Mollie do not work for voice payments through Shuttle.
ACH. Telnyx captures ACH debit as well as cards. For ACH on a call, use Authorize.net. Stripe's ACH runs on a hosted page, so it does not work on a call through Shuttle.
One gateway per payment method. Each payment method can go to its own gateway. For example, cards through Stripe and ACH through Authorize.net.
Currency. Telnyx describes Voice Payments as USD. If you need to charge in another currency, talk to us before you build.
Taking Payments for Several Clients
If you run calls for other businesses, as a platform, a BPO or an AI agent builder, each client runs on its own gateway and merchant account, with its own Telnyx payment connector. The money goes to each client's own account, never through yours. Talk to us about setting this up across your clients.
What It Costs
On Shuttle for Merchants, voice payments cost $49 per live instance per month. An instance is a payment channel, so taking payments by phone is one instance, and adding links makes two.
Each instance includes 245 Shuttle-billed transactions a month. Transactions on the Telnyx connector are billed by Shuttle, so they count toward the 245. After that, transactions are from $0.20 each, falling with volume. Telnyx bills its own usage separately.
Platforms rolling payments out to their merchants can use Shuttle for Platforms, from $2,500 of credit a month, spent on transactions. See pricing.
PCI: What Shuttle Changes and What It Does Not
Shuttle limits your PCI scope. It does not remove it.
Telnyx captures the card and keeps it out of your agents, recordings and transcripts. The card then passes through Shuttle's PCI DSS Level 1 environment to your gateway, which issues the token. Shuttle has no vault and stores nothing, and the card never touches your platform. Ask Telnyx for its PCI evidence for the capture step.
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. If you take payments for other businesses, as a BPO or an AI agent builder, you are a service provider, which means SAQ-D, or a Report on Compliance at Level 1 volumes.
Shuttle's PCI, ISO 27001 and SOC 2 evidence is on the security page.
Another Route: Keep the Payment Step on Twilio
If you would rather run the payment step on Twilio Pay, Shuttle's handoff route still works. Telnyx keeps your numbers and call routing, and only the payment segment runs on Twilio. This route needs a Twilio account. The Telnyx handoff guide has the details.
Telnyx Payments FAQ
Can Telnyx take card payments on a call? Yes. Telnyx Voice Payments captures the card by keypad during the call and sends it to a payment connector you configure. It is in beta as of September 2026.
Which payment processors work with Telnyx Pay? Telnyx says any processor you can reach through an HTTPS endpoint, using its generic connector. With Shuttle as the connector, that is 30+ providers that support voice.
Do I need a Twilio account? No. Shuttle's Telnyx connector runs on Telnyx's own Pay verb. You only need a Twilio account if you choose the handoff route.
How do I take card payments over the phone on Telnyx? Run Telnyx's <Pay> verb in your TeXML flow at the payment step, with a payment connector configured in Telnyx. The caller keys their card, and the connector charges it. With Shuttle as the connector, the charge goes through your own gateway, if it is one of the 30+ that support voice. See Setting It Up above for the steps.
Can I take IVR payments on Telnyx? Yes. An IVR built in TeXML can run <Pay> at the payment step, with Shuttle as the connector, so callers pay by keypad without an agent on the line. If your IVR runs on the Voice API rather than TeXML, talk to us before you build.
Does the caller have to be transferred to pay? No. Telnyx runs the payment step on the same call, and your flow picks up when it ends.
Does Shuttle store the card? No. The card passes through Shuttle on its way to your gateway. Your gateway issues the token and keeps it. Shuttle has no vault.
Does this take me out of PCI scope? No. It limits your scope. Merchants complete SAQ-A and platforms complete SAQ-D. If you take payments for other businesses, as a BPO or an AI agent builder, you are a service provider, which means SAQ-D, or a Report on Compliance at Level 1 volumes. Everyone taking card payments has to be PCI compliant, and your acquirer confirms which form applies to you.
Can I take ACH payments on a Telnyx call? Yes, through Authorize.net. Stripe's ACH runs on a hosted page, so it does not work on a call through Shuttle.
What happens if the caller cannot find their card? Shuttle can create a hosted payment link for you to send by SMS or email, so the caller can pay after the call. Links are a separate channel on Shuttle for Merchants.
Can a Telnyx AI agent take payments with Shuttle? Telnyx lets an AI Assistant start a payment with its Pay tool. Shuttle's connector is built for the Pay verb in TeXML, so if your agent will use the Pay tool, talk to us before you build. See Telnyx AI agent PCI payments.
Related Reading
Taking payments on Telnyx calls? Talk to us.