You Are Here:

Community: Blogs

Paul Coulton's Forum Nokia Blog

XML enabled payment scheme for mobile

coultonp | 25 June, 2006 15:31

Most new entrants into the mobile commerce marketplace are faced with a paradox; how can we attract users without merchants?, and how can we attract merchants without customers?

Without a huge investment in marketing to build consumer recognition, starting a new m-commerce service is risky.  Many successful companies on the web have managed to create successful payment services by utilizing the brand recognition and ubiquity of the popular card networks.  Attempts to marry credit cards and mobile phones are not new – encrypted phone wallet systems have been bundled with devices for a number of years. However, use of these wallet systems remains limited as the public failed to embrace shopping via WAP, frustrated by slow speeds and poor user interfaces. With mobile terminals more suited for browsing, and higher speeds from mobile data becoming the norm, we have developed a system to enable remote macro-purchases using existing credit card technology.

 

A number of banks use payment processing software from ClearCommerce Corp. to allow their customers who want to take credit card payments on-line to integrate payments into their e-commerce solution. ClearCommerce provides an XML payment API for e-commerce website builders to send complete information about a transaction to a capturing server at the associated financial institution. Typically an e-commerce web-server will generate an XML document associated with a transaction, including details about the products in the order, the delivery address, total price etc. This document is then sent to the bank’s processing servers, often via a HTTPS (Secure Sockets Layer-enabled) POST form. Merchants are able to define specific security rules that control a transaction, specifically using the Address Verification Service (AVS) to determine whether the delivery address matches the address registered with the card account. Further, advanced fraud detection rules can prevent transactions continuing given suspicious buying patterns such as a card being used to repeatedly buy high-value items.

 

The XEPS (XML-Enabled Payment System) project attempts to create a framework whereby developers could add this functionality to mobile applications and complete a transaction entirely from the device. This project used Python for Series 60 Nokia mobile phones in order to rapidly develop the concept on a mobile device. However, Python for Series 60 (PyS60) does not offer the complete XML package associated with standard Python releases. Fortunately, researchers at the Helsinki Institute for Information Technology have ported the pyexpat Python XML module from the full Python release for use with Python Series 60. This module enabled the generation of well-formed XML documents from the appropriate function calls.

payment scheme structure

The application was tested using the most verbose output XML that may be used to describe a transaction. This is quite a sizeable document for a device with only limited power to generate, approximately 200 lines of XML. In a real transaction, for something relatively simple, like a ticket for a train, the necessary XML describing the transaction may only be one-tenth of this length.

 

The generated XML feed is able to completely describe a transaction, including relevant shipping/billing addresses, recurrent order status, security features etc.

 

The full paper is being presented by one of our PhD students, Phil Garner,at the Mobile Business (ICMB 2006) conference today if anyone is attending the event and the XEPS software is available our research group website. 

 

 

 

RSSComments

You must login to post comments. Login
 

Rate This

 
 
