Mollie 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 want to process Mollie transactions during a phone call (via IVR, agent-assisted, or AI voice agent), 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 Mollie account processes the payment. 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 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, 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. Mollie isn't one of Twilio's built-in connectors, so there's no native path between the two platforms.
Shuttle doesn't change that for keypad capture: Mollie 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 Mollie processes the payment.
The same payment link works for local methods like iDEAL and Bancontact, as well as cards.
How It Works
Caller on Twilio call → Agent/IVR triggers Shuttle → SMS/email payment link → Mollie (processing) → Result webhook
Caller reaches payment step. Your agent, IVR or AI agent triggers Shuttle via API.
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 pay on their own device. Card data never passes through the call or your servers.
Mollie processes the payment. The transaction runs through your Mollie account.
Result returned in real time. Your webhook receives the payment reference and status. The call continues.
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 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; see pricing)
Step 1: 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 2: Configure your payment link
Set the currency, branding and which payment methods appear on the link (cards, plus local methods like iDEAL and Bancontact through Mollie).
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 payment reference and status.
Use the payment reference to look up the transaction in your Mollie Dashboard if needed. Update your order, confirm to the caller, and continue the flow.
Step 4: 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
Take Payment While the Caller Is on the Line
The caller pays by link while still on the call, and Mollie processes in EUR (or another supported currency). This suits Dutch, Belgian, and German contact centres taking bookings, invoice payments, or deposits by phone.
Cards and Local Methods by Link
The same Shuttle payment link can offer cards alongside iDEAL or Bancontact. Your agent sends it by SMS or email while the caller is still on the call, and the caller completes the payment through Mollie 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 integration.
Multi-PSP: Beyond Mollie
One of the key advantages of using Shuttle is flexibility. Your integration stays the same even if you:
Add a second gateway: serve your Dutch and Belgian merchants with Mollie and your UK or US merchants with a local acquirer
Serve enterprise customers who mandate a specific PSP (Stripe, Worldpay, Adyen, 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 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, per merchant. Your call flow doesn't change: it triggers Shuttle the same way, and Shuttle sends the payment to the provider you configured.
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 | Mollie |
Your systems | Merchants: SAQ-A. Platforms: SAQ-D. |
The customer enters payment details on a secure hosted page, and Mollie processes the payment. Your application only receives redacted data (payment 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 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.
Can callers pay by card or with iDEAL or Bancontact over the phone? Yes, by payment link rather than keypad: Mollie does not take in-call keypad capture through Shuttle. 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 before switching to your live_ key.
What does it cost? Links Checkout is $49 per live instance per month, with transactions from $0.20; see pricing. Mollie's standard transaction fees apply on top.
Can I switch from Mollie 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
Mollie: Mollie coverage, methods, and Shuttle support
Twilio Pay: Connect Any Compatible Payment Gateway to Twilio: all supported gateways, pricing, and setup
Take Mollie payments on Twilio calls with Shuttle payment links: PCI DSS Level 1, $49 per live instance per month, with transactions from $0.20. Install on Twilio or book a discovery call.