1. Create the Authorisation Transaction
Create an authorisation transaction with NACH as a payment method.
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_id
and 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.
Once the details are validated, the authorisation transaction is completed, and a token is generated. You can charge your customer as per your business model after the token status changes to confirmed
.
You can create an authorisation transaction:
- Using the .
- Using a .
To create an authorisation transaction using the Razorpay Standard Checkout, you need to:
- .
- .
- .
Curlec links recurring tokens to customers via a unique identifier. You can generate this identifier using the Customer API.
You can create
with basic information such asemail
and contact
and use them for various Curlec offerings. The following endpoint creates a customer.
name
mandatory
string
The name of the customer. For example, Nur Aisyah
.
mandatory
string
The email ID of the customer. For example, nur.aisyah@example.com
.
contact
mandatory
string
The phone number of the customer. For example, 60345675444
.
fail_existing
optional
boolean
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:
0
: Retrieve details of the existing customer.1
(default): Throws an exception error.
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”
.
id
string
The unique identifier of the customer. For example cust_1Aa00000000001
.
entity
string
The name of the entity. Here, it is customer
.
name
string
The name of the customer. For example, Nur Aisyah
.
string
The email ID of the customer. For example, nur.aisyah@example.com
.
contact
string
The phone number of the customer. For example, 60345675444
.
notes
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”
.
created_at
integer
A Unix timestamp, at which the customer was created.
You can create an order once you create a customer for the payment authorisation.
You can use the
to create a unique Curlecorder_id
that is associated with the authorisation transaction. The following endpoint creates an order.
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.
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”
.
token
Details related to the authorisation such as max amount, bank account information and NACH information.
auth_type
mandatory
string
In this case, it will be physical
.
bank_account
Customer's bank account details that will be printed on the NACH form.
account_number
mandatory
string
Customer's bank account number. For example 11214311215411
.
ifsc_code
mandatory
string
Customer's bank IFSC. For example UTIB0000001
.
beneficiary_name
mandatory
string
Customer's name. For example, Gaurav Kumar
.
account_type
optional
string
Customer's bank account type. Possible values:
savings
(default)current
cc
(Cash Credit)nre
(SB-NRE)nro
(SB-NRO)
max_amount
optional
integer
Use to set the maximum amount per debit request. The value can range from 500
- 1000000000
(1cr, default value).
expire_at
optional
integer
Timestamp, in Unix, that specifies when the registration link should expire. The value can range from the current date to 01-19-2038 (2147483647
).
nach
Additional information to be printed on the NACH form that your customer will sign.
form_reference1
optional
string
A user-entered reference that appears on the NACH form.
form_reference2
optional
string
A user-entered reference that appears on the NACH form.
description
optional
string
A user-entered description that appears on the hosted page. For example, Form for Gaurav Kumar.
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”
.
id
string
A unique identifier of the order created. For example order_1Aa00000000001
.
entity
string
The entity that is created. Here it is order
.
amount
integer
Amount in currency subunits. For NACH, the amount should be 0
.
amount_paid
integer
The amount that has been paid.
amount_due
integer
The amount that is yet to pay.
currency
string
The 3-letter ISO currency code for the payment. Currently, we only support INR
.
receipt
string
A user-entered unique identifier of the order. For example, rcptid #10
. You should map this parameter to the order_id
sent by Razorpay.
status
string
The status of the order. Here, it is created
.
notes
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”
.
created_at
integer
The Unix timestamp at which the order was created.
token
Details related to the authorisation such as max amount and bank account information.
method
string
Payment method used to make the authorisation payment. Here, it is nach
.
notes
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”
.
max_amount
integer
The maximum amount in paise a customer can be charged in a transaction. The value can range from 500
to 100000000
.
expire_at
integer
The Unix timestamp to indicate the date till which you can use the token (authorisation on the payment method) to charge the customer subsequent payments.
auth_type
string
NACH type used to make the authorisation payment. Here, it is physical
.
nach
Additional information to be printed on the NACH form that your customer will sign.
create_form
boolean
Indicates whether the form is created or not. Possible values:
true
: The NACH form is created.false
: The NACH form is not created.
form_reference1
string
A user-entered reference that appears on the NACH form.
form_reference2
string
A user-entered reference that appears on the NACH form.
prefilled_form
string
The link from where you can download the pre-filled NACH form.
upload_form_url
string
The link where the NACH form should be uploaded once it is signed by the customer.
description
string
A user-entered description that appears on the hosted page. For example, Paper NACH Gaurav Kumar
.
bank_account
Customer's bank account details that should be pre-filled on the checkout.
ifsc_code
string
Customer's bank IFSC. For example, HDFC0000001
.
bank_name
string
The bank name. For example, HDFC Bank
.
name
string
Name of the beneficiary. For example, Gaurav Kumar
.
account_number
string
Customer's bank account number.
account_type
string
Customer's bank account type. Possible values:
savings
(default value)current
cc
(Cash Credit)nre
(SB-NRE)nro
(SB-NRO)
beneficiary_email
string
Email address of the beneficiary. For example, gaurav.kumar@example.com
.
beneficiary_mobile
integer
Mobile number of the beneficiary.
Download and Upload the Pre-filled NACH Form
Once the order is created, the pre-filled form must be downloaded, signed by your customer and uploaded back to Razorpay to complete the transaction.
You receive the following parameters as part of the response:
prefilled_form
The link from where you can download the pre-filled NACH form.
upload_form_url
The link where the NACH form should be uploaded once it is signed by the customer.
Authorisation transaction + auto-charge first payment:
You can register a customer's mandate and charge them the first recurring payment as part of the same transaction. Refer to the
for more information.Given below is a list of possible errors you may face while creating an Order.
You should create an authorisation payment after you create an order.
To create an authorisation payment:
- Download the Paper NACH form and send it to the customer.
- Ask the customers to fill the form and either or send it to you to upload the form using the .
Create a payment checkout form for customers to upload the NACH form and make the Authorisation Transaction. You can use the Handler Function or Callback URL.
Watch Out!
The Callback URL is not supported for Recurring Payments created using the registration link.
You should send the following additional parameters along with the existing checkout options as a part of the authorisation transaction.
customer_id
mandatory
string
Unique identifier of the customer created in the
order_id
mandatory
string
Unique identifier of the order created in the
recurring
mandatory
boolean
Determines whether the recurring is enabled or not. Possible values:
1
: Recurring is enabled.0
: Recurring is not enabled.
Given below is a list of possible errors you may face while making the authorisation payment.
Use the following API to upload the NACH file sent by the customer.
order_id
mandatory
string
The unique identifier of the order that was created. For example, order_FoLdZrq6QGKUWg
.
recurring
mandatory
boolean
Determines whether the recurring is enabled or not. Possible values:
1
: Recurring is enabled.0
: Recurring is not enabled.
file
mandatory
strinng
The path where you have saved the NACH file.
razorpay_payment_id
string
The unique identifier of the payment that is created. For example, pay_FjDn43bvssCqEM
.
razorpay_order_id
string
The unique identifier of the order that is created. For example, order_FjDdQ6a0GluJ2c
.
razorpay_signature
string
The signature generated by the Razorpay. For example, f13775ea8a91e9bf229b9fdba3ad783f7ff2bdbce1c35e87a69ae7418808da04
Given below is a list of possible errors you may face while while uploading a NACH file.
Registration Link is an alternate way of creating an authorisation transaction. You can create a registration link using the
orHandy Tips
You do not have to create a customer if you choose the registration link method for creating an authorisation transaction.
- When you create a registration link, an is automatically issued to the customer. They can use this invoice to make the authorisation payment.
- A registration link should always have an order amount (in paise) the customer will be charged when making the authorisation payment. This amount should be
0
in the case of Paper NACH.
Handy Tips
You can
against a registration link.The following endpoint creates a registration link for recurring payments.
customer
object
Details of the customer to whom the registration link is sent.
name
mandatory
string
Customer's name.
mandatory
string
Customer's email address.
contact
mandatory
integer
Customer's contact number.
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. Currently, only MYR
is supported.
description
mandatory
string
A description that appears on the hosted page. For example, 12:30 p.m. Thali meals (Nur Aisyah)
.
subscription_registration
Details of the authorisation payment.
method
mandatory
string
The Paper NACH method used to make the authorisation transaction. Here, it is physical
.
auth_type
mandatory
string
The payment method used to make the authorisation transaction. Here, it is nach
.
bank_account
The customer's bank account details.
beneficiary_name
mandatory
string
The beneficiary name. For example, Gaurav Kumar
.
account_number
mandatory
integer
The customer's bank account number. For example, 11214311215411
.
account_type
mandatory
string
The customer's bank account type. Possible values:
savings
current
ifsc_code
mandatory
string
The customer's bank IFSC. For example, HDFC0000001
.
max_amount
optional
integer
Use to set the maximum amount, in paise, per debit request. The value can range from 500
- 1000000000
. The dafault value is 1cr.
expire_at
optional
integer
The Unix timestamp till when you can use the token (authorisation on the payment method) to charge the customer subsequent payments. The default value is 10 years. The value can range from the current date to 31-12-2099 (4101580799
).
nach
Additional information to be printed on the NACH form your customer will sign.
form_reference1
optional
string
A user entered reference that appears on the NACH form.
form_reference2
optional
string
A user entered reference that appears on the NACH form.
description
optional
string
A user entered description that appears on the hosted page. For example, Form for Gaurav Kumar.
sms_notify
optional
boolean
Indicates if SMS notifications are to be sent by Curlec. Possible values:
0
: Notifications are not sent by Curlec.1
: Notifications are sent by Curlec (default value).
email_notify
optional
boolean
Indicates if email notifications are to be sent by Curlec. Possible values:
0
: Notifications are not sent by Curlec.1
: Notifications are sent by Curlec (default value).
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 Curlec.
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”
.
id
string
The unique identifier of the invoice.
entity
string
The entity that has been created. Here, it is invoice
.
receipt
string
A user-entered unique identifier of the invoice.
invoice_number
string
Unique number you added for internal reference.
customer_id
string
The unique identifier of the customer. For example, cust_BMB3EwbqnqZ2EI
.
customer_details
Details of the customer.
id
string
The unique identifier associated with the customer to whom the invoice has been issued.
name
string
The customer's name.
string
The customer's email address.
contact
integer
The customer's phone number.
billing_address
string
Details of the customer's billing address.
shipping_address
string
Details of the customer's shipping address.
order_id
string
The unique identifier of the order associated with the invoice.
line_items
string
Details of the line item that is billed in the invoice. Maximum of 50 line items are allowed.
payment_id
string
Unique identifier of a payment made against the invoice.
status
string
The status of the invoice. Possible values:
draft
issued
partially_paid
paid
cancelled
expired
deleted
expire_by
integer
The Unix timestamp at which the invoice will expire.
issued_at
integer
The Unix timestamp at which the invoice was issued to the customer.
paid_at
integer
The Unix timestamp at which the payment was made.
cancelled_at
integer
The Unix timestamp at which the invoice was cancelled.
expired_at
integer
The Unix timestamp at which the invoice expired.
sms_status
string
The delivery status of the SMS notification for the invoice sent to the customer. Possible values:
pending
sent
email_status
string
The delivery status of the email notification for the invoice sent to the customer. Possible values:
pending
sent
date
integer
Timestamp, in Unix format, that indicates the issue date of the invoice.
terms
string
Any terms to be included in the invoice. Maximum of 2048 characters.
partial_payment
boolean
Indicates whether the customer can make a partial payment on the invoice. Possible values:
true
: The customer can make partial payments.false
(default): The customer cannot make partial payments.
amount
integer
Amount to be paid using the invoice. Must be in the smallest unit of the currency. For example, if the amount to be received from the customer is MYR 299.95, pass the value as 29995
.
amount_paid
integer
Amount paid by the customer against the invoice.
amount_due
integer
The remaining amount to be paid by the customer for the issued invoice.
currency
string
The currency associated with the invoice.
description
string
A brief description of the invoice.
notes
object
Any custom notes added to the invoice. Maximum of 2048 characters.
short_url
string
The short URL that is generated. This is the link that can be shared with the customer to receive payments.
type
string
Here, it is invoice
.
comment
string
Any comments to be added in the invoice. Maximum of 2048 characters.
The following endpoint sends/resends notifications with the short URL to the customer:
id
mandatory
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
success
boolean
Indicates whether the notifications were sent successfully. Possible values:
true
: The notifications were successfully sent via SMS, email or both.false
: The notifications were not sent.
The following endpoint cancels a registration link.
Watch Out!
You can only cancel the registration link that is in the issued
state.
id
mandatory
string
The unique identifier for the invoice linked to the registration link that you want to cancel. For example, inv_1Aa00000000001
.
id
string
The unique identifier of the invoice.
entity
string
The entity that has been created. Here, it is invoice
.
receipt
string
A user-entered unique identifier of the invoice.
invoice_number
string
Unique number you added for internal reference.
customer_id
string
The unique identifier of the customer. For example, cust_BMB3EwbqnqZ2EI
.
customer_details
Details of the customer.
id
string
The unique identifier associated with the customer to whom the invoice has been issued.
name
string
The customer's name.
string
The customer's email address.
contact
integer
The customer's phone number.
billing_address
string
Details of the customer's billing address.
shipping_address
string
Details of the customer's shipping address.
order_id
string
The unique identifier of the order associated with the invoice.
line_items
string
Details of the line item that is billed in the invoice. Maximum of 50 line items are allowed.
payment_id
string
Unique identifier of a payment made against the invoice.
status
string
The status of the invoice. Possible values:
draft
issued
partially_paid
paid
cancelled
expired
deleted
expire_by
integer
The Unix timestamp at which the invoice will expire.
issued_at
integer
The Unix timestamp at which the invoice was issued to the customer.
paid_at
integer
The Unix timestamp at which the payment was made.
cancelled_at
integer
The Unix timestamp at which the invoice was cancelled.
expired_at
integer
The Unix timestamp at which the invoice expired.
sms_status
string
The delivery status of the SMS notification for the invoice sent to the customer. Possible values:
pending
sent
email_status
string
The delivery status of the email notification for the invoice sent to the customer. Possible values:
pending
sent
date
integer
Timestamp, in Unix format, that indicates the issue date of the invoice.
terms
string
Any terms to be included in the invoice. Maximum of 2048 characters.
partial_payment
boolean
Indicates whether the customer can make a partial payment on the invoice. Possible values:
true
: The customer can make partial payments.false
(default): The customer cannot make partial payments.
amount
integer
Amount to be paid using the invoice. Must be in the smallest unit of the currency. For example, if the amount to be received from the customer is MYR 299.95, pass the value as 29995
.
amount_paid
integer
Amount paid by the customer against the invoice.
amount_due
integer
The remaining amount to be paid by the customer for the issued invoice.
currency
string
The currency associated with the invoice.
description
string
A brief description of the invoice.
notes
object
Any custom notes added to the invoice. Maximum of 2048 characters.
short_url
string
The short URL that is generated. This is the link that can be shared with the customer to receive payments.
type
string
Here, it is invoice
.
comment
string
Any comments to be added in the invoice. Maximum of 2048 characters.
Was this page helpful?