MTS (Monetary Transaction System)

Market Drivers
Nowadays market demand is specially focused on the following concepts:
Massive access
Ease of use
Simplicity
0 time consuming
100% availability (24/7)
Based on these, eCommerce appeared. However, eCommerce dependence on Internet is not convenient. To solve this issue, 
the mCommerce(mobile Commerce) concept arose, incorporating
 the main mobile technologies available,such as SMS, USSD and Web.Consequently,
mobile money solutions appeared.
Product Overview
MTS  is a Mobile Money solution that enables mobile phones to
perform eMoney transactions from standard GSM handsets
by means of USSD, IVR, SMS or Web.
MTS brings a complete new way of managing money. MTS enables mobile subscribers to have
 prepaid virtual wallets associated to their mobile accounts from
 where they can pay goods and utilities, or send money to family and friends, gaining
 security by reducing real money transactions. These are now replaced by
 electronic transactions. MTShelps making the prepaid model more
 profitable and at the same time gives subscribers a more convenient mobile services.
Subscribers can TopUP their eWallet accounts at authorized mobile agents (retailers) 
or directly through a subscriber’s bank account or credit card(cash inoperation).
 The cash in process credits the subscriber account into the MTS platform and debits the retailer’s
account, while the subscriber hand cashes
to the retailer. Subscribers can then manage their electronic funds directly
 from their mobile phones or convert it to cash at authorized stores (cash outoperation).
The solution holds interfaces with the operator’s Prepaid and Postpaid platforms, Billing
 System, Bank and Credit Card Gateways, and external gateways for utilities 
and goods payments. MAP links are used for USSD transactions and SMS transaction
 confirmation messages.

 


Key features:
USSD-based platform (SMS, IVR and Web interactions are also available)
Agents distribution chain and commissions configuration
Multiple  e-Money services:
1.Salary Payment
2.Bill Payment
3.Retail Purchases
4.Remittances
5.Self Top-UP
Security standards compliant (in-built fraud module);
Wester Union certified interface for international remittances;
API interface for allowing external entities to develop mobile money services;
High performance;
Scalability;
Standard integration interfaces with financial entities.

How To Bulid A Mobile Website

Over the past few years, mobile web usage has considerably increased to the point that webdevelopers and designers can no longer afford to ignore it.In wealthy countries,the shift is being fuele-d by faster mobile broadband connections and cheaper data service. However, a large increase has alsobeen seen in developing nations where people have skipped over buying PCs and gone straight to mobile.
Unfortunately, the mobile arena introduces a layer of complexity that can be difficult for developers to accommodate. Mobile development is more than cross-browser, it should be cross platform. The vast number of mobile devices makes thorough testing a practical impossibility, leaving developers nostalgic for the days when they only had to support legacy browsers.
In addition to supporting different platforms, each device may use any number of mobile web browsers. For instance, an Android user could access your site using the native Android browser, or could have also installed Opera Mini or Firefox Mobile. It’s fine as long as the smartphone uses a progressive web browser (and it’s safe to say that most browsers are progressive nowadays), but it doesn’t have to.

The mobile web reintroduces several issues that have been largely ignored in recent years. First, evenwith 4G networks, bandwidth becomes a serious issue for mobile consumers. Additionally, mobile devices have a significantly reduced screen size, which presents screen real estate issues that have not existed since the days of projection monitors. Combine these issues with crossplatform compatibility problems,and it isn’t hard to see how mobile development is a lot like‘stepping backwards in time’. So let’s tackle these issues one at a time and create a road map for mobile web development: 1.How To Implement Mobile Stylesheets 2.What To Change With Mobile Stylesheets 3 .Beyond Stylesheets 4. Special Concerns For iPhone / iPad
1.How To Implement Mobile StylesheetsThe first step to adding mobile support to a website is including a special stylesheet to adjustthe CSS for mobile devices:SERVER-SIDE METHODS & THE UA STRINGOne approach to including mobile stylesheets involves detecting the user agent string with a serverside language such as PHP. With this technique, the site detects mobile devices and either serves an appropriate stylesheet or redirects the user to a mobile subdomain, for instance m.facebook.com. This serverside approach has several advantages: it guarantees the highest level of compatibility and also allows thewebsite to serve special mark-up/content to mobile users.
While this technique is perfect for enterprise level websites, there are practical concerns that makeit difficult to implement on most sites. New user agent strings come out almost daily, so keepingthe UA list current is next to impossible. Additionally, this approach depends on the device torelay its true user agent. Even though, browsers have spoofed their UA string to get around this type of detection in the past. For instance, most UA strings still start with “Mozilla” to get through the Netscape checks used in the 90′s, and for several years Opera pretended to be IE. As Peter-Paul Koch writes:

