|
The following is an excerpt from a Mobile Money Transfer Report prepared by the GSM World Association: http://mmt.gsmworld.com/
Channels:
The mobile channel that the consumer will adopt is a key deciding factor on which mobile payment technology to support. The channels identified are:
Client Side –
Server Side –
Each channel presents differing benefits and concerns and can have an affect market adoption and the security of the application. Ironically the best technical and most secure solution (SIM) also has the highest barriers to implementation.
With SIM based/dependant applications it is understood that the consumer would have to either swap their SIM for another SIM bearing the application, or have the application downloaded to their SIM from the network. This has proven to be a stumbling block in many markets where consumers do not take to solutions that require consumer intervention in getting the application.
SIM based applications are however the most secure in that the data can be encrypted on the actual SIM card and be transported from the device to the bank in an encrypted format. SIM-based applications do offer the ability to prevent churn in that the consumer SIM is owned by the network.
JAVA applications offer a higher level of aesthetic value for the user than SIM, but face the same accessibility problems in getting the application to the device. JAVA applications reside on the actual device and need to be downloaded by the consumer. This typically requires a GPRS connection to a network and knowledge of how to access the site from which the application needs to be downloaded. This application could pose an issue in the usability of the service if the consumer has not already configured GPRS on their phone. Once the consumer has the application on the phone they should not see any further problems.
To alleviate the concerns around accessibility, MNO’s could have the application pre-installed on handsets as they saturate the market. This would mean that the consumer would not be affected by the download or settings required to operate the application.
It is believed that that the source from which you are downloading the application cannot be verified by the consumer and steps should be put in place not to make the application publicly available but rather facilitate a download process as part of registering for the service. There is not immediate lock in of the consumer to the MNO on JAVA as it can communicate across any network. It is also a concern, as with any client side application, that consumers would have to reload the application if the bank/MNO were to modify the application in any way.
USSD2 is a channel that has been successfully used in mobile banking implementations as an alternative to menu driven SIM based applications, in markets where the bank or MNO believe that the consumer swap or download would affect the adoption rate.
USSD2 does not offer the device level encryption of data and thus would require business rules and methodologies in protecting the consumer’s data. If the network supports USSD2, effectively each consumer can use the channel without affecting the SIM or the device.
IVR (interactive voice response) is DTMF tone entry in response to a voice based menu presented to the consumer. The most common channel for the consumer as the consumer knows how to make a call. The channel offers education on the phone in that the consumer can be instructed in their language.
The channel has existed for many years as telephone banking and is thus not innovative or new to the banking world. It suits emerging markets or markets that do not have any other technology choice.
The channel is seen to be expensive to the consumer that has to dial in to use the service at their going call tariff rate.
SMS based applications may be the simplest form of mobile banking implementation. The solution is not intuitive and has no aesthetic value but is as simple as sending an SMS.
SMS is used primarily as an informational banking tool as opposed to transactional banking. The reason being that transactional banking requires certain levels of security, and while SMS is encrypted using the standard GSM encryption across the air, it is stored in the sent items of the consumers handset, and possible stored in the open at the network and at the vendor.
There are examples of Transactional banking implementations on SMS where the risk has been managed through limitations in transaction amounts and data transmission.
WAP based solutions offer aesthetic value and a similar experience to that of the internet. It is device dependant and requires a GPRS connection with the network.
Consumers usually do not know how to browse on their mobile phones or have not configured GPRS.
|