MOBILE PAYMENT SERVICES

• US 20080275779A1
• Filed: 02/07/2008
• Published: 11/06/2008
• Est. Priority Date: 02/12/2007
• Status: Active Grant

• Current Assignee: Visa USA, Inc. (Visa, Inc.)
• Original Assignee: Visa USA, Inc. (Visa, Inc.)
• Inventors: Lakshminarayanan, Dhamodharan
• Granted Patent: US 8,793,184 B2
• Time in Patent Office: Days
• US Class Current: 705/14
• CPC Class Codes: G06Q 20/02 involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
• CPC Class Codes: G06Q 20/04 Payment circuits
• CPC Class Codes: G06Q 20/10 specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
• CPC Class Codes: G06Q 20/12 specially adapted for electronic shopping systems
• CPC Class Codes: G06Q 20/3223 Realising banking transactions through M-devices
• CPC Class Codes: G06Q 20/3227 using secure elements embedded in M-devices
• CPC Class Codes: G06Q 20/325 using wireless networks
• CPC Class Codes: G06Q 20/3267 In-app payments
• CPC Class Codes: G06Q 20/327 Short range or proximity payments by means of M-devices
• CPC Class Codes: G06Q 20/3823 combining multiple encryption tools for a transaction
• CPC Class Codes: G06Q 20/40 Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists

Abstract

A Java2 Enterprise Edition (J2EE) enabled server executing Java software provides a financial transaction Web service to a client each of which communicates wirelessly with the J2EE enabled server and executes Java software to conduct financial transactions between a merchant and a consumer upon an account issued by an issuer to the consumer. Each financial transaction is submitted by the merchant to an acquirer for processing by a transaction handler/payment processor, and is submitted by the transaction handler/payment processor to the issuer to obtain a payment amount for the financial transaction from the account, and wherein the issuer forwards the payment amount of the financial transaction to the transaction handler/payment processor who forwards the payment amount of the financial transaction to the acquirer to pay the merchant for the financial transaction.

Claims

1. A wireless financial transaction system comprising:

a Java 2 Enterprise Edition (J2EE) enabled server executing a Java software product to provide a financial transaction Web service;

and

a plurality of Web enabled clients each;

being served the financial transaction Web service in wireless communications with the J2EE enabled server;

and

executing a Java language software product to conduct a financial transaction between a merchant and a consumer upon an account issued by an issuer to the consumer in collaboration with the financial transaction Web service, wherein the financial transaction is conducted at least in part in a wireless communication with the client and the J2EE enabled server.

2. The wireless financial transaction system as defined in claim 1, wherein the J2EE enabled server serves each said client via a hot spot where the client can connect to the Internet using a wireless local area network.

3. The wireless financial transaction system as defined in claim 1, wherein each said financial transaction:

is submitted by the merchant to an acquirer for processing by a transaction handler/payment processor;

and

is submitted by the transaction handler/payment processor to the issuer to obtain a payment amount for the financial transaction from the account, and wherein the issuer forwards the payment amount of the financial transaction to the transaction handler/payment processor who forwards the payment amount of the financial transaction to the acquirer to pay the merchant for the financial transaction.

4. A wireless financial transaction system comprising:

a Java 2 Enterprise Edition (J2EE) enabled server executing a Java software product to provide a financial transaction Web service;

and

a Web and Java 2 Standard Edition (J2SE) enabled thick client selected from the group consisting of a workstation, a personal computer, and a laptop computer, the thick client being operated by a merchant and;

being served the financial transaction Web service in wireless communications with the J2EE enabled server;

and

executing a Java language software product to conduct a financial transaction in collaboration with the financial transaction Web service, wherein each said financial transaction;

is conducted by a consumer with a merchant upon an account issued by an issuer to a consumer; and

is conducted at least in part wireless communication with the Web and J2SE enabled thick client.

5. The wireless financial transaction system as defined in claim 4, wherein the J2EE enabled server serves each said thick client via a hot spot where the client can connect to the Internet using a wireless local area network.

6. The wireless financial transaction system as defined in claim 4, wherein:

the thick client executes an operating system (OS) to perform OS specific commands; and

the Java software product to conduct the financial transaction is byte code converted by a Java Virtual Machine (JVM) into the OS specific commands performed by the OS.

7. The wireless financial transaction system as defined in claim 4, wherein each said financial transaction:

is submitted by the merchant to an acquirer for processing by a transaction handler/payment processor;

and

is submitted by the transaction handler/payment processor to the issuer to obtain a payment amount for the financial transaction from the account, and wherein the issuer forwards the payment amount of the financial transaction to the transaction handler/payment processor who forwards the payment amount of the financial transaction to the acquirer to pay the merchant for the financial transaction.

