Explaining UPI — Bharat QR integration
Unified Payments Interface is the network powering the UPI / BHIM family of payment apps which lets consumers make and receive payments, and has its own QR code specifications. Most UPI apps let users generate a QR code for their VPA and since the specification is open, users can create QR codes following the scheme and use it for receiving payments.
UPI QR Code — Linking Specifications
- It’s a URI scheme, which when scanned on a phone can raise an intent to open UPI apps installed on the phone.
- Caters to both P2P as well as P2M transactions with some fields like txn_id specific for merchant transactions.
- Interoperable across all UPI applications.
- Pre-populates the transaction specific values, presents to users to directly authorise the transaction without having to enter values. In case of static QR codes, amount needs to be manually entered. Authorization through UPI PIN.
- Since UPI itself is linked to bank accounts only, option of paying with credit card doesn't arise.
- UPI is a single payment system and flows through a single payment network, hence data is available at NPCI and is published.
- When scanned, UPI QR looks like
The URI above contains series of values to identify payee and transaction specific metadata.
QR Code specifications created jointly by card networks VISA, MasterCard and Rupay to enable asset light digital payments for small merchants without the need for having a PoS machine. A consumer having a BharatQR enabled mobile banking app linked to debit / credit cards can scan the merchant’s QR code and complete the transaction. The merchant can choose to generate a static QR code for display in the store and even generate QR codes dynamically for each transaction. When static codes are used, the customer will have to enter the payment amount, while for dynamic codes, the amount and the merchant information is embedded in the QR code itself. The acquirer bank (of the merchant) allocates different merchant codes for each of the card networks and transaction goes through depending on the customer’s card network.
- It’s a Tag Length value based string encoding the merchant identifiers which when scanned inside mobile banking app with Bharat QR support can pre-populate transaction values.
- Caters only P2M transactions, effectively creating a digital, asset light PoS
- Pre-populates the transaction specific values, presents to users to directly authorize the transaction without having to enter values. In case of static QR codes, amount needs to be manually entered. Authorization may / may not have additional PIN entry, since the app itself is open only after PIN / password.
- Use of credit card too permitted, if the support exists in payment app.
- Bharat QR is a assortment of payment networks and transactions flow through multiple card networks(VISA,Mastercard,Rupay), and other payment networks(UPI and AePS soon), data on its usage is hence available at different networks, which are not published by respective owners.
- When scanned Bharat QR looks like
The text above in italics represent the tag identifiers and corresponding text in bold represent the tag values containing merchant payment identifiers across payment networks, transaction metadata and merchant information.
The need for integration
Aside from the notion of “Single QR” format, the real reason behind the integration move seems to leverage on other platform’s benefits. The UPI, even after 20 M downloads, growing transaction volumes, is still predominantly P2P, online / app based merchant payments and is hardly seen / accepted in brick and mortar stores, even at places where other digital modes are accepted.
Bharat QR on the other hand, which inherits the mVISA merchant base, offers incentives to acquiring banks which are more used to traditional modes merchant acquisition, rallies behind an established existing settlement systems which are used for PoS machines as against sometimes troubling IMPS (Oh where is the data, lets cover it later) settlement infrastructure. But the downside is, even after dozen odd banks updating its app to integrate Bharat QR, consumers do not use it much, as against popular UPI apps like BHIM, PhonePe which have strong brand recall.
Integration & Impact
As per a recent NPCI circular, all Bharat QR stickers / QR Codes generated after Sep 15, must have UPI VPA embedded as part of Bharat QR all UPI apps must support scanning Bharat QR code and auto populating the transaction similar to a UPI QR code and the transaction would be performed as UPI transaction.
A newer Bharat QR deployed might contain UPI handle
The integration will provide users more opportunities to pay using their UPI apps. One could see fewer stickers at shops, as wallets would be soon part of UPI and merchants might be dealing with fewer systems than before, without losing out on the user base. For acquiring banks, this could drive some volume into their UPI infrastructure, could make them remain invested in UPI, even though their apps might not have been a hit. There was also a talk of integrating Aadhaar Pay into Bharat QR a while back. By placing (almost) all payment systems into a single QR code, it gives the ultimate choice to consumer to use preferred payment mode / app.
We are probably going to be surrounded by QR codes sometime soon. Beyond app discovery / installs, browsing pages, making payments, there will soon be authorised instructions through QR codes as well — UPI e-mandates too has a QR code structure, which can launch the mandate creation screen pre-populating the values for the standing instructions. Filling forms / calling up your credit card provider’s customer care to convert purchases to EMI may soon be a thing of past when one can scan a QR code, get a notification on the app to create a SI.