METHOD AND SYSTEM FOR MOBILE BANKING USING A MOBILE APPLICATION

• US 20130013498A1
• Filed: 09/14/2012
• Published: 01/10/2013
• Est. Priority Date: 11/14/2007
• Status: Active Grant

• Current Assignee: Blaze Mobile, Inc. (iWin, Inc.)
• Original Assignee: Blaze Mobile, Inc. (iWin, Inc.)
• Inventors: Fisher, Michelle, Guha, Rathin
• Granted Patent: US 9,020,836 B2
• Time in Patent Office: Days
• US Class Current: 705/40
• CPC Class Codes: G06Q 20/04 Payment circuits
• CPC Class Codes: G06Q 20/102 Bill distribution or payments
• CPC Class Codes: G06Q 20/108 Remote banking, e.g. home banking
• CPC Class Codes: G06Q 20/3223 Realising banking transactions through M-devices
• CPC Class Codes: G06Q 20/3226 Use of secure elements separate from M-devices
• CPC Class Codes: G06Q 20/3227 using secure elements embedded in M-devices
• CPC Class Codes: G06Q 20/3229 Use of the SIM of a M-device as secure element
• CPC Class Codes: G06Q 20/3278 RFID or NFC payments by means of M-devices
• CPC Class Codes: G06Q 20/3552 Downloading or loading of personalisation data
• CPC Class Codes: G06Q 20/367 involving electronic purses or money safes
• CPC Class Codes: G06Q 20/382 insuring higher security of transaction
• CPC Class Codes: G06Q 20/3821 Electronic credentials
• CPC Class Codes: G06Q 20/401 Transaction verification
• CPC Class Codes: G06Q 30/0238 at point-of-sale [POS]
• CPC Class Codes: H04B 5/72 for local intradevice communication
• CPC Class Codes: H04L 2209/56 Financial cryptography, e.g. electronic payment or e-cash
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04W 12/062 Pre-authentication
• CPC Class Codes: H04W 12/068 using credential vaults, e.g. password manager applications or one time password [OTP] applications
• CPC Class Codes: H04W 12/082 using revocation of authorisation
• CPC Class Codes: H04W 4/80 : Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
• CPC Class Codes: H04W 88/06 : adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals

Abstract

A method for transmitting data between a mobile communication device and a server. The method includes running a mobile application on the mobile communication device. The mobile application is hosted on the mobile communication device through the server as a Software as a Service (SaaS). The method further includes transmitting data associated with the mobile application between the mobile communication device and the server, in which transmission of the data between the mobile communication device and the server is monitored through the server.

Claims

1. A method for conducting a mobile banking transaction using a handheld mobile device, the method comprising:

maintaining a mobile banking application in a handheld mobile device memory, wherein the mobile banking application is preinstalled or downloaded and installed by a user on the mobile communications device;

exchanging data associated with the mobile banking application with a remote server by using a handheld mobile device transceiver, wherein the remote server authenticates a user of the handheld mobile device to conduct a mobile banking transaction;

executing the mobile banking application on a handheld mobile device processor, wherein executing the mobile banking application comprises displaying an account balance associated with the user and displaying a transaction history associated with the user.

2. The method of claim 1, wherein the handheld mobile device comprises a secure element, the secure element including a secure element processor, a secure element memory, and a secure element transceiver configured to support a near field communication (NFC) protocol.

3. The method of claim 2, wherein the secure element is embedded in the handheld mobile device.

4. The method of claim 2, wherein the secure element is removably affixed to the handheld mobile device.

5. The method of claim 2, wherein the handheld mobile device transceiver is configured to support a mobile wireless communication protocol.

6. The method of claim 1, wherein exchanging data includes using a session key that is valid only for a given communication session between the handheld mobile device and the remote server.

7. The method of claim 1, wherein executing the mobile banking application further comprises scheduling a bill payment.

8. The method of claim 1, wherein executing the mobile banking application further comprises scheduling a funds transfer.

9. The method of claim 1, wherein executing the mobile banking application further comprises scheduling a loading funds.

10. The method of claim 1, wherein executing the mobile banking application further comprises specifying a default payment method.

11. The method of claim 1, wherein executing the mobile banking application further comprises establishing a payment account.

12. The method of claim 1, wherein exchanging data includes using a session key that is valid only for a given communication session between the handheld mobile device and the remote server.

13. The method of claim 12, wherein the mobile banking application is disabled after the session key is invalidated.

14. The method of claim 12, wherein the session key expires after a predetermined period of time.

15. A handheld mobile device for conducting a mobile banking transaction using comprising:

a handheld mobile device memory configured to maintain a mobile banking application, wherein the mobile banking application is preinstalled or downloaded and installed by a user on the handheld mobile device;

a handheld mobile device transceiver configured to exchange data associated with the mobile banking application with a remote server, wherein the remote server authenticates a user of the handheld mobile device to conduct a mobile banking transaction;

a handheld mobile device processor configured to execute the mobile banking application, wherein executing the mobile banking application comprises displaying an account balance associated with the user and displaying a transaction history associated with the user.

16. The method of claim 15, wherein the handheld mobile device comprises a secure element, the secure element including a secure element processor, a secure element memory, and a secure element transceiver configured to support a near field communication (NFC) protocol.

17. The method of claim 16, wherein the secure element is embedded in the handheld mobile device.

18. The method of claim 16, wherein the secure element is removably affixed to the handheld mobile device.

19. The method of claim 16, wherein the handheld mobile device transceiver is configured to support a mobile wireless communication protocol.

20. The method of claim 15, wherein exchanging data includes using a session key that is valid only for a given communication session between the handheld mobile device and the remote server.