# What Are Voice Payments? The Complete Guide | Shuttle

> Voice payments are transactions completed during a phone call, through an IVR system, a live agent, or an AI voice agent, where card data is captured...

Web page: https://www.shuttleglobal.com/guides/voice-payments/

# What Are Voice Payments? The Complete Guide

By Shuttle Team, February 20, 2026

Voice payments are transactions completed during a phone call, through an IVR system, a live agent, or an AI voice agent, where card data is captured securely without the business handling or storing it.

The customer stays on the call. They enter card details via keypad tones (DTMF). The payment is routed to a gateway, processed, and confirmed, all within the conversation. For the full setup, see how to take payments on Twilio.

What makes voice payments different from a standard card-not-present transaction is the channel. The customer is mid-conversation. They're not redirected to a checkout page. The payment happens inside the voice flow, which creates specific challenges around PCI compliance, audio security, and gateway connectivity that web checkout doesn't face.

Voice payments aren't new. IVR payment lines have existed for decades. What's changed is the context: AI voice agents now handle customer calls, contact centres are under pressure to automate, and platforms are embedding payments into workflows that previously had no payment capture at all. For outsourced parking, civil enforcement and toll operators specifically, see Payment Collection for Parking, Enforcement and Toll Operators.

## Why Voice Payments Matter Now

Three forces are converging:

1. Contact centres need to automate payment capture. Every payment call creates PCI exposure: agents hearing card numbers, call recordings containing sensitive data, and manual processes that don't scale. Automating secure payment capture mid-call reduces the compliance burden and frees agents to focus on the conversation.

2. AI voice agents are creating entirely new payment channels. Companies like PolyAI are deploying AI agents across regulated industries. These agents can qualify, sell, and service customers, but until recently, they couldn't close a payment. Voice payment infrastructure turns AI agents into revenue channels.

3. Payments are moving inside software workflows. The checkout page is no longer the only place a payment happens. Payments now occur inside IVR trees, during agent conversations, in AI-driven workflows, and via SMS links sent mid-call. Businesses that can capture payments wherever a conversation happens have a structural advantage over those that force customers to "go online and pay."

## Three Models of Voice Payment

Not all voice payments work the same way. The model you choose depends on who's on the call, what level of automation you need, and how you handle PCI scope.

### 1. IVR Payments (Automated)

The customer calls in and navigates a menu system. When they reach the payment step, the IVR prompts them to enter card details via keypad (DTMF tones). The system captures the digits, processes the transaction, and confirms, all without a human involved. For the full picture on automated self-service flows, see IVR Payments.

Best for: High-volume, repeat payments (utility bills, insurance premiums, account top-ups) PCI consideration: DTMF tones must be captured within a PCI-compliant environment and stripped from any recordings or monitoring feeds. Limitation: Clunky customer experience. Limited to predefined flows. No flexibility for complex transactions.

### 2. Agent-Assisted Payments

A live agent handles the call. When it's time to pay, a secure card capture takes over for the payment step. The customer enters card details on their keypad inside a PCI-certified environment, so the agent never hears the card digits and they never reach your recordings.

Alternatively, the agent sends a payment link via SMS during the call. The customer completes payment on their device while the conversation continues.

Best for: Sales calls, collections, complex transactions where a human guides the process PCI consideration: The critical requirement is that the agent never hears, sees, or has access to card data. Capturing the card inside a certified payment environment, rather than your own telephony, is what limits your PCI scope. Advantage: Combines the trust and flexibility of a human conversation with secure, compliant payment capture.

### 3. AI Voice Payments (Autonomous)

An AI voice agent handles the entire conversation, including payment. When the customer is ready to pay, the AI agent triggers a secure payment capture flow. Card details are entered via DTMF or a payment link is sent via SMS. The transaction is processed and confirmed within the conversation. No human handoff required.

Best for: AI-first contact centres, autonomous sales agents, high-volume transaction processing PCI consideration: Same as agent-assisted. Card data must be captured within a PCI-compliant environment, never processed by the AI model itself. Why this matters: AI voice payments don't replace an existing channel. They create a new one. Businesses that deploy AI agents with payment capability unlock revenue from conversations that previously ended with "please visit our website to pay."

For a deeper look at how AI agents handle PCI-compliant payments, see our guide on how AI voice agents take PCI-compliant payments.

## PCI Compliance: The Non-Negotiable

