US20140019322A1 - Mobile banking systems and related methods - Google Patents

Abstract

Embodiments of mobile banking systems are described herein. Other examples and related methods are also disclosed herein.

Description

CROSS-REFERENCE TO RELATED APPLICATION
• 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
• The present disclosure relates generally to banking systems, and relates, more particularly, to mobile banking systems and related methods.
BACKGROUND
• 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.
• 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
• 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.
• 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.
• FIG. 2 illustrates a computer suitable for implementing an embodiment of the bank server
• FIG. 3 illustrates a representative block diagram of elements of the computer ofFIG. 2.
• FIG. 4 illustrates a sample schematic of a mobile device at which the mobile module can be implemented.
• FIG. 5 illustrates a front display comprising a login interface and a quick-balance interface.
• FIG. 6 illustrates a security settings display of the mobile module.
• FIG. 7 illustrates a main display comprising a main account interface of the mobile module.
• FIG. 8 illustrates the front display ofFIG. 5 with the quick-balance interface revealing a quick-balance report.
• FIG. 9 illustrates a front display comprising dual quick-balance interface for different bank accounts.
• FIG. 10 illustrates a front display comprising a combine quick-balance interface for a combined quick-balance report of multiple bank accounts.
• FIG. 11 illustrates a flowchart for a method for facilitating mobile banking
• 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.
• 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.
• 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.
• 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.
• “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
• 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.
• 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.
• 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.
• Turning to the drawings,FIG. 1 illustrates a diagram of mobile banking system100, comprisingmobile module1600 for permittinguser1900 to communicate remotely withbank server1510 ofbanking institution1500. In the present embodiment,mobile module1600 is implemented viamobile device1200, which is associated withuser1900 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 instancemobile device1200 can be an electrical device manufactured by Research in Motion Limited (e.g., a Blackberry® device), Palm, Inc. (e.g., a Palm® device), Apple Computer, Inc. (e.g., an iPod® MP3 player, an iPod Touch® device, an iPad® device, and/or an iPhone® device), Samsung Electronics Co. Ltd. (e.g., a Galaxy® device). In other examples, portable electronic device1100 can be a portable computer.
• Mobile device1200 can be configured to establishwireless connection1710 withInternet1700. Similarly,bank server1510 ofbanking institution1500 can be configured to communicate viaInternet1700 throughconnection1720, which may be wired or wireless. Thus,mobile device1200 andbank server1510 can communicate viaInternet1700. In some examples, a portion ofconnection1710 and/or ofconnection1720 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®), 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.
• FIG. 2 illustrates acomputer900 suitable for implementing an embodiment ofbank server1510.Computer900 includes achassis902 containing one or more circuit boards (not shown), a USB (universal serial bus)port912, a Compact Disc Read-Only Memory (CD-ROM) and/or Digital Video Disc (DVD)drive916, and ahard drive914. A representative block diagram of the elements included on the circuit boards insidechassis902 is shown inFIG. 3. A central processing unit (CPU)1010 is coupled to asystem bus1014 inFIG. 3. In various embodiments, the architecture ofCPU1010 can be compliant with any of a variety of commercially distributed architecture families.
• System bus1014 also is coupled tomemory1008 that includes both read only memory (ROM) and random access memory (RAM). Non-volatile portions ofmemory1008 or the ROM can be encoded with a boot code sequence suitable for restoring computer900 (FIG. 2) to a functional state after a system reset. In addition,memory1008 can include microcode such as a Basic Input-Output System (BIOS). In the depicted embodiment ofFIG. 3, various I/O devices such as adisk controller1004, agraphics adapter1024, avideo controller1002, akeyboard adapter1026, amouse adapter1006, anetwork adapter1020, and other I/O devices1022 can be coupled tosystem bus1014.Keyboard adapter1026 andmouse adapter1006 are coupled in the present example tokeyboard904 andmouse910, respectively, ofcomputer900. Whilegraphics adapter1024 andvideo controller1002 are indicated as distinct units inFIG. 3,video controller1002 can be integrated intographics adapter1024, or vice versa in other embodiments.Video controller1002 is suitable forrefreshing monitor906 to display images on ascreen908 ofcomputer900.Disk controller1004 can controlhard drive914,USB port912, and/or CD-ROM orDVD drive916. In other embodiments, distinct units can be used to control each of these devices separately.
• Network adapters1020 can be coupled to one or more antennas. In some embodiments,network adapter1020 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) incomputer900. Such WNIC card can be a wireless network card built intointernal computer900 in some examples. A wireless network adapter can be built intointernal client computer900 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 adapters1020 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 adapter1020 can be a wired network adapter.
• Although other components ofcomputer900 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 ofcomputer900 and the circuit boards insidechassis902 need not be discussed herein.
• Whencomputer900 is in operation, program instructions stored onhard drive914, onmemory1008, on a USB drive inUSB port912, and/or on a CD-ROM or DVD in CD-ROM and/orDVD drive916, can be executed by CPU1010 (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.
• In the present example ofFIG. 1,bank server1510 is coupled todatabase1520, which can be similar to a memory device of computer900 (FIGS. 2-3) such ashard disk914.Bank server1510 anddatabase1520 can comprise a single unit in some implementations, or can be separate from each other as illustrated inFIG. 1.Database1520 comprises bank accounts1521-1522, which in the present example are bank accounts of or associated withuser1900.Mobile module1600 can be configured to communicate withbank server1510 to permituser1600 to accessbank accounts1521 and/or1522.
• FIG. 4 illustrates a sample schematic ofmobile device1200.Mobile device1200 comprisesprocessor module4100 and memory module4200 coupled together to runmobile device1200. Memory module4200 can comprise an operating system which can be accessed therefrom for execution byprocessor module4100 to operate different functions ofmobile device1200. In some examples, the operating system can comprise an operating system like an iOS® OS from Apple Computer Inc., an Android® OS from Google, Inc., and/or a Windows Phone OS), from Microsoft, Inc., among others.Mobile device1200 also comprisesdisplay module4300 coupled toprocessor module4100 and configured to present one or more user interfaces for the operation ofmobile device1200.Processor module4100 is also coupled to communications module4400, which can be configured to establish connection1710 (FIG. 1) via one or more of the wireless standards described above.
• Mobile module1600 is also shown inFIG. 4 as implemented inmobile device1200, and can be coupled to or accessed byprocessor module4100 and/ordisplay module4300. Although shown separate from memory module4200 inFIG. 4,mobile module1600 can be coupled to and/or stored at memory module4200 in some embodiments. For instance,mobile module1600 can comprise a mobile application (mobile app) which may be downloaded viaInternet1700 from a website or an online application store, and/or which may be stored atmobile device1200.
• As shown inFIG. 1,mobile module1600 can be configured to provideuser1900 with access tobank account1521 and/or1522 atbanking institution1500 viaInternet1700 throughconnection1710 betweenmobile device1200 andinternet1700 and throughconnection1720 betweenInternet1700 andbank server1510.Mobile module1600 can thus enableuser1900 to engage in mobile banking transactions forbank accounts1521 and/or1522. 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.
• As seen inFIG. 4,mobile module1600 can comprise several sub-modules, such aslogin module4610,main account module4620, and quick-balance module4630. Bothmain account module4620 and quick-balance module4630 can provide information aboutbank accounts1521 and/or1522, butmain account module4620 is configured to provide more information or greater functionality with respect tobank accounts1521 and/or1522 than quick-balance module4630, which can be limited to provide more basic information such as an account balance.
• Login module4610 (FIG. 4) can be configured to receive authentication information from a user, like user1900 (FIG. 1), to confirm the user's identity prior to providing access toaccounts1521 and/or1522 viamain account module4620. The authentication information can comprise a username and/or a password or personal identification number (PIN) in some examples.
• Main account module4620 (FIG. 4) is accessible vialogin module4610, and can comprise one or more account operation modules that can, for example, receiveaccount balance15211 ofbank account1521 oraccount balance15221 ofbank account1522, and/or further account information aboutbank account1521 orbank account1522.Main account module4620 can also request one or more transactions forbank account1521 and/or1522 (FIG. 1). For instance, as part of the further account information, main account module4620 (FIG. 4) can be configured to receive, from bank server1510 (FIG. 1), information about individual transactions throughout a certain time period forbank account1521 and/or1522. As another example, main account module can transmit tobank server1510 one or more account transaction requests, such as balance transfer requests or deposit requests, as received fromuser1900 forbank account1521 and/or1522.
• Quick-balance module4630 (FIG. 4) is accessible separate frommain account module4620, and can be configured to receive an account balance frombank server1510, such asaccount balance15211 ofbank account1521, and/oraccount balance15221 of bank account1522 (FIG. 1). Quick-balance module4630 can also be configured to provide one or more quick-balance reports4631 comprising or based onaccount balance15211 and/or15221, as described further below.
• FIG. 5 illustratesfront display5600 comprisinglogin interface5610 and quick-balance interface5630.Front display5600 can be presented, for example, oncemobile module1600 is activated when an icon corresponding tomobile module1600 is selected byuser1900. Quick-balance interface5630 is configured to presentquick balance report4631 of quick balance module4630 (FIG. 4) when actuated.
• The illustration ofFIG. 5 showsfront display5600 as it appears upon initial activation ofmobile module1600, such as whenmobile module1600 is first used and prior to any login of any user. Accordingly,login interface5610 is thus configured to receiveinitial authentication5611 of user1600 (FIG. 1) to enable initial access tomain account module4610 and toquick balance module4630 forbank account1521 and/or1522.
• Quick-balance interface5630 will not presentquick balance report4631 until the user has enabled quick-balance module4630 and/or quick-balance interface5630 as a feature after successfully logging in viainitial authentication5611. For instance,FIG. 6 illustrates security settings display6600 ofmobile module1600, which is accessible touser1900 once logged-in tomobile module1600, and which comprises quick-balance enablement interface6610. Thus,mobile module1600 can receive user input fromuser1900 via quick-balance enablement interface6610 to enable quick-balance interface5630 and thereby permit quick-balance module4630 to provide quick-balance report4631 via quick-balance interface5630 without requiring subsequent authentication fromuser1900. In some examples, ifuser1900 tries to actuate quick-balance interface5630 prior to enabling it and/or prior to successfully logging in viainitial authentication5611,mobile module1600 may present amessage prompting user1900 to log in and enable quick-balance module4630 and/or quick-balance interface5630.
• There can be embodiments where, whenuser1900 enables quick-balance module4630 as described above, an authentication token can be enabled for permitting quick-balance module4630 to provide reports such asquick balance report4631. In some examples, such authentication token can be similar to authentication token4210 (FIG. 4), which can be generated bymobile module1600 or can be received frombank server1510. In the present example,authentication token4210 is stored at memory module4200 ofmobile device1200, but there can be other examples whereauthentication token4210 can be stored atbank database1520 and associated withbank account1521 and/or1522.Mobile module1600 will thus providequick balance report4631 via quick-balance module4630 and/or quick-balance interface5630 only if the authentication token is enabled as described above.
• FIG. 7 illustratesmain display7600 comprisingmain interface7610 ofmobile module1600. Onceuser1900 has logged-in tomobile module1600 via login interface5610 (FIG. 5),main display7600 ofmobile module1600 can be presented via display module4300 (FIG. 4) so thatuser1900 can interface with main account module4620 (FIG. 4) viamain interface7610.Main interface7610 comprises several tools for interfacing withmain account module4620 so thatmain account module4620 can receive information and/or request transactions with respect tobank account1521 through bank server1510 (FIG. 1). For example,main interface7610 comprisestransactions interface7611 configured to present transaction details of the different transactions ofbank account1521 with respect to a time period.Budget interface7612 is configured to present budgeting information and/or to permit budget planning with respect tobank account1521.Deposit interface7613 is configured to permit the user to deposit a check intobank account1521, such as via a photo-check deposit where a picture of the deposit check is sent tobank server1510 for processing and deposit.Payment interface7614 is configured permit the user to select a payee and to transmit a request tobank server1510 to send a payment to the payee out ofbank account1521.Main balance interface7615 is configured to presentmain balance report7631 comprising atleast account balance15211 ofbank account1521.Main balance report7631 can also comprise further information, such as a summary of pending deposit(s) not included inaccount balance15211. In some embodiments,main account module4620 can provide the user with another interface similar tomain interface7610 but configured with respect tobank account1522 rather thanbank account1521.
• Onceuser1900 has successfully logged-in via initial authentication5611 (FIG. 5) and has enabled quick-balance module4630 and/or quick-balance interface5630 via quick-balance enablement interface6610 (FIG. 6),user1900 can eventually log offmobile module1600, whether intentionally or automatically after a time-out period. Accordingly, whenmobile module1600 is subsequently called at a later time,front display5600 will be presented withquick balance interface5630 along withlogin interface5610 requestingsubsequent authentication8611, as shown inFIG. 8. In other embodiments,quick balance interface5630 andlogin interface5610 need not be presented together. In any event,mobile module1600 will impede subsequent access tomain account module4620 until receipt ofsubsequent authentication8611 for login ofuser1900 vialogin interface5610. In contrast,mobile module1600 will permit access to quick balance module4630 (FIG. 4), without requiringsubsequent authentication8611 ofuser1900, ifuser1900 previously enabled such feature via quick-balance enablement interface6610 (FIG. 6). Such a feature can save time and effort foruser1900 if a quick glance ataccount balance15211 is needed, and would not permit any unauthorized user to access more sensitive information and/or to request transactions with respect toaccount1521 and/or1522. Quick-balance interface5630, as shown inFIGS. 5 and 8, presents only accountbalance15211 forbank account1521 and thereby conceals other information which may be more sensitive. Nevertheless, there can be other embodiments where further information aboutbank account1521 can be presented by quick-balance interface5630, 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 toaccount identifier9731 as described below with respect toFIG. 9.
• As seen in the examples ofFIGS. 5 and 8, quick-balance interface5630 comprisesactuator5635 configured to conceal quick-balance repot4631 whenactuator5635 is not actuated, and to reveal quick-balance report4631 whenactuator5635 is actuated. In thepresent embodiment actuator5635 comprises a slideblock that reveals quick-balance report4631 when actuated by a sliding gesture. For instance,FIG. 5 shows the slideblock ofactuator5635 prior to actuation and thus concealing quick-balance report4631, whileFIG. 8 shows theslideblock5635 being actuated by sliding, and revealing quick-balance report4631 as it is slid. More specifically, for the present embodiment, quick-balance interface5630 comprisesbottom interface layer8636 comprisingquick balance report4631, andtop interface layer5637 coveringbottom interface layer8636 and quick-balance report4631 thereat. Thus, as seen inFIG. 8, the slideblock ofactuator5635 removestop interface layer5637, asactuator5635 is slid, to reveal quick-balance report4631 atbottom interface layer8636. There can be other embodiments where actuator5636 need not comprise a slideblock or operate by sliding. For instance, in other embodiments, actuator5636 can be configured as a button that reveals quick-balance report4631 when actuated by a pressing gesture. As another example, actuator5636 can be actuated by a screen-pull gesture that grabs, drags, or otherwise displacesfront display5600 or at least a portion thereof to reveal quick-balance report4631.
• There can also be embodiments where quick-balance module4630 (FIG. 4) can be configured to provide quick balance reports for more than one bank account, and wheremobile module1600 can comprise quick-balance interfaces configured to handle more than one bank account. For instance, as seen inFIG. 4, quick-balance module4630 can be configured to provide quick-balance report4632 in addition to quick-balance report4631, where quick-balance report4631 can be correlated to accountbalance15211 ofbank account15221, and quick-balance report4632 can be correlated to accountbalance15221 of bank account1522 (FIG. 1).FIG. 9 illustratesfront display9600 ofmobile module1600, which can be similar to front display5600 (FIGS. 5,8), but further comprises quick-balance interface9630 similar to quick-balance interface9630 but configured to present quick-balance report4632 ofbank account1522. To prevent confusion of the user with respect to quick-balance interfaces5630 and9630,front display9600 further comprisesaccount identifier9731 to identify quick-balance interface5630 with respect tobank account1521, and also comprisesaccount identifier9732 to identify quick-balance interface9630 with respect tobank account1522.
• FIG. 10 illustratesfront display10600 ofmobile module1600, which can be similar to front display5600 (FIGS. 5,8) and/or front display9600 (FIG. 9).Front display10600 comprises quick-balance interface10630, which can be similar to quick-balance interface5630 (FIGS. 5,8), but is configured to present quick-balance report4633 instead, where quick-balance report4633 comprises a combined balance of account balances15211 and15221 ofrespective bank accounts1521 and1522 (FIG. 1). Thus,user1900 can quickly determine the combined balance of his bank accounts atbanking institution1500 through quick-balance interface10630 offront display10600.
• Moving on,FIG. 11 illustrates a flowchart for amethod11000 for facilitating mobile banking In some implementations,method11000 can implement or be part of a mobile banking system similar to mobile banking system100 as described above.
• Method11000 comprisesblock11100 for providing a mobile module for mobilely interfacing with a first bank account. In some examples, the mobile module can be similar tomobile module1600, as described above with respect toFIGS. 1-10. The first bank account can be similar tobank account1521 or bank account1522 (FIG. 1), which can be accessible viabank server1510 ofbanking institution1500. 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.
• Block11100 can comprise several sub-blocks in some implementations. For instance, block11100 can comprise sub-block11110 for providing a login module, which can be similar tologin module4610 as described above with respect toFIGS. 4-5 and8-10.Block11100 can also compriseblock11120 for providing a main account module accessible via the login module, where the main account module can be similar tomain account module4620 as described above with respect toFIGS. 4 and 7.Block11100 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 module4630 as described above with respect toFIGS. 4-10.
• Method11000 also comprises block11200 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 authentication8611 (FIG. 8), which is required to callmain display7600 and main interface7610 (FIG. 7) to gain access tomain account module4620.
• Method11000 further comprises block11300 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 report4631,4632, or4633 of quick-balance module4630, and can be accessed via a quick-balance interface similar to quick-balance interface5630 (FIGS. 5,8,9), quick-balance interface9630 (FIG. 9), and/or quick-balance interface10630 (FIG. 10).
• In some examples, one or more of the different blocks ofmethod11000 can be combined into a single block or performed simultaneously, and/or the sequence of such blocks can be changed. For example,sub-blocks11110,11120, and/or11130 can be combined into a single sub-block. In the same or other examples, some of the blocks ofmethod11000 can be subdivided into several sub-blocks. There can also be examples wheremethod11000 can comprise further or different blocks. As an example,method11000 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 wheremethod11000 can comprise only part of the steps described above.
• 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.
• 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.
• 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.
• 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.
• 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.

Claims (25)

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 ofclaim 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 ofclaim 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 ofclaim 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 ofclaim 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 ofclaim 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 ofclaim 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 ofclaim 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 ofclaim 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 ofclaim 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 ofclaim 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 ofclaim 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 ofclaim 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 ofclaim 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 ofclaim 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 ofclaim 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 ofclaim 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 ofclaim 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 ofclaim 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 ofclaim 15, wherein:

the first quick-balance report consists of the first account balance for the first bank account.

23. The method ofclaim 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 ofclaim 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 ofclaim 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.

Images