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

# Stripe Voice AI Integration Guide

> Connect DialNexa voice AI with Stripe to answer billing questions, check invoices and subscriptions, and send secure payment links.

The **Stripe voice AI integration** lets billing and support calls use current customer, invoice, subscription, and payment context. Keep the agent focused on status and safe next steps while sensitive billing changes remain controlled.

<Warning>
  A catalog page describes a possible workflow. It does not confirm that a native Stripe connector is enabled in your workspace. Check **Integrations** in the DialNexa dashboard first. If Stripe is not listed, use a custom function, agent webhook, or external automation service.
</Warning>

## When to use the Stripe voice AI integration

Use Stripe when:

* Customers call about invoices, subscriptions, failed payments, or receipts.
* The agent should read only the billing fields needed to answer the question.
* A failed-payment call should create a traceable recovery step.
* Cancellations, refunds, credits, and plan changes require clear approval rules.

<Tip>
  **Best first workflow:** Match the verified customer, read the latest invoice and subscription status, then send a Stripe-hosted payment link or route the requested account change to billing staff.
</Tip>

## Before you begin

Prepare the following:

* A published DialNexa agent that has already passed a basic test call.
* Access to the DialNexa workspace **Integrations** page.
* A Stripe account with permission to read or update the required records.
* One test record that does not affect a live customer.
* A list of actions that can run automatically and actions that require human review.

## Choose how to connect Stripe

| Connection method                                   | Use it when                                              | Important limit                                                             |
| --------------------------------------------------- | -------------------------------------------------------- | --------------------------------------------------------------------------- |
| Workspace connector                                 | Stripe appears in your DialNexa **Integrations** page    | Available actions and authentication depend on your workspace               |
| [Custom function](/docs/agent-settings/custom-functions) | The agent needs Stripe data during the live conversation | Keep the request fast and return only the fields the agent needs            |
| [Agent webhook](/docs/api-access/agent-webhooks)         | Stripe should receive a result after the call            | Your endpoint must authenticate, retry safely, and prevent duplicate writes |
| External automation                                 | The workflow spans Stripe and several other systems      | Monitor the external workflow separately from the DialNexa call             |

## Build the Stripe voice AI workflow

1. Define the exact event that starts the action, such as a confirmed booking, qualified lead, support escalation, or completed call.
2. Choose the connection method from the table above.
3. Map caller identity, the DialNexa call ID, the verified outcome, and the destination record ID.
4. Add a condition so uncertain, sensitive, destructive, or high-value changes go to a human-owned queue.
5. Store the destination record URL or ID with the call result so your team can trace the handoff.
6. Test success, no-match, duplicate, permission-error, and timeout cases before using live traffic.

## Data to map between DialNexa and Stripe

* Internal account ID plus Stripe customer, subscription, invoice, payment, and payment-link IDs
* Product or plan, amount due, currency, billing period, and safe status fields
* Call ID, identity-check result, requested change, disposition, and owner
* Link expiry and approved delivery channel for payment requests

## High-value Stripe voice AI workflows

| Call outcome                             | Stripe result                                           | Human control                                              |
| ---------------------------------------- | ------------------------------------------------------- | ---------------------------------------------------------- |
| Customer asks about an invoice           | Read amount, due date, and safe payment status          | Do not expose unrelated billing history                    |
| Payment failed                           | Explain the next safe step and send a hosted link       | Never collect card details by voice                        |
| Customer asks to change or cancel a plan | Capture the exact request                               | Require approval for prorations, credits, and cancellation |
| Customer disputes a charge               | Create a billing escalation with the matched payment ID | Keep dispute evidence and refunds human-owned              |

## Verify the Stripe integration

Run a test call and confirm that:

1. The Stripe customer and billing record match the verified application account.
2. The agent reads only the invoice, subscription, or payment fields required for the question.
3. Payment details are entered only on Stripe-hosted or otherwise approved secure pages.
4. The DialNexa call ID prevents duplicate links, notes, or billing requests.
5. Refunds, disputes, credits, cancellations, and failed writes reach a billing owner.

## Troubleshoot Stripe integration issues

| Problem                                    | What to check                                                                                                                                     |
| ------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| Stripe is not shown in the dashboard       | Use a custom function, webhook, or external automation service, or [request the integration](/docs/dashboard-integrations/requesting-new-integrations) |
| Authentication fails                       | Reconnect the account and verify scopes, workspace ownership, and token expiry                                                                    |
| Customer or invoice is not found           | Match your application account to a stored Stripe customer or billing record ID                                                                   |
| Duplicate links or billing requests appear | Use the DialNexa call ID as an idempotency key and make retries safe                                                                              |
| The live call becomes slow                 | Move nonessential writes to a post-call webhook and keep live lookups small                                                                       |

## Related pages

* [DialNexa integrations overview](/docs/integrations/overview)
* [Connect dashboard integrations](/docs/dashboard-integrations/connecting-integrations)
* [Use integrations in agents](/docs/dashboard-integrations/using-integrations-in-agents)
* [Use integrations in workflows](/docs/dashboard-integrations/using-integrations-in-workflows)
* [Integration workflow tutorials](/docs/tutorials/integration-workflows)