Skip to main content
You can use this feature where you can charge any amount to your customer as part of the authorisation transaction. The customer is charged an amount immediately while initiating the mandate registration in the background. This helps you to onboard the customer immediately without waiting for the mandate to be registered.
Feature RequestThis is an on-demand feature. Please raise a request with our Support team to get this feature activated on your Razorpay account.to get this feature activated on your account.

Use Cases

Following are a couple of use cases where you can use this feature:

Mutual Funds

When a customer starts a new Systematic Investment Plan (SIP), the investment needs to be made immediately. The customer needs to be charged as part of the mandate registered process. It is not possible to wait for a few days while the mandate is registered before charging the customer.

Insurance

If you are an insurance provider, you need to charge the customer the first premium immediately when selling them the policy.

Supported Banks

Currently, only HDFC and ICICI support this feature.

Integration Steps

The integration flow here is same as that for emandate registration.
  1. Create an authorisation transaction.
  2. Check token status.
  3. Create subsequent charges.

1. Create an Authorisation Transaction

You can create an authorisation transaction:

1.1. Using Razorpay Standard Checkout

To create an authorisation transaction using the Razorpay Standard Checkout, you need to:

1.1.1. Create a Customer

Razorpay links recurring tokens to customers using a unique identifier generated through the Customer API. You can create customers with basic information such as email and contact and use them for various Razorpay offerings. The following endpoint creates a customer. /customers

Sample Code

Curl
Response
Request Parameters
name : string The name of the customer. For example, Gaurav Kumar. email : string The email address of the customer. For example, gaurav.kumar@example.com. contact : string The phone number of the customer. For example, 9876543210. fail_existing optional : string The request throws an exception by default if a customer with the exact details already exists. You can pass an additional parameter fail_existing to get the existing customer’s details in the response. Possible values:
  • 1 (default): If a customer with the same details already exists, throws an error.
  • 0: If a customer with the same details already exists, fetches details of the existing customer.
notes optional : object Key-value pair that can be used to store additional information about the entity. Maximum 15 key-value pairs, 256 characters (maximum) each. For example, "note_key": "Beam me up Scotty”.

1.1.2. Create an Order

The Orders API allows you to create a unique Razorpay order_id, for example, order_1Aa00000000001, that would be tied to a payment. This order_id has a 1:1 mapping with the order created for the authorisation payment at your end. To learn more about Razorpay Orders, refer our detailed Order documentation. Use the below endpoint to create an order. /orders You can create a payment against the order_id generated in the response.
Emandate via Netbanking
Request Parameters
amount mandatory : integer Amount in currency subunits. Pass 100 for ₹1. currency mandatory : string The 3-letter ISO currency code for the payment. Currently, we only support INR. method mandatory : string The authorisation method. In this case the value will be emandate. payment_capture mandatory : boolean Determines if payment should be automatically captured. Possible values:
  • true (recommended): Automatically capture the payment.
  • false (default/not recommended): You have to manually capture payments.
customer_id mandatory : string The unique identifier of the customer, who is to be charged. For example, cust_D0cs04OIpPPU1F. receipt optional : string A user-entered unique identifier for the order. For example, rcptid #1. This parameter should be mapped to the order_id sent by Razorpay. notesoptional : object Key-value pair that can be used to store additional information about the entity. Maximum 15 key-value pairs, 256 characters (maximum) each. For example, "note_key": "Beam me up Scotty”. token : Details related to the authorization such as max amount and bank account information. auth_type optional : string Here, it has to be netbanking. max_amount optional : integer The maximum amount, in paise, that a customer can be charged in one transaction. Know about maximum and default values. expire_at optional : integer The timestamp, in Unix format, till when you can use the token (authorisation on the payment method) to charge the customer subsequent payments. Default is 10 years for emandate. The value can range from the current date to 31-12-2099 (4101580799). bank_account : Customer bank account details. account_number optional : string Customer’s bank account number. ifsc_code optional : string Customer’s bank IFSC. For example UTIB0000001. beneficiary_name optional : string Customer’s name. For example, Gaurav Kumar. account_type optional : string Customer’s bank account type. Possible values:
  • savings (default)
  • current