Bookmark this page: DeliciousDiggFacebookGoogleYahooStumbleUponRedditDiigoTechnocratiTwitter  Share this page Share this page Print this Page Print this page Invite a friend Invite a friend
京ICP备05048969号    Email Newsletters Press Terms & Conditions Privacy Policy Sitemap Contact Us © 2009 Nokia 
RDF Facets: qdcZdescriptionQSxMyE20principalE20interestE20inE20mobileE20applicationsE20isE20toE20pushE20theE20boundariesE20ofE20innovationE20toE20createE20uniE71uelyE20mobileE20eE78periencesE2eE20IE20hopeE20myE20blogsE20eE78citeE20andE20challengeE20developersE20toE20thinkE20E27outsideE20theE20boE78E27E2eE20coultonpE20E7cE2025E20JuneE2cE202006E2015E3a31E20MostE20newE20entrantsE20intoE20theE20mobileE20commerceE20marketplaceE20areE20facedE20withE20aE20paradoE78E3bE20howE20canE20weE20attractE20usersE20withoutE20merchantsE3fE2cE20andE20howE20canE20weE20attractE20merchantsE20withoutE20customersE3fE20WithoutE20aE20hugeE20investmentE20inE20marketingE20toE20buildE20consumerE20recognitionE2cE20startingE20aE20newE20mE2dcommE2eE2eE2eX qdcZidentifierQSxhttpE3aE2fE2fblogsE2eforumE2enokiaE2ecomE2fblogE2fpaulE2dcoultonsE2dforumE2dnokiaE2dblogE2f2006E2f06E2f25E2fE78mlE2denabledE2dpaymentE2dschemeE2dforE2dmobileX qdcZpublisherQUxhttpE3aE2fE2fswE2enokiaE2ecomE2fidE2fc764fd1cE2d8b06E2d499aE2d9a6aE2d17c3903d5a65E2fforumE5fnokiaE5fcrawlerE5fagentX qdcZtitleQSxPaulE20CoultonE27sE20ForumE20NokiaE20BlogE20E7cE20E58ME4cE20enabledE20paymentE20schemeE20forE20mobileX qdcZtypeQUqfnZE45E78cludedFromGeneralE4cistingsQ qdcZtypeQUqfntypeZBlogContentQ qdcZtypeQUqfntypeZBlogE45ntryQ qdcZtypeQUqfntypeZCommunityContentQ qdcZtypeQUqfntypeZE52esourceQ qdcZtypeQUqfntypeZWebpageQ qdcZtypeQUqmarsZManagedE52esourceQ qdcZtypeQUqwebZInformationE52esourceQ qdcZtypeQUqwebZPageQ qdcZtypeQUqwebZE52esourceQ qdcZtypeQUqrdfsZE52esourceQ qrssZdescriptionQSxMyE20principalE20interestE20inE20mobileE20applicationsE20isE20toE20pushE20theE20boundariesE20ofE20innovationE20toE20createE20uniE71uelyE20mobileE20eE78periencesE2eE20IE20hopeE20myE20blogsE20eE78citeE20andE20challengeE20developersE20toE20thinkE20E27outsideE20theE20boE78E27E2eE20coultonpE20E7cE2025E20JuneE2cE202006E2015E3a31E20MostE20newE20entrantsE20intoE20theE20mobileE20commerceE20marketplaceE20areE20facedE20withE20aE20paradoE78E3bE20howE20canE20weE20attractE20usersE20withoutE20merchantsE3fE2cE20andE20howE20canE20weE20attractE20merchantsE20withoutE20customersE3fE20WithoutE20aE20hugeE20investmentE20inE20marketingE20toE20buildE20consumerE20recognitionE2cE20startingE20aE20newE20mE2dcommE2eE2eE2eX qfnZdistributionQUxhttpE3aE2fE2fblogsE2eforumE2enokiaE2ecomE2fX qfnZtopicQUqfnTopicZbusinessE5fopportunitiesE5fservicesQRqdcZtypeQUqrdfsZE52esourceQRqmarsZrelevanceQNx100X qfnZtopicQUqfnTopicZbusinessE5ftechnicalE5fservicesQRqmarsZrelevanceQNx100X qfnZtopicQUqfnTopicZenterpriseQRqdcZtypeQUqrdfsZE52esourceQRqmarsZrelevanceQNx100X qfnZtopicQUqfnTopicZpythonQRqdcZtypeQUqrdfsZE52esourceQRqmarsZrelevanceQNx100X qfnZtypeQUqfntypeZBlogContentQ qfnZtypeQUqfntypeZBlogE45ntryQ qfnZtypeQUqfntypeZCommunityContentQ qfnZtypeQUqfntypeZE52esourceQ qfnZtypeQUqfntypeZWebpageQ qfnZupdatedQDx2006E2d06E2d25X qfnZuserE5ftagQSxbusinessE2dopportunitiesE2fservicesX qfnZuserE5ftagQSxbusinessE2ftechnicalE2dservicesX qfnZuserE5ftagQSxenterpriseX qfnZuserE5ftagQSxpythonX qmarsZdescriptionQSxMyE20principalE20interestE20inE20mobileE20applicationsE20isE20toE20pushE20theE20boundariesE20ofE20innovationE20toE20createE20uniE71uelyE20mobileE20eE78periencesE2eE20IE20hopeE20myE20blogsE20eE78citeE20andE20challengeE20developersE20toE20thinkE20E27outsideE20theE20boE78E27E2eE20coultonpE20E7cE2025E20JuneE2cE202006E2015E3a31E20MostE20newE20entrantsE20intoE20theE20mobileE20commerceE20marketplaceE20areE20facedE20withE20aE20paradoE78E3bE20howE20canE20weE20attractE20usersE20withoutE20merchantsE3fE2cE20andE20howE20canE20weE20attractE20merchantsE20withoutE20customersE3fE20WithoutE20aE20hugeE20investmentE20inE20marketingE20toE20buildE20consumerE20recognitionE2cE20startingE20aE20newE20mE2dcommE2eE2eE2eX qmarsZlanguageQUxhttpE3aE2fE2fswE2enokiaE2ecomE2flanguageE2d1E2fenX qrdfZtypeQUqfnZE45E78cludedFromGeneralE4cistingsQ qrdfZtypeQUqfntypeZBlogContentQ qrdfZtypeQUqfntypeZBlogE45ntryQ qrdfZtypeQUqfntypeZCommunityContentQ qrdfZtypeQUqfntypeZE52esourceQ qrdfZtypeQUqfntypeZWebpageQ qrdfZtypeQUqmarsZManagedE52esourceQ qrdfZtypeQUqwebZInformationE52esourceQ qrdfZtypeQUqwebZPageQ qrdfZtypeQUqwebZE52esourceQ qrdfZtypeQUqrdfsZE52esourceQ