UJET runs your contact centre. With its smartphone-first architecture, native cloud voice and IVR, web chat, SMS, email, social, an in-app mobile SDK, and an AI layer of virtual agents and agent assist, it powers the conversations your customers have with your brand across channels.
What UJET does not do is capture card payments. There is no built-in payments feature and no advertised payments product. UJET is designed to keep sensitive data in your connected CRM, which means the moment a customer needs to pay, the card capture has to come from somewhere else.
This guide is for two readers: merchants who use UJET to run their contact centre and want to take payments inside those conversations, and System Integrators (SIs) who implement UJET for clients and need a compliant way to add payment capture. Shuttle is the payment layer that fills that gap, and this guide sets out plainly how it works with a UJET operation today.
The Payment Challenge in UJET
When a customer reads a card number aloud on a UJET voice call, or types it into a chat, that data flows through the voice stream, the chat transcript, call recordings, and agent screens. Every system it touches falls into PCI DSS scope. For a contact centre, that is a wide and expensive footprint.
UJET has no native payment-capture product, so there is no built-in mechanism to keep that card data out of the conversation stack. Without a dedicated payment layer, the card details enter your recordings and your agents' field of view, dragging UJET, your CRM, and your agents into the highest tier of PCI scope.
Building PCI Level 1 capture yourself is not realistic for most teams. The faster route is to add a certified payment layer that handles capture outside the UJET stack.
See PCI DSS and PCI scope for the definitions that drive this.
How Shuttle Works With UJET Today
Be clear about the model first, because it determines whether Shuttle is a fit:
There is no native UJET integration today. Shuttle's voice payment capture runs on Twilio Pay. You invoke that Twilio-based setup; you do not install a Shuttle app inside UJET.
You need to be a Twilio customer to use voice capture with Shuttle.
You need technical resource to implement it. Shuttle ships ready-made interfaces for payment links and the PCI-compliant capture, IVR and APIs for voice, but you build the agent-side interface for your own UJET workflow, because every contact centre is different. There is no pre-built Shuttle widget for UJET.
Shuttle works with Twilio today, and any carrier coming soon.
If you have the technical resource and are (or can be) a Twilio customer, the payment moment fits together like this, with card data never entering your contact-centre systems:
The agent triggers a Shuttle payment request from the interface you build, while the customer stays in the UJET conversation.
For voice, the card is captured in a secure, PCI DSS Level 1 call via Twilio Pay: the customer keys their card in on the keypad, and the digits go to your gateway through Shuttle's certified environment. For follow-up, Shuttle sends a hosted payment link over SMS or email.
Card data goes to the gateway through Shuttle's PCI Level 1 environment, never touching UJET's voice stream, transcripts, or recordings.
Shuttle routes the transaction to your chosen gateway from 30+ supported gateways.
The agent sees only a success or failure result, keeping card data away from them and your UJET deployment, which limits your PCI scope.
How It Works
Agent workflow
When it is time to pay, the agent starts a Shuttle payment session from the interface you build against Shuttle's APIs. On voice, the card is captured in a PCI DSS Level 1 call via Twilio Pay while the customer keys in their digits; those digits go to the gateway through Shuttle's certified environment and never reach the agent or the recording. For follow-up, the agent sends a payment link by SMS or email. The agent watches a masked status update and confirms the result without ever seeing or hearing the full card number.
Customer experience
On voice, the caller is taken into the secure Twilio Pay capture, keys their card in privately, and the agent confirms the result once payment clears. By SMS or email they tap a hosted link and pay on a secure page. One honest caveat: secure capture at the point of payment is what's live now via Twilio Pay. Shuttle handles the payment segment of the call, not the whole conversation. Returning the caller to the same agent and call after payment works today: you program the return route in your Twilio flow and pass a conversation ID, so the agent resumes with context. Shuttle works with Twilio today, and any carrier coming soon.
Multi-PSP Support
Shuttle is gateway-neutral, which matters for contact centres that serve multiple brands or clients.
Connects to 30+ payment gateways for voice, including Stripe, Adyen, Worldpay, and Checkout.com.
Per-client routing lets a BPO or multi-brand operation send each client's transactions to that client's own gateway and merchant account.
Keep your existing acquirer and pricing while adding capture to your UJET operation, with no rip-and-replace. Switching gateways later is configuration, not a re-integration, though saved cards stay with the gateway that stored them.
One integration covers voice capture and payment links across every brand you run. One voice caveat: a few gateways (for example Braintree and Square) 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.
PCI Compliance
Shuttle is a PCI DSS Level 1 certified Service Provider, the highest level of validation. Because card data is captured through Twilio Pay, goes to your gateway through Shuttle, and never enters UJET, your contact centre's PCI scope is limited.
In practice this can move your assessment from SAQ-D (the broad, demanding questionnaire that applies when cardholder data flows through your systems) toward SAQ-A (the lightest questionnaire, for merchants who fully outsource capture to a compliant provider; platforms and other service providers complete SAQ-D). That is a meaningful reduction in PCI scope, audit effort, and risk.
Beyond Voice: Payment Links
Not every payment happens on a live voice call. Shuttle also generates hosted payment links your agents can send over UJET's SMS, web chat, email, or in-app mobile SDK channels, including mid-call to a customer still on the line. The customer pays on a secure Shuttle-hosted page, the result flows back to the agent, and the card data stays out of UJET. Links are the most turnkey part of Shuttle and work even with gateways that don't support voice capture, which covers asynchronous and self-service moments where voice capture is not the right fit, and pairs naturally with UJET's mobile-first design.
For Solution Providers and UJET Implementation Partners
If you implement UJET for clients, payment capture is a recurring gap you can close. UJET runs a Partner Program with Technology Partner, Channel, Delivery, and Strategic Alliance tracks. It does not operate its own public app marketplace, so integrations are delivered as technology-partner builds, and UJET also lists in host-CRM marketplaces such as Salesforce AppExchange and the Zendesk Marketplace.
Shuttle fits as the payment layer you add to UJET implementations, on Twilio today. You deliver the payment-capture integration as part of the build, limit your client's contact centre PCI scope, and let the client keep their existing gateway, as long as it is one of Shuttle's 30+ gateway options for voice. With voice at $49 per live instance per month, plus from $0.20 per transaction, falling with volume, billed through your Twilio account (see pricing), it is straightforward to scope into a UJET delivery and to roll out across multiple client deployments.
Use Cases
Bill-Pay and Collections
Take one-off bill payments and structured payment plans on UJET voice and SMS, with secure capture on live calls via Twilio Pay and links for self-service follow-up.
Order Taking and E-commerce Support
Capture card-not-present orders mid-conversation when a customer calls to place or amend an order, or by link when they chat, with no card data hitting the transcript.
Account Payments
Let customers settle account balances, top-ups, or subscription charges during a support interaction without a transfer to a separate payment line.
Bookings and Deposits
Collect deposits and balance payments for bookings and reservations over voice or chat, routed to the right merchant account per brand.
FAQ
Does UJET process payments natively? No. UJET has no built-in payments feature or advertised payments product. It is designed to keep sensitive data in your connected CRM, so card capture must come from a separate payment layer like Shuttle.
Does Shuttle have a native UJET integration? Not today. Shuttle's voice capture runs on Twilio Pay, and you invoke that setup rather than installing a Shuttle app in UJET. You need to be a Twilio customer and to build the agent-side interface for your workflow. Shuttle works with Twilio today, and any carrier coming soon.
Does this require Twilio? Yes, today, for voice. The secure card capture runs via Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways, so voice capture needs you to be a Twilio customer. Payment links do not require Twilio. Shuttle works with Twilio today, and any carrier coming soon.
How do I take PCI-compliant payments in UJET? Add Shuttle as the payment layer. Card data is captured in a secure Twilio Pay call, or on a hosted payment page, and goes to your gateway through Shuttle's PCI Level 1 environment, never entering UJET's voice stream, recordings, or chat transcripts, which limits your contact centre's PCI scope.
Which payment gateways does Shuttle support? Shuttle connects to 30+ gateways for voice, including Stripe, Adyen, Worldpay and Checkout.com. You keep your existing acquirer and route each brand or client to its own gateway, and switching gateways is configuration, not a re-integration, though saved cards stay with the gateway that stored them. A few gateways (for example Braintree and Square) don't work for voice capture but do work for links.
Can't I just build payment capture into UJET myself? You can, but a compliant PCI Level 1 build is expensive to engineer and to maintain. Shuttle gives you certified capture for $49 per live instance per month, plus from $0.20 per transaction, falling with volume, billed through your Twilio account (see pricing).
Can Shuttle handle outbound payment collection in UJET? Yes. For outbound campaigns, agents can trigger the secure Twilio Pay capture on a live outbound call or send a payment link over SMS, which suits collections, renewals, and proactive billing.
Related Reading
Contact centre payments: the hub guide covering payment capture across every major CCaaS platform.
Embedded payments for CCaaS: how the embedded payment layer works inside contact-centre software.
AI voice agent PCI payments: taking PCI-compliant payments through virtual and AI voice agents.
Payment collection for BPOs: multi-client, multi-gateway collection for outsourcers and multi-brand operations.
Payments for CCaaS implementation partners: how SIs add a payment layer to contact-centre builds.
Take Payments in Your UJET Contact Centre
Add PCI-compliant payment capture to your UJET voice and chat conversations while limiting your contact centre's PCI scope.
See Payment Services | Book a discovery call