Global Payments doesn't natively connect to Twilio for voice payments. If you want to process Global Payments 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 Global Payments (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 Global Payments + Twilio Don't Connect Directly
Global Payments is a major worldwide payment technology company, processing billions of transactions across merchant acquiring, issuing, and integrated payments. Its APIs handle payment processing, tokenisation, and reporting for businesses of all sizes.
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. Global Payments 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 Global Payments for processing. One integration connects the two platforms.
How It Works
`` Caller → Twilio (DTMF capture) → Shuttle (Pay Connector) → Global Payments (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 Global Payments. The connector creates a Global Payments transaction, processes the payment through your merchant account, and handles the response.
Result returned to your call flow. Your webhook receives the transaction reference, 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 Global Payments merchant 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 Global Payments Credentials to Shuttle
Log into the Shuttle dashboard. Navigate to Payment Profiles and create a new profile:
Gateway: Global Payments
Merchant ID: Your Global Payments merchant ID
Account / API credentials: Your Global Payments shared secret or API key
Currency: Set your default (GBP, USD, EUR, etc.)
Environment: Live or Test
Save the profile. Shuttle now has a live connection to your Global Payments 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="89.99" currency="GBP" description="Invoice 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-7890", "PaymentCardType": "visa", "PaymentConfirmationCode": "GP-TXN-REF-123...", "ProfileId": "your-shuttle-profile-id" } ``
Step 5: Test
Use Global Payments' test environment and Twilio's test credentials to verify the flow end-to-end before going live.
What You Can Do With Global Payments + Twilio
Charge Immediately
Standard auth-and-capture. The caller pays, Global Payments processes, done. Ideal for utility payments, insurance premiums, council tax, and account top-ups.
Authorise Now, Capture Later
Place a hold on the card during the call. Capture the payment later — useful for bookings, service deposits, or variable-amount transactions.
Tokenise for Future Use
Capture card details once over the phone. Shuttle tokenises the card via Global Payments and returns a reusable token. Use it for future payments across any channel — web, mobile, voice, or payment links.
Enterprise & Government
Global Payments is widely used across enterprise, healthcare, and government sectors. If your contact centre or BPO serves clients in these sectors, Shuttle connects their Global Payments merchant accounts to Twilio without those clients needing to change their payment infrastructure.
Multi-PSP: Beyond Global Payments
Your Twilio integration stays the same even if you:
Add a second gateway — route transactions to Global Payments for some clients and Stripe or Adyen for others
**Serve enterprise customers** who mandate a specific PSP
Need failover — if Global Payments is down, automatically route to a backup gateway
Expand internationally where a different acquirer gives better rates
You configure routing rules in Shuttle's dashboard. Your Twilio call flow doesn't change.
PCI Compliance
The Global Payments + 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 | Global Payments (PCI DSS Level 1) |
Your systems | No card data — SAQ-A |
Card data flows from Twilio → Shuttle → Global Payments. 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 Global Payments to Twilio without Shuttle? Twilio doesn't have a built-in Global Payments 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 and the payment flow works within your Studio flow.
Which Global Payments APIs does Shuttle support? Shuttle integrates with Global Payments' ecommerce APIs. The exact configuration depends on your merchant account setup — the Shuttle dashboard walks you through the credentials needed.
What does it cost? Shuttle charges $0.20 per transaction. Global Payments' standard processing fees apply on top (your negotiated rate). No Shuttle setup fees or monthly minimums.
Can I use Global Payments for both voice and online payments? Yes. Your Global Payments merchant account works the same across channels. Voice payment tokens created via Shuttle can be used for future online or recurring payments.
Can I switch from Global Payments 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 Global Payments 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.*