Skip to main content

Nokia Mobile Money Service

Yesterday while roaming at FC road, some marketing people from Nokia-Yes bank came to me and explained the newly launched Nokia mobile money service. The service is launched in Pune and Chandigarh on an introductory basis. The mobile application is available to Nokia handset users only.

They told that I have to pay 100 bucks for registration, and in return they will create a mobile payment account with Yes bank, credited with 100 bucks. The balance can be used either for payment at selected merchant locations, recharging / topping-up anyone's mobile account, transferring balance to another user's account or paying the utility bills. The added advantage is that after first payment via the application, Nokia credits an additional 50 bucks (within 24 hours).

For registration, they noted down my details and downloaded the application using a memory card. Then they sent an SMS using their mobile, and within 10 minutes, we got the account created with 100 bucks. They also did the first transaction, by topping up my account. Around 20 hours later, I also received the promotional reward of 50 bucks from Nokia.

Users can access the service via four modes: application, WAP, SMS, and IVR. Currently, only application mode is working and rest are not. For every transaction done using the application, one SMS charge is deducted.

More details can be found at http://www.mobilemoneyservices.co.in.

Comments

Popular posts from this blog

MPlayer subtitle font problem in Windows

While playing a video with subtitles in mplayer, I was getting the following problem: New_Face failed. Maybe the font path is wrong. Please supply the text font file (~/.mplayer/subfont.ttf). Solution is as follows: Right click on "My Computer". Select "Properties". Go to "Advanced" tab. Click on "Environment Variables". Delete "HOME" variable from User / System variables.

Kafka performance tuning

Performance Tuning of Kafka is critical when your cluster grow in size. Below are few points to consider to improve Kafka performance: Consumer group ID : Never use same exact consumer group ID for dozens of machines consuming from different topics. All of those commits will end up on the same exact partition of __consumer_offsets , hence the same broker, and this might in turn cause performance problems. Choose the consumer group ID to group_id+topic_name . Skewed : A broker is skewed if its number of partitions is greater that the average of partitions per broker on the given topic. Example: 2 brokers share 4 partitions, if one of them has 3 partitions, it is skewed (3 > 2). Try to make sure that none of the brokers is skewed. Spread : Brokers spread is the percentage of brokers in the cluster that has partitions for the given topic. Example: 3 brokers share a topic that has 2 partitions, so 66% of the brokers have partitions for this topic. Try to achieve 100% broker spread

wget and curl behind corporate proxy throws certificate is not trusted or certificate doesn't have a known issuer

If you try to run wget or curl in Ununtu/Debian behind corporate proxy, you might receive errors like: ERROR: The certificate of 'apertium.projectjj.com' is not trusted. ERROR: The certificate of 'apertium.projectjj.com' doesn't have a known issuer. wget https://apertium.projectjj.com/apt/apertium-packaging.public.gpg ERROR: cannot verify apertium.projectjj.com's certificate, issued by 'emailAddress=proxyteam@corporate.proxy.com,CN=diassl.corporate.proxy.com,OU=Division UK,O=Group name,L=Company,ST=GB,C=UK': Unable to locally verify the issuer's authority. To connect to apertium.projectjj.com insecurely, use `--no-check-certificate'. To solution is to install your company's CA certificate in Ubuntu. In Windows, open the first part of URL in your web browser. e.g. open https://apertium.projectjj.com in web browser. If you inspect the certifcate, you will see the same CN (diassl.corporate.proxy.com), as reported by the error above