Mobile Client Application for Mobile Payments

• US 20070244811A1
• Filed: 03/30/2007
• Published: 10/18/2007
• Est. Priority Date: 03/30/2006
• Status: Abandoned Application

• Current Assignee: Obopay Mobile Technology India Pvt Limited (OBP Investments, Inc.)
• Original Assignee: Obopay Incorporated (OBP Investments, Inc.)
• Inventors: Tumminaro, John
• Application Number:
  US11/694,895
• Publication Number:
  US 20070244811A1
• Time in Patent Office: Days
• US Class Current: 705/39
• 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/223 based on the use of peer-to-peer networks
• CPC Class Codes: G06Q 20/322 Aspects of commerce using mobile devices [M-devices]
• CPC Class Codes: G06Q 20/3223 Realising banking transactions through M-devices
• CPC Class Codes: G06Q 20/325 using wireless networks
• CPC Class Codes: G06Q 20/3255 using mobile network messaging services for payment, e.g. SMS
• CPC Class Codes: G06Q 20/3274 using a pictured code, e.g. barcode or QR-code, being displayed on the M-device
• CPC Class Codes: G06Q 20/3276 using a pictured code, e.g. barcode or QR-code, being read by the M-device
• CPC Class Codes: G06Q 20/386 using messaging services or messaging apps using mobile network messaging services for payment, e.g. SMS G06Q20/3255
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: H04M 3/16 with lock-out or secrecy provision in party-line systems
• CPC Class Codes: H04W 12/068 using credential vaults, e.g. password manager applications or one time password [OTP] applications
• CPC Class Codes: H04W 4/02 Services making use of location information

Abstract

A mobile client application executes on a mobile phone and interfaces with a mobile payment platform. A mobile payment platform and service provides a fast, easy way to make payments by users of mobile devices. The platform also interfaces with nonmobile channels and devices such as e-mail, instant messenger, and Web. In an implementation, funds are accessed from an account holder'"'"'s mobile device such as a mobile phone or a personal digital assistant to make or receive payments. Financial transactions may be conducted on a person-to-person (P2P) or person-to-merchant (P2M) basis where each party is identified by a unique indicator such as a telephone number or bar code. Transactions may be requested through any number of means including SMS messaging, Web, e-mail, instant messenger, a mobile client application, an instant messaging plug-in application or “widget.” The mobile client application, resident on the mobile device, simplifies access and performing financial transactions in a fast, secure manner.

Claims

1. A method comprising:

displaying a first screen on a display of a mobile phone to show a plurality of options comprising a first option to pay money to another and a second option to request balance information;

upon a user selecting the first option, displaying a second screen where the user enters a target phone number to which to send payment;

after the user enters the target phone number, displaying a third screen where the user enters a transaction amount;

after the user enters the phone number, displaying a fourth screen where the user enters a PIN code; and

after the user enters the PIN code, wirelessly sending transaction information comprising the target phone number, transaction amount, and PIN code to a server for processing.

3. The method of claim 1 comprising:

upon the user selecting the second option, wirelessly sending a request for balance information to the server;

receiving balance information from the server; and

displaying the balance information in a fifth screen.

4. The method of claim 1 where the first screen further provides a third option to request payment from another.

5. The method of claim 1 where the second screen has a third option which upon selection by the user provides the user access to an address book from which the user may select an entry to use as the target phone number.

6. The method of claim 1 wherein the transaction information comprises a sequence number generated by the mobile phone.

7. The method of claim 1 wherein funds are maintained at the server and not on the mobile phone.

8. The method of claim 1 further comprising:

upon receiving a request pay request at the mobile phone, displaying fifth screen where the user may enter a tip amount.

2. The method comprising:

after the user enters the target phone number, displaying a fifth screen where the user enters an optional message.