> ## 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.

# Razorpay Voice AI Integration Guide

> Connect DialNexa voice AI with Razorpay to answer payment-status questions, send safe payment links, and route failed-payment follow-up.

The **Razorpay voice AI integration** helps Indian businesses handle payment questions without asking callers to share sensitive payment credentials. Use it to look up an approved payment or invoice status, send a trusted payment link, and route disputes or refunds to a person.

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

## When to use the Razorpay voice AI integration

Use Razorpay when:

* Customers call about UPI, card, netbanking, payment-link, or invoice status.
* Collections teams need a safe way to send a fresh payment link after a call.
* Failed or pending payments should create a traceable follow-up.
* Refunds, disputes, and suspicious payments must reach a trained person.

<Tip>
  **Best first workflow:** Verify the customer using your own account data, read the status of one known payment or invoice, and send an official payment link when money is still due.
</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 Razorpay 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 Razorpay

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

## Build the Razorpay 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 Razorpay

* Internal customer or order ID plus the matching Razorpay customer, payment, invoice, or payment-link ID
* Amount, currency, payment status, created time, and safe failure reason
* Call ID, verification result, caller request, summary, and follow-up owner
* Payment-link expiry and delivery channel when a new link is sent

## High-value Razorpay voice AI workflows

| Call outcome                            | Razorpay result                                           | Human control                                       |
| --------------------------------------- | --------------------------------------------------------- | --------------------------------------------------- |
| Customer asks whether payment succeeded | Read the status of the matched payment                    | Never request an OTP, PIN, CVV, or full card number |
| Payment is still due                    | Send an official payment link through an approved channel | Confirm amount and recipient before sending         |
| Payment failed or remains pending       | Explain the safe status and create a follow-up            | Do not promise settlement timing you cannot verify  |
| Caller requests refund or reports fraud | Record the request and escalate with payment ID           | Keep refunds and disputes human-approved            |

## Verify the Razorpay integration

Run a test call and confirm that:

1. The payment, invoice, or link belongs to the verified internal customer or order.
2. The agent reads only safe status fields and never requests an OTP, PIN, CVV, or card number.
3. A sent payment link has the correct amount, recipient, expiry, and trusted domain.
4. The DialNexa call ID prevents duplicate links or follow-up actions.
5. Failed, disputed, suspicious, and refund requests create a visible human-owned task.

## Troubleshoot Razorpay integration issues

| Problem                                | What to check                                                                                                                                     |
| -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| Razorpay 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                                                                    |
| Payment or invoice is not found        | Match using your internal order or customer reference plus the exact Razorpay ID                                                                  |
| Duplicate links or actions 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)