If you're running an enterprise contact centre on RingCX, RingCentral's dedicated CCaaS product, for an insurance carrier, a debt-recovery operation, a multi-state utility, a travel and events business, or a multi-tenant BPO, you already know customers want to pay on the call. RingCentral sells a secure card payment add-on for RingCX, which keeps the card digits a caller keys in away from the agent.
RingCX sits separately from RingEX, RingCentral's UCaaS product. RingCX targets enterprise contact centre operations, outbound campaigns, predictive dialling, AI-driven agent assist, workforce engagement, omnichannel routing. RingSense AI handles transcription and analytics across the platform. Shuttle is a different kind of product: a payment layer between the call and each merchant's own payment gateway, with payment links on the same integration.
This guide is for merchants taking payments through RingCX, and for solution providers and RingCentral App Gallery partners deploying RingCX for clients. It covers how Shuttle adds PCI-compliant payment capture to RingCX, multi-PSP, RingSense-compatible, and built so payment moments fit into outbound and inbound flows alike. For the broader RingCentral platform (RingEX + RingCX combined), see the RingCentral Payments guide.
When a Separate Payment Layer Helps
RingCX is built for enterprise contact centre operations. RingCentral is not a payment processor, so the payment itself still needs a provider behind it. A separate payment layer earns its place here:
Multi-PSP support. Enterprise contact centres that run several brands or entities, or serve several BPO clients, need each one's payments to go to its own gateway, through one integration.
Voice and links on one layer. When a caller can't key a card in, or the call drops mid-payment, a payment link finishes the transaction through the same integration.
Per-transaction pricing. Payment add-ons priced per seat multiply cost across an enterprise deployment. A per-transaction model fits the underlying economics better.
How Shuttle Adds Payments to RingCX
Shuttle adds PCI-compliant card capture to your RingCX payment flows. When the customer is ready to pay, the card is captured through Twilio Pay and passed to Shuttle's PCI DSS Level 1 environment, and the card data never reaches your RingCX recordings, transcription, or your agents.
The setup is light. It runs on Twilio Pay, so you need to be a Twilio customer, and you build a small integration on your side. Shuttle ships the secure PCI capture, payment links, IVR, and the payment APIs; what it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call wired for RingCX specifically. So the part you build is small: pass the payment amount to Shuttle through its API (the minimum data we need), connect the secure capture into your RingCX call flow over Twilio, and add your own agent screen if your workflow needs one. If that fits, book a call and we will scope your exact setup. There is practical detail in the "What to Expect" section further down.
Secure card capture (voice)
When the agent (or an outbound campaign) is ready to take payment, the card is captured in a secure, PCI DSS Level 1 call via Twilio Pay. The customer enters their card details on their phone keypad, and the digits pass from Twilio Pay to Shuttle's PCI DSS Level 1 environment. Neither the agent nor RingCX recordings receive cardholder data, and RingSense transcription continues around the payment moment. See the Twilio IVR & Agent Assist payment docs for the technical flow.
Payment Links via SMS or email
This is the most turnkey path. Shuttle generates a payment link with the agreed amount, currency, and reference. The agent drops the link into an SMS or email, including mid-call while the customer is still on the line. The customer pays on a hosted, PCI-compliant page, and status posts back to your application. Useful for outbound recovery campaigns where the caller agrees to pay later, or where a follow-up payment plan is agreed, and links work even with gateways that don't support voice capture. See the Payment Links docs.
Agent experience
For voice, the agent triggers the capture and sees the result without ever handling card data. Shuttle does not ship a pre-built agent screen or input UX for RingCX, so you build that minimal piece against Shuttle's APIs: trigger the capture, pass the amount, and show the result in your own agent screen if your workflow needs one. There is more in the "What to Expect" section below.
How a voice payment works
Shuttle connects to RingCX via the Twilio Pay capture, an agent-side UI you build, and webhooks for status reporting back into your CRM, case management, or campaign tools.
Agent workflow
From the RingCX agent desktop, the agent stays on the live call. When the caller is ready to pay, whether on an inbound enquiry or an outbound recovery call, the agent triggers the capture from your interface and confirms the amount. They never see, type, or hear the card number. The card is captured in the secure Twilio Pay call, so nothing reaches the agent's audio or the RingCX recording. The agent sees status updates (entered card, validated, processed, approved or declined) without ever entering PCI scope. If the call drops mid-payment, the agent can send a payment link to finish the transaction asynchronously.
Customer experience
When prompted, the customer enters their card details on their phone keypad during the secure Twilio Pay call, and the digits pass from Twilio Pay to Shuttle's PCI DSS Level 1 environment. They hear confirmation in real time. RingSense AI assist remains active around the payment flow.
Multi-PSP Support
Shuttle is gateway-agnostic. We connect to 30+ PSPs, including Stripe, Adyen, Worldpay Access, Checkout.com, Authorize.Net, Global Payments, FreedomPay, and regional acquirers. Each merchant entity or brand can run on its own gateway, and each payment method can go to its own gateway, useful for enterprise RingCX deployments that span multiple business units, entities or BPO client portfolios.
Switching processors later is configuration, not a re-integration, though saved cards stay with the gateway that stored them. One caveat for voice specifically: a small number of gateways (for example Braintree) don't permit raw card data to be passed to them, so they don't work for voice capture, though they do work for payment links. This matters for RingCX customers who already have established acquirer relationships, who run multi-tenant BPO models, or who serve international markets where one PSP doesn't cover every country.
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 PCI DSS Level 1 certified. Because the card is captured in the secure Twilio Pay call, the model keeps cardholder data out of your RingCX environment entirely:
Card data never reaches the agent's audio, RingCX recordings, or RingSense transcripts.
Card data is captured through Twilio Pay and tokenised with your gateway before any result returns to your systems.
RingCX recordings, RingSense transcripts, and quality monitoring outputs never contain card numbers, which limits your PCI scope. Merchants complete SAQ-A and platforms complete SAQ-D, and a BPO taking payments for its clients is a service provider that completes SAQ-D.
Audit trails, plus transaction and refund data in one format, are available via Shuttle's reporting layer and feed into RingCX-adjacent reporting tools.
For RingCX customers in regulated verticals, financial services, insurance, healthcare, public sector, telco, Shuttle is designed to keep certified scope tight without compromising the AI-driven agent experience. Full compliance documentation, including the AOC scope, is in the security docs.
Voice payments cost $49 per live instance per month, plus from $0.20 per transaction, falling with volume, billed through your Twilio account, with no per-seat fees. See pricing.
For Solution Providers and RingCentral App Gallery Partners
If you're a RingCentral App Gallery partner or SI deploying RingCX for clients, Shuttle is the payment layer you can build into your deployment. We support white-label deployment and multi-PSP routing across your client portfolio (each client keeps its own supported acquirer). Shuttle is a Pay Connector provider on the Twilio Marketplace, and the Twilio Pay capture works on both inbound and outbound RingCX flows without disrupting RingSense AI assist. For partnership conversations, book a discovery call.
Use Cases
Outbound Collections and Recovery
RingCX is widely used for outbound debt-recovery campaigns. Shuttle lets agents take payment plans during the recovery call itself. Multi-PSP routing handles different agency-of-record arrangements across portfolios.
Insurance Premium and Renewal Collection
Insurance carriers using RingCX for premium collection, both inbound enquiries and outbound renewal nudges, can settle the payment moment inside the call. Useful for monthly premium chases and lapsed-policy reactivation.
Multi-Tenant BPO Operations
BPOs running RingCX across multiple end-clients can route payment transactions to each client's own supported acquirer. Shuttle supports per-tenant configuration without per-seat licensing penalties.
Utility and Telco Billing
Utilities and telcos using RingCX for billing enquiries can complete card payments inside the call rather than transferring customers to web portals, faster handle time, higher conversion, narrower PCI scope.
What to Expect
Shuttle is a payment layer you connect to your stack, not a pre-packaged RingCX plugin. Here is the honest detail so there are no surprises on the call:
It runs on Twilio Pay today. Shuttle's voice capture uses Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways, so you need to be a Twilio customer. Shuttle works with Twilio today, and any carrier coming soon.
You build a small integration, not a payment system. Shuttle ships the secure PCI capture, IVR, payment links, and payment APIs. What it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call for RingCX specifically. So you build that minimal glue: pass the amount to Shuttle via its API (the minimum data we need), connect the capture into your RingCX call flow over Twilio, and add your own agent screen if your workflow needs one. It is light.
Point-of-payment capture is what is live. Securely capturing the card at the moment of payment works today. Shuttle staying present across the entire conversation is not available today, and Shuttle does not ship call hand-back after payment out of the box. What happens to the caller after payment is part of the call flow you build in Twilio. Works with Twilio today, and any carrier coming soon.
Payment links are the most turnkey path and need the least build. Many teams start there and add voice capture later.
Frequently Asked Questions
Does Shuttle have a native RingCX integration?
Not today. Shuttle's voice capture runs on Twilio Pay, and you invoke that setup rather than installing a Shuttle app in RingCX. You'll need to be a Twilio customer and to build a small integration on your side (pass the amount to Shuttle's API and wire the secure capture into your call flow over Twilio). Shuttle works with Twilio today, and any carrier coming soon.
Does this require Twilio?
Yes, today. The secure card capture runs via Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways. Shuttle works with Twilio today, and any carrier coming soon.
How is taking payments on RingCX different from RingCentral overall?
RingCX is RingCentral's dedicated enterprise CCaaS, separate from RingEX (UCaaS). The Twilio Pay approach works on both, but RingCX deployments typically need outbound campaign support, multi-tenant routing, and tighter coexistence with RingSense AI than RingEX setups. For RingEX-only deployments, see the RingCentral Payments guide.
Does Shuttle affect RingSense analytics?
No. RingSense AI continues transcribing and analysing throughout the call. Because the card is captured in the secure Twilio Pay call, RingSense transcripts and analytics never contain card numbers, but the conversation context around the payment moment is preserved.
Will Shuttle work with outbound predictive dialling campaigns?
Yes. The Twilio Pay capture and payment links both work on inbound and outbound flows. For outbound recovery campaigns, agents can take payment during the call, with payment links as a fallback for customers who can't enter card details on the phone.
Can we just use payment links instead of voice capture?
Yes. Many teams use links only, sent via SMS or email, including mid-call. Links are the most turnkey part of Shuttle and work with gateways that don't support voice capture.
What is the pricing model?
Voice costs $49 per live instance per month, plus from $0.20 per transaction, falling with volume, billed through your Twilio account, with no per-seat fees. See pricing.
Related Reading
PCI-Compliant Payments for Contact Centres, the platform-by-platform merchant + SI guide
RingCentral Payments, broader RingEX + RingCX coverage
Twilio Pay Connectors, Shuttle's multi-gateway Pay Connector
Voice Payments, comprehensive voice payment capture guide
AI Voice Agent PCI Payments, for AI-led contact centres
Five9 Payments, enterprise CCaaS comparison
Genesys Payments, enterprise CCaaS comparison
Get Started
Shuttle adds enterprise-grade, PCI-compliant payments to a RingCX-based operation via Twilio, with multi-PSP routing and no gateway lock-in. We'll walk you through what's live today and the path for your setup.
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.