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 does not have native PCI-compliant payment processing. Marketplace DTMF options exist but are typically designed for small-scale operations and don't cover multi-PSP routing, multi-tenant operations, or enterprise-scale volumes.
This guide covers how an Aircall-based operation can add enterprise-grade, PCI-compliant payment capture using Shuttle. Some of the world's biggest brands use Shuttle for voice payments.
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 inside Shuttle's PCI DSS Level 1 certified environment via Twilio Pay (Shuttle is Twilio's preferred payments partner), and the card data never reaches your Aircall recordings, your connected CRM, or your agents. Shuttle customers already take payments this way on Aircall-based operations today.
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. Customers running Aircall have already built exactly this. 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 are captured inside Shuttle's certified 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. Customers running Aircall have already built this. 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 are captured inside Shuttle's certified 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 region: route by geography for optimal settlement and fees
By failover: automatic backup if the primary gateway is unavailable
By card type: route specific card brands through preferred processors
Switching processors later is straightforward; gateway choice is configuration, not a re-integration. 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 PCI scope, keeping you on the lighter SAQ-A path. 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 $0.20 per successful transaction with no setup fees, no per-seat fees, and no monthly minimums. Payment links are currently free (a new pricing model is coming).
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 without PCI exposure.
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 the certified payment connector, so you need to be a Twilio customer. A carrier-agnostic version that removes the Twilio requirement is on our roadmap for later in 2026.
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, and customers running Aircall have already done it.
A native Aircall integration is available as a paid project. If you would rather not build the bridge yourself, we were in talks to put a Shuttle app in the Aircall marketplace, and we can build one for your deployment with you.
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, or handing the caller back to the same agent afterwards, is part of the fuller call control coming with the carrier-agnostic version.
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 (we're Twilio's preferred payments partner), 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, which customers running Aircall have already done. We can build a native Aircall integration as a paid project if you'd rather not build it yourself, and a carrier-agnostic version is on our roadmap.
Does this require Twilio?
Yes, today. The secure card capture runs via Twilio Pay, where Shuttle is the certified payment connector. The carrier-agnostic version that removes this requirement is on our roadmap.
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?
$0.20 per successful transaction for voice, no setup fees, no per-seat licensing, no monthly minimums. Payment links are currently free.
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
Shuttle adds PCI-compliant payments to an Aircall-based operation via Twilio, with multi-PSP routing and no gateway lock-in. We'll walk you through what's live today and the path for your setup.
See Voice Checkout | Book a discovery call