News

Second anniversary of PayCircle: Success within the Java Community Process

Wednesday 21 January 2004 15:32 CET | News

Exactly two years after its foundation the PayCircle consortium reached further important milestones on the way to provide a mobile payment infrastructure based on mobile web service: The members of the worldwide consortium successfully have developed open application interfaces (APIs) that build the bridge between Independent Software Vendors (ISVs) producing ready-to-use payment-enabledapplications, and payment service providers (such as telecom operators) by allowing easy interoperability between their respective systems.Today PayCircle announces the harmonization of the co-branded PayCircle/Parlay specification with the JPay API. PayCircle additionally announces its partnership with the Liberty Alliance Project. The JPay API is the result of a corresponding Java Specification Request (JSR182) which PayCircle has filed in April 2002. JSR 182 defines an API to process payments between a Payment Service Provider (PSP) and a Merchant. JPay assumes that the PSP holds the identity of Consumer and Merchant, e.g. by having both subscribing to its service. JPay brings the PayCircle functionality into the Java Community Process (JCP). The Java Community Process (JCP) is an open process widely known among Java developers as the primary source for Java API specifications. The openness of the JCP fits Pay Circle’s approach to promote electronic payment by publishing open standards. As a result, PayCircle harmonized its APIs in both state of the art technologies for Mobile Web Services: Java and WSDL/XML (download at http://www.paycircle.org). The possible separation of the development of applications and payment systems is expected to accelerate the deployment of payment-enabled applications in the near future. This allows every player in the market to focus on his main business. Application developers for example do not have to worry about implementing payment systems and Mobile Network Operators are free to decide which applications and which payment systems they offer. Customers will have the freedom to decide individually each time "how to pay", if they use mobile services. A sample client developed at University of Augsburg (Germany) proves the practicality of the PayCircle-APIs. In addition to its ongoing theoretical research regarding mobile payment, the university is working on a second sample client which shows even better the advantages of the PayCircle specification. In order to accelerate standardization, PayCircle arranges liaisons with other consortia of the mobile market as well. The latest one is being signed with the Liberty Alliance Project. Liberty is working in the field of security and is representing some 160 companies. PayCircle supports very active the harmonization and de-fragmentation between different organizations. PayCircle and Parlay published in May 2003 a co-branded specification for mobile web services, embedding the payment APIs into the suite of more than dozen APIs, defined by Parlay.

Free Headlines in your E-mail

Every day we send out a free e-mail with the most important headlines of the last 24 hours.

Subscribe now

Keywords: ,
Categories: Payments & Commerce | Mobile Payments
Countries: World
This article is part of category

Payments & Commerce







Industry Events