Aircall is a cloud phone system popular with sales and support teams, particularly in the SMB and mid-market segments. It integrates deeply with CRMs like HubSpot, Salesforce, and Zendesk, making it a go-to for teams that want call centre functionality without a full enterprise CCaaS platform.
Aircall is not a payment processor. Secure card capture on Aircall comes from apps in its marketplace, which take the card by keypad (DTMF) and keep the numbers away from agents and call recordings. Shuttle is a different kind of product: a payment layer between the call and each merchant's own payment gateway, with payment links on the same integration.
This guide covers how an Aircall-based operation can add enterprise-grade, PCI-compliant payment capture using Shuttle.
How Shuttle Adds Payments to Aircall
Shuttle adds enterprise-grade, PCI-compliant card capture to your Aircall calls. When the customer is ready to pay, they enter their card on their phone keypad, the digits are captured through Twilio Pay and passed to Shuttle's PCI DSS Level 1 environment, and the card data never reaches your Aircall recordings, your connected CRM, or your agents.
The setup is light. It runs on Twilio Pay, so you need to be a Twilio customer, and you build a small integration on your side. Shuttle ships the secure PCI capture, payment links, IVR, and the payment APIs; what it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call wired for Aircall specifically. So the part you build is small: pass the payment amount to Shuttle through its API (the minimum data we need), connect the secure capture into your Aircall call flow over Twilio, and add your own agent screen if your workflow needs one. If that fits, book a call and we will scope your exact setup. There is practical detail in the "What to Expect" section further down.
Secure card capture (voice)
When it is time to pay, the card is captured in a secure, PCI DSS Level 1 call via Twilio Pay. The customer enters their card details on their phone keypad, and the digits pass from Twilio Pay to Shuttle's PCI DSS Level 1 environment. They never reach your Aircall recordings, your connected CRM, or your agents. See the Twilio IVR & Agent Assist payment docs for the technical flow.
Payment Links
This is the most turnkey path. Shuttle generates payment links and sends them via SMS or email, including mid-call to a customer who is still on the line. The customer taps the link, enters card details on a secure hosted page, and confirmation is returned in real time. Shuttle provides the link interfaces out of the box. See the Payment Links docs.
Agent experience
For voice, the agent triggers the capture and sees the result without ever handling card data. Shuttle does not ship a pre-built agent screen or input UX for Aircall, so you build that minimal piece against Shuttle's APIs: trigger the capture, pass the amount, and show the result in your own agent screen if your workflow needs one. There is more in the "What to Expect" section below.
How a voice payment works
The call proceeds on Aircall as normal.
Payment is triggered from your agent interface when the customer is ready to pay.
Card captured securely. The card is captured in a PCI DSS Level 1 call via Twilio Pay. The customer enters their card on the keypad, and the digits pass from Twilio Pay to Shuttle's PCI DSS Level 1 environment.
Transaction is processed. Shuttle routes to the configured PSP, any of 30+ supported gateways.
Result returned to your interface and your systems via webhook.
No card data in Aircall. The card digits never touch your Aircall recordings, your CRM, or your agent workstations.
Multi-PSP Support
Shuttle supports 30+ payment gateways with configurable routing:
By merchant: different clients or business units route to different gateways
By payment method: cards through one gateway and ACH through another
Manual failover: if a gateway 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
Switching processors later is configuration, not a re-integration, though saved cards stay with the gateway that stored them. One caveat for voice specifically: a small number of gateways (for example Braintree) don't permit the raw card data to be passed to them, so they don't work for voice capture, though they do work for payment links.
PCI Compliance
Shuttle is a PCI DSS Level 1 certified Service Provider. Because the card is captured in the secure Twilio Pay call, card data never enters your Aircall recordings, CRM data, transcriptions, or agent workstations. They stay out of the card data flow, which limits your PCI scope. Merchants complete SAQ-A; platforms, BPOs and other service providers collecting payments for other businesses complete SAQ-D. Your acquirer confirms which form applies to you. Full compliance documentation, including the AOC scope, is in the security docs.
This is especially important for Aircall users with deep CRM integrations. Without a secure capture, card data from calls flows into HubSpot, Salesforce, or whatever CRM you've connected. With Shuttle, your CRM stays clean.
Voice payments cost $49 per live instance per month, plus from $0.20 per transaction, falling with volume, billed through your Twilio account, with no per-seat fees. See pricing.
For Solution Providers and Aircall Implementation Partners
If your team deploys Aircall for clients, as a partner or a system integrator, Shuttle is the payment layer you deliver alongside the rest of the implementation. Each client keeps their own merchant account and their own gateway, and your side integrates once, so payments are not rebuilt for every engagement and client money never lands in yours.
Shuttle's voice capture runs on Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways. Shuttle is not a pre-packaged Aircall plugin, so your team builds a small integration between Aircall and Shuttle, and voice deployments need a Twilio account. For partnership conversations, book a discovery call.
Use Cases
Professional Services
Accountants, solicitors, and consultants using Aircall for client calls can collect invoice payments during the conversation. The client enters card details, payment confirms, and the call wraps up with everything handled.
Insurance Brokers
Small and mid-sized insurance brokers on Aircall handle premium collections and renewals. Shuttle captures payment during the call while limiting PCI scope.
E-commerce Support
E-commerce support teams on Aircall handling order issues, refunds, and re-orders can take replacement payments securely during the support call.
Debt Collection
Collections teams using Aircall capture payment at the moment of commitment, while the customer is still on the line.
What to Expect
Shuttle is a payment layer you connect to your stack, not a pre-packaged Aircall plugin. Here is the honest detail so there are no surprises on the call:
It runs on Twilio Pay today. Shuttle's voice capture uses Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways, so you need to be a Twilio customer. Shuttle works with Twilio today, and any carrier coming soon.
You build a small integration, not a payment system. Shuttle ships the secure PCI capture, IVR, payment links, and payment APIs. What it does not ship is an out-of-the-box agent screen, the input UX, or the amount-passing API call for Aircall specifically. So you build that minimal glue: pass the amount to Shuttle via its API (the minimum data we need), connect the capture into your Aircall call flow over Twilio, and add your own agent screen if your workflow needs one. It is light.
Point-of-payment capture is what is live. Securely capturing the card at the moment of payment works today. Shuttle staying present across the entire Aircall conversation is not available today, and Shuttle does not ship call hand-back after payment out of the box. What happens to the caller after payment is part of the call flow you build in Twilio. Works with Twilio today, and any carrier coming soon.
Payment links are the most turnkey path and need the least build. Many teams start there and add voice capture later.
Frequently Asked Questions
Does Shuttle have a native Aircall integration?
Not today. Shuttle's voice capture runs on Twilio Pay, and you invoke that setup rather than installing a Shuttle app in Aircall. You'll need to be a Twilio customer and to build a small bridge connecting your workflow to Twilio. Shuttle works with Twilio today, and any carrier coming soon.
Does this require Twilio?
Yes, today. The secure card capture runs via Twilio Pay, where Shuttle is Twilio's chosen provider to enable Twilio Pay for many payment gateways. Shuttle works with Twilio today, and any carrier coming soon.
Can we just use payment links instead of voice capture?
Yes. Many teams use links only, sent via SMS or email, including mid-call. Links are the most turnkey part of Shuttle and work with gateways that don't support voice capture.
Can we try it before committing?
Yes. You can build a proof of concept against Shuttle's sandbox gateway and demo app to see the IVR flow, then move to a compatible production gateway when you're ready.
Does Shuttle affect my Aircall CRM integrations?
No, and this is a key benefit. The card is captured in the secure Twilio Pay call, so your HubSpot, Salesforce, or Zendesk integrations never see card data.
What does Shuttle cost?
Voice costs $49 per live instance per month, plus from $0.20 per transaction, falling with volume, billed through your Twilio account, with no per-seat licensing. See pricing.
Related Reading
PCI-Compliant Payments for Contact Centres: the complete guide
Talkdesk Payments: PCI-compliant payment capture for Talkdesk
RingCentral Payments: secure voice payments for RingCX and RingEX
Zendesk Payments: payment collection for Zendesk support teams
Voice Payments: comprehensive guide to voice payment capture
Get Started
If you are a merchant taking payments on Aircall rather than building for clients, talk to us about your deployment, or see how Voice Checkout works.
