Offline mobile banking system

• US 9,384,478 B2
• Filed: 07/19/2013
• Issued: 07/05/2016
• Est. Priority Date: 07/19/2013
• Status: Active Grant

• Current Assignee: Bank of America Corp.
• Original Assignee: Bank of America Corp.
• Inventors: Calman, Matthew A., Jain, Dipika, Kelley, William, Purvis, Chris, Toth, Michael E.
• Primary Examiner(s): Patel, Jagdish
• Application Number:
  US13/946,519
• Publication Number:
  US 20150026055A1
• Time in Patent Office: 1,082 Days
• Field of Search: 705/39, 705/26.3, 705/26.8, 705/41, 705/42
• US Class Current: 1/1
• CPC Class Codes: G06Q 20/3223 Realising banking transactions through M-devices
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03

Abstract

Embodiments of the invention are directed to systems, methods and computer program products for providing an offline mobile banking system. An exemplary apparatus is configured to: provide, at a mobile device, a transaction request, determine a connection is not established between the mobile device and a device associated with the financial institution, store the transaction request in response to determining a connection has not been established, establish a connection between the mobile device and a server associated with the financial institution, and communicate the stored transaction request from the mobile device to a device associated with the financial institution.

Claims

1. An apparatus for providing offline mobile banking, the apparatus comprising:

a memory;

at least one processor; and

a module stored in the memory, executable by the processor, and configured to cause the at least one processor to;

provide access, at a mobile device, to a mobile banking application, wherein the mobile banking application is configured to be automatically operable in an online mode when a network connection is established between the mobile device and a device associated with the financial institution, and wherein the mobile banking application is configured to be automatically operable in an offline mode when a network connection is not established between the mobile device and the device associated with the financial institution, wherein the mobile device is associated with a user, and wherein the user has an account maintained by the financial institution;

authenticate the identity of the user based at least partially on one or more authentication credentials electronically received from the user at the mobile device via the mobile banking application;

in response to authenticating the identity of the user, electronically receive, at the mobile device via the mobile banking application, a transaction request from the user, wherein electronically receiving the transaction request comprises a user inputting information related to the transaction request into the mobile banking application;

electronically receive one or more user preferences associated with the transaction request from the user, the one or more user preferences comprising a network security status and a network type for a network connection to be established between the mobile device of the user and the device associated with the financial institution;

electronically receive, at the mobile device via the mobile banking application, a request from the user to submit the transaction request for processing by the financial institution;

in response to receiving the request to submit the transaction request for processing by the financial institution from the user, determine whether or not a network connection is established between the mobile device and the device associated with the financial institution, wherein the module is further configured to;

in response to determining that a network connection is established between the mobile device and the device associated with the financial institution;

determining whether a network security status and a network type associated with the established network connection matches the network security status and the network type associated with the one or more user preferences;

immediately electronically communicate the transaction request from the mobile device to a device associated with the financial institution based at least in part on the mobile banking application being in an online mode and determining that the network security status and the network type associated with the established network connection matches the network security status and the network type associated with the one or more user preferences; and

in response to determining that a network connection is not established between the mobile device and the device associated with the financial institution;

store the transaction request, locally on the mobile device, based at least in part on the mobile banking application being in an offline mode;

store the one or more authentication credentials received from the user locally on the mobile device;

repeatedly, over time, attempt to detect whether or not the network connection is available;

in response to detecting that the network connection is available, establish the network connection between the mobile device and a server associated with the financial institution;

electronically authenticate the mobile device prior to communicating the stored transaction request, wherein the mobile device is electronically authenticated based on device information automatically retrieved from the mobile device, and wherein the device information does not include external data stored locally on the mobile device;

electronically re-authenticate the identity of the user prior to communicating the stored transaction request, wherein the identity of the user is electronically re-authenticated based on the one or more stored authentication credentials such that user input is not required at the time of re-authentication; and

in response to authenticating the mobile device and re-authenticating the identity of the user, electronically communicate the stored transaction request from the mobile device to a device associated with the financial institution.

2. The apparatus of claim 1, wherein communicating the stored transaction request further comprises the module being configured to verify the mobile device is an authenticated device, and wherein verifying the mobile device is an authenticated device does not require user input.

