Making voice payments work like software.
Voice payments for contact centre integrators. We power the Twilio Pay Connector for CCaaS deployments today; later this year the any-gateway any-carrier platform ships. Looking for integrator partners who want in early.
Your clients hit the same wall every time they need voice payments
Their client wants payments on the call. Agent screen sees card data — PCI scope explodes. Or they bolt on a legacy service provider: another vendor, another integration project, dated UX.
Or worse — they have to rebuild for every CCaaS the client uses. Twilio for one, Genesys for another, Five9 for a third. Same payment problem, three times the build.
The integrator carries the integration burden. Or says no.
Live: PCI-safe voice payments on Twilio
We power the Twilio Pay Connector. Mid-call card capture via DTMF or payment links. Card data never touches the agent screen or your client’s CCaaS. PCI DSS Level 1.
Replaces legacy voice-payment service providers with modern, programmable payment infrastructure. Works with whatever PSP the merchant already has.
- PCI DSS Level 1
- DTMF + payment links
- Any PSP the merchant uses
Agent stays on the line. Agent screen sees nothing.
Customer pays via the IVR — DTMF tones are stripped before they reach the agent or your systems.
Live agent stays on the line while the customer enters card details securely.
Any gateway, any carrier
The version we’re shipping later this year works regardless of CCaaS or PSP. Your client runs Worldpay on Five9, Stripe on Genesys, a regional acquirer on AWS Connect — same Shuttle integration, same compliance posture, no per-client build.
One payment layer across every contact-centre stack you deploy.
- Twilio
- Genesys
- Five9
- AWS Connect
- 8x8
- RingCentral
- Stripe
- Adyen
- Worldpay
- Checkout.com
- Authorize.net
- + regional acquirers
Every interface your clients need, out of the box
Not just a connector. The full surface for voice and link payments — PCI-handled at every step.
Any-gateway any-carrier
One Shuttle integration. Mix and match CCaaS and PSP per client without a custom build.
AI voices, out of the box
Pre-built payment voice flows you can drop into IVR or AI agent stacks — no in-house voice work.
AI voice recognition
Capture card details by voice as well as keypad. Natural prompts, redacted before they reach you.
Agent-assisted voice
Live agent stays on the line through capture. DTMF stripped before it hits the agent screen.
Call forwarding
Route into Shuttle for the secure capture segment, hand the caller back when payment is done.
Payment link creation
Send a card-collection link via SMS or email mid-call. Digital wallets supported.
Merchant portal
White-label dashboard for your client — profiles, refunds, reporting, multi-PSP routing.
Checkout monitoring
Live transaction view across voice and link. Full or partial refunds, profile management.
PCI DSS Level 1, throughout
Every interface stays out of scope for your client and you. Same posture across every channel.
*Features, capabilities and timing subject to change as we iterate toward launch.
Voice is shifting. Faster than the legacy payments stack.
AI voice is eating the contact centre
Your clients are deploying AI voice agents alongside, and increasingly instead of, agent queues. Every modern build you ship from here needs to take payments across both.
Legacy voice-payment vendors weren’t built for this
The incumbents are DTMF-only, agent-only, single-CCaaS. Your clients’ AI-native flows don’t plug into them cleanly — and the integration burden lands on you when they don’t.
The integrators who move first win the next wave
Voice + AI + payments shipped as one architecture is the next default. We’re partnering with integrators who want to be the ones bidding that — not the ones losing deals to it.
Who we’re looking for
Right fit
- Twilio Flex / Twilio Voice partners
- Genesys partners (Cloud, PureConnect, Engage)
- Five9 / NICE / AWS Connect / 8x8 / RingCentral partners
- Voice AI integrators (Cognigy, Parloa, Replicant builds)
- Telecoms / CCaaS systems integrators with multiple deployments
Not a fit
- Pure CCaaS platforms (we partner, we don’t compete)
- Integrators who’ve built their own voice-payment product
- Single-deployment shops without multi-client referral surface
Become a launch partner
A small group of integrators getting in early. Selection is rolling — we onboard partners as we close them, then the early-access window shuts.
- Win the AI-voice deals — capture clients who need modern voice payments their AI flows can actually use, not a DTMF-only legacy bolt-on.
- Bigger ACVs per deployment — voice payments bundled into your CCaaS scope instead of subbed out to a separate vendor.
- Differentiate your practice — be the integrator who ships voice + AI + payments as one architecture, not three.
- Light integration, no PCI scope — your team still owns the CCaaS build; we slot in alongside and handle compliance + payment plumbing.
- Shape the roadmap — early API access and carrier prioritisation based on your real client backlog.
- Co-marketing on launch — we name you, you name us.
Book a conversation with us to see if we can work together.
First step is a short Collaboration Agreement — mutual, non-exclusive, 14-day notice. Customer introductions and product validation, with a 2-year non-solicit on anyone you introduce. Resale, revenue share, and deployment terms follow separately once we’ve validated the shape.