Gupshup is one of the world's leading conversational messaging platforms. It powers WhatsApp-first commerce and customer engagement across India and emerging markets, serving brands in BFSI, retail, healthcare, and utilities. As a Meta Business Solution Provider (BSP), Gupshup gives businesses a direct route to WhatsApp Business API, as well as reach across SMS, Instagram, RCS, and voice channels. Its ISV Partner Program extends that reach through solution providers and system integrators building on top of the platform.
What sets Gupshup apart from most conversational platforms is that it has a genuine native payment capability. It is not a messaging tool that simply redirects users to a payment page. Gupshup has built UPI-native bill pay, WhatsApp Pay integration via Meta-approved processors, and in-chat conversational commerce directly into its messaging stack. For India-first deployments, that is a significant head start.
This guide covers what Gupshup's native payments give you and, importantly, when you need to extend beyond them. Specifically: when you are handling international card payments, managing multiple clients each with their own acquirer, running voice-channel collections alongside messaging, or operating in markets where UPI does not reach.
If you are building or operating a platform that combines Gupshup's conversational reach with card payments, multi-currency support, or voice capture, this guide explains where the two approaches complement each other.
Gupshup's Native Payments: What You Get
Gupshup's native payment capabilities are real and well-integrated into its messaging channels. They are purpose-built for India's payment infrastructure:
1-Click Bill Pay: UPI payment links sent directly inside WhatsApp, SMS, Instagram, and RCS messages. Customers tap once and pay via UPI without leaving the conversation. Designed for bill-pay, renewals, and collections workflows in India.
WhatsApp Pay via Razorpay and PayU: In-chat WhatsApp Pay flows powered by Razorpay and PayU, which are the only Meta-approved processors for India. Card payments can also be handled through these processors within the WhatsApp interface.
GSPay: UPI-based payments for feature phone users via USSD and SMS flows, extending reach to customers without smartphones or reliable data connectivity.
Conversational commerce: In-chat product catalogues, cart flows, and payment collection for retail and D2C brands operating on WhatsApp.
For India-first messaging commerce, this is a genuinely strong native stack. If your business is collecting payments from Indian consumers via WhatsApp or SMS, Gupshup's native payments may cover the majority of your volume.
When You Need a Multi-PSP Card Layer
Gupshup's native payments are optimised for UPI and WhatsApp Pay in India. There are specific scenarios where a dedicated multi-PSP layer alongside Gupshup is the practical answer:
International card payments and multi-currency: UPI is India-specific. If you are collecting from customers in Europe, the US, Southeast Asia, or the Middle East, you need international card rails with multi-currency support. Gupshup's native stack does not provide this.
Bring-your-own-gateway and negotiated acquirer rates: Larger platforms and enterprises often have existing acquirer relationships and negotiated interchange rates. A multi-PSP layer lets you route to those preferred gateways rather than being tied to a fixed processor.
Per-client and per-tenant gateway routing: Agencies and platforms managing payments on behalf of multiple clients need to route each transaction to the correct merchant account. UPI flows do not support this kind of multi-tenant configuration.
Voice-channel card capture: Some collections and customer-service workflows require card capture over a phone call, with PCI scope handled by the payment layer rather than your contact centre. Gupshup's native payments do not cover voice card capture.
One integration across markets and channels: Platforms operating in India and internationally benefit from a single payment integration that handles both, rather than separate stacks per region.
How Shuttle Works with Gupshup Today
Shuttle has no native integration with Gupshup. Because Gupshup is messaging-led, payment links are the most relevant path: Shuttle generates hosted, PCI-compliant payment links that the Gupshup flow can deliver over SMS, email, or any messaging channel, including mid-conversation. For voice card capture, you invoke Shuttle's Twilio-based setup, where Shuttle is Twilio's preferred payments partner, and you must be a Twilio customer for that path.
The agent or messaging flow runs inside Gupshup: conversation, fulfilment, intent capture.
At the payment moment, your application triggers Shuttle via API or generates a hosted payment link.
Shuttle captures card details in isolation, via a hosted checkout page (links) or, on voice channels, via a secure PCI DSS Level 1 capture handed off via Twilio Pay. Card data does not enter Gupshup's environment or yours.
Shuttle routes the transaction to whichever of your 30+ gateways applies, based on currency, region, or client configuration.
The result returns to your system for fulfilment, confirmation, or CRM update.
The Gupshup-side conversational experience is unchanged. You build the orchestration and agent-side wiring yourself; Shuttle provides ready-made interfaces for payment links, plus the capture, IVR, and APIs. For a proof of concept, you can build against Shuttle's sandbox gateway and demo app.
Honest caveat: for voice, secure capture at the point of payment is live now via Twilio Pay. Shuttle being present for the entire call is not yet turnkey. Returning the caller to the same flow after payment works today: you program the return route in your Twilio flow and pass a conversation ID, so the agent picks the call back up with full context. A carrier-agnostic version, which removes the Twilio requirement, is landing later in 2026. A native Gupshup integration is possible only as a paid project.
Multi-PSP Support
Shuttle connects to 30+ payment gateways through a single integration. That list includes Stripe, Adyen, Worldpay, Checkout.com, Square, and Mollie, among others. Key capabilities:
Per-tenant gateway configuration: Each client or merchant on your platform can be mapped to their own acquirer relationship.
Routing by currency and region: Transactions are routed to the gateway best suited to the currency, card scheme, or geography of the payment.
Automatic failover: If a gateway is unavailable, Shuttle routes to a backup without manual intervention.
Switching is configuration, not re-integration. A few gateways (for example, Braintree) do not work for voice capture but do work for payment links.
This is what makes international and multi-client operations practical beyond UPI. You are not limited to the processors Gupshup has partnerships with, and you are not rebuilding integrations per market.
PCI Compliance
Shuttle is a PCI DSS Level 1 Service Provider, the highest tier of PCI certification. For card payments, cardholder data flows through Shuttle's certified environment, keeping your compliance scope on a lighter SAQ-A footing rather than SAQ-D.
UPI payments do not carry card PANs. A UPI transaction is an account-to-account transfer initiated by a VPA (Virtual Payment Address), so PCI DSS does not apply to that flow. If Gupshup's native UPI payments are your primary collection method for Indian customers, PCI scope is not a concern for those transactions.
Where PCI scope does matter is card payments and voice capture. If your platform handles international credit or debit cards, or captures card details over a phone call, you need a certified environment for that data. That is Shuttle's role in the stack.
Beyond Messaging: Payment Links and Voice
Gupshup's native UPI flows are channel-specific: they work inside WhatsApp, SMS, Instagram, and RCS. Shuttle adds two additional capture channels that Gupshup's native payments do not cover.
Hosted card payment links: Payment links are the turnkey path, and they work even with gateways that do not support voice capture. Shuttle generates hosted payment pages that can be sent via any channel, over SMS or email, including mid-conversation. The link opens a PCI-compliant checkout outside your environment. This is useful for email, SMS, or messaging flows where the recipient is outside India or using an international card. Payment links are currently free (a new pricing model is coming).
Secure voice card capture: For contact centres and IVR deployments, the call is handed to a secure PCI DSS Level 1 capture via Twilio Pay (you must be a Twilio customer for this path). The caller enters card digits on the keypad, and they never reach the agent, the recording, or your systems. This is the standard approach for PCI-compliant card capture over voice.
Both channels work alongside Gupshup's conversational flows rather than replacing them.
Use Cases
Cross-Border and International Card Payments
A utility or BFSI brand using Gupshup for India-based collections wants to extend payment collection to international customers or diaspora payers. UPI does not reach them. Shuttle provides international card rails across 30+ gateways with multi-currency support, using the same API and reporting layer as the India stack.
Multi-Client Platforms and Agencies
A CPaaS reseller or messaging integrator manages Gupshup deployments for multiple enterprise clients, each with their own acquirer. Shuttle's per-tenant gateway routing maps each client to their own merchant account, so collections stay correctly attributed without a separate payment integration per client.
Bill-Pay Beyond UPI
A collections or utilities platform handles UPI bill pay via Gupshup's 1-Click Bill Pay for Indian consumers. For customers paying by card, or customers in markets without UPI, Shuttle generates a hosted payment link that captures card details in a PCI-certified environment and routes to the appropriate gateway.
Voice and Card-Not-Present
A financial services or debt collections operation runs Gupshup-powered outbound messaging for payment reminders, then handles inbound calls for customers who want to pay by card. Shuttle's secure Twilio Pay capture handles the call-centre leg, keeping card digits out of the agent environment, while Gupshup continues to own the messaging channel.
FAQ
Does Gupshup process payments natively?
Yes. Gupshup has native payment capabilities including 1-Click Bill Pay (UPI payment links across WhatsApp, SMS, Instagram, and RCS), WhatsApp Pay via Razorpay and PayU (Meta's approved India processors), GSPay for feature phones, and in-chat conversational commerce. These are well-integrated into its messaging stack and cover Indian UPI-based payment flows.
Does Shuttle have a native Gupshup integration?
No. Shuttle has no native Gupshup integration. Payment links are the most relevant path for a messaging-led platform, and your application generates them or triggers Shuttle via API. For voice capture you invoke Shuttle's Twilio-based setup. A native Gupshup integration is possible only as a paid project.
Does this require Twilio?
For payment links, no. For the voice card capture path, yes: the secure capture runs via Twilio Pay, where Shuttle is Twilio's preferred payments partner, so you must be a Twilio customer. A carrier-agnostic version that removes the Twilio requirement is landing later in 2026.
Why use Shuttle if Gupshup has native payments?
Gupshup's native payments are optimised for India and UPI. If you need international card payments, multi-currency support, per-client gateway routing, payment links across markets, or voice card capture, those are not part of Gupshup's native stack. Shuttle extends the stack to cover those channels without replacing the UPI flows Gupshup handles well.
Which gateways does Shuttle support?
Shuttle connects to 30+ payment gateways, including Stripe, Adyen, Worldpay, Checkout.com, Square, and Mollie. Transactions can be routed per currency, region, or client configuration. See the full list on the payment providers page. A few gateways (for example, Braintree) do not work for voice but do work for payment links.
Does Shuttle support international card payments and multi-currency?
Yes. Shuttle routes card transactions to whichever gateway is configured for the relevant currency and region. You can run a single integration that handles Indian UPI flows via Gupshup's native stack and international card payments via Shuttle, without separate payment systems per market.
Related Reading
The Payment Layer for AI Agents: how a dedicated payment layer sits between conversational AI and card capture.
Voice Payments: guide to PCI-compliant card capture across voice channels.
AI Voice Agent PCI Payments: secure capture, PCI scope reduction, and voice agent architecture.
Payment Orchestration: how multi-PSP routing, failover, and per-tenant configuration work in practice.
Yellow.ai Payments: a similar native-vs-multi-PSP comparison for another conversational AI platform strong in emerging markets.
Add Multi-PSP Payments Alongside Gupshup
Shuttle is a PCI DSS Level 1 Service Provider offering card capture across 30+ gateways, via payment links and a secure Twilio Pay handoff for voice. Pricing is $0.20 per successful transaction with no setup, monthly, or per-seat fees (see pricing). Read the Twilio setup docs, the payment links docs, and the security overview.
See Voice Checkout | Book a discovery call