{"id":280,"date":"2020-11-02T19:34:37","date_gmt":"2020-11-02T14:04:37","guid":{"rendered":"https:\/\/razorpay.com\/unfiltered\/?p=280"},"modified":"2022-10-14T15:37:47","modified_gmt":"2022-10-14T10:07:47","slug":"paper-nach-offline-to-online-challenge","status":"publish","type":"post","link":"https:\/\/razorpay.com\/unfiltered\/paper-nach-offline-to-online-challenge\/","title":{"rendered":"Paper NACH – The Offline to Online Challenge"},"content":{"rendered":"Reading Time: <\/span> 7<\/span> minutes<\/span><\/span>

Change is always hard. Even more so when it\u2019s for something that\u2019s been done without question for many many years. It is not so much the process that acts as a hindrance as it is the willingness to alter the process. A similar stumbling block came our way while trying to build a product to support Physical NACH or Paper NACH payments.<\/span><\/p>\n

When we started discussing the viability of creating a Paper NACH product (I know that I have still not elaborated on what this Paper NACH is, but bear with me for just a bit), the business case was very straightforward. More than 80% of the mutual fund and lending sector continues to use Paper NACH to set up recurring payments. Furthermore, we had received multiple asks from our key enterprise clients to build a solution for them. What was less clear was how we wanted to approach this product.<\/span><\/p>\n

For a user to switch from an existing product to a new one, there need to be substantial gains – a commonly used framework is that the customer\u2019s experience must increase <\/span>10x<\/b> for the switching costs to be justified. Well then the solution was simple really – solve a key pain-point, or many such pain points for that matter, which can help NACH users. However, the key question remained, how do you improve a 2-decade old product?<\/span><\/p>\n

The Old Way<\/span><\/h3>\n

To understand how we went about solving this I need to first elaborate on the end-to-end NACH mandate process which exists today.\u00a0<\/span><\/p>\n

Q: What is a NACH Mandate?<\/span><\/p>\n

A: A NACH Mandate is an authorization (or permission) that customers provide to Institutions\/Businesses to Credit or Debit funds, especially on a recurring basis.<\/span><\/p>\n

The authorization is provided in the form of a signature by the customer on a piece of paper that has a whole host of other details (see the picture below). This form is then validated by the customer\u2019s bank and the mandate is registered if the necessary conditions are met. Although used widely, this is just like any other bank form that we hurriedly sign and have no clue about what it does.<\/span><\/p>\n

\"\"<\/p>\n

Not too complicated so far, eh? Well, this is where things get a little `messed up`.<\/span><\/p>\n

Let\u2019s take the example of setting up an investment. Commonly, the actors involved here would be the customer, the business (firm offering the investment option), and a financial advisor or agent who would be the goto between the customer and the business. The steps involved (after the customer has agreed in principle to buy the product) in setting up the NACH mandate which can be deducted periodically would look something like this:<\/span><\/p>\n

    \n
  1. The agent fixes up a meeting with the customer to get their documents along with the signature on the NACH form (<\/span>TAT: 2-4 days<\/b>)<\/span><\/li>\n
  2. The agent submits the NACH form at the local office\/branch from where it is couriered to the head office (<\/span>TAT: 2-4 days<\/b>)<\/span>\n
      \n
    1. Certain firms enlist the help of third parties to collect the documents in which case the TAT may increase<\/span><\/li>\n<\/ol>\n<\/li>\n
    2. The Ops team at the head office does a basic check on the NACH form and accepts\/rejects it (<\/span>TAT: 1-2 days<\/b>. If rejected, the process goes back to Step 1)<\/span><\/li>\n
    3. The Ops team then couriers the NACH forms to their payment service provider or PSP (<\/span>TAT: 2-4 days<\/b>)<\/span><\/li>\n
    4. The PSP receives the NACH forms and proceeds for manual verification of every form (<\/span>TAT: 1-2 days<\/b>)<\/span><\/li>\n
    5. The PSP submits a softcopy of the NACH form to their sponsor bank and it is finally routed to the customer\u2019s bank for verification (<\/span>TAT: upto 10 days. <\/b>If rejected, goes back to Step 1)<\/span><\/li>\n<\/ol>\n

      While breaking down the above process, it became increasingly evident that the time taken was extensive. Even when everything went smoothly and the NACH form was accepted on the first attempt, the registration process took between 10 – 22 working days i.e. anywhere between 2 weeks to 6 weeks!!! Coupled with the additional costs incurred on agents, mailing\/couriering of forms, and the salaries of Ops personnel, this is not only a time-consuming process but also an expensive one.<\/span><\/p>\n

      Add to this the hassle of keeping track of the forms across the registration lifecycle, ensuring that the forms are mapped to the correct customers, and the uncertainty of whether the signature of the customer would match that present in their records with the bank meant that there were enough headaches to go around.<\/span><\/p>\n

      Identifying the Problems with Paper NACH today<\/span><\/h3>\n

      Having broken down the process and after identifying the key pain points faced by merchants, the difficult part was on how to go about solving them. Broadly, these were the issues that businesses go through daily:<\/span><\/p>\n\n\n\n\n\n\n\n\n\n
      Problem<\/span><\/td>\nImpact<\/span><\/td>\nSolvable<\/span><\/td>\n<\/tr>\n
      Delivery of the NACH forms to the customer<\/span><\/td>\nTAT, Cost to company<\/span><\/td>\nYes<\/span><\/td>\n<\/tr>\n
      Customer to sign the NACH form<\/span><\/td>\nTAT<\/span><\/td>\nNo<\/span><\/td>\n<\/tr>\n
      Delivery of NACH form to the team which verifies the data<\/span><\/td>\nTAT, Cost to company<\/span><\/td>\nYes<\/span><\/td>\n<\/tr>\n
      Verification of NACH form (while meeting the industry standards on accuracy)<\/span><\/td>\nTAT, Cost to company<\/span><\/td>\nYes<\/span><\/td>\n<\/tr>\n
      Submission of form to the PSP<\/span><\/td>\nTAT, Cost to company<\/span><\/td>\nYes<\/span><\/td>\n<\/tr>\n
      Processing time taken to approve\/reject the mandate by the customer\u2019s bank<\/span><\/td>\nTAT<\/span><\/td>\nNo<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

      Any problem, however complex, seems less daunting once it is broken up into smaller problems; parts that can be solved. The behemoth that is the NACH mandate also seemed less of a Goliath once we were able to break it down.\u00a0<\/span><\/p>\n

      Obviously, there were parts that were outside of our control, namely the customer signing the NACH form and the time taken by the destination bank to approve the mandate.<\/span><\/p>\n

      On the first, well duh! Let\u2019s be honest – a customer signs a form when it is convenient to him\/her and not a second sooner (also, speaking from personal experience – I can never keep my signature consistent, and it looks different every time!). It didn\u2019t really make sense to lose sleep pondering over this. The second one, i.e the time taken by the destination bank to approve the mandate was again outside of our hands. Once the form is submitted, every bank and branch has its own process – and solving this for lakhs of bank branches across over 1300 member banks on the NACH platform was again a non-starter.<\/span><\/p>\n

      The others, however, could be solved. Maybe.\u00a0<\/span><\/p>\n

      The Switch to Online<\/span><\/h3>\n

      The `solvable` problems could be further classified into 2 buckets:<\/span><\/p>\n

        \n
      • Steps involving the delivery of the form across multiple stakeholders<\/span><\/li>\n
      • Verification of the data on the form\u00a0<\/span><\/li>\n<\/ul>\n

        The delivery problem was something Razorpay was already good at. Businesses using Razorpay\u2019s other recurring products already have the option of sending payment links directly to customers via email, WhatsApp, and SMS, to make a payment. It seemed all the more apt here since businesses could save on additional costs by sharing the NACH form directly with the customer as any other payment link. What we additionally provided was the ability to generate a prefilled NACH form on which the customer simply had to sign. This could be done by either using our powerful REST APIs or from the merchant dashboard.<\/span><\/p>\n

        Once the customer signed the form, the problem of delivering the form to the agent who in turn delivers the form to the local office could also be solved by simply asking the customer to submit a photo of the form on the payment link itself. Thus from a customer\u2019s perspective, it was just the case of receiving a link, downloading and signing the form from the link, and uploading a photo of the signed form onto the same link. To simplify the experience, we designed the process similar to that of uploading an image on WhatsApp. This completely removed the dependency on agents and other human touchpoints.<\/span><\/p>\n

        The delivery alone would not solve everything, sadly. Else everyone would\u2019ve done it. The industry norm was for every form to be manually verified before being submitted for approval to the bank. This was another time-consuming and expensive process. To tackle this, we put in place an Optical Character Recognition (OCR) engine to read the form. An OCR is a tool that uses Machine Learning algorithms to identify the text on a form. In our case, we used the OCR to read the data on the form which was being submitted by the customer and let them know in real-time whether the form submission was successful or not. If the event of an error, the customer immediately gets to know what the issue is and can take corrective measures.\u00a0<\/span><\/p>\n

        The below image is an illustration of the form used at Razorpay. The black boxes on the sides help the OCR engine identify the text, even in the case of a slight crumpling of the form. The rest of the form is as per the existing NPCI-mandated design. As an added measure of security, every form is also generated with a unique security code to ensure that the correct form is uploaded and to prevent tampering.<\/span><\/p>\n

        \"\"
        \n<\/span><\/p>\n

        We launched our Paper NACH product in February of 2020 to a select set of businesses as part of an initial pilot. Of course, we had no idea of what was going to happen, and when the Covid outbreak and the subsequent lockdown came upon us, the Paper NACH product was one of those which had to take a back seat for obvious reasons. But, as everyday life begins to slowly recover towards some semblance of normalcy, we were mildly surprised to see businesses warm up to our offering. What has proven particularly attractive is the drastic cut down in the human touchpoints. Working at reduced capacities, the option of eliminating the agent or middle man and to be able to bypass the Ops process has helped over 30 businesses continue using Paper NACH for their day-to-day work, thus making the pilot a success.<\/span><\/p>\n

        As we progress to the next phase of the product journey, it\u2019s important to note that we at Razorpay haven\u2019t broken the wheel. The process for NACH mandates remains the same. However, what we have done is to try to improve and optimize wherever possible. The TAT for form submission, before it reaches the destination bank, can be just a few hours as opposed to taking days or even weeks in the offline system. The costs incurred by businesses using our services have also substantially reduced. All it took was a little change.\u00a0<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

        Reading Time: <\/span> 7<\/span> minutes<\/span><\/span> Change is always hard. Even more so when it\u2019s for something that\u2019s been done without question for many many years. It is not so much the process that acts as a hindrance as it is the willingness to alter the process. A similar stumbling block came our way while trying to build a product to…<\/p>\n","protected":false},"author":8,"featured_media":286,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[11,19],"class_list":["post-280","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized","tag-emandate","tag-nach"],"_links":{"self":[{"href":"https:\/\/razorpay.com\/unfiltered\/wp-json\/wp\/v2\/posts\/280","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/razorpay.com\/unfiltered\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/razorpay.com\/unfiltered\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/razorpay.com\/unfiltered\/wp-json\/wp\/v2\/users\/8"}],"replies":[{"embeddable":true,"href":"https:\/\/razorpay.com\/unfiltered\/wp-json\/wp\/v2\/comments?post=280"}],"version-history":[{"count":1,"href":"https:\/\/razorpay.com\/unfiltered\/wp-json\/wp\/v2\/posts\/280\/revisions"}],"predecessor-version":[{"id":368,"href":"https:\/\/razorpay.com\/unfiltered\/wp-json\/wp\/v2\/posts\/280\/revisions\/368"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/razorpay.com\/unfiltered\/wp-json\/wp\/v2\/media\/286"}],"wp:attachment":[{"href":"https:\/\/razorpay.com\/unfiltered\/wp-json\/wp\/v2\/media?parent=280"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/razorpay.com\/unfiltered\/wp-json\/wp\/v2\/categories?post=280"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/razorpay.com\/unfiltered\/wp-json\/wp\/v2\/tags?post=280"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}