Intercom Handles Conversations. It Doesn't Handle Payments.
Intercom is built for customer messaging, live chat, in-app messages, email, and increasingly, phone. Sales teams qualify leads and close deals through it. Support teams resolve issues. Success teams manage renewals.
But when any of those conversations reaches the point where money needs to change hands, Intercom doesn't take the payment itself.
The result: agents copy-paste links from separate systems, tell customers to "go to your account settings and update your card," or, worse, ask customers to type card details into the chat. That last one is a PCI violation, and it happens more often than anyone admits.
Shuttle closes this gap for Intercom-based teams. Agents send branded payment links directly within chat, and customers pay from the conversation. For phone teams, Shuttle adds secure voice card capture via Twilio Pay. Card data never touches Intercom, your network, or your agents.
How Shuttle Adds Payments to Intercom
Shuttle adds PCI-compliant card capture to your Intercom payment flows. When the customer is ready to pay, the card is captured through Twilio Pay and passed to Shuttle's PCI DSS Level 1 environment, and the card data never reaches your Intercom environment 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 Intercom 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 Intercom workflow 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.
Why Intercom Teams Need Payment Capture
Intercom sits at the intersection of sales, support, and success. Each function has payment moments that the platform currently can't handle.
Failed payment recovery. A customer's card declines. Their subscription is at risk. The automated dunning email got ignored. But when a support agent reaches out in Intercom and can send a payment link right there in the chat, the customer can pay in the same conversation.
Upgrade and expansion revenue. A sales conversation in Intercom leads to a plan upgrade. Today, the rep says "I'll send you an invoice" or "you can upgrade in your dashboard." Both add steps. Both lose deals. If the rep can send a payment link for the upgrade amount mid-conversation, the deal closes on the spot.
Invoice collection. B2B customers with outstanding invoices are already in Intercom asking about their account. If the agent can send a payment link for the exact invoice amount during that conversation, collection happens immediately instead of entering a follow-up cycle.
One-off charges. Professional services, implementation fees, overage charges, custom work. These don't fit neatly into subscription billing. Payment links handle them cleanly, the agent sends a link for the specific amount, the customer pays, done.
Subscription changes. Pro-rata adjustments, add-on purchases, plan switches with price differences. The customer wants it handled now, in the conversation they're already having.
How to Add Payments to Intercom
Payment Links in Conversations
This is the primary integration pattern for Intercom. It works across every Intercom channel, live chat, in-app messenger, email, and social.
The flow:
During a conversation, the agent determines that a payment needs to be collected. They generate a payment link through Shuttle via an API call from your backend.
The agent sends the link in the conversation. It appears as a tappable, clickable URL, or as a rich card if you've built a custom Intercom app.
The customer taps the link. On mobile, it opens in their browser. On desktop, it opens in a new tab. They see a branded checkout page showing the amount, a description of what they're paying for, and standard card input fields.
The customer enters their card details and completes payment. Card data goes directly from their browser to Shuttle's PCI Level 1 certified infrastructure. It never passes through Intercom, your servers, or any agent-visible system.
The agent receives confirmation in real time. A webhook updates the conversation with payment status, transaction ID, and amount. The agent can confirm to the customer immediately.
Why this fits Intercom's model:
Intercom is conversational by design. Payment links extend that conversation to include the transaction itself, rather than breaking the flow with "please go to this other system." The customer pays from the conversation.
For automated flows, Intercom's bots and workflows, payment links can be generated programmatically and sent without agent involvement. A Resolution Bot that identifies a failed payment can automatically send a recovery link. A product tour that ends with a purchase step can include a payment link as the final message.
Payment links are available at /platforms/links-checkout/.
Voice Payments via Twilio Pay
For teams that handle payment-related phone calls, Shuttle's Voice Checkout captures the card in a secure Twilio Pay call. To use it you need to be a Twilio customer.
How it works:
The agent triggers a payment session during a call. This starts a secure Twilio Pay capture on the voice channel.
The customer enters their card details using their phone's keypad. Each digit is captured through Twilio Pay and passed to Shuttle's PCI DSS Level 1 environment.
The digits never reach your call recordings, your Intercom instance, or your agents.
The payment is processed through the configured gateway. The result is returned to the agent in real time.
This limits your telephony's PCI scope. Card numbers never reach your agents, recordings are clean, and your environment needs far fewer compliance controls. See the Twilio IVR & Agent Assist payment docs for the technical flow.
Voice Checkout details at /platforms/voice-checkout/.
Agent experience
In a conversation, the customer gets a payment link and the agent sees the result without ever handling card data. On voice calls, the agent triggers the capture and sees the outcome, again without handling card data. Shuttle ships payment links. It does not ship a pre-built agent screen or input UX for Intercom, so triggering payment from inside Intercom is the piece you build against Shuttle's APIs: pass the amount and surface the result where your workflow needs it. There is more in the "What to Expect" section below.
Payment Links in Intercom Conversations
The payment link approach deserves deeper exploration because it's where most Intercom teams will start.
Branded checkout pages. The payment page carries your brand, logo, colours, company name.
Pre-populated amounts and references. Links are generated with the exact amount, currency, and description already set. The customer doesn't need to enter an amount or find an invoice number. This reduces errors and speeds up completion.
Multi-currency support. If you operate internationally, payment links can be generated in the customer's local currency. You can set which currencies each payment method is offered in, and each method goes to the gateway configured for it.
Expiry and security. Links can be set to expire after a defined period, useful for time-sensitive offers or outstanding balances. Each link is single-use.
Automation-friendly. Payment links can be generated via API, making them available to Intercom's Custom Bots, workflows, and third-party automations. A Zapier or Make integration can trigger payment link generation based on Intercom events, conversation tags, custom attributes, or specific bot paths.
Mobile-first. Intercom's messenger is heavily used on mobile. Payment links open in the device's browser with a responsive checkout page. On iOS and Android, Apple Pay and Google Pay can be offered alongside card input, depending on your gateway configuration.
Multi-PSP Support
Your payment gateway choice shouldn't constrain how you take payments. Shuttle connects to 40+ payment service providers, including Stripe, Adyen, Worldpay, Checkout.com, Braintree, PayPal, Mollie, and GoCardless. 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 few gateways (for example Braintree) don't permit raw card data to be passed to them, so they don't work for voice capture, though they do work for payment links.
This matters in several scenarios:
You're migrating gateways. Moving from Stripe to Adyen? Your Intercom payment workflow doesn't change: you point the payment types at Adyen in Shuttle. Saved cards stay with Stripe, so customers paying by stored card enter it again.
Different markets, different gateways. Your EU business runs through Adyen, your US business through Stripe. Each merchant is configured against their own gateway.
Client-specific gateways. If you're a platform serving multiple businesses (each with their own merchant account), Shuttle sends each client's payments to that client's own gateway.
Agents don't need to know which gateway is processing a given payment. They send a link, the customer pays, the money lands in the right account.
PCI Compliance
Every organisation that processes card payments must comply with PCI DSS. The question is how much of your environment falls within scope, and how expensive that compliance is to maintain.
The risk with chat-based payments. If a customer types a card number into an Intercom chat, that data is now stored in Intercom's conversation history, potentially visible to multiple agents, and backed up across systems. This puts your Intercom environment, your network, and your data storage in PCI scope. You're looking at SAQ-D, 300+ compliance requirements and significant annual costs.
How payment links reduce scope. With Shuttle's payment links, card data never enters Intercom. The customer's browser communicates directly with Shuttle's PCI Level 1 certified infrastructure. Intercom sees only a URL (outbound) and a payment confirmation (inbound). Merchants complete SAQ-A, the lightest self-assessment level; platforms complete SAQ-D. Everyone taking card payments has to be PCI compliant, and your acquirer confirms which form applies to you.
Voice payment compliance. If you take phone payments with Shuttle's Twilio Pay capture, the same scope reduction applies. Card data is captured in the secure Twilio Pay call and never reaches your telephony, recordings, or agents.
Shuttle is a PCI DSS Level 1 certified Service Provider, the highest level of certification, validated annually by an independent Qualified Security Assessor.
For Solution Providers and Intercom Implementation Partners
If your team deploys Intercom 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 Intercom plugin, so your team builds a small integration between Intercom and Shuttle, and voice deployments need a Twilio account. For partnership conversations, book a discovery call.
Use Cases
SaaS Failed Payment Recovery
A customer's card expires. Automated dunning emails go unread. The customer opens an Intercom chat about an unrelated issue. The agent sees the failed payment flag, sends a payment link for the outstanding amount, and the customer pays the outstanding amount, all within the same conversation.
Professional Services Payment
A customer agrees to a paid implementation package during an Intercom sales conversation. The rep generates a payment link for the implementation fee and sends it in the chat. The customer pays immediately. No invoice. No accounts payable cycle. No follow-up.
E-commerce Order Issue Resolution
A customer contacts support about a damaged item. Instead of a full refund, the agent offers a partial refund plus a replacement, with the customer paying the price difference. A payment link for the difference is sent in the chat. The customer pays, and the replacement is dispatched.
Subscription Upgrade
A trial user is chatting with sales in Intercom. They're ready to upgrade to a paid plan. The sales rep sends a payment link for the first month (or annual subscription). The customer pays within the chat. The account is upgraded automatically via webhook.
What to Expect
Shuttle is a payment layer you connect to your stack, not a pre-packaged Intercom 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 Intercom 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 Intercom workflow 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 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 Intercom integration? Not today. Shuttle's voice capture runs on Twilio Pay, and you invoke that setup rather than installing a Shuttle app in Intercom. For voice you'll need to be a Twilio customer and to build the agent-side trigger for your workflow against Shuttle's APIs. Payment links require no Twilio relationship. Shuttle works with Twilio today, and any carrier coming soon.
Does this require Twilio? For voice capture, 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. Payment links do not require Twilio. Shuttle works with Twilio today, and any carrier coming soon.
Can payment links be sent by Intercom bots, or only by human agents? Both. Payment links are generated via API, so they can be triggered by Custom Bots, workflows, or any automation that can make an HTTP request. This enables fully automated payment recovery flows without agent involvement.
Does the customer need to leave the Intercom chat to pay? The payment page opens in a new browser tab or the device's browser. The customer completes payment there and returns to the conversation. The agent receives confirmation in real time, so the conversation carries on from there.
What payment methods are supported? Card payments are supported. Depending on your gateway configuration, Apple Pay, Google Pay, and other local payment methods can also be enabled on the checkout page.
How much does it cost? 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.
Can we track which Intercom conversations resulted in payments? Yes. Payment confirmations include metadata that can be mapped back to Intercom conversation IDs, allowing you to track conversion rates, recovery rates, and revenue generated through Intercom payment flows.
Related Reading
PCI-Compliant Payments for Contact Centres, comprehensive guide to secure payment capture in contact centre environments
Voice Payments: The Complete Guide, everything about DTMF, IVR, and agent-assisted voice payment capture
Multi-Channel Payment Collection, collecting payments across chat, email, SMS, and voice
Twilio Pay Connectors, how Shuttle connects to Twilio's payment infrastructure
Voice Checkout, Shuttle's voice payment product for phone-based transactions
Get Started
If you are a merchant taking payments on Intercom rather than building for clients, talk to us about your deployment, or see how Voice Checkout works.