Building a carrier-agnostic voice checkout. With you.
Shuttle is developing a carrier-agnostic voice checkout product for Talkdesk customers — PCI handled, AI-ready, no telephony lock-in. Usable today by Talkdesk deployments on Twilio voice (via Twilio Pay); the carrier-agnostic version is targeted for later in 2026. We’re looking for a collaboration partner to validate it with real customers.
Talkdesk does everything on the call — until the customer says “I’d like to pay.”
Autopilot can recognise payment intent. Copilot can guide the agent through it. Studio can branch on the outcome. But there’s no native way to securely capture a 16-digit card number inside a Talkdesk flow.
Take it via DTMF in-band and the tones land in the agent’s ear, the call recording, and every downstream AI model that touches the audio. Take it via a legacy voice-payment service provider and you’re bolting dated UX onto an AI-first contact centre. Either way, PCI scope explodes.
The AI handles the conversation. The payment kills the autonomy.
Live: PCI-safe payment capture for Talkdesk on Twilio voice
For Talkdesk deployments using Twilio as the telephony carrier, Shuttle is usable today via Twilio Pay. The card is captured inside Shuttle’s certified PCI environment at the point of payment — the digits never reach the agent, the call recording, or any AI pipeline that touches the audio. There’s no native Talkdesk app: you build the agent-side interface for your workflow against Shuttle’s APIs, and a packaged Talkdesk integration is available as a paid project.
Payment links are the most turnkey path — SMS sent mid-call from a Talkdesk agent or Autopilot flow, real-time status returned. Same Shuttle, two capture modes, one compliance posture. Links also work with gateways that don’t support voice capture.
- PCI DSS Level 1 — card data never enters Talkdesk
- Twilio Pay voice capture + SMS payment links
- Autopilot payment handoff via API (you build the agent UI)
- Whatever PSP the customer’s already on
Talkdesk keeps the customer. Shuttle handles the card. Result returns to Autopilot or the agent workspace.
AI-led flow: the caller pays via the voice agent. DTMF tones are stripped before they reach Talkdesk, the recording, or any downstream model.
Copilot-assisted flow: the Talkdesk agent stays on the line through capture, with no card data ever on screen.
Where we’re headed: any Talkdesk deployment, no Twilio dependency
A carrier-agnostic version is targeted for later in 2026. The goal is that Shuttle no longer needs Twilio sitting under the call — so it works regardless of what carrier a Talkdesk deployment is using underneath. Same PCI posture, same payment surfaces. This is roadmap, not a shipped capability today.
One payments layer for every Talkdesk deployment in your customer base.
Talkdesk on Twilio voice
Usable now by Talkdesk customers running Twilio as the telephony carrier. Secure card capture via Twilio Pay, plus SMS payment links and an Autopilot handoff API — you build the agent-side interface against Shuttle’s APIs.
Carrier-agnostic (roadmap)
The goal: same Shuttle, no Twilio required, working with whatever carrier a Talkdesk deployment runs on — one payments partner across every customer. Targeted for later in 2026; not available today.
- Stripe
- Adyen
- Worldpay
- Checkout.com
- Authorize.net
- FreedomPay
- Global Payments
- + regional acquirers
Every payment surface a Talkdesk customer actually needs
Not just a DTMF connector. The full surface for voice + AI + link payments — PCI-handled at every step, designed to slot into the Talkdesk workspace.
Autopilot payment handoff
Detect payment intent in Autopilot, hand off to Shuttle, return the outcome to the AI conversation. End-to-end without a human in the loop.
Copilot-friendly agent APIs
APIs to trigger payments from your Talkdesk agent workflow and monitor capture status without ever exposing card digits. You build the agent-facing screen for your setup; Shuttle does not ship a pre-built Talkdesk widget.
Secure keypad capture
When it’s time to pay, capture moves to Shuttle’s certified PCI environment (on Twilio Pay today). The caller keys in their card there — the decodable digits never reach Talkdesk, the recording, or any downstream model.
SMS payment links mid-call
Send a hosted-page link via SMS from the Talkdesk flow when DTMF isn’t the right fit. Digital wallets supported. Status returns to the workspace in real time.
Multi-PSP routing
Route by merchant, region, card type, or failover. Critical for BPOs running Talkdesk across many clients with different gateway relationships.
Merchant portal
White-label dashboard for the customer — profiles, refunds, reporting, routing rules. Optional to expose; it complements Talkdesk rather than replacing any part of it.
Live checkout monitoring
Real-time view across DTMF and link transactions. Full or partial refunds, retries, profile management — without touching Talkdesk’s data plane.
Out-of-band by design
Card capture runs outside Talkdesk’s telephony, recording, and AI pipelines. Your customer’s SAQ drops from D to A. Yours stays exactly where it is.
PCI DSS Level 1, throughout
Every surface stays out of PCI scope for Talkdesk and the customer. Same compliance posture across DTMF, link, agent-led, and AI-led flows.
*Capabilities and timing for the carrier-agnostic release are subject to change as we iterate toward launch.
The AI contact centre is shipping. The payments layer underneath it isn’t.
Autopilot is closing every loop — except payments
AI voice agents are taking over the conversation. Without a payments handoff, every payment intent still escalates to a human. The autonomy story breaks at the till.
Legacy voice-payment vendors don’t fit AI-native flows
The incumbents are DTMF-only, agent-only, and built for the era before AI orchestration. Their UX doesn’t plug into Studio or Autopilot — and the integration burden lands on Talkdesk and the customer.
Enterprise procurement is asking the payments question earlier
Insurance, utilities, collections, BPO — the verticals already on Talkdesk — treat voice payments as table stakes. A named payments partner short-circuits the “and how do you take a card?” objection in every late-stage deal.
A payments collaborator, not a contact-centre competitor
Talkdesk owns
- The conversation — agents, Copilot, Autopilot, Studio flows
- The customer relationship and contact-centre data plane
- Workforce, quality, and CX analytics
- Telephony and carrier strategy for the deployment
Shuttle owns
- PCI-safe payment capture — DTMF, link, voice-led
- Multi-PSP routing across 40+ gateways
- The merchant-side dashboard, refunds, profiles, reporting
- Voice payments roadmap — never a contact-centre platform
We don’t do CCaaS, telephony, workforce, or analytics. We don’t want a customer relationship that should be Talkdesk’s. We want to be the payments line item on every Talkdesk enterprise deal where voice payments come up — and disappear quietly underneath everything else.
A lightweight collaboration to validate the carrier-agnostic product
Short-form Collaboration Agreement. Mutual, non-exclusive, terminable on 14 days’ notice. The brief is product validation and pipeline development — not a long-form commercial tie-up.
Introduce us to customers
- Identify Talkdesk customers who would benefit from voice payments — especially insurance, utilities, collections, BPO.
- Facilitate the introduction and join the early discovery calls.
- Share what you’re hearing in those calls so we can shape the product accordingly.
Build the product around what we learn
- Carrier-agnostic voice checkout: development, PCI, gateway integrations, all of it.
- Treat every introduced customer as yours — a 2-year non-solicit, written into the agreement.
- Joint meetings, early product access, and roadmap input weighted toward Talkdesk-shaped needs.
Non-solicit, 2 years
We won’t directly approach any customer you introduce for the product, for 2 years after the agreement ends.
Confidential by default
Mutual NDA built in. Anything you share with us about your roadmap, customers, or strategy stays with us.
Non-exclusive, low commitment
No exclusivity in either direction. 14 days’ notice to end it. Nothing locks you in beyond what feels useful.