Available in🇮🇳 India
The flow to complete an authorisation transaction using paper NACH differs from the other payment method’s flow.
- Create a customer.
- Create an order by passing the
customer_idand the method asnach. Razorpay generates a NACH form with the customer information pre-filled and ready to sign. - The customer can get the form in one of the following ways to sign it:
- You can download the form from the Dashboard and send it to the customer.
- A customer can download the form from the Hosted page (in the case of registration links).
- The signed form can be uploaded in one of the following ways:
- Using the Standard Checkout page.
- Hosted page (in the case of registration links).
- The customer can send you the form and you can upload the form for the customer. The acceptable image formats and size are:
- jpeg
- jpg
- png
- Maximum accepted size is 6 MB.
confirmed.
1. Create an Authorisation Transaction
You can create an authorisation transaction using the Razorpay APIs or Registration Link.1.1. Using Razorpay APIs
To create an authorisation transaction using the Razorpay APIs, 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 asemail and contact and use them for various Razorpay offerings. The following endpoint creates a customer.
Handy TipsCreate one customer ID per customer, using a unique email or phone number. Reusing or duplicating customers breaks data analysis and stops the Fetch Tokens by Customer ID API from returning the expected tokens.
POST /customers
Sample Code
Sample Code
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
Use the Orders API to create a unique Razorpayorder_id that is associated with the authorisation transaction. The following endpoint creates an order.
POST /orders
order_id that is associated with the authorisation transaction. The following endpoint creates an order.
POST /orders
Request Parameters
amount mandatory
: integer Amount in currency subunits. For Paper NACH, the amount has to be 0.
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 nach.
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 authorisation transaction such as max amount and bank account information. Pass a value in the first_payment_amount parameter if you want to auto-charge the customer the first payment immediately after authorization. The first payment is created automatically with a new order_id and payment_id after the token is confirmed.
1.1.3. Create an Authorisation Payment
After you create an order, you have to create an authorisation payment. To create an authorisation payment:- Download the Paper NACH form and send it to the customers.
- Ask the customers to fill the form and send it to you.
- You upload the received form via the create NACH File API. The acceptable image formats and size are jpeg, jpg and png. Maximum accepted size is 6 MB.
POST /payments/create/nach/file
Razorpay’s OCR-enabled NACH engine submits the form to NPCI on successful verification and you will receive a success/failure response.
Use the following API to upload the NACH file sent by the customer.
1.2. Using a Registration Link
Registration Links are an alternate way of creating an authorisation transaction. If you create a registration link, you need not create a customer or an order. When you create a registration link, an invoice is automatically issued to the customer. The customer can use the invoice to make the Authorisation Payment. Know how to create Registration Links using the Dashboard.Handy TipsYou can use webhooks to get notifications about successful payments against a registration link. Know more about Webhooks.
0.
1.2.1. Create a Registration Link
The following endpoint creates a registration link for recurring payments.POST /subscription_registration/auth_links
Download and Upload the Pre-filled NACH FormOnce the registration link is created, the customer should complete these steps:
- Download the pre-filled form using the Download NACH Form option on the Razorpay hosted page.
- Sign the form.
- Upload the signed form using the Upload NACH Form option on the Razorpay hosted page.
Request Parameters
customer
: object Details of the customer to whom the registration link is sent.
type mandatory
: string In this case, the value is link.
amount mandatory
: integer The payment amount in the smallest currency sub-unit.
currency mandatory
: string The 3-letter ISO currency code for the payment.
description mandatory
: string A description that appears on the hosted page.
subscription_registration
: Details of the authorisation payment.
sms_notify optional
: boolean Indicates if SMS notifications are to be sent by Razorpay. Possible 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. Possible values:
true(default): Notifications are sent by Razorpay .false: Notifications are not sent by Razorpay.
expire_by optional
: integer The Unix timestamp indicates the expiry of the registration link.
receipt optional
: string A unique identifier entered by you for the order. For example, Receipt No. 1. You should map this parameter to the order_id sent by Razorpay.
notes optional
: object This is a key-value pair that is 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:POST /invoices/:id/notify_by/:medium
Sample Code
Sample Code
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:
smsemail
1.2.3. Cancel a Registration Link
The following endpoint cancels a registration link.POST /invoices/:id/cancel
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 arazorpay_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
Use the below endpoint to fetch thetoken_id using a payment_id.
GET /payments/:id
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
Use the below endpoint to fetch tokens linked to a customer. A customer can have multiple tokens tied to them. These tokens can be used to create subsequent payments for multiple products or services.GET /customers/:id/tokens
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.DELETE /customers/:customer_id/tokens/:token_id
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
You should perform the following steps to create and charge your customer subsequent payments: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.POST /orders
3.2. Create a Recurring Payment
Once you have generated anorder_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.
POST /payments/create/recurring
Request Parameters
email mandatory
: string The customer’s email address. For example, gaurav.kumar@example.com.
contact mandatory
: string 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 For Paper NACH, this must be true.
descriptionoptional
: string A user-entered description for the payment. For example, Creating recurring payment for Gaurav Kumar
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”.