Taking Card Payments on RingCentral
RingCentral is one of the largest UCaaS and CCaaS providers in the market. RingEX handles unified communications. RingCX is their contact centre product: AI-powered, omnichannel, with workforce engagement and analytics built in.
RingCentral also sells a secure card payment add-on for RingCX, RingEX and RingCentral Contact Centre, which keeps the card digits a caller keys in away from the agent.
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. That matters when your clients each need their own gateway, or when you want voice and links to run through one layer.
This matters for businesses running RingCentral in industries where phone payments are a daily operation: insurance, utilities, debt collection, travel, and professional services.
When a Separate Payment Layer Helps
RingCentral has invested heavily in AI: RingSense for conversation intelligence, AI-powered agent assist, automated summarisation. RingCX is a capable CCaaS platform. Here is where a separate payment layer helps:
AI features create additional exposure. RingSense transcribes and analyses calls. If a customer reads a card number aloud, that data is transcribed, stored, and potentially surfaced in analytics dashboards. The AI features that make RingCentral attractive also amplify the PCI risk of handling card data on the platform.
A payment API. RingCentral's API is built for call management, messaging, and video. Taking the payment itself, with each merchant on its own gateway, needs a payment API alongside it.
Multi-PSP support. Businesses running several brands, or BPOs serving several 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, a payment link sent mid-call finishes the payment through the same integration.
How Shuttle Adds Payments to RingCentral
Shuttle adds PCI-compliant card capture to your RingCentral calls. When the customer is ready to pay, they enter their card on their phone keypad, the digits are captured through Twilio Pay and passed to Shuttle's PCI DSS Level 1 environment, and the card data never reaches your RingCentral recordings, RingSense transcription and analytics, 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 RingCentral 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 RingCentral 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 it is time to pay, 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. They never reach your RingCentral recordings, RingSense transcription and analytics, or your agents. See the Twilio IVR & Agent Assist payment docs for the technical flow.
Payment Links
This is the most turnkey path. Shuttle generates payment links and sends them via SMS or email, including mid-call to a customer who is still on the line. The customer taps the link, enters card details on a secure hosted page, and confirmation is returned in real time. Shuttle provides the link interfaces out of the box, 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 RingCentral, 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
The call proceeds on RingCentral as normal. Standard call handling, queries, account management, issue resolution.
Payment is triggered from your agent interface when the customer is ready to pay.
Card captured securely. The card is captured in a PCI DSS Level 1 call via Twilio Pay. The customer enters their card on the keypad, and the digits pass from Twilio Pay to Shuttle's PCI DSS Level 1 environment.
Transaction is processed. Shuttle routes to the configured PSP, any of 30+ supported gateways. Provider selection can be configured by merchant and payment type.
Result returned to your interface and your systems via webhook. A tokenised reference is available for CRM logging.
No card data in RingCentral. The card digits never touch your RingCentral recordings, RingSense analytics, or your agent workstations.
Multi-PSP Support
Businesses running RingCentral often operate across multiple business units, each with their own PSP relationships. Shuttle supports 30+ PSPs for voice and allows flexible routing:
By merchant: different clients or business units route to different gateways
By payment method: cards through one gateway and ACH through another
Manual failover: if the primary gateway is unavailable, you can move the affected payment types to another connected gateway. There is no automatic failover, and saved cards stay with the gateway that stored them, so repeat payments on stored cards will not run through the second one
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 the raw card data to be passed to them, so they don't work for voice capture, though they do work for payment links. This flexibility is particularly relevant for BPO and outsourced contact centre operations running RingCentral, where different end clients have different PSP requirements.
PCI Compliance
Shuttle is a PCI DSS Level 1 certified Service Provider, the highest level of payment security certification.
Because the card is captured in the secure Twilio Pay call, card data never enters your RingCentral environment, which limits your PCI scope:
Card data never enters your RingCentral environment
Call recordings contain no cardholder data
RingSense transcription and analytics process no card information
Agents never hear, see, or handle card numbers
Your network infrastructure carries no card data
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 Implementation Partners
If your team deploys RingCentral for clients, as a partner or a system integrator, Shuttle is the payment layer you deliver alongside the rest of the implementation. Each client keeps their own merchant account and their own gateway, and your side integrates once, so payments are not rebuilt for every engagement and client money never lands in yours.
Shuttle's voice capture runs on Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways. Shuttle is not a pre-packaged RingCentral plugin, so your team builds a small integration between RingCentral and Shuttle, and voice deployments need a Twilio account. For partnership conversations, book a discovery call.
Use Cases
Insurance Brokers and Underwriters
Insurance businesses running RingCentral handle premium payments, policy renewals, and mid-term adjustments over the phone. Shuttle allows agents to collect payment during the renewal conversation, critical for retention, without creating PCI exposure or breaking the call flow.
Professional Services
Accountancy firms, legal practices, and consultancies using RingCentral for client communications can collect invoice payments during calls. The client confirms the amount, enters their card via keypad, and payment is confirmed before the call ends.
Debt Collection Agencies
Collections teams running RingCentral need to capture payment when the debtor is engaged and willing to pay. Transferring to a separate system or sending a link risks losing the commitment. Shuttle enables immediate, secure payment capture mid-call.
Travel and Events
Travel agencies and event companies processing bookings over the phone can capture payment at the point of commitment. The customer confirms their booking, enters card details via keypad, and receives confirmation, all on the same call.
What to Expect
Shuttle is a payment layer you connect to your stack, not a pre-packaged RingCentral 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 RingCentral 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 RingCentral 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 call 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 RingCentral integration?
Not today. Shuttle's voice capture runs on Twilio Pay, and you invoke that setup rather than installing a Shuttle app in RingCX or RingEX. You'll need to be a Twilio customer and to build a small bridge connecting your workflow to 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.
Will Shuttle work with both RingCX and RingEX?
Yes. The Twilio-based capture works wherever your voice calls are handled, so it applies to both RingCentral's contact centre (RingCX) and unified communications (RingEX) products. You build a small bridge to fit whichever you run.
Does Shuttle affect RingSense analytics?
No, and this is a key benefit. Because the card is captured in the secure Twilio Pay call, no card data enters RingCentral, so RingSense continues to transcribe and analyse calls normally. The only difference is that card data is absent from transcriptions and recordings, which is exactly what PCI compliance requires.
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 complete guide to secure contact centre payments
Twilio Pay Connectors: how Shuttle integrates with Twilio's payment infrastructure
Voice Payments: the definitive guide to taking payments over voice channels
AI Voice Agent PCI Payments: adding payment capture to AI-powered voice agents
Voice Checkout: Shuttle's voice payment product
Retell AI Payments: PCI-compliant payment capture for Retell AI voice agents
Get Started
If you are a merchant taking payments on RingCentral rather than building for clients, talk to us about your deployment, or see how Voice Checkout works.