USAePay doesn't natively connect to Twilio for voice payments. If you want to process USAePay 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 USAePay (and 30+ other gateways) to Twilio's <Pay> verb, so you can accept PCI-compliant card payments during any voice interaction.
This guide walks through how the integration works, how to set it up, and what to watch for.
Why USAePay + Twilio Don't Connect Directly
USAePay is a long-established US payment gateway, popular with ISVs, ISOs, and small-to-mid-sized US merchants. Its strength is processor flexibility: the gateway sits on top of the major US processing networks (TSYS, Fiserv/First Data, Global Payments, Chase Paymentech, Heartland, Elavon, and others), so merchants keep their existing processor and merchant account relationship rather than being forced onto a single acquirer.
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. USAePay isn't one of Twilio's built-in connectors, so there's no native path between the two.
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 USAePay's API for processing. One integration connects the two platforms, and your existing USAePay account (and the processor behind it) stays exactly as it is.
How It Works
`` Caller → Twilio (DTMF capture) → Shuttle (Pay Connector) → USAePay (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 USAePay. The connector creates a USAePay transaction request, processes it through your USAePay account and underlying processor, and handles the response.
Result returned to your call flow. Your webhook receives the USAePay reference, last four digits, card brand, and transaction status. The call continues.
The entire flow happens in seconds. 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 USAePay account with API credentials (API key + PIN, created under Settings then API Keys in the merchant console)
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 USAePay Credentials to Shuttle
Log into the Shuttle dashboard. Navigate to Payment Profiles and create a new profile:
Gateway: USAePay
API key: Your USAePay API key
PIN: The PIN set on that key (USAePay recommends a PIN, and most functionality requires one)
Currency: USD
Environment: Live or Sandbox
Save the profile. Shuttle now has a live connection to your USAePay 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 hash key.</Say> <Pay paymentConnector="shuttle-pay-connector" chargeAmount="49.99" currency="USD" description="Invoice payment" action="/payment-complete"> </Pay> </Response> ``
Key parameters:
paymentConnector: set toshuttle-pay-connectorchargeAmount: the amount to chargecurrency: ISO currency codeaction: 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:
``json { "Result": "success", "PaymentCardNumber": "xxxx-xxxx-xxxx-1234", "PaymentCardType": "visa", "PaymentConfirmationCode": "USAEPAY-REF-123...", "ProfileId": "your-shuttle-profile-id" } ``
Use the PaymentConfirmationCode to look up the transaction in the USAePay merchant console if needed. Update your order, confirm to the caller, and continue the flow.
Step 5: Test
USAePay provides a dedicated development sandbox at sandbox.usaepay.com. Point your Shuttle payment profile at the sandbox environment, use the test card numbers from USAePay's sandbox guide, and verify the flow end-to-end with Twilio before going live.
What You Can Do With USAePay + Twilio
Charge Immediately
Standard auth-and-capture. The caller pays, USAePay processes through your existing merchant account, done.
Authorise Now, Capture Later
Place a hold on the card during the call and capture the payment later. Useful for service bookings, deposits, or jobs where the final amount is confirmed after the call.
Tokenise for Future Use
Capture card details once over the phone. Shuttle tokenises the card via USAePay (which supports card reference tokens and stored payment methods in its customer database) 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.
Recurring and Repeat Billing
For service businesses, medical billing, and collections teams, the tokenise-once pattern is the big win. Take the first payment on a call, then run instalments or repeat charges against the stored token without asking the customer to read their card out again.
Multi-PSP: Beyond USAePay
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: route one business line through USAePay and another through a different provider
**Serve enterprise customers** who mandate a specific PSP (Stripe, Worldpay, Checkout.com, etc.)
Need failover: if one gateway has an outage, automatically route to a backup
Route by amount or region when different acquirers give better authorisation rates
You configure routing rules in Shuttle's dashboard. Your Twilio call flow doesn't change. The <Pay> verb always points to shuttle-pay-connector, and Shuttle handles which gateway processes the transaction.
This is particularly useful for ISVs and BPOs that serve multiple merchants. Each merchant can use their own USAePay account (or any other gateway) through the same Twilio integration.
PCI Compliance
The USAePay + 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 | USAePay |
Your systems | No card data (SAQ-A) |
Card data flows from Twilio to Shuttle to USAePay. Your application only receives redacted data (last 4 digits, card brand, transaction reference). You qualify for SAQ-A, the lightest PCI self-assessment.
For the full picture on PCI compliance with Twilio, see Twilio PCI Compliance: Payments Without Handling Card Data.
FAQ
Can I connect USAePay to Twilio without Shuttle? Twilio doesn't have a built-in USAePay 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, PCI-certified connector that handles this.
Does this work with Twilio Studio? Yes. Twilio Studio supports the <Pay> widget. Configure it with shuttle-pay-connector as the connector and the payment flow works within your Studio flow.
Do I need to change my processor or merchant account? No. USAePay works across the major US processors, and Shuttle simply connects to your existing USAePay account. Your processor relationship, rates, and settlement stay as they are.
What about USAePay's sandbox? Fully supported. Point your Shuttle payment profile at sandbox.usaepay.com credentials and test the full flow with Twilio before going live.
What does it cost? Shuttle charges $0.20 per successful transaction. USAePay's standard gateway fees and your processing rates apply on top. No Shuttle setup fees or monthly minimums.
Can I switch from USAePay 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.
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 & IVR Payments: step-by-step Adyen + Twilio setup
USAePay via Shuttle: supported features and channels
Twilio Pay: Connect Any Payment Gateway to Twilio: all supported gateways, pricing, and setup
*Connect USAePay 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.*