Every voice payment implementation lives or dies on PCI compliance. There is no workaround, no shortcut, and no "we'll deal with it later." If card data touches your infrastructure, even for a moment, you're in scope.

### What PCI Compliance Means for Voice

The core principle: Card data must never be heard by agents, stored in recordings, processed by your systems, or accessible through your infrastructure.

In practice, this means:

- The card is captured inside a PCI-certified environment, not your telephony stack, so the digits never reach the agent or your recordings
- Only redacted data (last four digits, transaction status) is returned to your systems
- Call recordings contain no payment card data
- Your PCI scope is heavily reduced. Merchants complete SAQ-A, the lightest self-assessment, and platforms complete SAQ-D; everyone taking card payments has to be PCI compliant
### The Cost of Getting It Wrong

PCI DSS Level 1 certification, the kind a voice payment provider needs, is expensive to achieve and maintain. That includes the annual audit, infrastructure, personnel, and operational controls.

For a platform or contact centre, the question isn't whether you can afford PCI compliance. It's whether you should carry that burden at all, or use a provider whose certification covers the payment segment of the call.

### What to Look For

- PCI DSS Level 1 Service Provider certification, not Level 2, not self-assessed
- Card capture inside the certified environment, so the digits are never decodable from your recordings or systems
- No card data in your environment
- ISO 27001 and SOC 2 as additional assurance (these cover operational security beyond PCI)
## The Multi-PSP Reality

Here's where voice payments get complicated for enterprise businesses.

Most voice payment vendors lock you into a single payment gateway. That works if all your transactions route through one processor. It breaks the moment an enterprise customer says: "We need Worldpay for our UK business and Stripe for our US business."

This is the same dynamic playing out across embedded payments: enterprise customers mandate specific PSPs by product line or by contractual obligation. A voice payment solution that only connects to one gateway becomes a ceiling on your growth.

### What Multi-PSP Voice Payments Look Like

A PSP-neutral voice payment layer connects to multiple gateways through a single integration. The platform, contact centre, or AI agent doesn't need to know which gateway processes a given transaction. Provider selection is a configuration, set per merchant and payment type.

This means:

- Enterprise customers can use their own PSP, if it is a compatible gateway
- Multiple business entities can each keep their own gateway
- Adding a new gateway doesn't require re-engineering your voice payment flow
- Gateway failures are handled by moving 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
For contact centres and platforms serving mid-market and enterprise merchants, PSP flexibility isn't a nice-to-have. It's the difference between winning and losing the account.

## AI Voice Payments: The New Frontier

Late 2025 is when AI agent payments started moving from theory to production.

Stripe launched its Agentic Commerce Suite. Google announced AP2 (Agent Payments Protocol) with over 60 partners including Adyen, Mastercard, and PayPal. Worldline connected AI agents to its global payment ecosystem via MCP servers. Visa and Aldar completed an end-to-end voice-enabled agentic payment in the UAE.

The infrastructure layer is forming. AI agents need the ability to:

- Initiate a payment flow within a conversation
- Capture card data securely (via DTMF, speech-to-text within a PCI environment, or payment link)
- Route the payment to the gateway you configured
- Confirm the result back to the customer in natural language
The critical point: the AI model itself must never process card data. Payment capture happens in a parallel PCI-compliant environment that the AI agent triggers but doesn't control. The agent handles the conversation. The Payment Layer handles the money.

Companies like PolyAI are already processing payments this way, with fully automated voice payments across regulated industries.

This isn't a future state. It's production today. For the full picture of how AI agents and payments are converging, see The Payment Layer for AI Agents.

## Payment Methods Over Voice

Voice payments aren't limited to card numbers entered via keypad.

### Cards (DTMF)

The most common method. The customer enters card digits via keypad tones during the call. Real-time BIN validation and Luhn checks confirm the card before processing. Supports Visa, Mastercard, Amex, and other major schemes.

### Cards (spoken aloud)

Card data spoken aloud is a compliance problem, not a capture method. The audio, the call recording and any transcript all enter PCI scope, which is why Shuttle captures card data on the keypad instead.

### ACH & Bank Transfers

Account and routing numbers captured via voice prompts. Supports ACH (US, through Authorize.net) and UK Direct Debit (through GoCardless).

### Payment Links & Digital Wallets

