Mollie doesn't natively connect to Twilio for voice payments. If you want to process Mollie 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 Mollie (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 Mollie + Twilio Don't Connect Directly
Mollie is an Amsterdam-based payment service provider built for European commerce. It's especially strong in the Netherlands, Belgium, and Germany, where it gives merchants a single integration for cards plus local payment methods like iDEAL, Bancontact, and SEPA. Its API and dashboard are designed to be simple enough for SMEs while scaling to larger platforms.
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. Mollie isn't one of Twilio's built-in connectors, so there's no native path between the two platforms.
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 Mollie's API for processing. One integration connects the two platforms.
One point worth noting up front: DTMF keypad capture is for card payments, while local methods like iDEAL and Bancontact work over the phone via a Shuttle payment link sent to the caller by SMS or email during the call, not keypad entry.
How It Works
`` Caller → Twilio (DTMF capture) → Shuttle (Pay Connector) → Mollie (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. 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 Mollie. The connector creates a Mollie payment request, processes the transaction through your Mollie account, and handles the response.
Result returned to your call flow. Your webhook receives the Mollie payment 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 Mollie account with an API key (Mollie issues keys in pairs: a
test_key for test mode and alive_key for production, found under Developers in your Mollie Dashboard)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 Mollie Credentials to Shuttle
Log into the Shuttle dashboard. Navigate to Payment Profiles and create a new profile:
Gateway: Mollie
API key: Your Mollie
live_API key (ortest_key for testing)Currency: Set your default (EUR for most Mollie merchants)
Save the profile. Shuttle now has a live connection to your Mollie account.
Step 3: Configure Your Twilio Call Flow
Add the <Pay> verb to your TwiML:
``xml <Response> <Say>Please enter your card number followed by the hash key.</Say> <Pay paymentConnector="shuttle-pay-connector" chargeAmount="49.99" currency="EUR" 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": "MOLLIE-PAYMENT-REF...", "ProfileId": "your-shuttle-profile-id" } ``
Use the PaymentConfirmationCode to look up the transaction in your Mollie Dashboard if needed. Update your order, confirm to the caller, and continue the flow.
Step 5: Test
Swap in your Mollie test_ API key in your Shuttle payment profile and run the flow end-to-end in Mollie's test mode before going live. Once verified, switch the profile to your live_ key.
What You Can Do With Mollie + Twilio
Charge Immediately
Standard card payment. The caller pays on the keypad, Mollie processes in EUR (or another supported currency), done. This suits Dutch, Belgian, and German contact centres taking bookings, invoice payments, or deposits by phone.
Tokenise for Future Use
Capture card details once over the phone. Shuttle tokenises the card and returns a reusable token, so you can charge repeat payments across any channel: web, mobile, voice, or payment links. The card data is never stored in your systems.
Card by Keypad, Local Methods by Link
DTMF capture handles card payments. For callers who prefer iDEAL or Bancontact, your agent can send a Shuttle payment link by SMS or email while still on the call, and the caller completes the payment through Mollie's local method rails on their own device.
Serve Multiple Merchants
BPOs and outsourced collection teams can run separate Shuttle payment profiles per client, each pointing at that client's own Mollie account, through a single Twilio integration.
Multi-PSP: Beyond Mollie
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 Dutch and Belgian transactions to Mollie and UK or US transactions to a local acquirer
**Serve enterprise customers** who mandate a specific PSP (Stripe, Worldpay, Adyen, etc.)
Need failover: if one gateway has an outage, automatically route to a backup
Expand to new markets where a different acquirer gives better authorisation rates
You configure routing rules in Shuttle's dashboard, splitting traffic by merchant, region, amount, or failover priority. Your Twilio call flow doesn't change. The <Pay> verb always points to shuttle-pay-connector, and Shuttle handles which gateway processes the transaction.
PCI Compliance
The Mollie + 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 Service Provider) |
Payment processing | Mollie |
Your systems | No card data: SAQ-A |
Card data flows from Twilio to Shuttle to Mollie. Your application only receives redacted data (last 4 digits, card brand, payment 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 Mollie to Twilio without Shuttle? Twilio doesn't have a built-in Mollie 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.
Can callers pay with iDEAL or Bancontact over the phone? Not via the keypad. DTMF capture is for card payments. For iDEAL, Bancontact, and other local methods, send the caller a Shuttle payment link by SMS or email during the call and they complete it on their own device.
What about Mollie's test mode? Fully supported. Use your Mollie test_ API key in your Shuttle payment profile and verify the full flow with Twilio before switching to your live_ key.
What does it cost? Shuttle charges $0.20 per successful transaction. Mollie's standard transaction fees apply on top. No Shuttle setup fees or monthly minimums.
Can I switch from Mollie 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
Mollie: Mollie coverage, methods, and Shuttle support
Twilio Pay: Connect Any Payment Gateway to Twilio: all supported gateways, pricing, and setup
*Connect Mollie 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.*