Prerequisites
- Emandate is enabled by default. If it is not active on your account, contact Razorpay Support.
- Use the Fetch Methods API to verify supported payment methods.
- Ensure the required banks from the List of Supported Banks are enabled for your account.
1. Emandate Registration
Emandate registration is a process of creating a payment checkout form for customers to make Authorisation Transaction and register their Emandate. A token will be generated once a customer makes this transaction. Using this authorisation transaction, we can authenticate the customer’s Emandate and ensure that we can charge them recurring payments.1.1 Create Authentication Transaction
The authorisation transaction can be created using:Razorpay Standard Checkout
Following is the authorisation transaction flow for Razorpay Standard Checkout method. To create checkout form for customers to complete authorisation transaction using the Razorpay Standard Checkout method:Registration Link
Registration Links are securely generated web addresses that allow your customers to complete the authorisation transaction. Registration links can be sent via SMS or email. Following is the authorisation transaction flow for Razorpay registration link method: For customers to complete the authorisation transaction via a registration link, you should create a registration link and send it to your customer You can create a Registration Link using: The customer completes the authorisation payment, which generates atoken.
No Need to Create a Customer and Order SeparatelyIf you use a registration link to create the authorisation transaction, Razorpay automatically creates a customer and the order for you.Video TutorialsWatch the below video to learn how to integrate recurring payments via the registration link method using Dashboard.Watch the below video to learn how to integrate recurring payments via the registration link method using APIs.
Registration Link Statuses
A registration link moves through the following states during its life cycle:Status | Description | Webhook
Issued | A registration Link is created and sent to the customer. | NA
Paid | Payment is made for the issued registration Link. Once the registration Link is paid, search for Token corresponding to the payment. | invoice.paid
Cancelled | The registration link has been canceled. In such cases, you need to create a registration link again.| NA
Expired | The registration link has expired. You can set an expiry timestamp at the time of creation. | invoice.expired1.2 Complete Authentication
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.
Aadhaar (Recommended Auth Type)
Handy TipsRazorpay’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.Given below is the authentication process via Aadhaar:
- The customer visits the registration link shared by you. This opens the invoice and displays the checkout. They enter their phone number and email and click Authenticate.
- They select the Pay via Netbanking - Bank Account payment method and proceed.
- They select their preferred bank and the authentication mechanism. In this case, it is Aadhaar.
- They enter their bank details such as account number, account type, IFSC and account holder name.
- The mandate summary page opens where customer then reviews the details and clicks Proceed.
- The bank’s mandate registration form opens. Customer confirms the details and submits the mandate registration request.
- The customer reads the Aadhaar disclaimer and agrees to provide their Aadhaar details for authentication.
- The customer submits their Aadhaar details.
- The customer enters the OTP to complete 2FA.
Handy TipsFor mandate amounts above ₹15,000, the customer must complete a second OTP verification as part of Aadhaar authentication.
- The customer is redirected to the NPCI mandate acceptance page.
- They are then automatically redirected to the Razorpay mandate success page, where they must click Proceed.
- The customer is redirected to the invoice checkout page which shows the final status. This completes the netbanking authentication process.
Netbanking
Given below is the authentication process via netbanking:- The customer visits the registration link shared by you. This opens the invoice and displays the checkout. They enter their phone number and email and click Authenticate.
- They select the Pay via Netbanking - Bank Account payment method and proceed.
- They select their preferred bank and the authentication mechanism. In this case, it is Netbanking.
- They enter their bank details such as account number, account type, IFSC and account holder name.
- The mandate summary page opens where customer then reviews the details and clicks Proceed.
- The bank’s mandate registration form opens. Customer confirms the details and submits the mandate registration request.
- The bank’s netbanking login page opens. Here, customer enters their login credentials and completes OTP verification process.
- The customer is redirected to the NPCI mandate acceptance page. They are then automatically redirected to the Razorpay mandate success page, where they must click Proceed.
- The customer is redirected to the invoice checkout page which shows the final status. This completes the netbanking authentication process.
Debit Card
Given below is the authentication process via debit card:- The customer visits the registration link shared by you. This opens the invoice and displays the checkout. They enter their phone number and email and click Authenticate.
- They select the Pay via Netbanking - Bank Account payment method and proceed.
- They select their preferred bank and the authentication mechanism. In this case, it is debit card.
- They enter their bank details such as account number, account type, IFSC and account holder name.
- The mandate summary page opens where customer then reviews the details and clicks Proceed.
- The bank’s mandate registration form opens. The customer enters the debit card details and submits the mandate registration request.
- They complete the OTP verification process.
- The customer is redirected to the NPCI mandate acceptance page. They are then automatically redirected to the Razorpay mandate success page, where they must click Proceed.
- The customer is redirected to the invoice checkout page which shows the final status. This completes the netbanking authentication process.
Authorisation Payment Statuses
Once the customer has made the Authorisation Payment, it moves through the following states as per the payment flow: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
Captured | Indicates that the payment is verified by you. Once a payment is captured you can retrieve the token. | payment.captured or order.paid
Failed | Indicates that the payment has failed. If the payment has failed, you need to create an authorisation transaction again. | payment.failed2. Fetch Token and Verify States
This is a process of fetching the token that contains the registration details of the customer and checking its status. A token represents a mandate registration and is generated after the authorisation transaction is successfully captured. A token contains customer’s payment details stored by Razorpay and is used to create a recurring payment.Token Statuses
As the authorisation transaction moves through its different states, the token that is generated also undergoes state changes. Following is the life cycle of a token:token_status | Description | Next Step
initiated | Indicates that the bank is processing the mandate registration. | Wait for the token.confirmed webhook.
confirmed | Indicates that the bank has completed the mandate registration. | Create recurring payment
rejected | Indicates that the mandate registration has failed. | Create the authorisation transaction again.
cancelled | Indicates that the token has been cancelled. | Create the authorisation transaction again if you want to charge the customer.
paused | Indicates that the token has been paused by your customer. | The token is inactive. Your customer has paused the token. Ask them to resume the token to charge them.
Know more about the turnaround time (TAT) for Emandate from the FAQs.
3. Charge Customers
This is the process of charging customers the actual subsequent amount using the fetched token and customer details.Handy TipsSubsequent payments can be charged without the need of any intervention from the customer. However, subsequent payments need to be created manually by you.Once a token goes to the confirmed state, you can start creating recurring payments for the customer as per your business requirements.
Handy TipsIf you want to collect the first payment immediately, you can charge customers during registration itself, combining authorisation and the first debit into a single step.You can create subsequent payments using:
Using the Dashboard
To create subsequent payments using the Dashboard:- Search for the token and check its status After the authorisation transaction is complete, a token is generated. You can use the search feature on the Dashboard to find the required token and check its status.
- Charge the token After you have found the required confirmed token, you can create a subsequent payment by charging the token according to your business needs.
Order is Created AutomaticallyWhile creating a subsequent charge using the Dashboard, Razorpay automatically creates an order for you when you charge a token. There is no need to create an order separately.
Using APIs
To create subsequent payments using APIs:- Create a new Order Like any other payment, each subsequent payment is tied to a unique order id. Associating a payment with an order id makes it easier to query Razorpay systems and handle multiple payment attempts and allows automatic capturing of payments.
- Create a Payment
Once the order is created, you can create a payment for it.
After our system validates the payment along with
token_id, arazorpay_payment_idis returned. In some cases, the payment entity returned is in the created state and may take 1 working day for confirmation.