Xendit doesn't natively connect to Twilio for voice payments. If you want to process Xendit card transactions during a phone call (via IVR, agent-assisted, or AI voice agent), you need a Twilio Pay Connector that bridges the two platforms.
Shuttle's Pay Connector does exactly this. It connects Xendit (and 30+ other gateways) to Twilio's <Pay> verb, so you can accept PCI-compliant card payments during any voice interaction.
This matters for two audiences in particular: businesses serving Indonesian and Philippine customers who want to take card payments over the phone, and Philippine BPOs collecting payments on behalf of their clients. This guide walks through how the integration works, how to set it up, and what to watch for.
Why Xendit + Twilio Don't Connect Directly
Xendit is one of Southeast Asia's leading payment gateways, built for online commerce across Indonesia, the Philippines, and neighbouring markets. Its APIs handle cards (Visa, Mastercard, American Express, JCB), local e-wallets such as OVO, DANA, and GCash, virtual accounts, and QR payments, with processing in IDR, PHP, and other regional currencies.
Twilio is built for voice and messaging. Its <Pay> verb captures card details during phone calls via DTMF keypad input, so the digits never reach the agent or the call recording.
The problem: Twilio's <Pay> needs a Pay Connector to route captured card data to a payment gateway. Xendit isn't one of Twilio's built-in connectors, so there is no native way to send a card captured on a Twilio call to your Xendit account.
This is where Shuttle comes in. Shuttle provides a Pay Connector that accepts card data from Twilio's <Pay> verb and routes it to Xendit's API for processing. One integration connects the two platforms.
One note on scope: voice payments are card payments. E-wallets like GCash and OVO require the customer's app, so they can't be captured on a keypad. For those methods, send a payment link by SMS during the call instead. Shuttle supports both from the same account.
How It Works
Caller → Twilio (DTMF capture) → Shuttle (Pay Connector) → Xendit (processing) → Result
Caller reaches payment step. Your Twilio call flow (IVR or custom TwiML) triggers the
<Pay>verb.Card details captured via DTMF. The caller enters their card number, expiry, and CVV on the keypad. The digits never reach the agent or the call recording.
Shuttle receives card data. The data passes from Twilio's PCI-compliant environment directly to Shuttle's connector. It never touches your servers.
Shuttle charges the card via Xendit. The connector creates a Xendit payment request, processes the transaction through your Xendit account, and handles the response.
Result returned to your call flow. Your webhook receives the Xendit reference, last four digits, card brand, and transaction status. The call continues.
The caller stays on the line. No redirects, no "please visit our website."
Step-by-Step Setup
Prerequisites
A Twilio account with voice capability
A Xendit account with API credentials (a secret API key generated from the Xendit dashboard)
A Shuttle account (free to create; see pricing)
Step 1: Install Shuttle's Pay Connector
Go to the Twilio Marketplace and install the Shuttle Pay Connector. This adds Shuttle as an available connector in your Twilio account's Pay configuration.
Step 2: Add Xendit Credentials to Shuttle
Log into the Shuttle dashboard, add Xendit, and enter the values from your Xendit dashboard:
Secret API Key
Public API Key
Webhook Verification Token
Country: select your country
Select Save. Shuttle shows Connected to Xendit when the connection succeeds.
Step 3: Configure Your Twilio Call Flow
Add the <Pay> verb to your TwiML:
<Response>
<Say>Please enter your card number followed by the hash key.</Say>
<Pay paymentConnector="shuttle-pay-connector"
chargeAmount="1499.00"
currency="PHP"
description="Invoice payment"
action="/payment-complete">
</Pay>
</Response>Key parameters:
paymentConnector: set toshuttle-pay-connectorchargeAmount: the amount to chargecurrency: ISO currency code (PHP, IDR, etc.)action: your webhook endpoint for the payment result
Step 4: Handle the Payment Result
Twilio sends a POST to your action URL with the payment result:
{
"Result": "success",
"PaymentCardNumber": "xxxx-xxxx-xxxx-1234",
"PaymentCardType": "visa",
"PaymentConfirmationCode": "XENDIT-REF-123...",
"ProfileId": "your-shuttle-profile-id"
}Use the PaymentConfirmationCode to look up the transaction in Xendit if needed. Update your order, confirm to the caller, and continue the flow.
What You Can Do With Xendit + Twilio
Charge Immediately
Standard auth-and-capture. The caller pays, Xendit processes, done. Ideal for phone orders, bill payments, and bookings in IDR or PHP.
Tokenise for Future Use
Capture card details once over the phone. Shuttle tokenises the card via Xendit and returns a reusable token, so you can charge future payments across any channel: web, mobile, voice, or payment links. The card data is never stored in your systems.
Multi-Client Collection for Philippine BPOs
The Philippines is a global BPO hub, and payment collection is a natural fit for contact centres already handling customer calls. With Shuttle, a BPO can collect payments on behalf of multiple clients through a single Twilio integration. Each client's transactions route to their own Xendit account (or their own compatible gateway), keeping funds and reporting cleanly separated.
Mix Voice and Payment Links
Not every caller wants to key in a card. Send a payment link by SMS mid-call for customers who prefer to pay by GCash, OVO, or another local method Xendit supports, while keeping card-on-call as the fast path.
Multi-PSP: Beyond Xendit
One of the key advantages of using Shuttle rather than a single-gateway connector is flexibility. Your Twilio integration stays the same even if you:
Add a second gateway: serve your Indonesian and Philippine merchants with Xendit, and other markets with a local acquirer
Serve enterprise customers who mandate a specific PSP (Stripe, Adyen, Worldpay, etc.)
Want a backup gateway: if one gateway has an outage, 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
Expand to new markets, with each merchant or entity there on its own gateway
You choose which connected provider handles each payment type in Shuttle’s dashboard. Your Twilio call flow doesn't change. The <Pay> verb always points to shuttle-pay-connector.
This is particularly important for BPOs and platforms serving multiple merchants: each merchant can use their own Xendit account (or their own compatible gateway) through the same Twilio integration.
PCI Compliance
The Xendit + Twilio integration via Shuttle limits your PCI scope:
Layer | PCI handled by |
|---|---|
DTMF capture | Twilio |
Card data processing | Shuttle (PCI DSS Level 1 Service Provider) |
Payment processing | Xendit |
Your systems | Merchants: SAQ-A. Platforms: SAQ-D. |
Card data flows from Twilio to Shuttle to Xendit. Your application only receives redacted data (last 4 digits, card brand, gateway reference). Merchants complete SAQ-A, the lightest PCI self-assessment; platforms complete SAQ-D. Everyone taking card payments has to be PCI compliant, and your acquirer confirms which form applies to you.
For the full picture on PCI compliance with Twilio, see Twilio PCI Compliance: Payments Without Handling Card Data.
FAQ
Can I connect Xendit to Twilio without Shuttle? Twilio doesn't have a built-in Xendit Pay Connector. You'd need to build a custom connector using Twilio's Generic Pay Connector framework, which means handling PCI compliance for card data processing yourself. Shuttle provides a pre-built connector that is PCI DSS Level 1 certified.
Can callers pay with GCash or OVO over the phone? Not via DTMF: e-wallet payments happen in the customer's app, not on a keypad. The standard pattern is to send a payment link by SMS during the call, which opens Xendit's supported local methods.
Does this work for Philippine BPOs collecting for multiple clients? Yes. Shuttle profiles let each client's payments route to their own Xendit account (or their own compatible gateway), all through one Twilio integration. See payment collection for BPOs.
What does it cost? Shuttle charges $49 per live instance per month, plus from $0.20 per transaction, falling with volume, billed through your Twilio account. Xendit's standard processing fees apply on top.
Can I switch from Xendit to another gateway later? Yes. Change the gateway in your Shuttle payment profile. Your Twilio call flow stays exactly the same, with no code changes needed. Saved cards stay with the gateway that stored them, so repeat payments on stored cards will not move to the new gateway.
Related Reading
Twilio Pay Connectors: How to Connect Any Compatible Payment Gateway: the complete guide to Twilio Pay Connectors and multi-PSP routing
Twilio PCI Compliance: Payments Without Handling Card Data: how to keep your PCI scope limited
How to Connect Stripe to Twilio for Voice Payments: step-by-step Stripe + Twilio setup
How to Connect PayU to Twilio for Voice Payments: connecting the other major emerging-markets gateway
Payment Collection for BPOs: multi-client payment collection for outsourcers
Xendit: Xendit on Shuttle, supported features and channels
Twilio Pay: Connect Any Compatible Payment Gateway to Twilio: all supported gateways, pricing, and setup
Connect Xendit to Twilio with Shuttle's Pay Connector: PCI DSS Level 1, $49 per live instance per month, plus from $0.20 per transaction, falling with volume, billed through your Twilio account. Install on Twilio or book a discovery call.