PayPal (via Braintree) doesn't natively connect to Twilio for voice payments. If you want to process card payments through PayPal's infrastructure 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 PayPal/Braintree (and 15+ other gateways) to Twilio's <Pay> verb, so you can accept PCI-compliant card payments during any voice interaction. Setup takes minutes.
This guide walks through how the integration works, how to set it up, and what to watch for.
Why PayPal + Twilio Don't Connect Directly
PayPal is the world's largest digital payments platform, and through its Braintree subsidiary handles card processing for millions of businesses. Its APIs are designed for web and mobile checkout — buttons, hosted fields, and drop-in UIs.
Twilio is built for voice and messaging. Its <Pay> verb captures card details during phone calls via DTMF keypad input, with tones suppressed so agents never hear them.
The problem: Twilio's <Pay> needs a Pay Connector to route captured card data to a payment gateway. PayPal/Braintree isn't one of Twilio's built-in connectors.
This is where Shuttle comes in. As Twilio's official payment partner, Shuttle provides a Pay Connector that accepts card data from Twilio's <Pay> verb and routes it to PayPal/Braintree for processing. One integration connects the two platforms.
How It Works
`` Caller → Twilio (DTMF capture) → Shuttle (Pay Connector) → PayPal/Braintree (processing) → Result ``
Caller reaches payment step. Your Twilio call flow — IVR, Studio, or custom TwiML — triggers the
<Pay>verb.Card details captured via DTMF. The caller enters their card number, expiry, and CVV on the keypad. Tones are suppressed from the agent audio and call recordings.
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 PayPal/Braintree. The connector creates a transaction through your PayPal/Braintree merchant account and handles the response.
Result returned to your call flow. Your webhook receives the transaction ID, last four digits, card brand, and transaction status. The call continues.
The entire flow happens in seconds. The caller stays on the line.
Step-by-Step Setup
Prerequisites
A Twilio account with voice capability
A PayPal Business or Braintree account with API credentials
A Shuttle account (free to create — you pay per transaction)
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 PayPal/Braintree Credentials to Shuttle
Log into the Shuttle dashboard. Navigate to Payment Profiles and create a new profile:
Gateway: PayPal / Braintree
Merchant ID: Your PayPal/Braintree merchant ID
API credentials: Your public key and private key (Braintree) or API credentials (PayPal)
Currency: Set your default (USD, GBP, EUR, etc.)
Environment: Live or Sandbox
Save the profile. Shuttle now has a live connection to your PayPal/Braintree account.
Step 3: Configure Your Twilio Call Flow
Add the <Pay> verb to your TwiML or Twilio Studio flow:
``xml <Response> <Say>Please enter your card number followed by the pound key.</Say> <Pay paymentConnector="shuttle-pay-connector" chargeAmount="35.00" currency="USD" description="Order payment" action="/payment-complete"> </Pay> </Response> ``
Step 4: Handle the Payment Result
Twilio sends a POST to your action URL with the payment result:
``json { "Result": "success", "PaymentCardNumber": "xxxx-xxxx-xxxx-2345", "PaymentCardType": "visa", "PaymentConfirmationCode": "BT-TXN-123...", "ProfileId": "your-shuttle-profile-id" } ``
Step 5: Test
Use Braintree's sandbox environment and Twilio's test credentials to verify the flow end-to-end. Braintree sandbox test card: 4111 1111 1111 1111 (Visa).
What You Can Do With PayPal + Twilio
Charge Immediately
Standard auth-and-capture. The caller pays, Braintree processes, done.
Authorise Now, Capture Later
Place a hold on the card during the call. Capture the payment later — useful for orders, reservations, or variable-amount transactions.
Tokenise for Future Use
Capture card details once over the phone. Shuttle tokenises the card via Braintree's Vault and returns a reusable token. Use it for future payments across any channel — web, mobile, voice, or payment links. The card data is never stored in your systems.
Marketplace Payments
If you use Braintree Marketplace (sub-merchants), Shuttle can route voice payments to the correct sub-merchant. Each merchant's transactions are processed through their own account.
Multi-PSP: Beyond PayPal
One of the key advantages of using Shuttle rather than a PayPal-only connector is flexibility. Your Twilio integration stays the same even if you:
Add a second gateway — route US transactions to Braintree and UK transactions to Worldpay
**Serve enterprise customers** who mandate a specific PSP — some require Adyen, Stripe, or Checkout.com
Need failover — if Braintree is down, automatically route to a backup gateway
Expand internationally where a local acquirer gives better rates
You configure routing rules in Shuttle's dashboard. Your Twilio call flow doesn't change.
PCI Compliance
The PayPal + Twilio integration via Shuttle keeps you completely out of PCI scope:
Layer | PCI handled by |
|---|---|
DTMF capture & suppression | Twilio |
Card data processing | Shuttle (PCI DSS Level 1) |
Payment processing | PayPal/Braintree (PCI DSS Level 1) |
Your systems | No card data — SAQ-A |
Card data flows from Twilio → Shuttle → PayPal/Braintree. Your application only receives redacted data. You qualify for SAQ-A — the lightest PCI self-assessment.
For the full picture, see Twilio PCI Compliance: Payments Without Handling Card Data.
FAQ
Can I connect PayPal to Twilio without Shuttle? Twilio doesn't have a built-in PayPal/Braintree Pay Connector. You'd need to build a custom connector using Twilio's Generic Pay Connector framework — handling PCI compliance yourself. Shuttle provides a pre-built, PCI-certified connector.
Does this work with Twilio Studio? Yes. Twilio Studio supports the <Pay> widget. Configure it with shuttle-pay-connector as the connector.
Is this PayPal or Braintree? Both. PayPal owns Braintree, and Shuttle integrates with the Braintree/PayPal payment processing APIs. If you have a Braintree merchant account or a PayPal Business account with card processing enabled, Shuttle can connect it to Twilio.
What does it cost? Shuttle charges $0.20 per transaction. PayPal/Braintree's standard processing fees apply on top (2.59% + 49¢ or your negotiated rate). No Shuttle setup fees or monthly minimums.
Can I accept PayPal wallet payments over the phone? Twilio's <Pay> verb captures card details via DTMF keypad. PayPal wallet (balance/bank) payments require the PayPal checkout flow, which is web-based. Over the phone, you'd capture the caller's card details instead.
Can I switch from PayPal to another gateway later? Yes. Change the gateway in your Shuttle payment profile. Your Twilio call flow stays exactly the same — no code changes needed.
Related Reading
Twilio Pay Connectors: How to Connect Any 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 at SAQ-A
How to Connect Stripe to Twilio for Voice Payments — step-by-step Stripe + Twilio setup
How to Connect Adyen to Twilio for Voice Payments — step-by-step Adyen + Twilio setup
How to Connect Worldpay to Twilio for Voice Payments — step-by-step Worldpay + Twilio setup
Twilio Pay — Connect Any Payment Gateway to Twilio — all supported gateways, pricing, and setup
*Connect PayPal to Twilio in minutes with Shuttle's Pay Connector — PCI DSS Level 1, $0.20/transaction, no setup fees. Install on Twilio or book a discovery call.*