notesoptional : object Key-value pair that can be used to store additional information about the entity. Maximum 15 key-value pairs, 256 characters (maximum) each. For example, "note_key": "Beam me up Scotty”.

1.1.3. Create an Authorisation Payment

Create a payment checkout form for customers to make Authorisation Transaction and register their mandate. You can use the Handler Function or Callback URL.

Handler Function | Callback URL

When you use the handler function, the response object of the successful payment (razorpay_payment_id, razorpay_order_id and razorpay_signature) is submitted to the Checkout Form. You need to collect these and send them to your server. | When you use a Callback URL, the response object of the successful payment (razorpay_payment_id, razorpay_order_id and razorpay_signature) is submitted to the Callback URL.
Watch Out!
  • The callback URL is not supported for recurring payments created using the registration link.
  • While handling the first time authorisation payment response, consume the error_reason field with value upi_dummy_payment and error_description field with value Payment was a dummy payment for one time mandate registration. to identify successful mandate registration. The parent error_code will be BAD_REQUEST_ERROR.
Checkout with handler functions
Additional Checkout Fields
customer_id mandatory : string Unique identifier of the customer created in the first step.order_id mandatory : string Unique identifier of the order created in the second step. recurring mandatory : integer In this case, the value has to be 1.
Registration Link is an alternate way of creating an authorisation transaction. You can create a registration link using the API or Dashboard.
Handy TipsWhen you create a registration link, an invoice is automatically issued to the customer. They can use this invoice to make the authorisation payment.Use the below endpoint to create a registration link./subscription_registration/auth_links
Emandate via Netbanking
Request Parameters
customer : Details of the customer to whom the registration link will be sent.name mandatory : string Customer’s name.email mandatory : string Customer’s email address.contactmandatory : string Customer’s phone number.type mandatory : string In this case, the value is link.currency mandatory : string The 3-letter ISO currency code for the payment. Currently, only INR is supported.amount mandatory : integer The payment amount in the smallest currency sub-unit.description mandatory : string A description that appears on the hosted page. For example, 12:30 p.m. Thali meals (Gaurav Kumar). subscription_registration : Details of the authorisation payment.method mandatory : string The authorisation method. In this case, it will be emandate.auth_type optional : string Here, it has to be netbanking.max_amount optional : integer The maximum amount, in paise, that a customer can be charged in one transaction. Know about maximum and default values.expire_at optional : integer The timestamp, in Unix, till when you can use the token (authorization on the payment method) to charge the customer subsequent payments. Default is 10 years for emandate. The value can range from the current date to 31-12-2099 (4101580799).bank_account : The customer’s bank account details.beneficiary_name optional : string The account holder’s name. For example Gaurav Kumar.account_number optional : integer Customer’s bank account number. For example 11214311215411.account_type optional : string Customer’s bank account type. Possible values:
  • savings (default)
  • current
ifsc_code optional : string Customer’s bank IFSC. For example HDFC0000001.sms_notify optional : boolean Indicates if SMS notifications are to be sent by Razorpay. Can have the following values:
  • true (default): Notifications are sent by Razorpay.
  • false: Notifications are not sent by Razorpay.
email_notify optional : boolean Indicates if email notifications are to be sent by Razorpay. Can have the following values:
  • true (default): Notifications are sent by Razorpay.
  • false: Notifications are not sent by Razorpay.
expire_by optional : integer The timestamp, in Unix, till when the registration link should be available to the customer to make the authorisation transaction.receipt optional : string A unique identifier entered by you for the order. For example, Receipt No. 1. This parameter should be mapped to the order_id sent by Razorpay.notes optional : object This is a key-value pair that can be used to store additional information about the entity. Maximum 15 key-value pairs, 256 characters (maximum) each. For example, "note_key": "Beam me up Scotty”.

1.2.2. Send/Resend Notifications

The following endpoint sends/resends notifications with the short URL to the customer:/invoices/:id/notify_by/:medium

Sample Code

