Braintree, PayPal's full-stack payment gateway, is one of the few PSPs that Twilio supports natively. Twilio launched a first-party Braintree Pay Connector, so you can wire Braintree straight into Twilio's <Pay> verb and take PCI-compliant card payments during phone calls, IVR flows, and agent-assisted conversations.
One thing to know up front: the native connector is the standard in-call keypad (DTMF) path for Braintree. Braintree only accepts raw card data, which is what DTMF capture requires, on merchant accounts specifically configured for it, so Shuttle does not offer Braintree as a standard voice-capture gateway. What Shuttle offers instead is a different path: secure payment links sent by SMS or email mid-call, processed by Braintree's own hosted checkout, plus 30+ voice-capable gateways if in-call capture is a hard requirement.
This guide explains both paths, when the native connector is the right choice, and when the payment-links route (or a different voice gateway) fits better.
Two Ways to Connect Braintree to Twilio
Path 1: Twilio's native Braintree Pay Connector (in-call DTMF)
Twilio ships branded Pay Connectors for a handful of gateways. Its support docs have named Stripe, Braintree, CardConnect, Base Commerce, Chase Paymentech, and Adyen among them, and Braintree also appears in Twilio's Ireland (IE1) and Australia (AU1) regional documentation for <Pay>. You install the Braintree connector in the Twilio Console, add your Braintree credentials, and point <Pay> at it. The caller keys in their card details, the digits never reach the agent or the recording, and the transaction lands in your Braintree account.
Native connectors are single-gateway by design: one connector instance links <Pay> to one gateway account. Through Twilio, <Pay> exposes chargeAmount, currency, description, and tokenType. Anything beyond that (refunds, splitting authorisation and capture, statement descriptors, transaction metadata) is handled directly in the Braintree Control Panel or API, not through Twilio.
Path 2: Shuttle payment links, with Braintree processing
Shuttle's connector, listed on the Twilio Marketplace and also available in Twilio's IE1 and AU1 regions, takes a different route for Braintree merchants. Instead of keypad entry, your IVR, AI voice agent or agent-side system triggers a secure payment link via Shuttle's API, sent to the caller by SMS or email while they are still on the line. The customer pays on Braintree's hosted, tokenised checkout, where PayPal and Venmo can appear alongside card entry. Braintree processes the payment as normal, and your systems never touch card data.
And because Shuttle is multi-gateway, the same integration gives you 30+ voice-capable PSPs (Stripe, Adyen, Worldpay, Cybersource, and more) if you also need true in-call DTMF capture on some calls or for some clients.
Comparison
Twilio's native Braintree connector | Shuttle (links + multi-gateway) | |
|---|---|---|
In-call DTMF capture with Braintree | Yes | No (Braintree does not accept raw card data from third parties) |
Payment links mid-call | No | Yes, by SMS or email, on Braintree's hosted checkout |
PayPal and Venmo as payment options | No (card capture only) | Yes, via Braintree's hosted checkout on the link |
Gateway coverage | Braintree only | 30+ gateways behind one connector |
Multi-PSP gateway selection | No | Yes (by merchant and payment method) |
Multi-merchant management | One Braintree account per connector | Many merchants and gateways behind one integration |
Pricing | Twilio | $49 per live instance per month, with transactions from $0.20 (see pricing) |
When the native connector is the right choice
If you have a single Braintree account, in-call keypad capture is a hard requirement, and you have no plans for other gateways or merchants, Twilio's native Braintree connector is a clean, first-party option. It is fully supported by Twilio and there is no extra layer to configure.
When Shuttle fits better
Choose Shuttle when the payment-link experience suits your callers (it unlocks PayPal and Venmo), or when you need more than one gateway or merchant behind the same call flow: BPOs and platforms serving multiple clients, enterprise customers that mandate a specific PSP, manual failover to a backup gateway (saved cards stay with the gateway that stored them), or in-call DTMF via a voice-capable gateway alongside Braintree links.
How the Shuttle Path Works
Caller on Twilio call → Agent/IVR triggers Shuttle → SMS/email payment link → Braintree hosted checkout → Result webhook
Caller reaches the payment step. Your IVR, AI voice agent or agent-side system triggers Shuttle via API.
Shuttle sends a payment link. The caller receives it by SMS or email while still on the line.
Customer pays on Braintree's hosted page. Card, PayPal, or Venmo. Card data goes straight to Braintree; it never passes through your systems or the call.
Result returned in real time. Your webhook receives the transaction reference and status. The agent sees confirmation and the call continues.
For the full walkthrough of this pattern, see How to Take PayPal / Braintree Payments Alongside Twilio Voice Calls.
Step-by-Step Setup (Shuttle + Braintree Links)
Prerequisites
A Twilio account with voice (and SMS if you want in-call link delivery)
A Braintree account with API credentials (Merchant ID, Public Key, Private Key, all found under Settings, then API in the Braintree Control Panel)
A Shuttle account (see pricing)
Step 1: Connect Braintree to Shuttle
In the Shuttle dashboard, go to Payment Profiles and create a new profile with your Braintree credentials. Braintree issues separate credentials for sandbox and production, so keep two profiles if you want a permanent test path.
Step 2: Configure your payment link template
Set currency, branding, and which payment methods appear (card, PayPal, Venmo via Braintree's hosted checkout).
Step 3: Trigger links from your call flow
Your IVR, AI voice agent or agent-side system can trigger them via Shuttle's API mid-call.
Step 4: Handle the result
Shuttle sends a webhook with the transaction reference and status. Use it to update your order and confirm to the caller before they hang up.
Step 5: Test with Braintree sandbox
Point a test payment profile at your Braintree sandbox credentials and run the flow end-to-end. Braintree's standard test card 4111 1111 1111 1111 (Visa) works in sandbox.
What You Can Do With Braintree + Twilio via Shuttle
Take Payment While the Caller Is on the Line
The link arrives by SMS. The agent stays on the call, sees the payment land in real time, and confirms before hanging up.
Offer PayPal and Venmo, Not Just Card
This is something no DTMF flow can do: Braintree's hosted checkout on the link presents PayPal and Venmo alongside card entry.
Tokenise for Future Use
Braintree's Vault stores the customer's payment method from the link checkout, so repeat payments do not need a new link each time. Card data never enters your systems.
Mix Channels and Gateways
Use Braintree links for some calls and true in-call DTMF through a voice-capable gateway for others, all behind one Shuttle integration. Your call flow decides which one each call uses.
Multi-PSP: Beyond Braintree
The structural difference between the two paths shows up as soon as you need a second gateway. With Shuttle, your Twilio integration stays the same when you:
Add another gateway, for example taking cards through another gateway while Braintree handles PayPal-heavy consumer flows
Serve enterprise customers who mandate a specific PSP
Want a backup gateway: if one is down, 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
Need in-call DTMF capture on some flows, via any of Shuttle's 30+ voice-capable gateways
Gateway settings live in Shuttle's dashboard. This matters most for BPOs and platforms collecting on behalf of many merchants, each with their own gateway account, behind one Twilio integration.
PCI Compliance
Both paths keep card data out of your systems. On the native connector, Twilio's PCI-compliant <Pay> capture passes card data to Braintree. On the Shuttle path, the customer enters card details directly on Braintree's hosted checkout page, so cardholder data goes straight to Braintree:
Layer | PCI handled by |
|---|---|
Call and link delivery | Twilio (no card data in the call) |
Payment links | Shuttle (PCI DSS Level 1 Service Provider) |
Card entry and processing | Braintree (PCI DSS Level 1) |
Your systems | No card data on your systems: SAQ-A for merchants, SAQ-D for platforms |
Your application only ever sees redacted data (last four digits, payment method, transaction reference), which limits your PCI scope. 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, see Twilio PCI Compliance: Payments Without Handling Card Data.
FAQ
Does Twilio have a native Braintree Pay Connector? Yes. Twilio launched a first-party Braintree Pay Connector, and Braintree appears in Twilio's IE1 and AU1 regional <Pay> documentation. It is the only way to do in-call keypad capture with Braintree.
Can Shuttle capture card details over the phone into Braintree? No. Braintree only permits raw card data, which DTMF capture requires, on merchant accounts specifically configured for it. Shuttle's standard Braintree path uses payment links on Braintree's own hosted checkout instead.
Why use Shuttle instead of the native Braintree connector? Payment links that support PayPal and Venmo, multi-gateway coverage from one integration, gateway selection by merchant and payment method, and multi-merchant management for BPOs and platforms. If you only need single-account keypad capture, the native connector may be all you need.
Can I refund a voice payment through Twilio? No. Twilio's <Pay> has no refund API. Refunds are issued in the Braintree Control Panel or via Braintree's API, or through Shuttle's dashboard and APIs if you are on the Shuttle path.
Does this work with Braintree's sandbox? Yes. Braintree issues separate sandbox credentials; add them as a test payment profile in Shuttle and verify the full flow before going live.
What does it cost? On the Shuttle path, Links Checkout costs $49 per live instance per month, with transactions from $0.20; see pricing for volume rates. Braintree's standard processing fees apply on either path, and Twilio's <Pay> usage fees apply on the native path.
Related Reading
How to Take PayPal / Braintree Payments Alongside Twilio Voice Calls: the full payment-links walkthrough for PayPal and Braintree
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
Braintree: Braintree on Shuttle, channels, features, and coverage
Twilio Pay: Connect Any Compatible Payment Gateway to Twilio: all supported gateways, pricing, and setup
Take Braintree payments on Twilio calls with Shuttle payment links: PayPal and Venmo included, PCI DSS Level 1, $49 per live instance per month, with transactions from $0.20. Install on Twilio or book a discovery call.