LivePerson runs the Conversational Cloud, an enterprise conversational AI and digital-messaging platform. It is messaging-first: web and in-app messaging, SMS, WhatsApp, Apple Messages for Business, RCS and Facebook Messenger sit at the centre, with conversational bots and human agents handling customers across all of them. If you are a merchant running customer conversations on LivePerson, or a system integrator implementing it, payments are a natural extension of those conversations.
LivePerson already orchestrates payments. Through Bring Your Own Payments (BYOP) in Conversation Builder, an Apple Pay integration, and a specialist partnership for PCI-descoped capture, customers can transact inside the conversation. LivePerson is messaging-first today, with its voice and agentic story growing (it is being acquired by SoundHound AI, announced April 2026, to add voice and agentic AI capabilities).
This guide is for merchants and SIs weighing when a single multi-PSP payment layer that spans both messaging and voice fits alongside what LivePerson provides. The goal is not to replace LivePerson's orchestration. It is to show where one payment layer across channels, with gateway breadth and secure in-call capture, adds value, and exactly what that involves with Shuttle today.
LivePerson's Payments Today: What You Get
LivePerson does not process cards itself. It orchestrates payment flows so the customer transacts without leaving the conversation:
Bring Your Own Payments (BYOP) in Conversation Builder lets you connect your existing payment provider into the conversational flow. LivePerson orchestrates the steps; your provider processes the card.
Apple Pay integration supports a fast, native checkout for customers in supported channels.
PCI-descoping partnership (announced August 2024) adds secure, PCI-descoped payment capture inside Conversational Cloud, designed to remove agents from PCI DSS scope.
Enterprise compliance, including PCI-DSS, is part of LivePerson's platform posture.
This is a capable starting point. If your business already routes through one payment provider and your conversations are messaging-only, BYOP plus LivePerson's PCI-descoping partner may cover what you need. The questions below help you decide when a broader layer is worth adding.
When a Multi-PSP Layer Across Channels Helps
A dedicated payment layer like Shuttle fits when you need more than a single provider wired into a single channel:
One layer across messaging and voice. LivePerson is messaging-first, with voice growing. A single payment layer covers messaging links and in-call voice capture so the experience is consistent as your voice channels expand.
30+ payment gateways. Connect 30+ payment gateways including Stripe, Adyen, Worldpay, Checkout.com, Braintree and Square, rather than wiring up one provider per flow.
Bring your own gateway. Keep your existing acquiring relationships and processing rates. Shuttle routes; it does not force a switch.
Per-client and per-tenant routing. Route different brands, regions or business units to different gateways from one integration.
PCI DSS Level 1 as a certified Service Provider, with secure in-call capture for voice conversations.
How Shuttle Adds Payments to LivePerson
Shuttle adds PCI-compliant card capture to your LivePerson payment flows. When the customer is ready to pay, the card is captured inside Shuttle's PCI DSS Level 1 certified environment via Twilio Pay (Shuttle is Twilio's preferred payments partner), and the card data never reaches your LivePerson recordings, transcription, or your agents. Shuttle customers already take payments this way on LivePerson-based operations today.
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 LivePerson 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 LivePerson call flow over Twilio, and add your own agent screen if your workflow needs one. Customers running LivePerson have already built exactly this. 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.
How It Works
Agent and bot workflow
In a messaging conversation, a bot or human agent shares a Shuttle payment link at the right step. The agent never sees or handles card numbers. In a voice conversation, the agent initiates a secure capture session via Twilio Pay and stays on the line while the customer keys in card details; the digits are captured inside Shuttle's certified environment, so the agent and any call recording never receive them. Confirmation lands back in the agent workspace so the conversation can continue.
Customer experience
The customer pays where they already are. In messaging, they tap a link, see a branded checkout, and pay with card or Apple Pay without downloading an app or leaving the thread. On voice, they enter card details on their phone keypad in the secure call while the agent waits, with no need to read numbers aloud. The result is one consistent, secure flow across channels.
Multi-PSP Support
Connect 30+ payment gateways including Stripe, Adyen, Worldpay, Checkout.com, Braintree and Square.
Bring your own gateway and keep existing acquiring and pricing.
Route per client, per brand, per region or per business unit from a single integration.
Add or switch gateways without rebuilding your conversational flows; gateway choice is configuration, not re-integration. One caveat for voice specifically: a few 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.
Pricing is $0.20 per successful transaction for voice with no setup, monthly or per-seat fees. Payment links are currently free.
PCI Compliance
Shuttle is a PCI DSS Level 1 certified Service Provider. Card data is captured inside Shuttle's compliant environment via the secure Twilio Pay call and never reaches LivePerson, your agents or your infrastructure. That keeps card data out of your PCI scope: instead of the broader SAQ-D obligations that apply when sensitive data touches your systems, most merchants using Shuttle qualify for the lighter SAQ-A. The effect is similar in spirit to what LivePerson's descoping partner offers for messaging, extended across messaging and voice through one layer. Full compliance documentation is in the security docs.
Beyond Messaging: Voice Capture
LivePerson's voice and agentic story is growing. As you add voice channels, payments need to follow. Shuttle provides secure in-call capture via Twilio Pay: the customer types card details on the phone keypad during a live call, the digits are captured inside Shuttle's certified environment before they reach the agent or the recording, and the transaction is processed in the background. The agent stays in conversation throughout. One payment layer covers both your messaging conversations today and your voice conversations as they scale, with no second integration to maintain.
For Solution Providers and LivePerson Implementation Partners
If you implement LivePerson for clients, Shuttle is the certified payment capture you add through the LivePerson Developer Center (developers.liveperson.com) and Twilio. The same surface where BYOP, Apple Pay and custom integrations are built, using the platform's APIs and Functions, is where you wire Shuttle in:
Use Functions and API integrations to trigger Shuttle payment sessions from bot or agent workflows.
Deliver hosted payment links into messaging conversations, and secure capture sessions into voice flows.
Keep card data outside the LivePerson environment so your client's PCI scope stays minimal.
Offer per-client gateway routing so one implementation pattern serves multiple brands.
You build the agent-side and bot-side interface against Shuttle's APIs once and reuse it across clients, and a native LivePerson integration is available as a paid project. This lets you deliver payment capture as a repeatable part of your LivePerson builds, across messaging and voice, without becoming a payments company yourself.
Use Cases
Conversational Commerce and Order Taking
Let customers complete a purchase inside a messaging or voice conversation, with the gateway and methods you already use.
Bill-Pay and Account Payments
Collect outstanding balances and recurring bills in-conversation, with secure links or in-call capture and instant confirmation.
Bookings and Deposits
Take deposits and booking payments at the moment of intent, before the conversation ends, across any channel.
Customer Support Payments
Resolve payment-related support issues in the same thread or call, from upgrades to renewals, without handing customers off.
What to Expect
Shuttle is a payment layer you connect to your stack, not a pre-packaged LivePerson 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 the certified payment connector, so you need to be a Twilio customer. A carrier-agnostic version that removes the Twilio requirement is on our roadmap for later in 2026.
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 LivePerson 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 LivePerson call flow over Twilio, and add your own agent screen if your workflow needs one. It is light, and customers running LivePerson have already done it.
A native LivePerson integration is available as a paid project. If you would rather not build the integration yourself, we can build one for your deployment with you.
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, or handing the caller back to the same agent afterwards, is part of the fuller call control coming with the carrier-agnostic version.
Payment links are the most turnkey path and need the least build. Many teams start there and add voice capture later.
FAQ
Does Shuttle have a native LivePerson integration? Not today. Shuttle's voice capture runs on Twilio Pay (we're Twilio's preferred payments partner), and you invoke that setup rather than installing a Shuttle app in LivePerson. You'll need to be a Twilio customer and to build the agent-side and bot-side interface for your workflow against Shuttle's APIs. We can build a native LivePerson integration as a paid project if you'd rather not build it yourself, and a carrier-agnostic version is on our roadmap.
Does this require Twilio? Yes, today, for voice. The secure card capture runs via Twilio Pay, where Shuttle is the certified payment connector. Payment links do not require Twilio. The carrier-agnostic version is on our roadmap for later in 2026.
Does LivePerson take payments? Yes, by orchestration. LivePerson does not process cards itself, but through BYOP in Conversation Builder, an Apple Pay integration and its PCI-descoping partnership, customers can pay inside the conversation while your provider processes the card.
What does Shuttle add? One payment layer across messaging and voice, 30+ gateways with bring-your-own-gateway, per-client routing, PCI DSS Level 1 capture, and secure in-call capture for voice via Twilio.
Which gateways does Shuttle support? 40+ including Stripe, Adyen, Worldpay, Checkout.com, Braintree and Square. You can keep your existing acquiring relationship and route per client or brand. Switching gateways later is configuration, not re-integration.
Can it handle outbound conversations? Yes. Payment links and in-call capture work in outbound messaging and outbound voice, such as collections, renewals and proactive billing.
How much does it cost? $0.20 per successful transaction for voice, with no setup, monthly or per-seat fees. Payment links are currently free.
Related Reading
Contact centre payments: the hub for secure payment capture across contact centre channels.
Embedded payments for CCaaS: how payment capture embeds into conversational and contact centre platforms.
AI voice agent PCI payments: taking PCI-compliant payments on AI voice agents.
Zendesk payments: payment capture for another messaging-first support platform.
Payments for CCaaS implementation partners: how SIs add a payment layer to contact centre builds.
Take Payments Across Messaging and Voice in LivePerson
Add one PCI Level 1 payment layer to your LivePerson conversations via Twilio, with 30+ gateways, per-client routing and secure in-call capture across messaging and voice. We'll walk you through what's live today and the path for your setup.
See Payment Services | Book a discovery call