CLIENT-SIDE METHODS & MEDIA QUERIESAlternately, the easiest approach involves detecting the mobile device on the client side. One of the earliesttechniques for including mobile stylesheets involves taking advantage of the stylesheet’s media type, for instance:<link rel=”stylesheet” href=”site.css” media=”screen” /> <link rel=”stylesheet” href=”mobile.css” media=”handheld” />Here we’ve included two stylesheets, the first site.css targets desktops and laptops using the screen media type, while the second mobile.css targets mobile devices using handheld. While this would otherwise be an excellent approach, device support is another issue. Older mobile devices tend to support thehandheld media type, however they vary in their implementation: some disable the screen stylesheets and only load handheld, whereas others load both.
Additionally, most newer devices have done away with the handheld distinction altogether, in order toserve their users fully-featured web pages as opposed to duller mobile layouts. To support newer devices,we’ll need to use media queries, which allow us to target styles to the device width (you can see another practical adaptation of media queries in Ethan Marcotte’s articleResponsive Web Design). Since mobile devices typically have smaller screens, we can target handheld devices by detecting screens that are 480px and smaller:<link rel=”stylesheet” href=”mobile.css” media=”only screen and (max-device width:480px)”/>While this targets most newer devices, many older devices don’t support media queries, so we’ll need ahybrid approach to get the largest market penetration.First, define two stylesheets: screen.css with everything for normal browsers and antiscreen.css to overwrite any styles that you don’t want on mobile devices. Tie these two stylesheets together in ano-ther stylesheet core.css:@import url(“screen.css”); @import url(“antiscreen.css”) handheld; @import url(“antiscreen.css”) onlyscreen and (max-device-width:480px);Finally, define another stylesheet handheld.css with additional styling for mobile browsers and link them on the page:<link rel=”stylesheet” href=”core.css” media=”screen”/> <link rel=”stylesheet” href=”handheld.css” media=”handheld, only screen and (max-device-width:480px)”/>While this technique reaches a large market share of mobile devices, it is by no means perfect. Some mobile devices such as iPad are more than 480 pixels wide and will not work with this method. However, these larger devices arguably don’t need a condensed mobile layout. Moving forward, there will likely be more devices that don’t fit into this mold. Unfortunately, it is very difficult to futureproof mobile detection, since standards are still emerging.Besides device detection, the media query approach also presents other issues. Mainly, media queries can only style content differently and provide no control over content delivery. For instance, a media query can be used to hide a side column’s content, but it cannot prevent that markup from being downloaded by your users. Given mobile bandwidth issues, this additional HTMlshould not simply be ignored.

Considering the difficulties with mobile UA detection and the pitfalls of media queries, some companies such as IKEA have opted to simply allow the user to decide whether to view the mobile version of their website. While this has the clear disadvantage of requiring more user interaction, it is arguably the most fool-proof method and also the easiest to accomplish.The site contains a link that reads “Visit our mobile site” which transports the user to a mobile subdomain. This approach has some drawbacks. Of course, some mobile users may miss the link, and other non-mobile visitors may click it, since it is visible regardless of what device is being used. Even though, this technique has the advantage of allowing the user to make the mobile decision.Some users prefer a condensed layout that is optimized for their device, whereas other users may prefer to access the entire website, without the restrictions of a limited mobile layout.

 

 

