Regal.ai is a voice AI agent platform built for outbound contact: AI phone calls plus SMS and chat, with particular strength in collections, financial services, insurance, healthcare, and BPO operations. Its agents place outbound calls at scale, hold natural conversations, and move accounts toward resolution.
When it comes to money, Regal.ai today arranges the payment and directs the caller to a payment portal. Its collections agents confirm intent to pay, offer repayment options, schedule payment dates, and send a portal link so the borrower can complete the transaction. The actual card entry happens after the call, on a separate page the borrower has to visit.
This guide covers how to close that last step inside the call itself: how Regal.ai handles payments now, why capturing at the moment of agreement matters for collections, and how Shuttle adds secure in-call PCI-compliant payment capture across 30+ gateways via a Twilio Pay handoff.
How Regal.ai Handles Payments Today
Regal.ai is designed to drive conversations to an outcome. In a collections context, the agent works the account: it confirms the right party, discusses the balance, offers repayment options, agrees a plan or a payment date, and provides a payment-portal link so the customer can pay.
This is a clean, respectful model. Regal advertises PCI Compliant infrastructure and SOC 2 Type II, consistent with routing the customer to a portal rather than handling raw card data in the conversation. The agent secures the commitment, and the portal handles the card.
The trade-off is the handoff. Once the call ends, completion depends on the borrower actually opening the link and finishing the payment. The agreement was reached live, but the money lands later, if it lands at all.
Why In-Call Capture Matters for Collections
In collections, the hardest part is reaching the right party. Right-party contact is expensive: dialler time, retries, compliance windows, and the cost of the conversation itself. When an agent finally has the borrower on the line and they agree to pay, that is the moment of maximum intent.
Relying on a later portal visit lets that intent cool. People agree on the call and never open the link. Promise-to-pay rates always beat actual-payment rates, and every gap between agreement and payment is leakage.
Capturing in the call closes the gap. The agent takes the first instalment while the borrower is still committed, and tokenises the card with your gateway, so you can build the remaining instalments into your own workflow. You collect at the moment of agreement instead of hoping the borrower returns to a portal.
How Shuttle Works with Regal.ai Today
Shuttle has no native integration with Regal.ai. Instead, you invoke Shuttle's Twilio-based payment setup. The handoff is API-driven: your application code triggers the Shuttle payment handoff at the point of payment. To use the in-call capture path, you must be a Twilio customer.
The Regal.ai agent agrees the amount or repayment plan with the borrower and confirms intent to pay.
At the point of payment, your application code triggers the Shuttle payment handoff.
The call is handed to a secure PCI DSS Level 1 capture via Twilio Pay. The borrower enters their card details on the keypad, and the digits pass from Twilio Pay to Shuttle's PCI DSS Level 1 environment, so the raw card number never reaches the agent's hearing, the call recording, Regal.ai, or your systems.
Shuttle sends the payment to the creditor's chosen gateway, and the card is tokenised with that gateway.
The result returns to your application in real time, so the conversation can continue with a confirmed payment instead of a pending link.
You build the orchestration and agent-side wiring yourself. Shuttle provides ready-made interfaces for payment links, plus the capture, IVR, and APIs. For a proof of concept, you can build against Shuttle's sandbox gateway and demo app.
Honest caveat: secure capture at the point of payment is live now via Twilio Pay. Shuttle handles the payment segment of the call, not the whole conversation. Returning the caller to the same Regal.ai agent after payment works today: you program the return route in your Twilio flow and pass a conversation ID, so the agent picks the call back up with full context. Shuttle works with Twilio today, and any carrier coming soon.
Multi-PSP Support
Collections operations rarely run on a single gateway. Shuttle connects to 30+ payment gateways with per-client routing:
Route each creditor or client to their own gateway and merchant account.
Supported gateways include Stripe, Adyen, Worldpay, and Checkout.com. See the full list at /payment-providers/.
BPOs and collections agencies handling multiple creditors can keep funds and reporting cleanly separated per client.
Add or switch gateways as configuration, not a new integration, though saved cards stay with the gateway that stored them. A few gateways (for example, Braintree) do not work for voice capture but do work for payment links.
This makes Shuttle a fit for agencies that collect on behalf of many creditors, each with their own banking and PSP requirements.
PCI Compliance
Shuttle is a PCI DSS Level 1 certified Service Provider, the highest level of card data security validation.
Handing the call to Shuttle's secure capture keeps raw card data out of your environment entirely. The borrower enters their card on the keypad, the digits pass from Twilio Pay to Shuttle's PCI DSS Level 1 environment, and they never reach the agent, the recording, Regal.ai, or your call infrastructure. That limits your PCI scope.
The practical effect is the difference between a heavyweight SAQ-D obligation, which applies when card data flows through your systems, and a much smaller scope when a certified Service Provider handles capture for you. Merchants complete SAQ-A, the lightest PCI self-assessment; platforms, BPOs and other service providers collecting payments for other businesses complete SAQ-D. Everyone taking card payments has to be PCI compliant, and your acquirer confirms which form applies to you.
Beyond Voice: Payment Links
Payment links are the turnkey path, and they work even with gateways that do not support voice capture. In-call capture does not mean abandoning the portal model. Shuttle also generates hosted payment links you can send by SMS or email, including mid-call, so you keep the link option inside the same payment layer.
If a borrower prefers to pay later, or the call drops before completion, the agent (or an automated follow-up) sends a Shuttle payment link by text. Whether the customer pays in the call or via a link, it runs through the same gateways, the same tokenisation, and the same reporting. See pricing.
Use Cases
Debt Collection and Repayment Plans
Take the first instalment in the call and tokenise the card with your gateway for the agreed plan. No reliance on the borrower returning to a portal.
Bill-Pay and Past-Due Balances
Settle overdue invoices, subscriptions, and account balances live during the outbound call, with confirmation back to your application before the conversation ends.
Outbound Sales
Convert an outbound AI sales call into a completed purchase in the same conversation, capturing the card at the point of yes rather than emailing a checkout link.
Insurance and Loan Servicing
Collect premiums, reinstatement payments, and loan instalments on outbound servicing calls, with per-client gateway setup for carriers and servicers managing multiple books.
FAQ
Does Regal.ai capture card payments in the call? Public evidence shows Regal.ai arranging the payment and directing the caller to a payment portal link rather than completing card capture in the conversation. Its agents confirm intent, schedule dates, and hand off to the portal for the actual transaction. Shuttle adds the in-call capture step on top of that workflow via a secure Twilio Pay handoff.
Does Shuttle have a native Regal.ai integration? No. Shuttle has no native Regal.ai integration. You invoke Shuttle's Twilio-based setup, and your application code triggers the payment handoff at the point of payment.
Does this require Twilio? Yes, for the in-call capture path today. The secure capture runs via Twilio Pay, so you must be a Twilio customer. Shuttle works with Twilio today, and any carrier coming soon. Payment links do not require Twilio.
How do I take payment during a Regal.ai call? Your application code triggers the Shuttle payment handoff at the point of payment. The call is handed to a secure PCI DSS Level 1 capture via Twilio Pay, the borrower enters their card on the keypad, the digits pass from Twilio Pay to Shuttle's PCI DSS Level 1 environment, and Shuttle processes it through the creditor's gateway and returns confirmation to your application.
Can an AI agent split a balance into a payment plan? Yes. Shuttle tokenises the card with your gateway when the first instalment is taken, so you can build the remaining instalments into your own workflow.
Which payment gateways does Shuttle support? Shuttle connects to 30+ gateways including Stripe, Adyen, Worldpay, and Checkout.com, with per-client routing. See /payment-providers/. A few gateways (for example, Braintree) do not work for voice but do work for payment links. Switching gateways is configuration, not re-integration, though saved cards stay with the gateway that stored them.
Does this work for outbound calls? Yes. Shuttle supports the outbound, collections-led calling that Regal.ai specialises in, capturing payment at the moment of agreement on outbound calls.
Related Reading
AI Voice Payments for Debt Collection: taking payments and running repayment plans on AI collections calls.
Secure Payment Collection for Debt Agencies: secure, multi-creditor payment collection for debt agencies.
AI Voice Agent PCI Payments: how PCI-compliant payment capture works inside an AI voice agent.
Voice Payments: the full picture on taking payments over voice channels.
The Payment Layer for AI Agents: why AI agents need a dedicated payment layer.
Add Payments to Your Regal.ai Agents
Capture payments at the moment of agreement on Regal.ai calls via a secure Twilio Pay handoff. 30+ gateways, per-client routing, PCI DSS Level 1, and $49 per live instance per month, plus from $0.20 per transaction, falling with volume, billed through your Twilio account. Read the Twilio setup docs, the payment links docs, and the security overview.
See Voice Checkout | Book a discovery call