When a phone payment isn't practical (or when the customer prefers Apple Pay, Google Pay, or PayPal), a branded payment link is sent via SMS or email during the call. The customer completes payment on their device while the conversation continues. This bridges voice and digital channels without friction.

## How to Choose a Voice Payment Solution

Not all solutions are built the same. Here's what to evaluate:

### 1. PCI Certification Level

Ask: Are you PCI DSS Level 1 certified as a Service Provider? Why: Level 1 is the highest certification. Anything less is a risk, especially for enterprise or regulated industries. For a detailed breakdown of what Twilio PCI compliance covers (and what it doesn't), see our dedicated guide.

### 2. Gateway Coverage

Ask: How many payment gateways do you support? Can we bring our own PSP? Why: If you serve enterprise customers or operate across regions, single-gateway solutions will limit you. Look for 30+ PSP support. (Note: a few gateways, such as Braintree, won't allow raw card data over voice, so they work for payment links but not for keypad capture. Confirm voice support for the specific gateways you need.)

### 3. Channel Coverage

Ask: Do you support IVR, agent-assisted, and AI voice? What about SMS payment links? Why: Your needs will evolve. A solution that only handles IVR today won't serve you when you deploy AI agents tomorrow.

### 4. Carrier Requirements

Ask: Which telephony provider does the solution require today, and which carriers does it work with? Why: Voice capture is often tied to a specific carrier today. Shuttle's secure voice capture, for example, runs on Twilio Pay or Telnyx <Pay> today, so using it for voice means having a Twilio or Telnyx account. Shuttle works with Twilio and Telnyx today, and any carrier coming soon. On Telnyx, in-call payments are cards or ACH. Knowing the current requirement avoids surprises.

### 5. Integration Complexity

Ask: How long does integration take, and what does my team need to build? Why: Be wary of fixed go-live promises. Payment links are typically the quickest path because they need no telephony work. Voice and AI-agent flows usually involve building your own agent-side interface against the provider's capture, IVR, and APIs, and the effort depends on your stack. Ask for an honest scope rather than a headline timeline.

### 6. White-Label Capability

Ask: Can we brand the payment experience? Will our customers know a third party is involved? Why: For platforms embedding voice payments into their product, white-labelling is essential. The end customer should experience your brand, not your payment provider's.

## FAQ

What's the difference between voice payments and phone payments? They're often used interchangeably. "Voice payments" is the broader term covering any payment initiated during a voice interaction: IVR, agent-assisted, or AI-driven. "Phone payments" typically refers to the simpler case of paying over a phone call.

Are voice payments PCI compliant? They can be, but only if card data is captured within a PCI-certified environment and never touches your systems. Using a PCI DSS Level 1 certified provider is the most reliable way to limit your PCI scope.

How long does it take to set up voice payments? It depends on the path. Payment links are the quickest because they need no telephony work. Voice capture involves building your own agent-side interface against the provider's capture, IVR, and APIs, and the effort depends on your stack and platform, so treat any fixed "go live in X weeks" claim with caution and ask for a scoped estimate.

Can AI agents take payments? Yes. AI voice agents can trigger secure payment capture flows during a conversation. The AI handles the dialogue; a PCI-compliant Payment Layer handles the card data. This is in production today with providers like PolyAI.

Do customers trust paying over the phone? Trust increases when the process is smooth and secure. DTMF capture (keypad entry) is familiar, and SMS payment links offer an alternative for customers who prefer a visual checkout.

What if my customer's gateway isn't supported? This is a common limitation with single-gateway voice payment providers. PSP-neutral solutions that support 30+ gateways reduce this problem, provided the customer's PSP is a compatible gateway. One caveat: a few gateways (such as Braintree) won't allow raw card data over voice, so they work for payment links but not for keypad capture.

## Related Reading

- PCI Compliant Phone Payments: How to Take Card Payments Over the Phone - how to limit the PCI scope of card payments by phone
- How AI Voice Agents Take PCI-Compliant Payments: technical deep dive on DTMF capture, secure handoff architecture, and voice agent PCI compliance
- The Payment Layer for AI Agents: why AI agents need a payment layer, not a payment provider
- PCI-Compliant Payments for Contact Centres: the full guide for human and AI agent payment flows
- Voice AI Is Booming, But Can It Take a Payment? (the infrastructure gap between conversational AI and payment capability)
- Gateway vs Orchestrator vs PayFac vs Payment Layer: how the four categories of payment infrastructure compare
- Payment Links for Hotels & Holiday Accommodation: how hotels use payment links alongside voice channels for deposits and no-shows
- Prommt Alternatives for Platforms: comparing payment link providers for multi-merchant and multi-channel use cases
- How Voice AI Ordering Platforms Handle Payments: why voice AI for restaurant ordering can't solve the payment problem alone
- Payment Infrastructure for Food Ordering Platforms: multi-PSP routing for food delivery, ghost kitchens, and ordering platforms
- Twilio Pay Connectors: How to Connect Any Compatible Payment Gateway to Twilio: connecting Twilio to any compatible PSP via Pay Connectors
- Twilio PCI Compliance: How to Take Payments Without Handling Card Data (PCI scope, DTMF capture, and compliance architecture for Twilio)
- How to Connect Stripe to Twilio for Voice & IVR Payments: step-by-step Stripe + Twilio integration guide
- Twilio Pay: Connect Any Compatible Payment Gateway to Twilio: install the Pay Connector, 30+ gateways, $49 per live instance per month, billed by Shuttle, plus from $0.20 per transaction, falling with volume, billed through Twilio
- Vapi Payments: PCI-compliant payment capture for Vapi voice agents
- Bland AI Payments: secure payment capture for Bland AI phone agents
- ElevenLabs Payments: native Stripe vs multi-PSP for ElevenLabs agents
- Synthflow Payments: native Stripe vs multi-PSP for Synthflow voice agents
- Phonely Payments: PCI-compliant payment capture for Phonely AI phone agents
- Sierra AI Payments: native Level 1 PCI payments vs a multi-PSP layer
- Parloa Payments: native Payment Skill vs multi-PSP capture
- Decagon Payments: verified PCI-compliant capture for Decagon AI agents
- Kore.ai Payments: PCI-compliant in-call capture for Kore.ai agents
- Yellow.ai Payments: in-call DTMF capture vs payment links on VoiceX
- Regal.ai Payments: in-call capture for outbound collections calls
- Voiceflow Payments: PCI-compliant capture for Voiceflow voice and chat agents
- Thoughtly Payments: in-call card capture for Thoughtly AI voice agents
- boost.ai Payments: multi-PSP capture for boost.ai virtual agents
- Gupshup Payments: native UPI and WhatsApp Pay vs multi-PSP card capture
- Ada Payments: PCI-compliant capture for Ada AI voice and chat agents
- Lindy Payments: in-call capture for Lindy Gaia phone agents
Shuttle Voice Checkout connects your IVR, agent, or AI voice flows to 30+ payment gateways with PCI DSS Level 1 compliance. Voice capture works on Twilio and Telnyx today, and any carrier coming soon. Payment links are the turnkey path that works with any supported gateway. Install on Twilio or book a discovery call.

## Take payments over the phone

Card capture for contact centres, IVR flows and AI voice agents, connected to 30+ payment gateways including Stripe, Adyen, and Worldpay Access.

Explore More

### Can You Take Card Payments on a Retell AI Voice Agent?

### Voice Payments Are an Architecture Decision, Not a Feature Request

### Sage Invoice Payments: How to Let Customers Pay Online

### Payment Links for QuickBooks Payments: Send Branded Checkout Links Beyond Email Invoices

### The Future of Voice Commerce: From IVR to Intelligent Payments

### Visa, BILL and Billtrust pilot an AI agent that pays approved supplier invoices


## Links
- [DTMF](/guides/dtmf-payments/)
- [take payments on Twilio](/integrations/twilio-pay/)
- [PCI compliance](/glossary/pci-dss/)
- [Payment Collection for Parking, Enforcement and Toll Operators](/guides/parking-enforcement-toll-payments/)
- [PCI scope](/glossary/pci-scope/)
- [IVR Payments](/guides/ivr-payments/)
- [how AI voice agents take PCI-compliant payments](/guides/ai-voice-agent-pci-payments/)
- [PCI DSS Level 1](/guides/pci-compliance-service-provider/)
- [contact centre](/guides/contact-centre-payments/)
- [payment gateway](/blog/what-is-a-payment-gateway/)
- [Worldpay](/payment-providers/worldpay-access/)
- [Stripe](/payment-providers/stripe/)
- [embedded payments](/guides/what-is-embedded-payments/)
- [enterprise customers mandate specific PSPs](/guides/enterprise-psp-mandates/)
- [PSP-neutral](/guides/psp-neutral-vs-single-psp/)
- [The Payment Layer](/guides/payment-layer-explained/)
- [The Payment Layer for AI Agents](/guides/the-payment-layer-for-ai-agents/)
- [payment link](/merchants/links-checkout/)
- [Twilio PCI compliance](/guides/twilio-pci-compliance/)
- [30+ PSP support](/payment-providers/)
- [Payment Layer](/guides/payment-layer-explained/)
- [DTMF capture](/guides/dtmf-payments/)
- [30+ gateways](/payment-providers/)
- [PCI Compliant Phone Payments: How to Take Card Payments Over the Phone](/guides/pci-compliant-phone-payments/)
- [How AI Voice Agents Take PCI-Compliant Payments](/guides/ai-voice-agent-pci-payments/)
- [PCI-Compliant Payments for Contact Centres](/guides/contact-centre-payments/)
- [Voice AI Is Booming, But Can It Take a Payment?](/blog/voice-ai-payment-infrastructure-gap/)
- [Gateway vs Orchestrator vs PayFac vs Payment Layer](/guides/payment-layer-explained/)
- [Payment Links for Hotels & Holiday Accommodation](/guides/payment-links-for-hotels/)
- [Prommt Alternatives for Platforms](/alternatives/prommt/)
- [How Voice AI Ordering Platforms Handle Payments](/guides/voice-ai-ordering-payments/)
- [Payment Infrastructure for Food Ordering Platforms](/guides/food-ordering-platform-payments/)
- [Twilio Pay Connectors: How to Connect Any Compatible Payment Gateway to Twilio](/guides/twilio-pay-connectors/)
- [Twilio PCI Compliance: How to Take Payments Without Handling Card Data](/guides/twilio-pci-compliance/)
- [How to Connect Stripe to Twilio for Voice & IVR Payments](/guides/stripe-twilio-integration/)
- [Twilio Pay: Connect Any Compatible Payment Gateway to Twilio](/integrations/twilio-pay/)
- [Vapi Payments](/guides/vapi-payments/)
- [Bland AI Payments](/guides/bland-ai-payments/)
- [ElevenLabs Payments](/guides/elevenlabs-payments/)
- [Synthflow Payments](/guides/synthflow-payments/)
- [Phonely Payments](/guides/phonely-payments/)
- [Sierra AI Payments](/guides/sierra-payments/)
- [Parloa Payments](/guides/parloa-payments/)
- [Decagon Payments](/guides/decagon-payments/)
- [Kore.ai Payments](/guides/kore-ai-payments/)
- [Yellow.ai Payments](/guides/yellow-ai-payments/)
- [Regal.ai Payments](/guides/regal-ai-payments/)
- [Voiceflow Payments](/guides/voiceflow-payments/)
- [Thoughtly Payments](/guides/thoughtly-payments/)
- [boost.ai Payments](/guides/boost-ai-payments/)
- [Gupshup Payments](/guides/gupshup-payments/)
- [Ada Payments](/guides/ada-payments/)
- [Lindy Payments](/guides/lindy-payments/)
- [30+ payment gateways](/payment-providers/)
- [Install on Twilio](/integrations/twilio-pay/)
- [book a discovery call](/discovery/)
- [Get Started with Twilio Pay](/integrations/twilio-pay/)
- [Book a Call](/discovery/?product=voice-checkout)
- [BlogCan You Take Card Payments on a Retell AI Voice Agent?→](/blog/can-you-take-card-payments-on-a-retell-ai-voice-agent/)
- [BlogVoice Payments Are an Architecture Decision, Not a Feature Request→](/blog/voice-payments-architecture-decision/)
- [BlogSage Invoice Payments: How to Let Customers Pay Online→](/blog/sage-invoice-payments/)
- [BlogPayment Links for QuickBooks Payments: Send Branded Checkout Links Beyond Email Invoices→](/blog/payment-links-for-quickbooks-payments/)
- [BlogThe Future of Voice Commerce: From IVR to Intelligent Payments→](/blog/the-future-of-voice-commerce/)
- [BlogVisa, BILL and Billtrust pilot an AI agent that pays approved supplier invoices→](/blog/visa-bill-billtrust-ai-agent-supplier-payments/)