Watch Out, E-Commerce and M-Commerce: Here Comes ‘F-Commerce’ and He’s everywhere and Ready to Steal Your Girlfriend

Make room on the spreadsheet, there’s a new Romeo in town. Business’ romance with new revenue channels is a tortured tale. E-Commerce is now beloved and has had a home among st the Excel columns for some time, but the courtship wasn’t easy. M-Commerce has just barely made the conversation, let alone the financial and segmentation review, but we’re interested and willing to date. And to tell you the truth,Turn your e-commerce store into an m-commerce app. Offer your products on a range of mobile devices.Now here comes F-Commerce, strutting his social media bling, all spiffy, full of promise, and Facebook-y.Damn, I love this guy. And, yes, the “F” stands for Facebook. As in “Facebook Commerce.” The next final frontier.

Although I did not make the NRF’s Innovate 2011 conference (thanks to the Continental/United airlines “cluster-merge,” which bungled, canceled, and otherwise screwed the pooch and my travel plans) – Facebook and the ability to sell products and make money was a topic du jour.

Wet Seal was a prime example. According to Investor’s business daily, Chief Information Officer, Jon Kubo, explained the company’s recent efforts, which included a social-media-driven model search contest, giving customers the ability to build and recommend outfits, and an iPhone game that lets customers run their own virtual Wet Seal stores.

By Kubo’s account, the model search started with video postings on Facebook and YouTube and drew 35,000 entries. By involving customers in every step of the contest, the company generated 100,000 store visits, 300,000 YouTube views, and 10 million Facebook posts.IBD reported that the interactive approach has helped Wet Seal accumulate 1.3 million Facebook fans, placing it among the top 15 retailers by that measure, Kubo says.By Kubo’s estimate, the company’s social media efforts are generating 20% of Wet Seal’s e-commerce sales. He ranks the return on investment among the best he’s ever gotten from a tech project.

At Lane Bryant, we did a model search in the same manner  I’m interested in how Wet Seal measured all of this, particularly the store visits. I’ll shoot Kubo an email and see if he’ll spill the beans.

Many businesses, including mine, are having success driving sales via Facebook. Good news, there’s still a long way to go. The discovery of what works and what surprises is much of the fun. But the promise is undeniable, unstoppable, and substantial.

Facebook is now an ecosystem, and hardly qualifies as social media, a website, or even the internet anymore. Me and most of my followers connect by a mobile device decidedly more often than by computer.

But I disagree with Kubo that “engagement” is the Holy Grail. The concept of engagement as a goal is lazy marketing-speak that’s too easy to hide behind in the absence of activating a customer or fan base to buy your products in numbers enough to matter (although Kubo says Wet Seal did accomplish that). Rather, I contend, engagement is the first step to social sales, as I outlined in The Art of Social Sales (click to get your copy) two years ago.

The difference between engagement and social sales is that engagement is like chatting in a coffee shop. It’s pleasant. It makes both parties feel good. It has value. But the result of social sales is a delighted customer trucking home or to the shopping cart with your products in a bag.

The true art of social sales is understanding how to move your strategy from engagement to consideration to activation to purchase, and to do it with honesty, persuasion, and grace. Potential customers do not follow brands because they mistakenly think they’re people. But they will respond to brands which humanize themselves, creating the opportunity for engagement. A good social media strategy must pull the engaged follower through the purchase cycle to reap the rewards of engagement.

Business may entertain social media as an expense in the face of all the chatter about it, but eventually the cash register had better ring, and ring consistently.

E-Commerce. M-Commerce. F-Commerce. There’s room for all of these, since it’s more about customer channel of preference than which platform wins. The only losers are the businesses not migrating to where its shoppers are headed.

Still, I’d keep an eye on your girlfriend anyway. That Zuckerberg dude may dress a little crappy, but rumor is he’s about to throw a hell of a party over at his place.