QuickBooks Payments doesn't take in-call keypad card capture through Shuttle, but callers can still pay during a Twilio call with a secure payment link. If you invoice from QuickBooks and want to take a payment during a phone call (a deposit, an overdue invoice, a phone order), you need something that bridges the two platforms.
Shuttle sends the secure payment link by SMS or email during or after the call, and your QuickBooks Payments account processes the payment, so your books stay in QuickBooks. If in-call keypad capture is a hard requirement, Shuttle's Pay Connector works with 30+ voice-capable gateways.
This guide walks through how the integration works, how to set it up, and what to watch for.
Why QuickBooks Payments + Twilio Don't Connect Directly
QuickBooks Payments is Intuit's payment processing service, built around QuickBooks Online. It's invoicing-led: a customer receives a QuickBooks invoice, pays it online, and the payment is matched to the invoice with the deposit and fees recorded in your books. That tight reconciliation loop is why it's so popular with US small businesses and service firms.
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. QuickBooks Payments isn't one of Twilio's built-in connectors, so there's no out-of-the-box way to charge a card over the phone and have it land in your QuickBooks Payments account.
Shuttle doesn't change that for keypad capture: QuickBooks Payments is not one of the gateways Shuttle supports for in-call card capture. What Shuttle adds is the payment-link path: the caller gets a secure link while still on the line, and QuickBooks Payments processes the payment.
How It Works
Caller on Twilio call → Agent/IVR triggers Shuttle → SMS/email payment link → QuickBooks Payments (processing) → Result webhook
Caller reaches payment step. Your agent, IVR or AI agent triggers Shuttle via API. Typical trigger: a customer calls to pay a deposit or settle an overdue QuickBooks invoice.
Shuttle sends a payment link. The caller receives it by SMS or email while still on the line.
Customer pays on a secure hosted page. They enter their card details on their own device. Card data never passes through the call or your servers.
QuickBooks Payments processes the payment. The transaction runs through your QuickBooks Payments merchant account.
Result returned in real time. Your webhook receives the transaction reference and status. The call continues, and you can record the payment against the customer's invoice in QuickBooks Online.
The caller can stay on the line while they pay, and the agent sees the result before the call ends.
Step-by-Step Setup
Prerequisites
A Twilio account with voice (and SMS if you want in-call link delivery)
A QuickBooks Payments account. API access runs through Intuit's developer platform: apps authenticate with OAuth 2.0 credentials from an Intuit developer app, using the QuickBooks Payments scope
A Shuttle account (free to create; see pricing)
Step 1: Connect QuickBooks Payments to Shuttle
Log into the Shuttle dashboard. Navigate to Payment Profiles and create a new profile:
Gateway: QuickBooks Payments
Credentials: authorise Shuttle against your QuickBooks Payments account via Intuit's OAuth flow
Currency: USD (QuickBooks Payments serves US merchants)
Environment: Live or Sandbox
Save the profile. Shuttle now has a live connection to your QuickBooks Payments account.
Step 2: Configure your payment link
Set the currency, branding and description for the payment link.
Step 3: Trigger the link and handle the result
Your agent-side system, IVR or AI voice agent triggers the link via Shuttle's API mid-call. Shuttle then sends a webhook with the transaction reference and status.
Use the transaction reference to record the payment against the invoice in QuickBooks Online. Because the charge runs through your QuickBooks Payments account, the deposit and processing fees flow into QuickBooks the same way as your online invoice payments, so reconciliation stays in one place.
Step 4: Test
Intuit provides a sandbox environment for QuickBooks Payments through its developer platform. Use sandbox credentials in your Shuttle payment profile and verify the link flow end to end before going live.
What You Can Do With QuickBooks Payments + Twilio
Collect Overdue Invoices by Phone
A customer with an unpaid QuickBooks invoice calls in (or your team calls out), the amount is confirmed, and a secure payment link goes out by SMS or email while the caller is still on the line. No chasing, no "the cheque is in the post."
Take Deposits and Phone Orders
Service firms that quote by phone (contractors, repair shops, professional services) can take a deposit at the moment of commitment instead of sending an invoice and waiting.
Keep Reconciliation in QuickBooks
Because payments taken on calls settle through your QuickBooks Payments merchant account rather than a separate phone-payments provider, you avoid running a second merchant account that needs its own reconciliation workflow.
Multi-PSP: Beyond QuickBooks Payments
One of the key advantages of using Shuttle is flexibility. Your integration stays the same even if you:
Add a second gateway: keep QuickBooks Payments for invoice-linked payments and add a voice-capable gateway for in-call keypad capture
Serve enterprise customers who mandate a specific PSP (Stripe, Worldpay, Checkout.com, 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 beyond the US, where QuickBooks Payments doesn't process, by putting the merchants or entities there on a local gateway
You choose which connected provider handles each payment type in Shuttle’s dashboard. Your call flow doesn't change: it triggers Shuttle the same way, and Shuttle sends the payment to the provider you configured.
This is particularly important for BPOs and firms that serve multiple clients. Each client can use their own QuickBooks Payments account (or another supported gateway) through the same integration.
PCI Compliance
The payment-link path via Shuttle limits your PCI scope:
Layer | PCI handled by |
|---|---|
Call and link delivery | Twilio (no card data in the call) |
Payment link and hosted page | Shuttle (PCI DSS Level 1 Service Provider) |
Payment processing | QuickBooks Payments (Intuit) |
Your systems | Merchants: SAQ-A. Platforms: SAQ-D. |
The customer enters card details on a secure hosted page, and QuickBooks Payments processes the payment. Your application only receives redacted data (transaction reference and status). 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 QuickBooks Payments to Twilio without Shuttle? Twilio doesn't have a built-in QuickBooks Payments 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.
Do phone payments show up in QuickBooks? Payments processed this way settle through your QuickBooks Payments merchant account, so deposits and fees flow into QuickBooks like your other QuickBooks Payments transactions. Use the transaction reference from the webhook to record the payment against the right invoice.
Can Shuttle capture card details over the phone into QuickBooks Payments? No. QuickBooks Payments does not take in-call keypad capture through Shuttle. The QuickBooks Payments path is a payment link, which your IVR or AI agent can send by SMS or email during the call, so a caller can still pay an invoice with no agent involved.
Is there a test environment? Yes. Intuit provides a sandbox for QuickBooks Payments via its developer platform. Use sandbox credentials in Shuttle and test the full flow before going live.
What does it cost? Links Checkout is $49 per live instance per month, with transactions from $0.20; see pricing. QuickBooks Payments' standard processing fees apply on top.
Can I switch from QuickBooks Payments to another gateway later? Yes. Change the gateway in your Shuttle payment profile. Your call flow stays 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 Adyen to Twilio for Voice & IVR Payments: step-by-step Adyen + Twilio setup
QuickBooks Invoice Payments: How to Get Paid Faster: speeding up invoice collection in QuickBooks
QuickBooks Payment Links: Send a Pay-Now Link From Your Books: payment links for QuickBooks users
Twilio Pay: Connect Any Compatible Payment Gateway to Twilio: all supported gateways, pricing, and setup
Take payments into QuickBooks Payments on Twilio calls with Shuttle payment links: PCI DSS Level 1, $49 per live instance per month, with transactions from $0.20. Book a discovery call.