U.S. patent application number 13/941492 was filed with the patent office on 2014-01-16 for mobile banking systems and related methods.
The applicant listed for this patent is Green Dot Corporation. Invention is credited to Samuel Harris Altman, Alok Deshpande, David Kenneth Schreiber, Steven William Streit.
Application Number | 20140019322 13/941492 |
Document ID | / |
Family ID | 49914824 |
Filed Date | 2014-01-16 |
United States Patent
Application |
20140019322 |
Kind Code |
A1 |
Streit; Steven William ; et
al. |
January 16, 2014 |
MOBILE BANKING SYSTEMS AND RELATED METHODS
Abstract
Embodiments of mobile banking systems are described herein.
Other examples and related methods are also disclosed herein.
Inventors: |
Streit; Steven William;
(Pasadena, CA) ; Altman; Samuel Harris; (San
Francisco, CA) ; Deshpande; Alok; (Mountain View,
CA) ; Schreiber; David Kenneth; (Mountain View,
CA) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
Green Dot Corporation |
Pasadena |
CA |
US |
|
|
Family ID: |
49914824 |
Appl. No.: |
13/941492 |
Filed: |
July 13, 2013 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
61671478 |
Jul 13, 2012 |
|
|
|
Current U.S.
Class: |
705/35 |
Current CPC
Class: |
G06Q 40/02 20130101 |
Class at
Publication: |
705/35 |
International
Class: |
G06Q 40/02 20060101
G06Q040/02 |
Claims
1. A system for mobile banking, the system comprising: a mobile
module for providing access to a first bank account of a user;
wherein: the mobile module comprises: a login module; a main
account module accessible via the login module and configured to at
least one of: receive a first account balance of the first bank
account and further account information about the first bank
account; or request one or more transactions for the first bank
account; a quick-balance module accessible separate from the main
account module and configured to: receive the first account balance
of the first bank account; and provide a first quick-balance report
of the first account balance; a front display actuated upon
activation of the mobile module; and a main display for transacting
with the first bank account; the login module is configured to:
receive initial authentication of the user to enable initial access
to the main account module and to the quick balance module for the
first bank account; and receive subsequent authentication of the
user for subsequent access to the main account module; the mobile
module impedes the subsequent access to the main account module
until receipt of the subsequent authentication of the user via the
login module; and the mobile module permits access to the
quick-balance report of the quick-balance module without requiring
the subsequent authentication of the user; the front display
comprises a first quick-balance interface configured to present the
first quick-balance report of the quick-balance module; the first
quick-balance interface comprises a first actuator and is
configured to: conceal the first quick-balance report when the
first actuator is not actuated; and reveal the first quick-balance
report, if the quick-balance module is enabled and without
requiring the subsequent authentication, when the first actuator is
actuated; the first actuator comprises a first slideblock
configured to reveal the first quick-balance report when actuated
by sliding; the main display is actuafted upon the subsequent
authentication of the user via the login module and is configured
to present a main interface for the main account module; the main
display is devoid of the first quick-balance interface but
comprises a main-balance report at the main interface; the main
balance report comprises at least the first account balance for the
first bank account; and the first quick-balance report at the
quick-balance interface of the front display consists of the first
account balance for the first bank account.
2. A system for mobile banking, the system comprising: a mobile
module for providing access to a first bank account of a user;
wherein: the mobile module comprises: a login module; a main
account module accessible via the login module and configured to at
least one of: receive a first account balance of the first bank
account and further account information about the first bank
account; or request one or more transactions for the first bank
account; and a quick-balance module accessible separate from the
main account module and configured to: receive a first account
balance of the first bank account; and provide a first
quick-balance report of the first account balance; the login module
is configured to: receive initial authentication of the user to
enable initial access to the main account module and to the quick
balance module for the first bank account; and receive subsequent
authentication of the user for subsequent access to the main
account module; the mobile module impedes the subsequent access to
the main account module until receipt of the subsequent
authentication of the user via the login module; and the mobile
module permits access to the quick-balance report of the
quick-balance module without requiring the subsequent
authentication of the user.
3. The system of claim 2, wherein: the mobile module comprises a
front display actuated upon activation of the mobile module; and
the front display comprises a first quick-balance interface
configured to present the first quick-balance report of the
quick-balance module.
4. The system of claim 3, wherein: the first quick-balance
interface comprises a first actuator and is configured to: conceal
the first quick-balance report when the first actuator is not
actuated; and reveal the first quick-balance report, if the
quick-balance module is enabled and without requiring the
subsequent authentication, when the first actuator is actuated.
5. The system of claim 4, wherein: the first actuator is configured
to reveal the first quick-balance report when actuated via at least
one of: a pressing gesture upon the actuator; a sliding gesture
upon the actuator; or a screen-pull gesture upon the actuator;
6. The system of claim 4, wherein: the first actuator is actuatable
to reveal the first quick-balance report via a sliding gesture; the
first quick-balance interface comprises: a bottom interface layer
comprising the first quick-balance report; and a top interface
layer configured to cover the first quick-balance report and the
bottom interface layer; and the first actuator is configured to
remove the top interface layer, as the first actuator is slid, to
reveal the first quick-balance report at the bottom interface
layer.
7. The system of claim 3, wherein: the front display comprises a
login interface configured to receive the subsequent authentication
for the login module; and the login interface is presented along
with the first quick-balance interface at the front display.
8. The system of claim 3, wherein: the mobile module comprises a
main display actuated upon the subsequent authentication of the
user via the login module and configured to present a main
interface for the main account module; and the main display is
devoid of the first quick-balance interface.
9. The system of claim 8, wherein: the main display comprises at
least one of: a main balance interface configured to present a
main-balance report having the first account balance for the first
bank account; or a transactions interface configured to present
transaction details of the first bank account with respect to a
time period and based on the further account information.
10. The system of claim 8, wherein: the main display comprises a
main-balance report; the main balance report comprises at least the
first account balance for the first bank account; and the first
quick-balance report consists of the first account balance for the
first bank account.
11. The system of claim 3, wherein: the mobile module is configured
to provide access to a second bank account of the user; the
quick-balance module is configured to receive a second
quick-balance report for a second account balance of the second
bank account; and the front display comprises: a second
quick-balance interface configured to present the second
quick-balance report of the quick-balance module; a first
identifier of the first quick-balance interface for the first bank
account; and a second identifier of the second quick-balance
interface for the second bank account.
12. The system of claim 3, wherein: the mobile module is configured
to provide access to a second bank account of the user; the
quick-balance module is configured to receive a second account
balance of the second bank account; and the first quick-balance
report comprises a combined balance of the first and second account
balances.
13. The system of claim 2, wherein: the mobile module is configured
to: receive user input regarding whether to permit the
quick-balance module to provide the first quick-balance report
without requiring the subsequent authentication; enable an
authentication token for permitting the quick-balance module to
provide the first quick-balance report based on the user input; and
provide the first quick-balance report via the quick-balance module
only if the authentication token is enabled.
14. The system of claim 13, wherein: the mobile module is
implementable via a mobile device and configured to wirelessly
receive bank account information about the first bank account from
a bank server of a bank; and the authentication token is storable
in the mobile device.
15. A method for facilitating mobile banking, the method
comprising: providing a mobile module for mobilely interfacing with
a first bank account; wherein: providing the mobile module
comprises: providing a login module; providing a main account
module accessible via the login module; and providing a
quick-balance module accessible separate from the main account
module; the login module is configured to: receive user initial
authentication for initial access to the main account module and to
the quick balance module for the first bank account; and receive
user subsequent authentication for subsequent access to the main
account module; the main account module is configured to at least
one of: receive a first account balance of the first bank account
and further account information about the first bank account; or
request one or more transactions for the first bank account; the
quick-balance module is configured to: receive the first account
balance for the first bank account; and provide a first
quick-balance report of the first account balance; the mobile
module is configured to impede the subsequent access to the main
account module until receipt of the user subsequent authentication
via the login module; and the mobile module is configured to permit
access to the quick-balance report of the quick-balance module
without requiring the user subsequent authentication.
16. The method of claim 15, wherein: the mobile module is
configured to generate a front display upon activation of the
mobile module; and the front display comprises a first
quick-balance interface configured to present the first
quick-balance report of the quick-balance module.
17. The method of claim 16, wherein: the first quick-balance
interface comprises a first actuator and is configured to: conceal
the first quick-balance report when the first actuator is not
actuated; and reveal the first quick-balance report, if the
quick-balance module is enabled and without requiring the
subsequent authentication, when the first actuator is actuated.
18. The method of claim 17, wherein: the first actuator is
actuatable to reveal the first quick-balance report via at least
one of: a pressing gesture upon the actuator; a sliding gesture
upon the actuator; or a screen-pull gesture upon the actuator;
19. The method of claim 17, wherein: the first actuator is
actuatable to reveal the first quick-balance report via a sliding
gesture; the first quick-balance interface comprises: a bottom
interface layer comprising the first quick-balance report; and a
top interface layer configured to cover the first quick-balance
report and the bottom interface layer; and the first actuator is
configured to remove the top interface layer, as the first actuator
is slid, to reveal the first quick-balance report at the bottom
interface layer.
20. The method of claim 16, wherein: the front display comprises a
login interface configured to receive the subsequent authentication
for the login module; and the login interface is presented along
with the first quick-balance interface at the front display.
21. The method of claim 16, wherein: the mobile module comprises a
main display actuated upon the user subsequent authentication via
the login module and configured to present a main interface
comprising at least one of: a main balance interface configured to
present a main-balance report having at least the first account
balance for the first bank account; or a transactions interface
configured to present transaction details of the first bank account
with respect to a time period and based on the further account
information. and the main display is devoid of the first
quick-balance interface.
22. The method of claim 15, wherein: the first quick-balance report
consists of the first account balance for the first bank
account.
23. The method of claim 15, wherein: the mobile module is further
configured to provide access to a second bank account; the
quick-balance module is further configured to receive a second
quick-balance report for a second account balance of the second
bank account; and the front display comprises at least one of: a
second quick-balance interface configured to present the second
quick-balance report of the quick-balance module; or a combined
quick-balance interface configured to present a combined balance of
the first and second account balances.
24. The method of claim 15, wherein: providing the mobile module
comprises: making the mobile module available for installation in a
mobile device; and making the mobile module configurable to
wirelessly receive bank account information about the first bank
account from a bank server of a bank.
25. The method of claim 15, wherein: the mobile module is
configurable for: receiving user input regarding whether to permit
the quick-balance module to provide the first quick-balance report
without requiring the subsequent authentication; enabling an
authentication token for permitting the quick-balance module to
provide the first quick-balance report based on the user input; and
providing the first quick-balance report via the quick-balance
module only if the authentication token is enabled for a mobile
device where the mobile module is implemented.
Description
CROSS-REFERENCE TO RELATED APPLICATION
[0001] This application claims the benefit of U.S. Provisional
Application Ser. No. 61/671,478, filed on Jul. 13, 2012. The
disclosure of the such application is incorporated herein by
reference.
TECHNICAL FIELD
[0002] The present disclosure relates generally to banking systems,
and relates, more particularly, to mobile banking systems and
related methods.
BACKGROUND
[0003] The popularity and widespread use of mobile devices, such as
smartphones, has opened new gateways from which to engage in
banking transactions. Because of the sensitive nature of
information contained in bank accounts, however, strenuous security
and authentication features are required to permit safe banking
transactions through such mobile devices. Such security can come at
a convenience cost in terms of repeated required authentications to
access specific non-critical data about such bank accounts.
[0004] Considering the above, further developments can be made to
ease access to such specific non-critical data without compromising
the security of the bank accounts.
BRIEF DESCRIPTION OF THE DRAWINGS
[0005] The present disclosure will be better understood from a
reading of the following detailed description of examples of
embodiments, taken in conjunction with the accompanying figures in
the drawings.
[0006] FIG. 1 illustrates a diagram of a mobile banking system
comprising a mobile module for permitting a user to communicate
remotely with a bank server.
[0007] FIG. 2 illustrates a computer suitable for implementing an
embodiment of the bank server
[0008] FIG. 3 illustrates a representative block diagram of
elements of the computer of FIG. 2.
[0009] FIG. 4 illustrates a sample schematic of a mobile device at
which the mobile module can be implemented.
[0010] FIG. 5 illustrates a front display comprising a login
interface and a quick-balance interface.
[0011] FIG. 6 illustrates a security settings display of the mobile
module.
[0012] FIG. 7 illustrates a main display comprising a main account
interface of the mobile module.
[0013] FIG. 8 illustrates the front display of FIG. 5 with the
quick-balance interface revealing a quick-balance report.
[0014] FIG. 9 illustrates a front display comprising dual
quick-balance interface for different bank accounts.
[0015] FIG. 10 illustrates a front display comprising a combine
quick-balance interface for a combined quick-balance report of
multiple bank accounts.
[0016] FIG. 11 illustrates a flowchart for a method for
facilitating mobile banking
[0017] For simplicity and clarity of illustration, the drawing
figures illustrate the general manner of construction, and
descriptions and details of well-known features and techniques may
be omitted to avoid unnecessarily obscuring the present disclosure.
Additionally, elements in the drawing figures are not necessarily
drawn to scale. For example, the dimensions of some of the elements
in the figures may be exaggerated relative to other elements to
help improve understanding of embodiments of the present
disclosure. The same reference numerals in different figures denote
the same elements.
[0018] The terms "first," "second," "third," "fourth," and the like
in the description and in the claims, if any, are used for
distinguishing between similar elements and not necessarily for
describing a particular hierarchical, sequential, or chronological
order. It is to be understood that the terms so used are
interchangeable under appropriate circumstances such that the
embodiments described herein are, for example, capable of operation
in sequences other than those illustrated or otherwise described
herein. Furthermore, the terms "include," and "have," and any
variations thereof, are intended to cover a non-exclusive
inclusion, such that a process, method, system, article, device, or
apparatus that comprises a list of elements is not necessarily
limited to those elements, but may include other elements not
expressly listed or inherent to such process, method, system,
article, device, or apparatus.
[0019] The terms "left," "right," "front," "back," "top," "bottom,"
"over," "under," and the like in the description and in the claims,
if any, are used for descriptive purposes and not necessarily for
describing permanent relative positions. It is to be understood
that the terms so used are interchangeable under appropriate
circumstances such that the embodiments described herein are, for
example, capable of operation in other orientations than those
illustrated or otherwise described herein.
[0020] The terms "couple," "coupled," "couples," "coupling," and
the like should be broadly understood and refer to connecting two
or more elements or signals, electrically, mechanically or
otherwise. Two or more electrical elements may be electrically
coupled, but not mechanically or otherwise coupled; two or more
mechanical elements may be mechanically coupled, but not
electrically or otherwise coupled; two or more electrical elements
may be mechanically coupled, but not electrically or otherwise
coupled. Coupling (whether mechanical, electrical, or otherwise)
may be for any length of time, e.g., permanent or semi-permanent or
only for an instant.
[0021] "Electrical coupling" and the like should be broadly
understood and include coupling involving any electrical signal,
whether a power signal, a data signal, and/or other types or
combinations of electrical signals. "Mechanical coupling" and the
like should be broadly understood and include mechanical coupling
of all types. The absence of the word "removably," "removable," and
the like near the word "coupled," and the like does not mean that
the coupling, etc. in question is or is not removable.
DESCRIPTION
[0022] In one embodiment, a system for mobile banking can comprise
a mobile module for providing access to a first bank account of a
user. The mobile module can comprise a login module and a main
account module accessible via the login module and configured to at
least one of receive a first account balance of the first bank
account and further account information about the first bank
account, or request one or more transactions for the first bank
account. The mobile module can also comprise a quick-balance module
accessible separate from the main account module and configured to
receive a first account balance of the first bank account and to
provide a first quick-balance report of the first account balance.
The login module can be configured to receive initial
authentication of the user to enable initial access to the main
account module and to the quick balance module for the first bank
account, and to receive subsequent authentication of the user for
subsequent access to the main account module. The mobile module can
impede the subsequent access to the main account module until
receipt of the subsequent authentication of the user via the login
module. In addition, the mobile module can permit access to the
quick-balance report of the quick-balance module without requiring
the subsequent authentication of the user.
[0023] In one implementation, a method for facilitating mobile
banking can comprise providing a mobile module for mobilely
interfacing with a first bank account. Providing the mobile module
can comprises providing a login module, providing a main account
module accessible via the login module, and providing a
quick-balance module accessible separate from the main account
module. The login module can be configured to receive user initial
authentication for initial access to the main account module and to
the quick balance module for the first bank account, and to receive
user subsequent authentication for subsequent access to the main
account module. The main account module can be configured to at
least one of receive a first account balance of the first bank
account and further account information about the first bank
account, or request one or more transactions for the first bank
account. The quick-balance module can be configured to receive the
first account balance for the first bank account and to provide a
first quick-balance report of the first account balance. The mobile
module can be configured to impede the subsequent access to the
main account module until receipt of the user subsequent
authentication via the login module. Furthermore, the mobile module
can be configured to permit access to the quick-balance report of
the quick-balance module without requiring the user subsequent
authentication.
[0024] Other examples and embodiments are further disclosed herein.
Such examples and embodiments may be found in the figures, in the
claims, and/or in the present description.
[0025] Turning to the drawings, FIG. 1 illustrates a diagram of
mobile banking system 100, comprising mobile module 1600 for
permitting user 1900 to communicate remotely with bank server 1510
of banking institution 1500. In the present embodiment, mobile
module 1600 is implemented via mobile device 1200, which is
associated with user 1900 and can be, for instance a portable or
handheld electronic device such as a cellular phone, a smartphone,
a personal digital assistant (PDA), and/or a tablet device. For
instance mobile device 1200 can be an electrical device
manufactured by Research in Motion Limited (e.g., a Blackberry.RTM.
device), Palm, Inc. (e.g., a Palm.RTM. device), Apple Computer,
Inc. (e.g., an iPod.RTM. MP3 player, an iPod Touch.RTM. device, an
iPad.RTM. device, and/or an iPhone.RTM. device), Samsung
Electronics Co. Ltd. (e.g., a Galaxy.RTM. device). In other
examples, portable electronic device 1100 can be a portable
computer.
[0026] Mobile device 1200 can be configured to establish wireless
connection 1710 with Internet 1700. Similarly, bank server 1510 of
banking institution 1500 can be configured to communicate via
Internet 1700 through connection 1720, which may be wired or
wireless. Thus, mobile device 1200 and bank server 1510 can
communicate via Internet 1700. In some examples, a portion of
connection 1710 and/or of connection 1720 can be carried out via a
network configured for a wireless and/or cellular standard such as
WiFi (IEEE 802.11a/b/g/n), WiPAN (IEEE 802.15, Bluetooth.RTM.),
W-CDMA (Wideband Code Division Multiple Access), HSPA (High Speed
Packet Access), EDGE (Enhanced Data Rate for GSM Evolution), WiMAX
(Worldwide Interoperability for Microwave Access), LTE (Long Term
Evolution), etc.
[0027] FIG. 2 illustrates a computer 900 suitable for implementing
an embodiment of bank server 1510. Computer 900 includes a chassis
902 containing one or more circuit boards (not shown), a USB
(universal serial bus) port 912, a Compact Disc Read-Only Memory
(CD-ROM) and/or Digital Video Disc (DVD) drive 916, and a hard
drive 914. A representative block diagram of the elements included
on the circuit boards inside chassis 902 is shown in FIG. 3. A
central processing unit (CPU) 1010 is coupled to a system bus 1014
in FIG. 3. In various embodiments, the architecture of CPU 1010 can
be compliant with any of a variety of commercially distributed
architecture families.
[0028] System bus 1014 also is coupled to memory 1008 that includes
both read only memory (ROM) and random access memory (RAM).
Non-volatile portions of memory 1008 or the ROM can be encoded with
a boot code sequence suitable for restoring computer 900 (FIG. 2)
to a functional state after a system reset. In addition, memory
1008 can include microcode such as a Basic Input-Output System
(BIOS). In the depicted embodiment of FIG. 3, various I/O devices
such as a disk controller 1004, a graphics adapter 1024, a video
controller 1002, a keyboard adapter 1026, a mouse adapter 1006, a
network adapter 1020, and other I/O devices 1022 can be coupled to
system bus 1014. Keyboard adapter 1026 and mouse adapter 1006 are
coupled in the present example to keyboard 904 and mouse 910,
respectively, of computer 900. While graphics adapter 1024 and
video controller 1002 are indicated as distinct units in FIG. 3,
video controller 1002 can be integrated into graphics adapter 1024,
or vice versa in other embodiments. Video controller 1002 is
suitable for refreshing monitor 906 to display images on a screen
908 of computer 900. Disk controller 1004 can control hard drive
914, USB port 912, and/or CD-ROM or DVD drive 916. In other
embodiments, distinct units can be used to control each of these
devices separately.
[0029] Network adapters 1020 can be coupled to one or more
antennas. In some embodiments, network adapter 1020 can be
configured for WiFi communication (IEEE 802.11), and/or may be part
of a WNIC (wireless network interface controller) card (not shown)
plugged or coupled to an expansion port (not shown) in computer
900. Such WNIC card can be a wireless network card built into
internal computer 900 in some examples. A wireless network adapter
can be built into internal client computer 900 by having wireless
Ethernet capabilities integrated into the motherboard chipset, or
implemented via a dedicated wireless Ethernet chip, connected
through the PCI (peripheral component interconnector) or a PCI
express bus. In the same or other embodiments, network adapters
1020 can be configured for communication via other wireless
protocols, such as via WPAN, W-CDMA, HSPA, EDGE, WiMAX, LTE, or
others. In other embodiments, network adapter 1020 can be a wired
network adapter.
[0030] Although other components of computer 900 are not shown,
such components and their interconnection are well known to those
of ordinary skill in the art. Accordingly, further details
concerning the construction and composition of computer 900 and the
circuit boards inside chassis 902 need not be discussed herein.
[0031] When computer 900 is in operation, program instructions
stored on hard drive 914, on memory 1008, on a USB drive in USB
port 912, and/or on a CD-ROM or DVD in CD-ROM and/or DVD drive 916,
can be executed by CPU 1010 (FIG. 3). Such program instructions may
correspond to an operating system (OS) such as a Microsoft Windows
OS, a Linux OS, and/or a UNIX OS, among others. A portion of such
program instructions can be suitable for implementing or carrying
out the systems and methods described herein.
[0032] In the present example of FIG. 1, bank server 1510 is
coupled to database 1520, which can be similar to a memory device
of computer 900 (FIGS. 2-3) such as hard disk 914. Bank server 1510
and database 1520 can comprise a single unit in some
implementations, or can be separate from each other as illustrated
in FIG. 1. Database 1520 comprises bank accounts 1521-1522, which
in the present example are bank accounts of or associated with user
1900. Mobile module 1600 can be configured to communicate with bank
server 1510 to permit user 1600 to access bank accounts 1521 and/or
1522.
[0033] FIG. 4 illustrates a sample schematic of mobile device 1200.
Mobile device 1200 comprises processor module 4100 and memory
module 4200 coupled together to run mobile device 1200. Memory
module 4200 can comprise an operating system which can be accessed
therefrom for execution by processor module 4100 to operate
different functions of mobile device 1200. In some examples, the
operating system can comprise an operating system like an iOS.RTM.
OS from Apple Computer Inc., an Android.RTM. OS from Google, Inc.,
and/or a Windows Phone OS), from Microsoft, Inc., among others.
Mobile device 1200 also comprises display module 4300 coupled to
processor module 4100 and configured to present one or more user
interfaces for the operation of mobile device 1200. Processor
module 4100 is also coupled to communications module 4400, which
can be configured to establish connection 1710 (FIG. 1) via one or
more of the wireless standards described above.
[0034] Mobile module 1600 is also shown in FIG. 4 as implemented in
mobile device 1200, and can be coupled to or accessed by processor
module 4100 and/or display module 4300. Although shown separate
from memory module 4200 in FIG. 4, mobile module 1600 can be
coupled to and/or stored at memory module 4200 in some embodiments.
For instance, mobile module 1600 can comprise a mobile application
(mobile app) which may be downloaded via Internet 1700 from a
website or an online application store, and/or which may be stored
at mobile device 1200.
[0035] As shown in FIG. 1, mobile module 1600 can be configured to
provide user 1900 with access to bank account 1521 and/or 1522 at
banking institution 1500 via Internet 1700 through connection 1710
between mobile device 1200 and internet 1700 and through connection
1720 between Internet 1700 and bank server 1510. Mobile module 1600
can thus enable user 1900 to engage in mobile banking transactions
for bank accounts 1521 and/or 1522. Such banking transactions can
comprise, for example, the review of bank account balances,
requests for transfers of funds between accounts, and/or
photo-check deposits, among others.
[0036] As seen in FIG. 4, mobile module 1600 can comprise several
sub-modules, such as login module 4610, main account module 4620,
and quick-balance module 4630. Both main account module 4620 and
quick-balance module 4630 can provide information about bank
accounts 1521 and/or 1522, but main account module 4620 is
configured to provide more information or greater functionality
with respect to bank accounts 1521 and/or 1522 than quick-balance
module 4630, which can be limited to provide more basic information
such as an account balance.
[0037] Login module 4610 (FIG. 4) can be configured to receive
authentication information from a user, like user 1900 (FIG. 1), to
confirm the user's identity prior to providing access to accounts
1521 and/or 1522 via main account module 4620. The authentication
information can comprise a username and/or a password or personal
identification number (PIN) in some examples.
[0038] Main account module 4620 (FIG. 4) is accessible via login
module 4610, and can comprise one or more account operation modules
that can, for example, receive account balance 15211 of bank
account 1521 or account balance 15221 of bank account 1522, and/or
further account information about bank account 1521 or bank account
1522. Main account module 4620 can also request one or more
transactions for bank account 1521 and/or 1522 (FIG. 1). For
instance, as part of the further account information, main account
module 4620 (FIG. 4) can be configured to receive, from bank server
1510 (FIG. 1), information about individual transactions throughout
a certain time period for bank account 1521 and/or 1522. As another
example, main account module can transmit to bank server 1510 one
or more account transaction requests, such as balance transfer
requests or deposit requests, as received from user 1900 for bank
account 1521 and/or 1522.
[0039] Quick-balance module 4630 (FIG. 4) is accessible separate
from main account module 4620, and can be configured to receive an
account balance from bank server 1510, such as account balance
15211 of bank account 1521, and/or account balance 15221 of bank
account 1522 (FIG. 1). Quick-balance module 4630 can also be
configured to provide one or more quick-balance reports 4631
comprising or based on account balance 15211 and/or 15221, as
described further below.
[0040] FIG. 5 illustrates front display 5600 comprising login
interface 5610 and quick-balance interface 5630. Front display 5600
can be presented, for example, once mobile module 1600 is activated
when an icon corresponding to mobile module 1600 is selected by
user 1900. Quick-balance interface 5630 is configured to present
quick balance report 4631 of quick balance module 4630 (FIG. 4)
when actuated.
[0041] The illustration of FIG. 5 shows front display 5600 as it
appears upon initial activation of mobile module 1600, such as when
mobile module 1600 is first used and prior to any login of any
user. Accordingly, login interface 5610 is thus configured to
receive initial authentication 5611 of user 1600 (FIG. 1) to enable
initial access to main account module 4610 and to quick balance
module 4630 for bank account 1521 and/or 1522.
[0042] Quick-balance interface 5630 will not present quick balance
report 4631 until the user has enabled quick-balance module 4630
and/or quick-balance interface 5630 as a feature after successfully
logging in via initial authentication 5611. For instance, FIG. 6
illustrates security settings display 6600 of mobile module 1600,
which is accessible to user 1900 once logged-in to mobile module
1600, and which comprises quick-balance enablement interface 6610.
Thus, mobile module 1600 can receive user input from user 1900 via
quick-balance enablement interface 6610 to enable quick-balance
interface 5630 and thereby permit quick-balance module 4630 to
provide quick-balance report 4631 via quick-balance interface 5630
without requiring subsequent authentication from user 1900. In some
examples, if user 1900 tries to actuate quick-balance interface
5630 prior to enabling it and/or prior to successfully logging in
via initial authentication 5611, mobile module 1600 may present a
message prompting user 1900 to log in and enable quick-balance
module 4630 and/or quick-balance interface 5630.
[0043] There can be embodiments where, when user 1900 enables
quick-balance module 4630 as described above, an authentication
token can be enabled for permitting quick-balance module 4630 to
provide reports such as quick balance report 4631. In some
examples, such authentication token can be similar to
authentication token 4210 (FIG. 4), which can be generated by
mobile module 1600 or can be received from bank server 1510. In the
present example, authentication token 4210 is stored at memory
module 4200 of mobile device 1200, but there can be other examples
where authentication token 4210 can be stored at bank database 1520
and associated with bank account 1521 and/or 1522. Mobile module
1600 will thus provide quick balance report 4631 via quick-balance
module 4630 and/or quick-balance interface 5630 only if the
authentication token is enabled as described above.
[0044] FIG. 7 illustrates main display 7600 comprising main
interface 7610 of mobile module 1600. Once user 1900 has logged-in
to mobile module 1600 via login interface 5610 (FIG. 5), main
display 7600 of mobile module 1600 can be presented via display
module 4300 (FIG. 4) so that user 1900 can interface with main
account module 4620 (FIG. 4) via main interface 7610. Main
interface 7610 comprises several tools for interfacing with main
account module 4620 so that main account module 4620 can receive
information and/or request transactions with respect to bank
account 1521 through bank server 1510 (FIG. 1). For example, main
interface 7610 comprises transactions interface 7611 configured to
present transaction details of the different transactions of bank
account 1521 with respect to a time period. Budget interface 7612
is configured to present budgeting information and/or to permit
budget planning with respect to bank account 1521. Deposit
interface 7613 is configured to permit the user to deposit a check
into bank account 1521, such as via a photo-check deposit where a
picture of the deposit check is sent to bank server 1510 for
processing and deposit. Payment interface 7614 is configured permit
the user to select a payee and to transmit a request to bank server
1510 to send a payment to the payee out of bank account 1521. Main
balance interface 7615 is configured to present main balance report
7631 comprising at least account balance 15211 of bank account
1521. Main balance report 7631 can also comprise further
information, such as a summary of pending deposit(s) not included
in account balance 15211. In some embodiments, main account module
4620 can provide the user with another interface similar to main
interface 7610 but configured with respect to bank account 1522
rather than bank account 1521.
[0045] Once user 1900 has successfully logged-in via initial
authentication 5611 (FIG. 5) and has enabled quick-balance module
4630 and/or quick-balance interface 5630 via quick-balance
enablement interface 6610 (FIG. 6), user 1900 can eventually log
off mobile module 1600, whether intentionally or automatically
after a time-out period. Accordingly, when mobile module 1600 is
subsequently called at a later time, front display 5600 will be
presented with quick balance interface 5630 along with login
interface 5610 requesting subsequent authentication 8611, as shown
in FIG. 8. In other embodiments, quick balance interface 5630 and
login interface 5610 need not be presented together. In any event,
mobile module 1600 will impede subsequent access to main account
module 4620 until receipt of subsequent authentication 8611 for
login of user 1900 via login interface 5610. In contrast, mobile
module 1600 will permit access to quick balance module 4630 (FIG.
4), without requiring subsequent authentication 8611 of user 1900,
if user 1900 previously enabled such feature via quick-balance
enablement interface 6610 (FIG. 6). Such a feature can save time
and effort for user 1900 if a quick glance at account balance 15211
is needed, and would not permit any unauthorized user to access
more sensitive information and/or to request transactions with
respect to account 1521 and/or 1522. Quick-balance interface 5630,
as shown in FIGS. 5 and 8, presents only account balance 15211 for
bank account 1521 and thereby conceals other information which may
be more sensitive. Nevertheless, there can be other embodiments
where further information about bank account 1521 can be presented
by quick-balance interface 5630, such as an account identifier that
may comprise a portion of the account number and/or an account
nickname. In some examples, such an account identifier can be
similar to account identifier 9731 as described below with respect
to FIG. 9.
[0046] As seen in the examples of FIGS. 5 and 8, quick-balance
interface 5630 comprises actuator 5635 configured to conceal
quick-balance repot 4631 when actuator 5635 is not actuated, and to
reveal quick-balance report 4631 when actuator 5635 is actuated. In
the present embodiment actuator 5635 comprises a slideblock that
reveals quick-balance report 4631 when actuated by a sliding
gesture. For instance, FIG. 5 shows the slideblock of actuator 5635
prior to actuation and thus concealing quick-balance report 4631,
while FIG. 8 shows the slideblock 5635 being actuated by sliding,
and revealing quick-balance report 4631 as it is slid. More
specifically, for the present embodiment, quick-balance interface
5630 comprises bottom interface layer 8636 comprising quick balance
report 4631, and top interface layer 5637 covering bottom interface
layer 8636 and quick-balance report 4631 thereat. Thus, as seen in
FIG. 8, the slideblock of actuator 5635 removes top interface layer
5637, as actuator 5635 is slid, to reveal quick-balance report 4631
at bottom interface layer 8636. There can be other embodiments
where actuator 5636 need not comprise a slideblock or operate by
sliding. For instance, in other embodiments, actuator 5636 can be
configured as a button that reveals quick-balance report 4631 when
actuated by a pressing gesture. As another example, actuator 5636
can be actuated by a screen-pull gesture that grabs, drags, or
otherwise displaces front display 5600 or at least a portion
thereof to reveal quick-balance report 4631.
[0047] There can also be embodiments where quick-balance module
4630 (FIG. 4) can be configured to provide quick balance reports
for more than one bank account, and where mobile module 1600 can
comprise quick-balance interfaces configured to handle more than
one bank account. For instance, as seen in FIG. 4, quick-balance
module 4630 can be configured to provide quick-balance report 4632
in addition to quick-balance report 4631, where quick-balance
report 4631 can be correlated to account balance 15211 of bank
account 15221, and quick-balance report 4632 can be correlated to
account balance 15221 of bank account 1522 (FIG. 1). FIG. 9
illustrates front display 9600 of mobile module 1600, which can be
similar to front display 5600 (FIGS. 5, 8), but further comprises
quick-balance interface 9630 similar to quick-balance interface
9630 but configured to present quick-balance report 4632 of bank
account 1522. To prevent confusion of the user with respect to
quick-balance interfaces 5630 and 9630, front display 9600 further
comprises account identifier 9731 to identify quick-balance
interface 5630 with respect to bank account 1521, and also
comprises account identifier 9732 to identify quick-balance
interface 9630 with respect to bank account 1522.
[0048] FIG. 10 illustrates front display 10600 of mobile module
1600, which can be similar to front display 5600 (FIGS. 5, 8)
and/or front display 9600 (FIG. 9). Front display 10600 comprises
quick-balance interface 10630, which can be similar to
quick-balance interface 5630 (FIGS. 5, 8), but is configured to
present quick-balance report 4633 instead, where quick-balance
report 4633 comprises a combined balance of account balances 15211
and 15221 of respective bank accounts 1521 and 1522 (FIG. 1). Thus,
user 1900 can quickly determine the combined balance of his bank
accounts at banking institution 1500 through quick-balance
interface 10630 of front display 10600.
[0049] Moving on, FIG. 11 illustrates a flowchart for a method
11000 for facilitating mobile banking In some implementations,
method 11000 can implement or be part of a mobile banking system
similar to mobile banking system 100 as described above.
[0050] Method 11000 comprises block 11100 for providing a mobile
module for mobilely interfacing with a first bank account. In some
examples, the mobile module can be similar to mobile module 1600,
as described above with respect to FIGS. 1-10. The first bank
account can be similar to bank account 1521 or bank account 1522
(FIG. 1), which can be accessible via bank server 1510 of banking
institution 1500. The first bank account can refer to any bank
account of a user, regardless of whether such bank account is
primary or secondary with respect to others, or whether such bank
account was created before or after other bank accounts.
[0051] Block 11100 can comprise several sub-blocks in some
implementations. For instance, block 11100 can comprise sub-block
11110 for providing a login module, which can be similar to login
module 4610 as described above with respect to FIGS. 4-5 and 8-10.
Block 11100 can also comprise block 11120 for providing a main
account module accessible via the login module, where the main
account module can be similar to main account module 4620 as
described above with respect to FIGS. 4 and 7. Block 11100 can
further comprise providing a quick-balance module accessible
separate from the main account module, where the quick-balance
module can be similar to quick-balance module 4630 as described
above with respect to FIGS. 4-10.
[0052] Method 11000 also comprises block 11200 for impeding
subsequent access to the main account module until receipt of user
subsequent authentication via the login module. In some examples,
the user subsequent authentication can be as described above with
respect to subsequent authentication 8611 (FIG. 8), which is
required to call main display 7600 and main interface 7610 (FIG. 7)
to gain access to main account module 4620.
[0053] Method 11000 further comprises block 11300 for permitting
access to a quick-balance report of the quick-balance module
without requiring the user subsequent authentication. In some
examples, the quick-balance report can be similar to quick-balance
report 4631, 4632, or 4633 of quick-balance module 4630, and can be
accessed via a quick-balance interface similar to quick-balance
interface 5630 (FIGS. 5, 8, 9), quick-balance interface 9630 (FIG.
9), and/or quick-balance interface 10630 (FIG. 10).
[0054] In some examples, one or more of the different blocks of
method 11000 can be combined into a single block or performed
simultaneously, and/or the sequence of such blocks can be changed.
For example, sub-blocks 11110, 11120, and/or 11130 can be combined
into a single sub-block. In the same or other examples, some of the
blocks of method 11000 can be subdivided into several sub-blocks.
There can also be examples where method 11000 can comprise further
or different blocks. As an example, method 11000 can further
comprise a block for accessing further detailed information about
the first bank account, and/or for requesting transactions for the
first bank account. In addition, there may be examples where method
11000 can comprise only part of the steps described above.
[0055] In some instances, the exemplary modules described above may
be implemented as machine-accessible instructions utilizing any of
many different programming codes stored on any combination of
machine-accessible media embodied in a mobile application (e.g., an
app) and/or an online application for various wired and/or wireless
mobile communication devices such as handheld computers,
smartphones, portable media players, tablet computers, etc. In
addition or alternatively, the machine-accessible instructions may
be embodied in a volatile or non-volatile memory or other mass
storage device (e.g., a USB drive, a CD, or a DVD). For example,
the machine-accessible instructions may be embodied in a
machine-accessible medium such as a programmable gate array, an
application specific integrated circuit (ASIC), an erasable
programmable read only memory (EPROM), a read only memory (ROM), a
random access memory (RAM), a flash memory, a magnetic media, an
optical media, and/or any other suitable type of medium. The
systems, apparatus, methods, and articles of manufacture described
herein are not limited in this regard.
[0056] Although the mobile banking systems and related methods
herein have been described with reference to specific embodiments,
various changes may be made without departing from the spirit or
scope of the present disclosure. Examples of such changes have been
given in the foregoing description. Other permutations of the
different embodiments having one or more of the features of the
various figures are likewise contemplated. Accordingly, the
specification and drawings herein are intended to be illustrative
of the scope of the disclosure and are not intended to be limiting.
It is intended that the scope of this application shall be limited
only to the extent required by the appended claims.
[0057] The mobile banking systems and related methods discussed
herein may be implemented in a variety of embodiments, and the
foregoing discussion of certain of these embodiments does not
necessarily represent a complete description of all possible
embodiments. Rather, the detailed description of the drawings, and
the drawings themselves, disclose at least one preferred
embodiment, and may disclose alternative embodiments.
[0058] All elements claimed in any particular claim are essential
to the embodiment claimed in that particular claim. Consequently,
replacement of one or more claimed elements constitutes
reconstruction and not repair. Additionally, benefits, other
advantages, and solutions to problems have been described with
regard to specific embodiments. The benefits, advantages, solutions
to problems, and any element or elements that may cause any
benefit, advantage, or solution to occur or become more pronounced,
however, are not to be construed as critical, required, or
essential features or elements of any or all of the claims, unless
such benefits, advantages, solutions, or elements are expressly
stated in such claims.
[0059] Moreover, embodiments and limitations disclosed herein are
not dedicated to the public under the doctrine of dedication if the
embodiments and/or limitations: (1) are not expressly claimed in
the claims; and (2) are or are potentially equivalents of express
elements and/or limitations in the claims under the doctrine of
equivalents.
* * * * *