Skip to main content
Available in🇮🇳 India
Integrate Recurring Payments using Paper NACH as a payment method.

Prerequisites

NACH Mandate Registration

Mandate registration is the process of creating a payment checkout form for the customer to make an authorisation transaction and register their NACH mandate. A recurring token is generated once the customer makes this transaction. Using this authorisation transaction, you can authenticate the customer’s NACH mandate and charge them recurring payments. The flow to complete an authorisation transaction using Paper NACH differs from the regular recurring payment flow:
  1. Create a customer.
  2. Create an order by passing customer_id and method nach. Razorpay generates a NACH form with the customer’s information pre-filled and ready to sign.
  3. The customer signs the form. They can obtain the form by:
    • downloading it from the Dashboard and you send it to them, or
    • downloading it from the hosted page (for registration links).
  4. The signed form is uploaded to Razorpay. This can be done through the hosted page (for registration links), or the customer sends you the form and you upload it. Accepted image formats are .jpeg, .jpg and .png, up to a maximum size of 6 MB.
Once the details are validated, the authorisation transaction is completed and a recurring token is generated. You can charge your customer once the recurring token status changes to confirmed.

Integration Steps

Integrate Paper NACH using Razorpay APIs in these steps:
  1. Create the Authorisation Transaction: create the order that generates the pre-filled NACH form, and get the signed form uploaded. See Paper NACH Form.
  2. Fetch and Manage Tokens: check that the mandate is registered and track the token status.
  3. Create Subsequent Payments: charge the customer on the confirmed token whenever a payment is due.
  4. Webhooks: subscribe to webhooks to track token and payment status changes.
To register NACH and charge the first payment together, see Register NACH and Charge First Payment Together.

Authorisation Payment Statuses

Once the customer has made the authorisation payment, it moves through the following states:

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: Know more about the turnaround time (TAT) for NACH from the FAQs.

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. In some cases, the payment entity returned is in the created state and may take 1 working day for confirmation.
Last modified on November 17, 2026