Curl
Response
Path Parameters
idmandatory : string The unique identifier of the invoice linked to the registration link for which you want to send the notification. For example, inv_1Aa00000000001. medium mandatory : string Determines through which medium you want to resend the notification. Possible values:
  • sms
  • email
The following endpoint cancels a registration link. /invoices/:id/cancel
Handy TipsYou can only cancel registration link in the issued state.

Sample Code

Curl
Response
Path Parameter
id mandatory : string The unique identifier for the invoice linked to the registration link that you want to cancel. For example, inv_1Aa00000000001.

2. Fetch and Manage Tokens

Once you capture a payment, Razorpay Checkout returns a razorpay_payment_id. You can use this id to fetch the token_id, which is used to create and charge subsequent payments. You can retrieve the token_id using the Dashboard or the APIs given below.

2.1. Fetch Token by Payment ID

The following endpoint retrieves the token_id using a payment_id. /payments/:id
Curl
Handy TipsYou can also retrieve the token_id via the payment.authorized webhook.

Path Parameter

id mandatory : string The unique identifier of the payment to be retrieved. For example, pay_1Aa00000000002.

2.2. Fetch Tokens by Customer ID

A customer can have multiple tokens and these tokens can be used to create subsequent payments for multiple products or services. The following endpoint retrieves tokens linked to a customer.
Watch Out!This endpoint will not fetch the details of expired and unused tokens./customers/:id/tokens
Curl

Path Parameter

id mandatory : string The unique identifier of the customer for whom tokens are to be retrieved. For example, cust_1Aa00000000002.

2.3. Delete Tokens

The following endpoint deletes a token. /customers/:customer_id/tokens/:token_id
Curl
Response

Path Parameter

customer_id mandatory : string The unique identifier of the customer with whom the token is linked. For example, cust_1Aa00000000002. token_id mandatory : string The unique identifier of the token that is to be deleted. For example, token_1Aa00000000001.

3. Create Subsequent Payments

Following are the two steps to create and charge your customer a subsequent payment: You should perform the following steps to create and charge your customer subsequent payments:
  1. Create an order to charge the customer
  2. Create a recurring payment

3.1. Create an Order to Charge the Customer

You have to create a new order every time you want to charge your customers. This order is different from the one created during the authorisation transaction. The following endpoint creates an order. /orders
Curl
Success Response

Request Parameters

amount mandatory : integer Amount in currency subunits. currency mandatory : string The 3-letter ISO currency code for the payment. receipt optional : string A user-entered unique identifier for the order. For example, Receipt No. 1. You should map this parameter to the order_id sent by Razorpay. notes optional : object Key-value pair you can use to store additional information about the entity. Maximum of 15 key-value pairs, 256 characters each. For example, "note_key": "Beam me up Scotty”. payment_capture mandatory : boolean Determines whether the payment status should be changed to captured automatically or not. Possible values:
  • true: Payments are captured automatically.
  • false: Payments are not captured automatically. You can manually capture payments using the Manually Capture Payments API.

3.2. Create a Recurring Payment

Once you have generated an order_id, use it with the token_id to create a payment and charge the customer. The following endpoint creates a payment to charge the customer. /payments/create/recurring
Curl
Success Response

Request Parameters

email mandatory : string The customer’s email address. For example, gaurav.kumar@example.com. contact mandatory : integer The customer’s phone number. For example, 9876543210. currency mandatory : string 3-letter ISO currency code for the payment. Currently, only INR is allowed. amount mandatory : integer The amount you want to charge your customer. This should be the same as the order amount. order_idmandatory : string The unique identifier of the order created. For example, order_1Aa00000000002. customer_id mandatory : string The unique identifier of the customer you want to charge. For example, cust_1Aa00000000002. token mandatory : string The token_id generated when the customer successfully completes the authorisation payment. Different payment instruments for the same customer have different token_id. recurring mandatory : boolean Determines whether recurring payment is enabled or not.
  • true: Recurring payment is enabled.
  • false: Recurring payment is not enabled.
notesoptional : object Key-value pair you can use to store additional information about the entity. Maximum of 15 key-value pairs, 256 characters each. For example, "note_key": "Beam me up Scotty”.