{"id":799,"date":"2018-03-22T12:54:28","date_gmt":"2018-03-22T07:24:28","guid":{"rendered":"https:\/\/rzpwp.blog\/?p=799"},"modified":"2025-04-10T16:26:04","modified_gmt":"2025-04-10T10:56:04","slug":"npci-circular-on-upi-interoperability","status":"publish","type":"post","link":"https:\/\/razorpay.com\/blog\/npci-circular-on-upi-interoperability\/","title":{"rendered":"NPCI circular on UPI Interoperability and What it Means"},"content":{"rendered":"

NPCI recently issued a circular on 16 March titled <\/span>\u201cGuidelines on Interoperability features for all BHIM UPI Apps\u201d<\/span><\/em> (Link <\/span>here<\/span><\/a>). This circular contains the design as per which UPI payments in India will be accepted and processed in the future. <\/span><\/p>\n

Here at Razorpay, we are excited by the developments and wanted to break down the circular, so you don\u2019t have to! We have also analyzed the immediate and long-term impact of these new guidelines.
\n<\/span><\/p>\n

What is the scope of the NPCI circular? Who needs to follow it?<\/h3>\n

The circular calls out all <\/span>UPI<\/span><\/a> apps with specific mention to apps introduced by banks and third-party apps like PhonePe, Paytm and Google Tez.<\/span><\/p>\n

\"NPCI<\/p>\n

The BHIM UPI App developed by NPCI definitely falls under the purview of this circular. In addition, \u201cbank apps\u201d refers to apps developed by any bank specifically for UPI transactions, For example, BHIM SBI Pay, BHIM Axis Pay, BHIM Baroda Pay etc. <\/span><\/p>\n

Also, apps such as HDFC Bank MobileBanking and Pockets by ICICI Bank which have BHIM UPI embedded as a module also come under the purview.<\/span><\/p>\n

\u201cMerchant \/ third party\u201d apps basically covers three categories here – <\/span><\/p>\n

    \n
  1. All P2P apps which are built on top of SDKs provided by either banks or NPCI itself. PhonePe, Paytm, Google Tez etc come under the category.<\/span><\/span><\/li>\n
  2. All payment service providers who allow generation of VPA IDs via their SDKs. The relevant mobile SDK thus provided by Razorpay will have to comply with these guidelines from now on.<\/span><\/span><\/li>\n
  3. Apps such as Ola or Uber which provide you an option to onboard \/ register a customer on BHIM UPI also fall under compliance.<\/span><\/li>\n<\/ol>\n

    .<\/span>At Razorpay, we follow a methodology of trying to reduce the integration efforts of our merchants to the minimum. As a Razorpay merchant using checkout, you can rest easy knowing that you won\u2019t have to carry out any integration by yourself.<\/p>\n

    What are the new changes under the NPCI guidelines?<\/h3>\n

    The circular proposes interoperability features which will be mandatory from 16 April onwards, which are listed below – <\/span><\/p>\n

    1. Send and receive money using any BHIM UPI ID (VPA)<\/h4>\n

    \"BHIM<\/p>\n

    Though this functionality has generally existed, there have been outliers like Whatsapp <\/span>(beta stage)<\/span><\/em> where this was lacking previously. <\/span>One could only pay to Whatsapp users and UPI IDs but not collect money<\/a> via Whatsapp generated VPAs. On the last update, the functionality is still not available on iOS via Whatsapp. <\/span><\/p>\n

    Our view is that this will provide a level playing field in the market. There are a lot of incentives for any private organization in keeping the P2P payment ecosystem within their own ecosystem. But this feature will make it compulsory to provide the functionality to complete P2M transfers as well as P2P transfers outside of an app\u2019s ecosystem.<\/span><\/p>\n

    \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0Related Read: What is UPI ID & How to Create UPI ID?<\/a><\/span><\/p>\n

    2. Generate and respond to collect request from any BHIM UPI ID (VPA)<\/h4>\n

    \"Collect<\/p>\n

    This is an extension of the above feature in the sense that a collect request for payment can now be created from any UPI app. So we have both the aspects, sending someone money and asking for a payment covered well with this.<\/span><\/p>\n

    One theory is also that this feature helps limit the ability of banks \/ apps \/ PSPs to reject transactions on a business logic, say transaction starting out of another UPI app instead of their own. There haven\u2019t been any reported malpractices in this regard, but this is a welcome feature for security nevertheless. <\/span><\/p>\n

    If this holds up to potential, this makes UPI a truly interoperable system architecture in which all UPI apps can collect payments from all other apps.<\/span><\/p>\n

    3. Generate BHIM UPI QR and Scan & Pay BharatQR and BHIM UPI QR<\/h4>\n

    \"Generate<\/p>\n

    This is the feature we believe will have the most significant impact. QR codes have always been a simple, infrastructure light solution for accepting digital payments. BharatQR has been designed by the NPCI as a universal QR payments system that can be leveraged across retail stores, petrol pumps, restaurants, schools, etc <\/span><\/p>\n

    The BHIM App from day one has provided features to –<\/span><\/p>\n

      \n
    1. Showcase your own BHIM UPI QR code to collect payments (Generate)<\/span><\/li>\n
    2. Scan a QR code with a merchant or a peer from inside the app and pay (Scan & Pay)<\/span><\/li>\n<\/ol>\n

      Other apps had just provided an option to collect payments from offline merchants who had their specific QR codes for the app. The merchants\/retail stores also had to display different QR codes for each app and BharatQR<\/a> will definitely provide relief here.<\/span><\/p>\n

      As now mandated by NPCI, each app will have to support generating a Scan & Pay QR code for payments via BharatQR which means any retail store owner with a smartphone is now empowered completely. The additional functionality of BharatQR being able to collect the money from Debit & Credit cards issued by Mastercard, Visa, Amex and Rupay make this even more significant.<\/span><\/p>\n

      4. Respond to Intent call on the same phone by any BHIM UPI app or merchant<\/h4>\n

      \"Intent<\/p>\n

      The intent call is a feature by which apps on the same phone communicate with each other. An action is started in one app and a connection is made to the apps within the device that can support the particular intent on phone. <\/span><\/p>\n

      Currently, the UPI payment flow on mobile goes like this – <\/span><\/p>\n

        \n
      1. Merchant app in which UPI payments is made asks for VPA<\/a> and generates a collect request over internet.<\/span><\/li>\n
      2. An SMS is received notifying the user that the collect request has been made from the installed UPI app of choice (optional)<\/span><\/li>\n
      3. User opens up the UPI app on the phone and approves of the request by inputting their UPI PIN<\/a><\/span><\/li>\n
      4. User sees the payment successful notification on his UPI app and then switches back to Merchant App.<\/span><\/li>\n
      5. Merchant app shows the transaction as successful.<\/span><\/li>\n<\/ol>\n

        With UPI intent coming in, the crucial step in which abandonment can happen, which is switching from one app to another goes away. From the merchant app itself, you would get an option to see which UPI apps you want to transact from, click on the option and straight away jump to your choice UPI app.<\/span><\/p>\n

        This is a great improvement in terms of customer experience and also will have a positive impact on success rates. Also, with UPI intent, cases of payment abandonment will reduce. It hurts the most once you have acquired a user, converted them and the only step left is collecting payments. And the user does not complete the payment because of a trivial issue like this. <\/span><\/p>\n

        However, if you are using Razorpay\u2019s mobile SDKs, you would have the functionality within your mobile app already.<\/span><\/p>\n

        \"UPI-Intent-Low\"<\/p>\n

         <\/p>\n

        Specifications for merchant apps<\/h3>\n

        All of these features do not make sense for everyone. Like for example, a cab service aggregator does not have a requirement of users sending money anywhere except for their own current accounts.<\/span><\/p>\n

        \"7\"<\/p>\n

        Provisions have therefore been made that the merchant apps do not have to build all the features. Universal response to payment collect requests and ability to scan and pay via BharatQR or BHIM UPI QR is the only mandate that they have to follow.
        \n<\/span><\/p>\n

        What this means for the industry?<\/h3>\n

        This NPCI circular will bring about much-needed parity in terms of what features need to be built and cannot be escaped from. This has been a long standing discussion in the industry and hopefully, the concerns will now be addressed by the circulars.<\/span><\/p>\n

        The move to make BharatQR mandatory is a great step to increase the user base. Everyone in the physical world with a smartphone can now easily use a universal QR code i.e. BharatQR for collecting payments via any and every UPI app. <\/span><\/p>\n

        This could mean a significant impact on mobile wallets<\/a> that have thrived on this market for a while now but with the government push behind UPI, BHIM and BharatQR, one can only see a net positive effect on the ecosystem.<\/span><\/p>\n

        The interoperability between UPI and cards offered by BharatQR is one of the biggest wins. Rather than different organizations trying to encourage digital payments in the physical world in silos, all major card networks<\/a> including Visa and Mastercard now have incentive as well to get behind BharatQR and promote one solution.<\/span><\/p>\n

        Customer Experience also gets a major uplift once these features are universally available. Customers will have a bare minimum set of features provided by all apps and so users will have realistic expectations while shifting over. Also, features like intent will allow for a seamless experience of transacting via UPI on mobile phones and improve performance.<\/span><\/p>\n

        NPCI has called out a deadline of 16 April 2018 for the implementation of these features, with a warning that non-complying apps can have their transactions declined by PSP banks or NPCI beyond that. We believe that though workable, the deadline could have been a bit longer considering these are core infrastructure changes. <\/span><\/p>\n

        Also with payments, one eye is always focused on security and that will have to be kept in mind by all apps while making the changes.<\/span><\/p>\n

        At Razorpay, we have always believed in UPI and BharatQR as the initiative that will bring the next stage of massive adoption in digital payments. In September 2016, Razorpay was the first payments platform to provide UPI transactions to its entire merchant base. <\/span><\/p>\n

        We intend to continue on with the tradition and bring the very best of what BharatQR and UPI Intent has to offer to you. <\/span>Keep checking this space for more updates.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

        NPCI recently issued a circular on 16 March titled \u201cGuidelines on Interoperability features for all BHIM UPI Apps\u201d read on to see how we’ve explained it.<\/p>\n","protected":false},"author":22,"featured_media":808,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[26],"tags":[51,57],"class_list":{"0":"post-799","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-payments","8":"tag-payments","9":"tag-technology"},"_links":{"self":[{"href":"https:\/\/razorpay.com\/blog\/wp-json\/wp\/v2\/posts\/799","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/razorpay.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/razorpay.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/razorpay.com\/blog\/wp-json\/wp\/v2\/users\/22"}],"replies":[{"embeddable":true,"href":"https:\/\/razorpay.com\/blog\/wp-json\/wp\/v2\/comments?post=799"}],"version-history":[{"count":6,"href":"https:\/\/razorpay.com\/blog\/wp-json\/wp\/v2\/posts\/799\/revisions"}],"predecessor-version":[{"id":21936,"href":"https:\/\/razorpay.com\/blog\/wp-json\/wp\/v2\/posts\/799\/revisions\/21936"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/razorpay.com\/blog\/wp-json\/wp\/v2\/media\/808"}],"wp:attachment":[{"href":"https:\/\/razorpay.com\/blog\/wp-json\/wp\/v2\/media?parent=799"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/razorpay.com\/blog\/wp-json\/wp\/v2\/categories?post=799"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/razorpay.com\/blog\/wp-json\/wp\/v2\/tags?post=799"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}