8. A wireless financial transaction system comprising:

a Java 2 Enterprise Edition (J2EE) enabled server and executing a plurality of Java software products to serve a financial transaction Web service;

and

a Web and Java 2 Micro Edition (J2ME) enabled thin client;

being served the financial transaction Web service in wireless communications with the J2EE enabled server;

and

executing a Java language software product to conduct a financial transaction in collaboration with the financial transaction Web service, wherein each said financial transaction;

is conducted at least in part wireless communication with the Web and J2ME enabled thin client;

is conducted with the merchant upon an account issued by an issuer to a consumer.

9. The wireless financial transaction system as defined in claim 8, wherein the thin client has a Connective Device Configuration (CDC) with a J2ME configuration.

10. The wireless financial transaction system as defined in claim 9, wherein:

the thin client executes an operating system (OS) to perform OS specific commands;

the Java software product to conduct the financial transaction is byte code converted by a Java Virtual Machine (JVM) into the OS specific commands performed by the OS.

11. The wireless financial transaction system as defined in claim 9, wherein the thin client is selected from the group consisting of a palm top computer, a Personal Digital Assist (PDA), a network card, a cable or satellite set-top box, and an audio visual telephonic screen phone.

12. The wireless financial transaction system as defined in claim 8, wherein the thin client has a Connected Limited Device Configuration (CDLC) with a J2ME configuration.

13. The wireless financial transaction system as defined in claim 12, wherein:

the thin client executes an operating system (OS) to perform OS specific commands;

the Java software product to conduct the financial transaction is byte code converted by a compact Java Virtual Machine (KVM) into the OS specific commands performed by the OS.

14. The wireless financial transaction system as defined in claim 13, wherein the Java language software product to conduct a financial transaction is an application written in the Mobile Information Device Profile (MIDP) specification for a J2ME profile and corresponds to a top layer of a J2ME device stack for the thin client, wherein the J2ME device stack has a Digital Signal Processor (DSP) as the bottom layer of the J2ME device stack, the KVM is the layer upon the bottom layer and has thereon a J2ME core application program interface (API) layer, and the API layer has thereon an MIDP over which is the top layer of the J2ME device stack.

15. The wireless financial transaction system as defined in claim 14, wherein the application written in the MIDP specification for the J2ME profile is selected from the group consisting of thin client is selected from the group consisting of a payment application to pay a merchant, an application providing an identification function for a consumer, an application for awarding loyalty of a consumer having a credit, debit, or pre-paid card for use of the card in a plurality of said financial transactions, an application permitting a consumer access to a transit facility.

16. The wireless financial transaction system as defined in claim 13, wherein the thin client is selected from the group consisting of a Point Of Sale terminal (POS) operated by the merchant, a pager, and a smart cellular telephones.

17. The wireless financial transaction system as defined in claim 13, wherein the Web and J2ME enabled thin client is served the financial transaction Web service in a blue tooth wireless communications with the J2EE enabled server.

18. The wireless financial transaction system as defined in claim 8, wherein each said financial transaction:

is submitted by the merchant to an acquirer for processing by a transaction handler/payment processor;

and

is submitted by the transaction handler/payment processor to the issuer to obtain a payment amount for the financial transaction from the account, and wherein the issuer forwards the payment amount of the financial transaction to the transaction handler/payment processor who forwards the payment amount of the financial transaction to the acquirer to pay the merchant for the financial transaction.

19. A wireless financial transaction system comprising:

a Java 2 Enterprise Edition (J2EE) enabled server executing a Java software product to provide a financial transaction Web service;

and

a smart card having a digital signal processor executing an operating system (OS) to perform OS specific commands and executing a Java software product to conduct a financial transaction in byte code converted by a Card Virtual Machine (KVM) into the OS specific commands performed by the OS, the smart card;

being served the financial transaction Web service in wireless communications with the J2EE enabled server;

and

executing a Java language software product to conduct a financial transaction in collaboration with the financial transaction Web service, wherein each said financial transaction;

is conducted at least in part wireless communication with the smart card; and

is conducted with a merchant upon an account issued by an issuer to a consumer.

20. The wireless financial transaction system as defined in claim 19, wherein each said financial transaction:

is submitted by the merchant to an acquirer for processing by a transaction handler/payment processor;

and

is submitted by the transaction handler/payment processor to the issuer to obtain a payment amount for the financial transaction from the account, and wherein the issuer forwards the payment amount of the financial transaction to the transaction handler/payment processor who forwards the payment amount of the financial transaction to the acquirer to pay the merchant for the financial transaction.