If you're running a contact centre on Talkdesk — for an insurance brokerage, a debt-recovery agency, a utility, a hospitality group, or a multi-tenant BPO — you've already met the payment gap. Customers want to pay on the call. Talkdesk doesn't have a native, PCI-compliant way to capture their card.
Talkdesk Autopilot handles intent recognition, account lookups, scheduling, and escalation. Talkdesk Copilot supports live agents with real-time guidance. But the moment a 16-digit card number needs to be collected, every option leaves you exposed: agents reading numbers into recordings, transferring callers to separate IVRs, or single-PSP integrations that lock you to one acquirer.
This guide is for merchants taking payments through Talkdesk, and for solution providers and AppConnect partners implementing Talkdesk for their clients. It covers how Shuttle adds PCI-compliant payment capture — multi-PSP, AI-friendly, and built so Talkdesk Autopilot can hand off to a payment flow without breaking conversation.
The Payment Gap in Talkdesk
Talkdesk's AI capabilities are industry-leading for conversation handling. But payment capture requires a fundamentally different kind of infrastructure, and the gap is significant:
No native payment processing. Talkdesk does not have a built-in payment engine. There is no way to trigger a card transaction from within a Talkdesk Studio flow, an Autopilot conversation, or an agent interaction without external integration.
No DTMF isolation. If a customer enters card digits via keypad during a Talkdesk call, those DTMF tones are audible to the agent and captured in call recordings. This immediately puts your telephony, recording, and storage infrastructure into full PCI scope.
No AI-to-payment handoff. Talkdesk Autopilot can detect when a customer wants to pay, but it cannot execute the payment. The typical workaround is escalating to a human agent — which defeats the purpose of AI-driven automation and increases cost per interaction. There is no defined handoff protocol from Autopilot to a secure payment flow that returns a result to the AI conversation.
No multi-PSP routing. Enterprise customers need to route payments to their own gateways. A utility company on Talkdesk needs payments going to Worldpay. An insurance company needs Adyen. A BPO needs to route to a different gateway for each of its clients. Without multi-PSP support, every customer is forced onto whatever gateway the payment partner supports.
Full PCI scope. Any attempt to capture card data within the Talkdesk environment — whether through agent conversation, IVR, or AI — creates PCI scope across your entire infrastructure. SAQ-D compliance is expensive, time-consuming, and operationally burdensome.
For organisations that chose Talkdesk for its AI capabilities, the inability to complete payment transactions autonomously is a significant limitation. The AI can do everything except the thing the customer called to do.
How to Add Payments to Talkdesk
Shuttle integrates with Talkdesk to provide PCI-compliant payment capture for both human-assisted and AI-driven voice flows. The integration adds payment capability without modifying your core Talkdesk infrastructure.
DTMF Masking
When a payment is triggered, the call's audio path is routed through Shuttle's PCI-certified environment. The customer enters their card number, expiry, and CVV via phone keypad. Shuttle captures the DTMF tones securely and replaces them with flat masking tones in the audio returned to Talkdesk.
The agent (or AI agent) remains connected throughout. Agents hear a confirmation tone for each keypress without knowing the actual digits. Call recordings contain only masked tones — no card data.
Integration connects via:
Twilio carrier — if Talkdesk uses Twilio as the telephony backbone, Shuttle connects through existing Twilio infrastructure
Direct SIP — for other telephony configurations, Shuttle integrates via SIP for the payment leg
Autopilot Payment Handoff
This is particularly relevant for Talkdesk's AI-first positioning. When Autopilot detects payment intent ("I'd like to pay my bill," "Can I make a payment?"), it triggers the Shuttle payment flow via API. The call remains active. Shuttle handles the secure card capture via DTMF. The payment result is returned to Autopilot, which continues the conversation — confirming the payment, providing a reference number, or handling follow-up queries.
The customer never leaves the AI conversation. No human agent is involved. The payment is fully autonomous.
Payment Links
For calls where DTMF is not suitable, Shuttle generates a payment link sent via SMS during the call. The customer taps the link, enters card details on a secure hosted page, and payment confirmation is returned to the agent or Autopilot in real time.
Agent-Assist Interface
For human-assisted calls, Shuttle provides a widget that integrates with the Talkdesk agent workspace. Agents trigger payments, monitor card entry progress, and receive results — all without seeing or handling card data.
How It Works
The payment flow on Talkdesk with Shuttle:
Customer is on a call managed by Talkdesk — either with a live agent or Talkdesk Autopilot.
Payment intent is detected. Autopilot recognises payment intent and triggers the Shuttle payment flow via API. Or a live agent clicks "Take Payment" in the Shuttle widget, specifying the amount and merchant.
Audio routing activates. The call audio is routed through Shuttle's PCI-certified environment. The conversation is uninterrupted — the agent or Autopilot remains connected.
Customer enters card details. Shuttle prompts the customer to enter their card number, expiry date, and CVV via phone keypad. DTMF tones are captured by Shuttle and replaced with flat masking tones in the audio stream.
**Transaction is processed.** Shuttle routes the card data to the merchant's configured payment gateway — any of the 40+ supported PSPs. The transaction is authorised in real time.
Result returned. The payment outcome (approved, declined, or error with reason) is returned to the Talkdesk agent workspace or Autopilot flow. Autopilot can confirm: "Your payment of forty-seven pounds has been processed. Your reference number is..." The live agent sees the result in their widget.
Audio routing disengages. The call returns to its normal path. No card data has entered the Talkdesk environment.
For fully autonomous AI payments, steps 1 through 7 happen without any human involvement. The customer calls, Autopilot handles the conversation, Shuttle handles the payment, and Autopilot confirms the outcome. End to end.
Agent workflow
From the Talkdesk agent desktop, the agent stays on the live call. When the caller is ready to pay, the agent clicks a payment action in their workspace and confirms the amount. They never see, type, or hear the card number — DTMF tones are masked from recordings and from the agent's audio. The agent can see status updates (entered card, validated, processed, approved or declined) without ever entering PCI scope. If the call drops mid-payment, the agent can resume or send a payment link to finish the transaction asynchronously.
Customer experience
The customer stays on the same call with the same agent. When prompted, they enter their card details on their phone keypad — the tones are masked so neither the agent nor the recording captures them. They hear confirmation in real time and stay on the line for follow-up questions, receipt delivery, or scheduling. There's no transfer to a separate IVR, no callback to complete payment, and no link they have to action later. Talkdesk Autopilot can hand off to a payment flow and resume the conversation when payment completes.
Multi-PSP Support
Enterprise organisations using Talkdesk typically need payment routing flexibility that goes beyond a single gateway.
Shuttle supports 40+ payment gateways with configurable routing:
By merchant — each end client or business unit routes to its own gateway. A BPO using Talkdesk for multiple clients routes Client A's payments to Stripe, Client B's to Worldpay, Client C's to Adyen — all through one integration.
By region — multinational enterprises route UK payments to one gateway, US payments to another, and European payments to a third, optimising for settlement speed and transaction costs.
By failover — if the primary gateway is unavailable, transactions automatically route to a backup. For AI-driven payment flows that operate 24/7 without human oversight, failover is essential.
By card type — route specific card brands to gateways with better rates for those brands.
For Talkdesk deployments where Autopilot handles payment flows autonomously, multi-PSP routing ensures the right gateway is selected automatically based on the merchant context — no human decision-making required.
Pricing is transparent and volume-based — see Shuttle pricing for the per-transaction model and what you pay across multiple PSPs.
PCI Compliance
Shuttle is a PCI DSS Level 1 certified Service Provider — the highest level of payment security certification in the industry.
With Shuttle, card data never enters your Talkdesk environment. Your telephony systems, call recordings, agent workstations, Autopilot infrastructure, and AI pipelines are all out of PCI scope.
This is especially important for Talkdesk users running AI transcription, summarisation, and analytics. Without DTMF isolation, card data spoken during calls flows through Talkdesk's AI pipelines — models you may not fully control processing data you are responsible for protecting. With Shuttle, card data is never in the audio stream, so your AI processes only non-sensitive conversation data.
Your PCI compliance drops from SAQ-D (300+ controls) to SAQ-A (the lightest assessment). This saves significant time, cost, and operational complexity — particularly for organisations in regulated industries where PCI compliance is a procurement requirement.
For Solution Providers and Talkdesk AppConnect Partners
If you're a Talkdesk AppConnect partner or system integrator deploying Talkdesk for clients, Shuttle is the payment layer that plugs in alongside your build. We support white-label deployment, multi-PSP routing across your client portfolio (so each client keeps their preferred acquirer), and partner-friendly commercials. Shuttle is Twilio's official payment partner and integrates with Talkdesk Autopilot handoffs, so AI-led conversations can pass to a compliant payment flow and back without breaking flow. For partnership conversations, book a discovery call.
Use Cases
Insurance
Insurance contact centres are among the largest Talkdesk adopters. Premium collections, renewal payments, claims settlements, and payment plan adjustments are daily operations. Talkdesk Autopilot can handle the conversation; Shuttle handles the payment. Fully autonomous premium collection — no agent needed.
Collections and Debt Recovery
The moment a debtor agrees to pay is the highest-conversion moment in a collections call. Any delay — transferring to a website, sending a link, escalating to a human — reduces the likelihood of payment. With Shuttle on Talkdesk, the payment is captured immediately, in-call, whether the conversation is with an agent or an AI.
Utilities
Utility companies process high volumes of bill payments through contact centres. Talkdesk's AI capabilities can handle the majority of "I want to pay my bill" calls autonomously. Adding Shuttle's payment capture completes the autonomous loop — the customer calls, the AI handles the conversation and the payment, and no human is involved. At scale, this dramatically reduces cost per interaction.
Travel and Hospitality
Travel companies use Talkdesk for booking changes, cancellations, and upgrades — all involving payments. Multi-currency support and multi-PSP routing handle the complexity of international travel transactions.
Frequently Asked Questions
Can Shuttle work with Talkdesk Autopilot for fully autonomous payments?
Yes. Shuttle provides an API that Autopilot can trigger when payment intent is detected. The payment capture happens within the call, and the result is returned to Autopilot so the conversation continues without human involvement.
Does the integration require changes to my Talkdesk telephony?
If you use Twilio as your carrier, no changes are needed. For other carriers, a SIP configuration is added for the payment leg only. Your existing Talkdesk call flows and routing remain unchanged.
How many gateways does Shuttle support?
40+ payment gateways including Stripe, Adyen, Worldpay, Checkout.com, Braintree, Square, Mollie, and many more. Multiple gateways can be active simultaneously with routing rules.
What does Shuttle cost?
$0.20 per transaction. No setup fees, no per-seat licensing, no monthly minimums.
Can I use Shuttle for both AI and human-assisted payment flows on Talkdesk?
Yes. The same Shuttle integration supports both Autopilot-triggered payments and agent-assisted payments via the desktop widget. The underlying payment capture and gateway routing are identical.
Related Reading
PCI-Compliant Payments for Contact Centres — the complete guide to contact centre payment processing
Twilio Pay Connectors — how Shuttle integrates with Twilio's payment infrastructure
Voice Payments — comprehensive guide to voice payment capture
AI Voice Agent PCI Payments — adding payments to AI voice agents
Embedded Payments for CCaaS — the platform operator's guide to CCaaS payments
Genesys Cloud Payments — PCI-compliant payments for Genesys Cloud
Five9 Payments — secure payment processing for Five9
NICE CXone Payments — payment capture for NICE CXone
RingCentral Payments — voice payments for RingCX and RingEX
Get Started
Shuttle adds enterprise-grade, PCI-compliant payment infrastructure to Talkdesk without changes to your telephony, agent training, or customer experience. Most deployments go live in under two weeks across multiple PSPs.
If you take payments in a contact centre, see how Shuttle works for merchants, or book a discovery call to walk through your specific deployment.