How to Connect Worldpay to Twilio for Voice & IVR Payments

Worldpay doesn't natively connect to Twilio for voice payments. If you want to process Worldpay 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 Worldpay (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 Worldpay + Twilio Don't Connect Directly

Worldpay (now part of Global Payments) is one of the world's largest payment processors, handling billions of transactions across ecommerce, in-store, and recurring billing. Its APIs are built for traditional payment processing: authorisation, settlement, and reporting.

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. Worldpay isn't one of Twilio's built-in connectors: there's no native integration between the two.

This is where Shuttle comes in. Shuttle provides a Pay Connector that accepts card data from Twilio's <Pay> verb and routes it to Worldpay's API for processing. One integration connects the two platforms.

How It Works

Caller → Twilio (DTMF capture) → Shuttle (Pay Connector) → Worldpay (processing) → Result

Caller reaches payment step. Your Twilio call flow (IVR or custom TwiML) triggers the <Pay> verb.
Card details captured via DTMF. The caller enters their card number, expiry, and CVV on the keypad. The digits never reach the agent or the call recording.
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 Worldpay. The connector creates a Worldpay authorisation request, processes the transaction, and handles the response.
Result returned to your call flow. Your webhook receives the Worldpay transaction ID, last four digits, card brand, and transaction status. The call continues.

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 Worldpay Access account with API credentials
A Shuttle account (free to create; see pricing)

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 Worldpay Credentials to Shuttle

Log into the Shuttle dashboard. On your integrations list, choose Add, pick Worldpay Access, and enter the connection details:

Processor: Worldpay Access
Username and password: the Worldpay Access API credentials Worldpay support issues
Entity and merchant name: also supplied by Worldpay support
Enable 3DS and Require address (AVS): set these to match your Worldpay account

Select Save. Shuttle tests the connection and shows Connected to Worldpay when it succeeds. It then gives you a webhook URL: send it to Worldpay support to set up on your Worldpay Access account, so asynchronous payment updates reach Shuttle.

Step 3: Configure Your Twilio Call Flow

Add the <Pay> verb to your TwiML:

<Response>
  <Say>Please enter your card number followed by the hash key.</Say>
  <Pay paymentConnector="shuttle-pay-connector"
       chargeAmount="75.00"
       currency="GBP"
       description="Account payment"
       action="/payment-complete">
  </Pay>
</Response>

Key parameters:

paymentConnector: set to shuttle-pay-connector
chargeAmount: the amount to charge
currency: ISO currency code
action: 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:

{
  "Result": "success",
  "PaymentCardNumber": "xxxx-xxxx-xxxx-5678",
  "PaymentCardType": "mastercard",
  "PaymentConfirmationCode": "WORLDPAY-ORDER-123...",
  "ProfileId": "your-shuttle-profile-id"
}

Use the PaymentConfirmationCode to look up the transaction in Worldpay if needed.

Step 5: Test

Use Worldpay's test environment and Twilio's test credentials to verify the flow end-to-end before going live. Worldpay test card numbers: 4444 3333 2222 1111 (Visa), 5555 5555 5555 4444 (Mastercard).

What You Can Do With Worldpay + Twilio

Charge Immediately

Standard auth-and-capture. The caller pays, Worldpay processes, done. Ideal for utility bills, insurance premiums, and account top-ups.

Authorise Now, Capture Later

Place a hold on the card during the call. Capture the payment later: useful for bookings, deposits, or transactions where the final amount may change.

Tokenise for Future Use

Capture card details once over the phone. Shuttle tokenises the card via Worldpay 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.

Enterprise Multi-Merchant

Many enterprises mandate Worldpay as their payment processor. If you're a platform or BPO serving enterprise clients, Shuttle lets each client's transactions route to their own Worldpay merchant account, all through a single Twilio integration.

Multi-PSP: Beyond Worldpay

One of the key advantages of using Shuttle rather than a Worldpay-only connector is flexibility. Your Twilio integration stays the same even if you:

Add a second gateway: serve your UK merchants with Worldpay and your international merchants with Adyen
Serve enterprise customers who mandate a specific PSP: some clients require Worldpay, others require Stripe or Checkout.com
Want a backup gateway: if Worldpay 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
Expand to new markets, with each merchant or entity there on its own gateway

You choose which connected provider handles each payment type in Shuttle’s dashboard. Your Twilio call flow doesn't change.

This is particularly important for contact centres and BPOs serving multiple enterprise clients, each with their own Worldpay account and settlement requirements.

PCI Compliance

The Worldpay + Twilio integration via Shuttle limits your PCI scope:

Layer	PCI handled by
DTMF capture	Twilio
Card data processing	Shuttle (PCI DSS Level 1)
Payment processing	Worldpay (PCI DSS Level 1)
Your systems	Merchants: SAQ-A. Platforms: SAQ-D.

Card data flows from Twilio → Shuttle → Worldpay. Your application only receives redacted data (last 4 digits, card brand, transaction ID). 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 Worldpay to Twilio without Shuttle? Twilio doesn't have a built-in Worldpay 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 connector that is PCI DSS Level 1 certified.

Which Worldpay API does Shuttle use? Worldpay Access, which is the only Worldpay gateway Shuttle supports. The Shuttle dashboard guides you through the correct credentials.

What does it cost? Shuttle charges $49 per live instance per month, plus from $0.20 per transaction, falling with volume, billed through your Twilio account. Worldpay's standard processing fees apply on top (interchange++ or your negotiated rate).

Can I use Worldpay for both voice and online payments? Yes. Your Worldpay account works the same way across channels. Voice payment tokens created via Shuttle can be used for future online or recurring payments through Worldpay.

Can I switch from Worldpay 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. Saved cards stay with the gateway that stored them, so repeat payments on stored cards will not move to the new gateway.

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 Payments: step-by-step Adyen + Twilio setup
How to Connect Checkout.com to Twilio for Voice Payments: step-by-step Checkout.com + Twilio setup
Adyen vs Worldpay: Which PSP for Platforms? (head-to-head comparison)
Twilio Pay: Connect Any Compatible Payment Gateway to Twilio: all supported gateways, pricing, and setup

Connect Worldpay to Twilio with Shuttle's Pay Connector: PCI DSS Level 1, $49 per live instance per month, plus from $0.20 per transaction, falling with volume, billed through your Twilio account. Install on Twilio or book a discovery call.

Take payments over the phone

Card capture for contact centres, IVR flows and AI voice agents, connected to 30+ payment gateways including Stripe, Adyen, and Worldpay Access.

Book a Call