Moneris doesn't natively connect to Twilio for voice payments. If you want to process Moneris 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 Moneris (and 30+ other gateways) to Twilio's <Pay> verb, so you can accept PCI-compliant card payments during any voice interaction.
For Canadian businesses this matters. Moneris is Canada's largest payment processor, a joint venture of RBC and BMO, and the default acquirer for hundreds of thousands of Canadian merchants. If your business already settles through Moneris, this guide shows you how to take CAD payments over the phone without changing processors.
Why Moneris + Twilio Don't Connect Directly
Moneris is built for Canadian commerce: in-store terminals, ecommerce via the Moneris Gateway, and card-present processing with CAD settlement into Canadian bank accounts. Its APIs handle purchases, pre-authorisations, and tokenisation through the Moneris Vault.
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. Moneris isn't one of Twilio's built-in connectors, so there's no direct path from a Twilio call to your Moneris account.
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 Moneris for processing. One integration connects the two platforms.
How It Works
`` Caller → Twilio (DTMF capture) → Shuttle (Pay Connector) → Moneris (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 Moneris. The connector creates a Moneris payment request, processes the transaction through your Moneris account, and handles the response.
Result returned to your call flow. Your webhook receives the Moneris 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 Moneris account with gateway credentials (store ID + API token, found in the Merchant Resource Center under Admin > Store Settings)
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 Moneris Credentials to Shuttle
Log into the Shuttle dashboard. Navigate to Payment Profiles and create a new profile:
Gateway: Moneris
Store ID: Your Moneris store ID
API token: Your Moneris API token
Currency: CAD (USD is also supported if your Moneris account processes it)
Environment: Live or Test
Save the profile. Shuttle now has a live connection to your Moneris 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.50" currency="CAD" description="Account payment" action="/payment-complete"> </Pay> </Response> ``
Key parameters:
paymentConnector: set toshuttle-pay-connectorchargeAmount: the amount to chargecurrency: ISO currency code (CAD for Canadian merchants)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:
``json { "Result": "success", "PaymentCardNumber": "xxxx-xxxx-xxxx-1234", "PaymentCardType": "visa", "PaymentConfirmationCode": "MONERIS-REF-123...", "ProfileId": "your-shuttle-profile-id" } ``
Use the PaymentConfirmationCode to look up the transaction in the Merchant Resource Center if needed. Update your account records, confirm to the caller, and continue the flow.
Step 5: Test
Use Moneris's test environment credentials in your Shuttle payment profile and verify the flow end-to-end before going live. Moneris's test environment simulates issuer responses, approving or declining transactions based on the amount you send, so you can rehearse both success and failure paths in your call flow.
What You Can Do With Moneris + Twilio
Charge Immediately
Standard purchase. The caller pays, Moneris processes, funds settle to your Canadian bank account on your normal Moneris schedule.
Authorise Now, Capture Later
Place a pre-authorisation on the card during the call. Capture the payment later through Moneris, useful for bookings, deposits, or amounts that are finalised after the call.
Tokenise for Future Use
Capture card details once over the phone. Shuttle tokenises the card via the Moneris Vault, which returns a permanent token (a data key) for that stored card. Use it for future payments across any channel: web, mobile, voice, or payment links. This is the pattern for recurring billing, instalment plans, and card-on-file collections. The card data is never stored in your systems. Note that the Vault option must be enabled on your Moneris account; your Moneris representative can switch it on.
Serve Canadian Phone-Payment Use Cases
Moneris + Twilio via Shuttle fits anywhere Canadian customers pay by phone: utilities taking bill payments through IVR, insurers collecting premiums on renewal calls, collections teams processing settlements and payment plans, and healthcare providers taking patient billing over the phone. The caller pays in CAD, your agents stay out of PCI scope, and settlement lands with your existing acquirer.
Multi-PSP: Beyond Moneris
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 Canadian transactions to Moneris and US or international transactions to another acquirer
**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
Expand beyond Canada, where a local acquirer may 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, routing by merchant, region, amount, or failover.
This is particularly important for platforms and BPOs that serve multiple merchants. Each merchant can use their own Moneris account (or any other gateway) through the same Twilio integration.
PCI Compliance
The Moneris + 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 | Moneris |
Your systems | No card data: SAQ-A |
Card data flows from Twilio → Shuttle → Moneris. 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 Moneris to Twilio without Shuttle? Twilio doesn't have a built-in Moneris 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.
Can I take CAD payments over the phone with this? Yes. That's the primary use case. Transactions process in CAD through your Moneris account and settle to your Canadian bank account as normal.
What about Moneris's test environment? Fully supported. Use your Moneris test credentials in Shuttle and test the full flow with Twilio before going live. Moneris's test environment simulates issuer approvals and declines based on the transaction amount.
What does it cost? Shuttle charges $0.20 per successful transaction. Moneris's standard processing fees apply on top. No Shuttle setup fees or monthly minimums.
Can I switch from Moneris 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 & IVR Payments: step-by-step Adyen + Twilio setup
Payment Collection for BPOs: multi-client phone payments for outsourcers
Moneris: Moneris on Shuttle: supported features and channels
Twilio Pay: Connect Any Payment Gateway to Twilio: all supported gateways, pricing, and setup
*Connect Moneris 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.*