Taking a new look at USSD for mobile banking

USSD or Unstructured Supplementary Service Data is a capability of all GSM phones. It is a technology that is built into the signalling layer of the GSM specification, and is therefore already present in all GSM phones and networks. It is session oriented, unlike SMS which is a store-and-forward, transaction-oriented technology. Using an Internet analogy: If SMS is email, USSD is Telnet.

You may wonder? Telnet? My phone has Telnet ability? Yes. It is a powerful technology with many applications, and it is particularly useful for mobile banking and mobile payment. USSD opens a secure session that leaves no message trail and requires no local storage in the phone.

USSD response times are faster than SMS, and there is a session between the application and the mobile phone, just like a remote, old style, mainframe terminal. This means that if a carrier includes a USSD gateway into their network you can easily build all kinds of applications for a mass user base (yes, even old GSM phones can use USSD). USSD is part of the standard GMS stack, and all that is required to implement it is the USSD gateway.

Other than its use for banking and terminal initiated sessions, USSD also has server initiated messages that can be used, for example, for local oriented marketing. We can send a service message to all the users near a particulare base station indicating that a nearby store is running a sale.

Unfortunately most carriers and Value Added Service companies have never heard of USSD. Why? Well this can be explained when you understand the culture prevailing in mobile carriers, particularly in the developing world. I have had the opportunity to meet and I know lots of people from a number of different carriers. I have even had the opportunity to watch some of these carrier owners talk, and can confirm first hand that the culture prohibits the exploration of technologies such as USSD.

I also believe that in most companies, the owners or the founders are responsible for setting the tune of the company or the corporate culture. Once this is in place, it is very difficult to change. Therefore – if you know the origin of the company, you can take an educated guess as to what to expect when you try to do business with them.

Everybody knows that the cell phone carrier business is a good business to be in, particularly in the developing world, because people in these markets have very few alternative communication options. And since everybody needs to communicate, no matter how poor they are, the market is captive.

Every country has its upper class, wealthy and successful people. Again, no matter how poor the country is, there is always someone rich enough. It can be a land owner, coffee salesman, a politically influential oil company owner … there is always someone wealthy enough to buy or build his own carrier. It is no surprise that most countries have GSM coverage.

Contrary to popular belief, you don’t need to know a thing about technology or networking to build your own carrier. You can always call Sony Ericsson or Nokia-Siemens and tell them “I have purchased a spectrum from my country’s government, and now I want you to build a GSM carrier network for me”. They will be glad to do it.

After your business is up and running, thanks to the GSM standard you can try to make your operational costs lower by using other network providers and playing them against each other. Then you can start doing what you are good at. These guys are good into buying cheap and selling high, understanding their customers’ needs and how things work in their country.

As a technology provider we have to understand how these companies operate to enable us to work with them. If you want to sell a great technical project to them you have to understand that they don’t care about technology, and can barely understand how great or innovative your idea is. They want to increase their profit and they know that their user base is very different from their European or Japanese counterparts. They probably understand their user base a lot better than you do. Be prepared to learn from them, be patient in explaining the good points of your product and be ready to adapt to whatever they have in mind. Keep in mind that you will have a more difficult sell and probably a lower margin than you can could get from European carriers. You will probably have to shoulder all the risk for yourself and try to negotiate a kind of revenue sharing that does not require investments from them.

As a user I just want to have more payment options. As a technical guy I know that USSD can enable people that cannot have a bank account today to have access to banking services. Thus, I have to say that USSD technology may be old but it’s very new and useful in many places.

Related Posts

  1. Mobile Payment Systems – An Itch Just Waiting To Be Scratched?
  2. Could Apple’s rejection of NFC disrupt the mobile payments industry?
  3. The proliferation of mobile VoIP and the potential effect on cell network operators
  4. Developing Apps for Mobile
  5. Developer problem solving technique #1: Taking a mental break

Categories: Mobile  |  Tags: , , , , ,

Roberto Nunes

Roberto is a hands on manager, developer and solution architect focused on turning great ideas into reality. A confessed geek, he has been in love with internet since day one.
  • http://stii.co.za Stii

    Damn straight! Great, interesting article Roberto. Much opportunities do exist with ‘old’ tech like these!

  • Peterhd

    Ja very interesting, Question, can only the carrier build the gateway or is the analogy to telnet (or ssh if its is seccure) such that one could build ones own gateway?

  • Roberto Nunes

    The USSD gateway must be installed inside the carrier network but once installed a single gateway can be used to connect to any number of external providers/applications. Some carriers outsource their gateways but they usually have some control over it (just like an WAP gateway).

  • Roberto Nunes

    A video demostrationg USSD in a very old phone

  • Roberto Nunes
  • Peterhd

    The video certainly takes one back in time but there are definitely opportunities there. Check out Jacques’s post wrt Africa.

  • Roberto Nunes

    Yes, for example today in Brazil we have much more cell phones them bank accounts. There is a great opportunity to provide banking services via this kind of technology for people who cannot afford regular bank accounts.

  • http://eyeline.mobi/blog Ivan Komarov

    You are 100% right. We are in USSD and indeed, the main obstacle is the mindset of operators. However, now we are close to overcome this and have USSD as an operator independent (at least for third parties) technology.

    There are still issues with security for mobile banking, but their existence depends on the nature of mobile banking that you want to provide.

    Visit my blog, where USSD is discussed at http://www.eyeline.mobi/blog/category/ussd/

  • http://manjerok.ru/blog/2008/10/11/links-for-2008-10-11/ links for 2008-10-11

    [...] Taking a new look at USSD for mobile banking | MIH SWAT (tags: blog) [...]

  • http://www.sessa.co.za Stefano

    What irks me is that USSD generally cuts out after 1 and a half minutes of use…. Not ideal when doing banking.

  • http://www.mihswat.com/2008/11/08/mobile-payment-systems/ Mobile Payment Systems – An Itch Just Waiting To Be Scratched? | MIH SWAT

    [...] and operators to wake up and smell the mobile money? As Roberto reported earlier on the SWAT Blog, USSD is another great potential enabling technology for mobile banking and payments, especially when it comes to the unbanked. The text-based [...]

  • http://itechkranti.blogspot.com Sachin

    Hey i want to develop USSD application for banking as a project how can i start?
    any references? plz
    thankx

  • marvin

    i also want to develop a USSD application, is there a specific programming language or how do i go about it?

  • Tashinga Pemhiwa

    Hi I am also looking to develop USSD applications. Where can I get information regarding USSD: tutorials, open source tools, etc, please?

blog comments powered by Disqus