EximSoft International - Innovative Software Resource Partner


					Careers		Sitemap


You are here : home >> showcase >> Mobile E-Commerce Trial System

	Showcase / Case Study

	Voice of Our IP Telephony

	Security Toolkits Porting

	Mobile E-Commerce Trial System

	Mobile Games Porting

	Security Messaging System

	Global Customer Support

	Cashless Meterless Parking

Mobile E-Commerce Trial System

A mobile e-commerce system is in development for experimental use by a global wireless equipment manufacturer. The system is aimed at demonstrating wireless commerce applications using a mobile phone in a real world environment. As such, the system is currently focused on security and authentication in order to raise user confidence in making purchases over mobile systems.

To address the need for confidence, our system supports making secure payment transactions from a Shopping Cart using signText for user authentication. This authentication is augmented with merchant identification to improve the validation of the payment transaction through the Payment Proxy/ Institutions. The phones have a SIM/WIM Smartcard that is used for cryptographic and Wireless Application Protocol (WAP) functions. The phones communicate through a live wireless data connection to several servers on the Internet. The internet servers include WTLS WAP gateway. Merchant and Payment Proxy servers.

EximSoft is responsible for all of the software development on the Merchant, and Payment Proxy servers. This responsibility includes end-to-end integration at the customer's location, and management of the project. The development for the lab demo has been completed in January, 2002. The software is packaged with Java APIs so that they may be readily extended for use in the customer's planned second phase. We are a partner with Entrust Technologies and, as such, EximSoft is incorporating PKI technology into our payment systems.

The MeT Account-Based Payment scenario specification is a public source of information about the application we are developing, although in our case the WAP Gateway and Merchant functions are separate. The scenario specification can be found at the link.