> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dialai.ca/llms.txt
> Use this file to discover all available pages before exploring further.

# Phone payments

> Take a card payment from the caller during a voice call, without the card number ever touching Dial AI

<Frame caption="The caller is transferred to a secure line to enter their card, and your payment provider charges it through its API">
  <img className="block dark:hidden" src="https://mintcdn.com/dialai/sweGC_bgB-FJYwZy/images/phone-payments-light.svg?fit=max&auto=format&n=sweGC_bgB-FJYwZy&q=85&s=3026e3f297ce13ba3e46278e43c4d31f" alt="How phone payments work, light mode" width="1040" height="470" data-path="images/phone-payments-light.svg" />

  <img className="hidden dark:block" src="https://mintcdn.com/dialai/sweGC_bgB-FJYwZy/images/phone-payments-dark.svg?fit=max&auto=format&n=sweGC_bgB-FJYwZy&q=85&s=98958fc57ecb8e59bb56a05644de4b73" alt="How phone payments work, dark mode" width="1040" height="470" data-path="images/phone-payments-dark.svg" />
</Frame>

Your voice agent can take a payment right on the call. When a caller is ready to pay a balance, the agent hands them to a **secure card capture**, the card is charged through your existing payment provider, and the agent picks the conversation back up with the result. Dial AI never sees the card number.

## How it works

<Steps>
  <Step title="The agent offers to take payment">
    During a voice call, when the caller is ready to pay their balance, the agent offers to take the payment and hands the call to secure capture.
  </Step>

  <Step title="The caller enters their card on a secure line">
    The caller is moved to a secure line to key in their card number, expiry, and security code. The conversation is **paused**, not ended, so the agent is still there when it finishes.
  </Step>

  <Step title="Your payment provider charges the card">
    The captured card goes to your existing payment provider and is charged through its API. Dial AI only ever handles tokenized references, never the raw card number.
  </Step>

  <Step title="The agent resumes with the result">
    The call reopens and the agent continues with the outcome: a confirmation code and the last four digits on success, or a failure it can retry or route around. The result is available to the rest of the conversation.
  </Step>
</Steps>

## What the caller hears

The caller is told the payment is being taken securely, then enters their card on the phone. The capture prompts (card number, expiry, security code) are spoken inside the call, and their wording can be tailored to match your brand.

<Note>
  Phone payments run on **voice** calls only, and the amount must be greater than zero. Saving a card for later use is not supported yet.
</Note>

## Security

* **Dial AI never sees the card number.** The capture is owned by your telephony and payment providers, and the platform only ever handles tokenized aliases.
* **Payments run through your existing provider.** Nothing changes about who processes the money or settles it. Dial AI just orchestrates the hand-off.
* **The card is never on the recording.** Call recording is stopped before the capture and restarted after, so the digits the caller keys never land on tape.

## Related

<CardGroup>
  <Card title="Agent Voice" icon="microphone" href="/agent-voice">Configure your voice agent.</Card>
  <Card title="Conversations" icon="messages" href="/conversations">Review calls, including the card-payment step.</Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.