3. The apparatus of claim 1, wherein the transaction request is stored locally on the mobile device.

4. The apparatus of claim 1, wherein the transaction request is store remotely in cloud storage.

5. The apparatus of claim 1, wherein the module is further configured to notify the user that the transaction request cannot be processed in response to response to determining a connection has not been established.

6. The apparatus of claim 1, wherein the module is further configured to temporarily update an account history displayed on the mobile device based at least partially on the stored transaction request.

7. The apparatus of claim 1, wherein storing the transaction request further comprises the module being configured to queue a transaction request based on the order in which it was received.

8. The apparatus of claim 1, wherein storing the transaction request further comprises the module being configured to queue a transaction request based on a priority for the transaction request specified by one or more user preferences.

9. The apparatus of claim 1, wherein storing the transaction request further comprises the module being configured to queue a transaction request based on a priority for the transaction request specified by one or more user preferences.

10. The apparatus of claim 1, wherein the module is further configured to notify the user that the stored transaction request has been successfully processed by the financial institution.

11. The apparatus of claim 1, wherein the module is further configured to notify the user that the stored transaction request has been unsuccessfully processed by the financial institution.

12. A computer-implemented method for providing offline mobile banking, the method comprising:

providing access, at a mobile device, to a mobile banking application, wherein the mobile banking application is configured to be automatically operable in an online mode when a network connection is established between the mobile device and a device associated with the financial institution, and wherein the mobile banking application is configured to be automatically operable in an offline mode when a network connection is not established between the mobile device and the device associated with the financial institution, wherein the mobile device is associated with a user, and wherein the user has an account maintained by the financial institution;

authenticating the identity of the user based at least partially on one or more authentication credentials electronically received from the user at the mobile device via the mobile banking application;

in response to authenticating the identity of the user electronically receiving, at the mobile device via the mobile banking application, a transaction request from the user, wherein electronically receiving the transaction request comprises a user inputting information related to the transaction request into the mobile banking application;

electronically receiving one or more user preferences associated with the transaction request from the user, the one or more user preferences comprising a network security status and a network type for a network connection to be established between the mobile device of the user and the device associated with the financial institution;

electronically receiving, at the mobile device via the mobile banking application, a request from the user to submit the transaction request for processing by the financial institution;

in response to receiving the request to submit the transaction request for processing by the financial institution from the user, determining whether or not a network connection is established between the mobile device and the device associated with the financial institution,

wherein determining whether or not a network connection is established between the mobile device and the device associated with the financial institution further comprises;

in response to determining that a network connection is established between the mobile device and the device associated with the financial institution;

determining whether a network security status and a network type associated with the established network connection matches the network security status and the network type associated with the one or more user preferences;

immediately electronically communicating the transaction request from the mobile device to a device associated with the financial institution based at least in part on the mobile banking application being in an online mode and determining that the network security status and the network type associated with the established network connection matches the network security status and the network type associated with the one or more user preferences; and

in response to determining that a network connection is not established between the mobile device and the device associated with the financial institution;

storing the transaction request, locally on the mobile device, based at least in part on the mobile banking application being in an offline mode;

storing the one or more authentication credentials received from the user locally on the mobile device;

repeatedly, over time, attempting to detect whether or not the network connection is available;

in response to detecting that the network connection is available, establishing the network connection between the mobile device and a server associated with the financial institution;

electronically authenticating the mobile device prior to communicating the stored transaction request, wherein the mobile device is electronically authenticated based on device information automatically retrieved from the mobile device, and wherein the device information does not include external data stored locally on the mobile device;

electronically re-authenticating the identity of the user prior to communicating the stored transaction request, wherein the identity of the user is electronically re-authenticated based on the one or more stored authentication credentials such that user input is not required at the time of re-authentication; and

in response to authenticating the mobile device and re-authenticating the identity of the user, electronically communicate the stored transaction request from the mobile device to a device associated with the financial institution.

13. The method of claim 12, wherein communicating the stored transaction request further comprises verifying the mobile device is an authenticated device, and wherein verifying the mobile device is an authenticated device does not require user input.

14. The method of claim 12, wherein the transaction request is stored locally on the mobile device.

