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 embedded payment layer that fills that gap.
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. A compliant in-house build typically runs $500k+ in initial engineering and $200k+ per year to maintain, before you have processed a single payment. 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 Adds Payment Capture to UJET
Shuttle sits alongside UJET and takes ownership of the payment moment, so card data never enters your contact-centre systems.
The agent stays on the UJET call or chat and triggers a Shuttle payment request without leaving the conversation.
The customer enters their card via secure DTMF (phone keypad) or a hosted payment link sent over SMS or chat.
Card data is captured directly by Shuttle's PCI Level 1 environment, never touching UJET's voice stream, transcripts, or recordings.
Shuttle routes the transaction to your chosen gateway from 40+ supported gateways.
The agent sees only a success or failure result, keeping them and your UJET deployment out of cardholder data scope.
How It Works
Agent workflow
The agent keeps the customer on the UJET voice call or chat throughout. When it is time to pay, the agent starts a Shuttle payment session. On voice, the customer is prompted to key in their card using their phone keypad, and the tones are captured by Shuttle and never spoken aloud or recorded. On chat, the agent sends a payment link inline. The agent watches a masked status update and confirms the result without ever seeing or hearing the full card number.
Customer experience
The customer never leaves the conversation or gets transferred to a separate IVR they do not trust. On voice they type their card digits on the keypad while still talking to the agent. On chat or SMS they tap a hosted link, pay on a secure page, and return to the thread. The experience feels native to UJET while the sensitive step happens entirely inside Shuttle.
Multi-PSP Support
Shuttle is gateway-neutral, which matters for contact centres that serve multiple brands or clients.
Connects to 40+ payment gateways, including Stripe, Adyen, Worldpay, Checkout.com, Braintree, and Square.
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 inside UJET, with no rip-and-replace.
One integration covers voice DTMF and payment links across every brand you run.
PCI Compliance
Shuttle is a PCI DSS Level 1 certified Service Provider, the highest level of validation. Because card data is captured inside Shuttle and never enters UJET, your contact centre stays out of scope.
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). 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. The customer pays on a secure Shuttle-hosted page, the result flows back to the agent, and the card data stays out of UJET. This covers asynchronous and self-service moments where DTMF 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 embedded payment layer you add to UJET implementations through the Technology Partner track. You deliver the payment-capture integration as part of the build, keep your client's contact centre out of cardholder data scope, and let the client retain their existing gateway via Shuttle's 40+ gateway routing. With no setup, monthly, or per-seat fees and $0.20 per transaction 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 DTMF on live calls and links for self-service follow-up.
Order Taking and E-commerce Support
Capture card-not-present orders mid-conversation when a customer calls or chats to place or amend an order, 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 an embedded layer like Shuttle.
How do I take PCI-compliant payments in UJET? Add Shuttle as the payment layer. Card data is captured via secure DTMF or hosted payment links inside Shuttle's PCI Level 1 environment, never entering UJET's voice stream, recordings, or chat transcripts, which keeps your contact centre out of scope.
**Which payment gateways does Shuttle support?** Shuttle connects to 40+ gateways, including Stripe, Adyen, Worldpay, Checkout.com, Braintree, and Square. You keep your existing acquirer and route each brand or client to its own gateway.
**Can't I just build payment capture into UJET myself?** You can, but a compliant PCI Level 1 build typically costs $500k+ to engineer and $200k+ per year to maintain. Shuttle gives you certified capture for $0.20 per transaction with no setup, monthly, or per-seat fees.
Can Shuttle handle outbound payment collection in UJET? Yes. For outbound campaigns, agents can trigger DTMF 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 without bringing your contact centre into PCI scope.
See Payment Services | Book a discovery call