Unlike most AI voice platforms, ElevenLabs Agents already has a native payment story. Its Stripe integration lets conversational AI agents take payments through saved one-click methods and secure payment links, with the actual card processing handled inside Stripe's PCI DSS Level 1 infrastructure. ElevenLabs explicitly steers agents away from collecting card numbers by voice and toward secure links instead.
That is a genuinely good starting point. So this guide is not "ElevenLabs can't take payments." It can. This guide covers what the native Stripe integration does, where it stops, and when teams reach for Shuttle as the payment layer instead of, or alongside, the native option.
The short version: if you only need Stripe, and you only need link or saved-method payments, the native ElevenLabs integration may be all you need. If you need more than one payment gateway, in-call card capture by keypad, or a single payment layer across ElevenLabs and your other channels, that is where Shuttle fits.
What the Native ElevenLabs + Stripe Integration Covers
The native integration is built specifically on Stripe. From the documentation, it provides:
Secure payment links for card data collection, sent during or after the conversation
One-click payments using a customer's saved Stripe payment method
Conversational checkout including cart management, order confirmation, and receipts
PCI DSS Level 1 processing via Stripe's infrastructure, so card data is handled by Stripe rather than stored on your systems
Notably, ElevenLabs guidance is explicit that agents should never request card numbers through voice and should direct customers to secure payment links. So the native model is link-first and saved-method-first, by design.
For a business that runs entirely on Stripe and is happy with link or saved-method payments, that covers a lot.
Where the Native Integration Stops
Three limits matter for many teams.
It is Stripe-only. The native integration connects to Stripe and nothing else. If your business uses Adyen, Worldpay, Checkout.com, or any other gateway, or an enterprise client mandates a specific PSP, the native path does not reach them. Agencies running ElevenLabs agents for multiple clients cannot route each client to its own gateway.
There is no in-call card capture by keypad. Because the native model deliberately avoids voice card entry, there is no way for a caller to key their card in on the phone mid-call and have it captured securely in the same flow. The customer is sent to a link. For some journeys that is fine; for others, especially older or less digital callers, the link adds friction and drop-off where a keypad payment would have closed there and then.
It is one channel. The native integration lives inside ElevenLabs. If you also take payments through a contact centre, an IVR, or human agents on another platform, you end up with separate payment setups and separate reporting per channel.
How Shuttle Fits
Shuttle is a PCI DSS Level 1 certified Service Provider that acts as a payment layer across your channels, including ElevenLabs agents. You can use it instead of the native integration when its limits bite, or alongside it.
There is no native ElevenLabs integration for Shuttle. The handoff is API-driven and built on Shuttle's Twilio-based capture, so you must be a Twilio customer, and your application code triggers the handoff at the point of payment.
Multi-PSP routing. Shuttle connects to 30+ payment gateways including Stripe, Adyen, Worldpay, and Checkout.com. Set which provider handles each payment type, and set amount and currency limits on when each method is offered. For agencies and enterprises, each client or business entity can use its own gateway through a single integration. Switching gateway is configuration, not re-integration, though saved cards stay with the gateway that stored them. A few gateways (Braintree, for example) work for payment links but not for voice capture, because they will not allow raw card data to be passed.
Secure in-call keypad capture. When you do want the customer to pay by keypad during the call, your application invokes Shuttle's secure capture at the point of payment. The card is captured in a secure PCI DSS Level 1 capture (today, via Twilio Pay) and passed to Shuttle's PCI DSS Level 1 environment, so the digits never reach the ElevenLabs platform or your recordings. The agent's voice pauses during entry and resumes on the result.
Payment links too. Shuttle also generates hosted payment links by SMS or email, including mid-call, so you keep the link option where it suits, across any of your supported gateways rather than Stripe alone. Payment links are the turnkey path and work even with gateways that do not support voice capture.
One layer across channels. If you run ElevenLabs with other voice or contact-centre channels, Shuttle is the single payment layer and single source of payment reporting across all of them.
How It Works with Shuttle
Your ElevenLabs agent runs the conversation and reaches the payment step.
A tool call from your application triggers Shuttle to create a payment session with the amount, currency, and gateway configuration.
The customer pays either by keypad, where a secure PCI DSS Level 1 capture takes the card at the point of payment (today, via Twilio Pay), or by a secure link Shuttle sends.
Shuttle sends the payment to your configured gateway inside its certified environment.
The result returns to your application as a webhook with the outcome, a transaction reference, and a masked card number, and the agent confirms.
Card data never enters the ElevenLabs platform, your transcripts, or your recordings, which heavily reduces your PCI scope. Merchants complete SAQ-A and platforms complete SAQ-D.
One honest caveat to set expectations: the secure capture at the point of payment is live now. Shuttle handles the payment segment of the call, not the whole conversation. Returning the caller to the same ElevenLabs agent after payment works today: you program the return route in your Twilio flow and pass a conversation ID, so the agent picks the call back up with full context. Shuttle works with Twilio today, and any carrier coming soon. You also need some technical resource: Shuttle provides ready-made interfaces for payment links plus the capture and APIs, and you build the agent-side wiring against Shuttle's sandbox gateway for the proof of concept.
When to Use Which
Native ElevenLabs + Stripe: you are Stripe-only, link and saved-method payments are enough, and ElevenLabs is your only payment channel.
Shuttle: you need more than one gateway, an enterprise client or market mandates a specific PSP, you want in-call keypad payments, or you want one payment layer across ElevenLabs and your other channels.
Many teams start native and move to Shuttle when a second PSP, an enterprise mandate, or a multi-client requirement appears.
FAQ
Can ElevenLabs agents take payments natively? Yes. ElevenLabs has a native Stripe integration with secure payment links and one-click saved-method payments, processed under Stripe's PCI DSS Level 1 infrastructure.
Does Shuttle have a native ElevenLabs integration? No. There is no native ElevenLabs integration for Shuttle today. The handoff is API-driven: your application invokes Shuttle's Twilio-based secure capture at the point of payment.
Does this require Twilio? Yes, today. Shuttle's secure capture currently runs over Twilio Pay, so you must be a Twilio customer. Shuttle works with Twilio today, and any carrier coming soon.
Does the native integration support gateways other than Stripe? No. It is Stripe-only. For Adyen, Worldpay, Checkout.com, or per-client routing, you need a multi-PSP payment layer such as Shuttle, which connects to 30+ gateways. Switching gateway is configuration, not re-integration, though saved cards stay with the gateway that stored them.
Can a customer pay by keypad during an ElevenLabs call? Not with the native integration, which directs customers to payment links rather than voice or keypad card entry. With Shuttle, your application can invoke a secure PCI DSS Level 1 capture at the point of payment (today, via Twilio Pay) so the customer keys their card in without it reaching ElevenLabs.
Does card data stay out of ElevenLabs? With Stripe-native links, card data is handled by Stripe. With Shuttle, card data is captured through Twilio Pay and passed to Shuttle's PCI DSS Level 1 environment, so it never reaches the ElevenLabs platform or your recordings. Either way, your PCI scope is heavily reduced: merchants complete SAQ-A and platforms complete SAQ-D.
What does Shuttle cost? For voice, $49 per live instance per month, plus from $0.20 per transaction, falling with volume, billed through your Twilio account. See pricing.
Related Reading
Retell AI Payments: PCI-compliant payment capture for Retell AI voice agents
Vapi Payments: secure payment capture for Vapi voice agents
Bland AI Payments: secure payment capture for Bland AI phone agents
Synthflow Payments: native Stripe vs multi-PSP for Synthflow voice agents
How AI Voice Agents Take PCI-Compliant Payments: the technical architecture for secure payment capture during AI voice calls
What Are Voice Payments? The Complete Guide: IVR, agent-assisted, and AI voice payment models compared
Add Multi-PSP Payments to Your ElevenLabs Agents
Shuttle is a PCI DSS Level 1 certified Service Provider. If your ElevenLabs agents have outgrown Stripe-only payments, or you need in-call card capture and routing across multiple gateways:
See Voice Checkout | Book a discovery call
