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

# How Emandate Works

> Know how to integrate Recurring Payments using Emandate as a payment method.

Available in
🇮🇳 India

Emandate lets you debit a customer's bank account automatically after they register a mandate once using Aadhaar, netbanking or a debit card.

## Prerequisites

* Emandate is enabled by default. If it is not active on your account, contact [Razorpay Support](https://razorpay.com/support/).
* Use the [Fetch Payment Methods API](https://razorpay.com/docs/payments/payment-gateway/s2s-integration/recurring-payments/emandate/authorization-transaction.md#1-1-1-fetch-payment-methods) to verify supported payment methods.
* Ensure the required banks from the [List of Supported Banks](https://razorpay.com/docs/payments/payment-gateway/s2s-integration/recurring-payments/emandate/supported-banks.md) are enabled for your account.

## Authentication Types

When setting up an Emandate, customers can authenticate the registration using one of three methods depending on their preferences.

* **Aadhaar-based authentication** (recommended): Provides real-time registration and instant confirmation.
* **Netbanking authentication**: Redirects customers to their bank's internet banking portal for credential-based verification.
* **Debit card authentication**: Allows customers to verify using their card details and OTP.

> [!NOTE]
>
> **Handy Tips**
>
> Razorpay's real-time Aadhaar Emandate registration solution eliminates the traditional 2-4 day manual approval process, delivering instant registration confirmation in minutes.
>
> By streamlining the authentication flow, Razorpay reduces failed first debits and customer drop-off, providing immediate status visibility to both businesses and customers.

> [!NOTE]
>
> **Handy Tips**
>
> For mandate amounts above ₹50,000 (effective July 1, 2026), the customer must complete a second OTP verification as part of Aadhaar authentication.

## Integration Steps

Integrate Emandate using Razorpay APIs in these steps:

1. [Create the Authorisation Transaction](https://razorpay.com/docs/payments/payment-gateway/s2s-integration/recurring-payments/emandate/authorization-transaction.md): register the customer's Emandate. The recurring token is created when this payment is captured.
2. [Fetch and Manage Tokens](https://razorpay.com/docs/payments/payment-gateway/s2s-integration/recurring-payments/emandate/tokens.md): check that the mandate is registered and track the token status.
3. [Create Subsequent Payments](https://razorpay.com/docs/payments/payment-gateway/s2s-integration/recurring-payments/emandate/subsequent-payments.md): charge the customer on the confirmed token whenever a payment is due.
4. [Webhooks](https://razorpay.com/docs/payments/payment-gateway/s2s-integration/recurring-payments/webhooks.md): subscribe to webhooks to track token and payment status changes.

To register the Emandate and charge the first payment together, see [Register Emandate and Charge First Payment Together](https://razorpay.com/docs/payments/payment-gateway/s2s-integration/recurring-payments/emandate/auto-debit.md).

## Authorisation Payment Statuses

Once the customer has made the Authorisation Payment, it moves through the following states:

| Status | Description | Webhook |
| - | - | - |
| Created | Payment is created when a customer enters and submits the payment information. | NA |
| Authorized | Payment is authorized when the customer's payment details are successfully authenticated by the bank. | [payment.authorized](https://razorpay.com/docs/payments/payment-gateway/s2s-integration/recurring-payments/webhooks.md#payment-authorized) |
| Captured | Indicates that the payment is verified by you. Once a payment is captured you can [retrieve the recurring token](https://razorpay.com/docs/payments/payment-gateway/s2s-integration/recurring-payments/dashboard.md#3-search-for-the-token). | [payment.captured](https://razorpay.com/docs/payments/payment-gateway/s2s-integration/recurring-payments/webhooks.md#payment-captured) or [order.paid](https://razorpay.com/docs/payments/payment-gateway/s2s-integration/recurring-payments/webhooks.md#order-paid) |
| Failed | Indicates that the payment has failed. If the payment has failed, you need to [create an authorisation transaction](https://razorpay.com/docs/payments/payment-gateway/s2s-integration/recurring-payments/emandate/authorization-transaction.md) again. | [payment.failed](https://razorpay.com/docs/payments/payment-gateway/s2s-integration/recurring-payments/webhooks.md#payment-failed) |

## Token Statuses

As the authorisation transaction moves through its different states, the recurring token that is generated also undergoes state changes. Following is the life cycle of a recurring token:

| `token_status` | Description | Next Step |
| - | - | - |
| `initiated` | Indicates that the bank is processing the mandate registration. | Wait for the [token.confirmed](https://razorpay.com/docs/payments/payment-gateway/s2s-integration/recurring-payments/webhooks.md#token-confirmed) webhook. |
| `confirmed` | Indicates that the bank has completed the mandate registration. | [Create recurring payment](https://razorpay.com/docs/payments/payment-gateway/s2s-integration/recurring-payments/dashboard.md) |
| `rejected` | Indicates that the mandate registration has failed. | Create the authorisation transaction again. |
| `cancelled` | Indicates that the recurring token has been cancelled. | Create the authorisation transaction again if you want to charge the customer. |

Know more about the turnaround time (TAT) for Emandate from the [FAQs](https://razorpay.com/docs/payments/payment-gateway/s2s-integration/recurring-payments/emandate/faqs.md).

## Charge Customers

Once a recurring token goes to the `confirmed` state, you can create subsequent payments without any intervention from the customer. Subsequent payments need to be created by you, using [Create Subsequent Payments](https://razorpay.com/docs/payments/payment-gateway/s2s-integration/recurring-payments/emandate/subsequent-payments.md). In some cases, the payment entity returned is in the `created` state and may take up to 2 working days for confirmation.

### Related Information

* [Supported Banks](https://razorpay.com/docs/payments/payment-gateway/s2s-integration/recurring-payments/emandate/supported-banks.md)
* [Error Codes](https://razorpay.com/docs/payments/payment-gateway/s2s-integration/recurring-payments/emandate/error-codes.md)
* [FAQs](https://razorpay.com/docs/payments/payment-gateway/s2s-integration/recurring-payments/emandate/faqs.md)
* [Webhooks](https://razorpay.com/docs/payments/payment-gateway/s2s-integration/recurring-payments/webhooks.md)