15. The method of claim 12, wherein the transaction request is store remotely in cloud storage.

16. The method of claim 12, the method further comprising notifying the user that the transaction request cannot be processed in response to response to determining a connection has not been established.

17. The method of claim 12, the method further comprising temporarily updating an account history displayed on the mobile device based at least partially on the stored transaction request.

18. The method of claim 12, the method further comprising queuing a transaction request based on the order in which it was received.

19. The method of claim 12, the method further comprising queuing a transaction request based on a priority for the transaction request specified by one or more user preferences.

20. The method of claim 12, wherein communicating the transaction request further comprises communicating a transaction request based on the order in which it was received.

21. The method of claim 12, wherein communicating the transaction request further comprises communicating a transaction request based on a priority for the transaction request specified by one or more user preferences.

22. The method of claim 12, wherein the module is further configured to notify the user that the stored transaction request has been successfully processed by the financial institution.

23. The method of claim 12, wherein the module is further configured to notify the user that the stored transaction request has been unsuccessfully processed by the financial institution.

25. The computer program product of claim 17, the set of codes for causing a computer to communicate the stored transaction request from the mobile device to a device associated with the financial institution further comprises a set of codes for causing a computer to verify the mobile device is an authenticated device, and wherein verifying the mobile device is an authenticated device does not require user input.

26. The computer program product of claim 17, the computer program product further comprising a set of codes for causing a computer to temporarily update an account history displayed on the mobile device based at least partially on the stored transaction request.

24. A computer program product for providing offline mobile banking, the computer program product comprising:

a non-transitory computer-readable medium comprising a set of codes for causing a computer to;

provide access, at a mobile device, to a mobile banking application, wherein the mobile banking application is configured to be automatically operable in an online mode when a network connection is established between the mobile device and a device associated with the financial institution, and wherein the mobile banking application is configured to be automatically operable in an offline mode when a network connection is not established between the mobile device and the device associated with the financial institution, wherein the mobile device is associated with a user, and wherein the user has an account maintained by the financial institution;

authenticate the identity of the user based at least partially on one or more authentication credentials electronically received from the user at the mobile device via the mobile banking application;

in response to authenticating the identity of the user, electronically receive, at the mobile device via the mobile banking application, a transaction request from the user, wherein electronically receiving the transaction request comprises a user inputting information related to the transaction request into the mobile banking application;

electronically receive one or more user preferences associated with the transaction request from the user, the one or more user preferences comprising a network security status and a network type for a network connection to be established between the mobile device of the user and the device associated with the financial institution;

electronically receive, at the mobile device via the mobile banking application, a request from the user to submit the transaction request for processing by the financial institution;

in response to receiving the request to submit the transaction request for processing by the financial institution from the user, determine whether or not a network connection is established between the mobile device and the device associated with the financial institution,

in response to determining that a network connection is established between the mobile device and the device associated with the financial institution;

determining whether a network security status and a network type associated with the established network connection matches the network security status and the network type associated with the one or more user preferences;

immediately electronically communicate the transaction request from the mobile device to a device associated with the financial institution based at least in part on the mobile banking application being in an online mode and determining that the network security status and the network type associated with the established network connection matches the network security status and the network type associated with the one or more user preferences; and

in response to determining that a network connection is not established between the mobile device and the device associated with the financial institution;

store the transaction request, locally on the mobile device, based at least in part on the mobile banking application being in an offline mode;

store the one or more authentication credentials received from the user locally on the mobile device;

repeatedly, over time, attempt to detect whether or not the network connection is available;

in response to detecting that the network connection is available, establish the network connection between the mobile device and a server associated with the financial institution;

electronically authenticate the mobile device prior to communicating the stored transaction request, wherein the mobile device is electronically authenticated based on device information automatically retrieved from the mobile device, and wherein the device information does not include external data stored locally on the mobile device;

electronically re-authenticate the identity of the user prior to communicating the stored transaction request, wherein the identity of the user is electronically re-authenticated based on the one or more stored authentication credentials such that user input is not required at the time of re-authentication; and

in response to authenticating the mobile device and re-authenticating the identity of the user, electronically communicate the stored transaction request from the mobile device to a device associated with the financial institution.