Skip to main content

Missed call to pay on KooKoo using UPI

The launch of UPI can be considered as a watershed moment. This has opened up a whole new way of sending and receiving payments and will surely lead to a lot of innovation.
The API is really well designed for a government effort. But guess it was expected given the great efforts put in by a lot of volunteers. So,hats off to them.
Whenever innovative things happen, you know KooKoo is not far behind :)
So, in this blog post, I will show you an easy way to collect payments using a missed call.

1. Register for a KooKoo missed call account. and specify an app URL. You will receive a missed call number.
2. When some one calls on your missed call number, KooKoo makes a http request to your URL with the caller details.
3. Build UPI payment request URL based on specification provided by NCPI. So lets say your VPA is ozonetel@somebank and you need to request Rs.2, your request will be something like, upi://pay?pa=ozonetel@somebank&am=2.
4. Send this link in an SMS back to the caller. The caller can use this link to pay for the amount.

Wanna see this in action, just give a  
Missed Call to +918030088469(080-30088469)

I have made some small adjustments. Since the upi:// protocol is still not recognized by messaging apps, I have redirected through a web URL so that the link becomes clickable. Just click on the link in the SMS and pay. This assumes you have an app installed which understands UPI(This is most of the bank apps)

This is a very basic use case which we have showcased. You can now use a phone number to collect payments. You can even do IVR payments

UPI is still in early stages. This is really good for P2P payments, but the merchant payment piece is still lagging in some respects. I am sure, things will be resolved soon.

Thanks:

Popular posts from this blog

Integrating Arborjs with Angular to create a live calls dashboard

Arborjs  is a cool graph visualization library. Angular  is one of the best JavaScript frameworks and we have been using Angular in a lot of our front end development. When you handle millions of calls, proper visualization becomes very important. Without proper visualization, you can get lost in the mountains of data. So we spend a lot of time to come up with good visualizations to represent the data. Since we loved the cool way in which Arbor represented graph data, we could not wait to hook it up with Angular. Because of Angular's two way data binding, when you hook up Angularjs with Arbor.js you can get a dynamically updated visualization of graph data with cool animations. To give back to the community, we have put up the code online at Github . Basically we have created an Angularjs directive for Arborjs. Please feel free to fork the code and add extensions and use it for your own visualizations. The code is self explanatory with comments inline. Best way to ...

First Post

In this blog, I will be talking about my experiences in trying to build a cloud telephony platform , KooKoo . Along the way I will also be talking about different design choices I made, good programming practices and the IVR domain in general. For technoratti: NNFJW8EW86C3

Cloud Telephony-History and state of the art

Well, its been 11 years since Twilio launched their voice API in November 2008. I would say that was a major turning point in the cloud telephony industry. Before that, for people to build telephony applications, you either had to depend on proprietary platforms like Avaya dialog designer or build on arcane technologies like VXML which again was supported at varying degrees by the incumbents. Enter Twilio with their voice API and the industry changed for the better. Since it's been almost 11 years now I thought now might be a good time to do a comprehensive review of the cloud telephony industry as a whole in general and in India in particular. The Beginning Twilio was undoubtedly the startup which ushered in the era of cloud telephony. They started in November 2008. At that time in India, we at Ozonetel had launched a hosted VXML platform. There were no takers. After all who coded in VXML :) So when Twilio launched and we saw them take off, we immediately realized tha...