Lindy is a no-code AI agent builder that lets businesses create "AI employees": autonomous agents that handle email triage, meeting scheduling, CRM updates, and phone calls without human intervention. Its phone capability, Lindy Gaia, lets teams deploy inbound and outbound voice agents that can qualify leads, answer queries, book appointments, and follow up on outstanding tasks. Businesses use Lindy across sales, customer support, and operations to reduce the manual overhead of repetitive communications work.
The payment wall is a predictable friction point for Gaia deployments. Lindy does connect to Stripe, but that integration is read-only workflow automation: it triggers on Stripe events (payments received, invoices created), retrieves invoice and refund data, and feeds that into downstream Lindy workflows. It is used primarily for internal operations and billing Lindy's own subscribers, not for capturing card details from a Lindy user's customers. Gaia itself has no DTMF suppression, no PCI-compliant capture path, and no ability to initiate a customer charge inside a call. When a Gaia agent reaches the payment moment, whether that is closing an inbound sale, collecting an overdue balance, or taking a deposit, it has no native way to handle it securely.
This guide is for developers and operations teams building Lindy Gaia workflows that need to take payments from customers: inbound sales calls, outbound collections, appointment deposits, and subscription renewals. It explains how to connect Shuttle's PCI DSS Level 1 payment layer to Lindy so Gaia agents can complete transactions without card data ever touching Lindy's infrastructure. There is no native Lindy integration: instead, your application invokes Shuttle's Twilio-based secure capture (Shuttle is Twilio's preferred payments partner), which does require you to be a Twilio customer today.
The Payment Challenge for Lindy Agents
Lindy's compliance posture covers what its core product handles. The platform holds SOC 2 Type II, GDPR, HIPAA, and PIPEDA certifications. PCI DSS is not on that list because Lindy is not a payment processor and does not handle cardholder data. That is not a criticism: it is a sensible scope decision for a workflow automation platform.
The practical consequence is that any Gaia agent that needs to collect a card payment runs into a hard wall. You cannot instruct Gaia to ask for a card number and store it, because there is no compliant capture mechanism to do so. Asking a customer to read card digits aloud on a call that is not PCI-scoped creates a PCI scope problem for your organisation immediately.
Teams working around this today typically end the call, send a payment link by email, and ask the customer to complete checkout separately. That break in the conversation costs conversions. Customers who are ready to pay during the call do not always come back. Shuttle closes this gap by acting as the compliant payment capture layer your application hands the payment to, without requiring Lindy to become a payments platform.
How Shuttle Works with Lindy Today
There is no native Lindy integration. The handoff is API-driven and built on Shuttle's Twilio-based capture: you must be a Twilio customer, and your application code triggers the handoff at the point of payment via webhook. For non-voice channels, Shuttle provides hosted payment links. The flow for a voice call is straightforward:
Gaia runs the call and handles the full conversation: qualification, product explanation, pricing, and any objections. When the customer confirms they want to pay, the workflow reaches the payment handoff point.
Your application triggers Shuttle via a webhook or API call, passing session context (amount, currency, customer reference, routing rules).
A secure PCI capture takes the card. At the point of payment, the card is captured in a secure PCI DSS Level 1 capture (today, via Twilio Pay, with Shuttle as the certified connector). The customer keys their card number on their phone keypad, and the digits are captured directly inside Shuttle's certified environment. The card number is never spoken aloud and never reaches Lindy or Gaia.
Shuttle processes and routes the transaction to your chosen payment gateway, applies any per-tenant or per-merchant routing rules, and handles authorisation and confirmation.
Shuttle returns the result to your application. Gaia receives a success or failure signal and continues the conversation accordingly, confirming the payment, offering a receipt, or handling a retry.
Card data never enters Lindy at any point in this flow. Lindy and Gaia remain entirely outside PCI scope, which simplifies your compliance obligations significantly.
One honest caveat to set expectations: the secure capture at the point of payment is live now. Shuttle being present for the entire call is not yet turnkey. Returning the caller to the same Gaia 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. A carrier-agnostic version, which removes the Twilio requirement, is landing later in 2026. You also need some technical resource: Shuttle provides ready-made interfaces for payment links plus the capture and APIs, and you build the agent-side wiring against Shuttle's sandbox gateway for the proof of concept. A native Lindy integration is possible only as a paid project.
Multi-PSP Support
Shuttle connects to 30+ gateways through a single integration. You are not locked to one processor: Stripe, Adyen, Worldpay, Checkout.com, Braintree, Square, and Mollie are all supported, alongside regional and specialist processors. Switching gateway is configuration, not re-integration. A few gateways (Braintree, for example) work for payment links but not for voice capture, because they will not allow raw card data to be passed.
For teams building multi-client or multi-tenant Gaia deployments, Shuttle supports per-tenant payment routing. Each client or business unit can use its own gateway credentials, settlement account, and currency configuration, while sharing the same Lindy workflow template. You can also bring your existing gateway relationship rather than switching processors, and Shuttle handles failover between processors if a primary gateway is unavailable.
This is particularly useful for agencies building Lindy-powered voice agents across multiple customers, where each customer needs payments to settle into their own merchant account.
PCI Compliance
Shuttle is a PCI DSS Level 1 Service Provider, the highest certification tier for payment processors. The practical implication for your Lindy deployment is scope reduction.
Because Shuttle handles all cardholder data capture, storage, and transmission, your Lindy environment and your Gaia agents are not in scope for PCI DSS. You move from SAQ-D (the most demanding self-assessment questionnaire, covering full cardholder data environments) toward SAQ-A (the lightest category, applicable when all capture is outsourced to a certified provider). Your annual compliance effort shrinks substantially.
Shuttle does not vault card data on your behalf. Card numbers are passed directly to your gateway for authorisation and are not stored in Shuttle's infrastructure after the transaction. This no-vault posture reduces the attack surface further and keeps Shuttle's own PCI scope tight.
Beyond the Call: Payment Links
Gaia is not the only channel where Lindy agents operate. Lindy runs across email, Slack, Teams, and thousands of other connected apps via Pipedream's 5,000+ integrations. For these non-voice channels, Shuttle provides hosted payment links.
A Lindy email or Slack agent can generate a Shuttle payment link as part of an automated workflow, insert it into a message, and send it to the customer. The customer clicks through to a Shuttle-hosted checkout page, enters card details there, and the result is returned to your application for downstream processing. No card data passes through Lindy's environment at any point. Payment links are the turnkey path: they can be sent by SMS or email, including mid-call, and work even with gateways that do not support voice capture.
This means a single Lindy workflow can handle both the conversation and the payment across channels: voice via Gaia with the secure capture, and email or messaging via hosted payment links.
Use Cases
Inbound Sales and Order Taking
Gaia agents handling inbound sales calls frequently reach a point where the customer is ready to buy. Rather than ending the call and sending a follow-up email, your application can hand off to Shuttle's secure capture at the point of payment. The customer keys their card on the keypad, the transaction is authorised, and the result is confirmed. Capturing payment while intent is highest converts better than post-call payment requests. For flows where you would rather avoid the keypad capture entirely, a payment link sent mid-call by SMS is the turnkey alternative.
Outbound Collections and Payment Plans
Outbound Gaia agents used for debt collection or account recovery can present balance information, negotiate payment plans, and then collect the first payment in the same call. Shuttle supports instalment structures and recurring payment setups, so a collections agent can lock in a plan and take the initial payment without requiring the customer to visit a portal or wait for a link.
Appointment Deposits
Service businesses using Gaia to handle booking calls often require a deposit to confirm an appointment. Shuttle allows Gaia to collect the deposit at the end of the booking conversation, reducing no-shows and removing the friction of a separate payment step that customers frequently abandon.
Subscription and Renewal Payments
Lindy's workflow automation is well suited to subscription management: renewal reminders, failed payment retries, and plan upgrade conversations. Where those workflows involve Gaia calls, Shuttle handles the card capture for renewal or upgrade payments, with the result fed back into Lindy's CRM and billing workflows.
FAQ
Does Lindy process payments natively? No. Lindy does not have a customer-facing payment capture product. Its Stripe integration is read-only workflow automation: it triggers on Stripe events (payments received, invoices created) and retrieves invoice or refund data for use in Lindy workflows. It is not a mechanism for charging a Lindy user's customers and does not handle cardholder data.
Does Shuttle have a native Lindy integration? No. There is no native Lindy integration today. The handoff is API-driven: your application invokes Shuttle's Twilio-based secure capture (Shuttle is Twilio's preferred payments partner) at the point of payment. A native Lindy integration is possible only as a paid project.
Does this require Twilio? Yes, today. The secure capture currently runs over Twilio Pay, so you must be a Twilio customer. A carrier-agnostic version that removes the Twilio requirement is landing later in 2026.
How do I take PCI-compliant payments on Lindy Gaia? Connect Shuttle to your workflow via webhook or API. When the workflow reaches the payment moment in a call, your application triggers Shuttle, which handles the card in a secure PCI DSS Level 1 capture (today, via Twilio Pay). Card data never enters Lindy or Gaia. Shuttle processes the transaction against your chosen gateway and returns a success or failure signal to the workflow.
Which gateways does Shuttle support? Shuttle connects to 30+ gateways, including Stripe, Adyen, Worldpay, Checkout.com, Braintree, Square, and Mollie. You can bring your existing gateway or use a new one. Switching gateway is configuration, not re-integration. Per-tenant routing is supported for multi-client deployments. A few gateways (Braintree, for example) work for payment links but not for voice capture.
Does this work for outbound calls? Yes. Gaia outbound calls follow the same pattern as inbound. The Shuttle capture is triggered by your application when the workflow reaches the payment point, regardless of whether the call was initiated by the agent or the customer.
Can Lindy's Stripe integration capture customer card payments? No. The Stripe connection in Lindy is an event-driven workflow automation tool. It listens for Stripe webhooks (a payment succeeded, an invoice was created, a refund was issued) and uses that data to trigger or inform other Lindy workflows. It does not provide a mechanism for a Gaia agent to initiate a charge against a customer's card, and it does not handle cardholder data in any form. For actual card capture, a dedicated PCI-compliant layer like Shuttle is required.
Related Reading
The Payment Layer for AI Agents: how a compliant payment layer fits into AI agent infrastructure
AI Voice Agent PCI Payments: secure card capture and PCI scope reduction for voice agents
Voice Payments: end-to-end guide to PCI-compliant payment capture over phone and IVR
Vapi Payments: adding payment capture to Vapi AI voice agents
Bland AI Payments: payment integration for Bland AI phone agent deployments
Add Payments to Your Lindy Agents
Shuttle is a PCI DSS Level 1 Service Provider with connections to 30+ gateways. Voice pricing is $0.20 per successful transaction with no setup fees, monthly fees, or per-seat charges; payment links are currently free, with a new model coming (see pricing). Your Lindy environment stays out of PCI scope, Gaia agents take payment at the point of capture, and card data never touches Lindy's infrastructure.
See Voice Checkout | Book a discovery call