US20180108083A1 - Financial status display - Google Patents

Abstract

Systems and methods are provided for displaying account information. The systems and methods may include a status display device connected to a network in a home or office environment. The status display may be configured to provide a constant status indicator, to provide a user with a quick and simple account status, without the need for multi-step login and verification processes. The status display may receive account status information from a server, the account status information excluding sensitive information identifying the user or the account. The status display may provide colored indicators to inform the user of their financial situation while reducing security risks and reducing processing capability requirements, thereby allowing for a simple status display device that can be placed throughout a household or integrated into common household items.

Description

CROSS REFERENCE TO RELATED APPLICATIONS
• This application is entitled to and claims the benefit of priority from U.S. Provisional Application No. 62/067,525 filed Oct. 23, 2014, the contents of which are expressly incorporated herein by reference.
BACKGROUND
• In today's society, individuals often worry about their financial health, but often lose touch with their current financial health status. Individuals also lose sight of upcoming events such as payment due dates. In order to stay informed, many individuals rely on their financial service providers' notification systems.
• Some financial service providers allow customers to set up notifications and reminders for payment due dates, fraudulent account activity, spending goals/limits, account overdrafts, and other events warranting special attention. Typical notification systems provide the notifications and reminders in the form of text messages, emails, and social media notifications. Similar to junk mail and advertisements, many of these notifications or reminders go unnoticed or soon become a nuisance to the customer and, thus, get ignored. On the other hand, a lack of any notification or reminder leaves individuals in the dark about their financial situation, and places the burden on the individuals to proactively monitor their account statuses. Manual account monitoring usually requires the individual to navigate to a website or mobile application (app) and enter authentication credentials just to ascertain whether their account status is normal or abnormal.
• Thus, a notification system is desired that provides constant, yet passive, account status indications in order to effectively and efficiently inform individuals of their financial situations.
SUMMARY
• Disclosed embodiments provide methods and systems for using a status display to provide account statuses.
• Consistent with a disclosed embodiment, a display device for providing an account status is provided. The device may include a processor, a display, a transceiver, and a memory having stored thereon instructions executable by the processor. When executed, the instructions may configure the processor to establish a connection with a communication network via the transceiver to access account status information for a first account associated with a user, receive the account status information via the connection, determine an indication based on the received account status information, and output, via the display, the determined indication.
• Consistent with another disclosed embodiment, a system for providing an account status is provided. The system may include a transceiver, a memory, and a processor. The processor may be coupled to the transceiver and configured to execute instructions stored in the memory to receive information for a first account associated with a user, analyze the received information to identify one or more status indicators, determine a status for the first account based on the one or more status indicators, generate account status information based on the determined status, the account status information excluding sensitive information that identifies the user or the first account, and transmit, by the transceiver, the account status information to a display device.
• Consistent with another disclosed embodiment, a computer-implemented method of providing an account status is provided. The method may comprise accessing information from a database for a first account associated with a user, analyzing, by a processor, the received information to identify one or more status indictors, determining a status for the first account based on the one or more status indicators, generating, by the processor, account status information based on the determined status, the account status information excluding sensitive information that identifies the user or the first account, and transmitting, by a transceiver, the account status information to a display device.
• Consistent with other disclosed embodiments, non-transitory computer-readable storage media may store program instructions, which are executed by at least one processor device and perform any of the methods described herein.
• The foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the claims.
BRIEF DESCRIPTION OF THE DRAWINGS
• The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate several embodiments and, together with the description, serve to explain the disclosed principles. In the drawings:
• FIG. 1 is a diagram of an exemplary system that may be used to generate and display account status information using a status display, consistent with disclosed embodiments.
• FIG. 2 is a diagram of an exemplary status display, consistent with disclosed embodiments.
• FIG. 3 is a diagram of an exemplary mobile device, consistent with disclosed embodiments.
• FIG. 4 is a diagram of an exemplary financial service provider server, consistent with disclosed embodiments.
• FIG. 5 is a flowchart of an exemplary process for status display setup, consistent with disclosed embodiments.
• FIG. 6 is a flowchart of an exemplary status display update and display process, consistent with disclosed embodiments.
• FIGS. 7A-7C are illustrations of exemplary status displays, consistent with disclosed embodiments.
DESCRIPTION OF THE EMBODIMENTS
• Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings and disclosed herein. Wherever convenient, the same reference numbers will be used throughout the drawings to refer to the same or like parts.
• The disclosed embodiments are generally directed to systems, devices, and methods for providing account status information using a status display. The status display may include a continuous, easy-to-read indication of financial health. For example, the status display may display a color like green, yellow, or red, corresponding to one of a plurality of simple statuses like “normal,” “notification/warning”, and “urgent/alert,” respectively. In some embodiments, the status display may display a simple icon representative of account status such as a check-mark for a normal status or an exclamation point for an alert status. In some embodiments, the status display may display an avatar which changes appearance depending on the account status, such as a happy character for a normal status, a curious character for a warning status, and an upset character for an alert status. The status display may provide a constant reassurance to customers that their finances are in order, and provide multiple levels of simple notifications when their attention is required. By displaying the indication continuously and passively in a household environment, the individual may glance at the status device any time and instantly gain a basic understanding of their current financial situation.
• According to some embodiments, the status display may receive account status information from a server operated by a service provider such as a financial service provider (“FSP”). The FSP may be a bank, credit card company, or other entity associated with financial transactions. The server may store the account information for one or more accounts associated with an individual, and analyze the account information to generate account status information. In some embodiments, the account status information may exclude sensitive data identifying the account or the individual, and merely provide instructions for the status display to display a certain color, icon, status message, or reminder. The absence of sensitive data in the account status information may improve server and status display performance by reducing the amount of data transferred over network and by eliminating the need for strong encryption and decryption methods, thereby reducing power and processing capability requirements for the status device, reducing communication network bandwidth, and reducing security risks.
• In some embodiments, an application (“app”) may compliment the status display. The individual may access the app via a computer or mobile device to receive more detailed information regarding their financial health after observing the simple status indication on the status display. For example, when the status display indicates an alert or warning status, such as a red or yellow light, respectively, the individual may launch the app and login to their account in order to receive more detailed account information or messages associated with the red or yellow light. Using the app as a secondary tool for observing account status, the present embodiments may improve system functionality by transmitting sensitive personal information only when needed to the app, rather than constantly encrypting and transmitting sensitive data to the status display, and decrypting and analyzing the sensitive data on the status display. While reducing the amount of necessary power and processing capabilities, the disclosed embodiments also provide an enhanced user experience through simple continuous reminders of financial health.
• In some embodiments, the status display may be a small, button magnet-sized device having a display such as LED lights or a digital display screen. The status display may communicatively link to a communication network such as WiFi or a cellular network, to communicate with a FSP server. The status display may receive account status information updates initiated by the FSP server as “push” updates at a predetermined time interval and/or when a change in account status is detected, and display an indication corresponding to the account status information. The status display may provide the indication continuously and passively in environment such as a household or office.
• In some embodiments, the individual may access an app installed on a mobile device, or access a web app via a computer web browser, to authenticate the individual and retrieve detailed account information and messages related to the indication displayed on the status display. The app may be a standalone software application for a personal computing device, such as personal computer software or a mobile device app, or part of another software application provided by the FSP for managing finances related to banking, checking credit cards, debit cards, and/or loans.
• FIG. 1 shows a diagram of an exemplary accountstatus display system100 that may be configured to perform one or more software processes that, when executed by one or more processors, retrieve and display account statuses, consistent with disclosed embodiments. The components and arrangements shown inFIG. 1 are not intended to limit the disclosed embodiments, as the components used to implement the disclosed processes and features may vary.
• In accordance with disclosed embodiments, accountinformation display system100 may include astatus display110, one or moremobile device120, a financial service provider (“FSP”)server140, and one or morethird party servers160.Mobile device120, FSPserver140, andthird party server160 may communicate throughnetwork150, andstatus display110 may communicate throughlocal network152, such as a home WiFi network.
• Status display110 may be a small standalone device placed inuser130's home, office, or other preferred location. In some embodiments,status display110 may be a refrigerator magnet with one or more colored lights or a graphic display. In some embodiments,status display110 may be a module integrated within a household item such as a mirror, clock, doorknob, light fixture, thermostat, television, or any other item placed in a central location in a house or office, to informuser130 of their account status.
• User130 may be a customer of the financial service provider, such as an individual who holds a credit card, debit card, checking, and/or savings account with a financial service provider bank.User130 may operatestatus display110 and/ormobile device120 or another computer (not shown) to set upstatus display110.
• Mobile device120 may be a personal computing device such as, for example, a general purpose or notebook computer, a mobile device with computing ability, a tablet, smartphone, wearable device such as Google Glass™ or smart watches, or any combination of these computers and/or affiliated components. In one embodiment,mobile device120 may be a computer system or mobile computer device that is operated bycustomer130 who is a customer of the FSP.
• Mobile device120 may be connected toFSP server140 and/orthird party server160 directly or vianetwork150. Other components known to one of ordinary skill in the art may be included insystem100 to gather, process, transmit, receive, and provide account information consistent with the disclosed embodiments.
• FSP server140 may be operated by a FSP such as a bank, credit card company, merchant, lender, and the like, offering financial services to customers.FSP server140 may be a computer-based system including computer system components, desktop computers, workstations, tablets, hand held computing devices, memory devices, and/or internal network(s) connecting the components.
• Network150 may comprise any type of computer networking arrangement used to exchange data. For example,network150 may be the Internet, a private data network, virtual private network using a public network, and/or other suitable connection(s) that enablessystem100 to send and receive information between the components ofsystem100.Network150 may also include a public switched telephone network (“PSTN”) and/or a wireless network.
• Local network152 may comprise any type of computer networking arrangement used to exchange data in a localized area, such as WiFi, Bluetooth™, Ethernet, and other suitable short-range connections that enablestatus display110 to send and receive information between the components ofsystem100. In some embodiments,local network152 may be excluded, andstatus display110 may communicate withsystem100 components vianetwork150. In some embodiments,status display110 may communicate with one ormore system100 components via a direct wired or wireless connection.
• Third party server160 may be operated by an entity whereuser130 holds a non-FSP account, such as a financial institution other than the FSPoperating FSP server140. In some embodiments, third party server may be operated by a credit reporting agency.Status device110,mobile device120 and/orFSP server140 may receive information aboutuser130's financial situation fromthird party server160 such as, for example, information about another account belonging touser130, a credit report, a credit score, or other financial information associated withuser130.Third party server160 may include a computer system for handling tasks and data processing related to the operation of the third party (not shown in figure).
• FIG. 2 shows a diagram ofstatus display110, consistent with disclosed embodiments. As shown,status display110 may include adisplay210, one ormore processors220, input/output (“I/O”)devices230, atransceiver240,memory250, one ormore sensors260, and abattery270 with charging circuitry (not shown in figure).
• Display210 may include one or more devices for displaying account information such as, for example, one or more indicator lights, progress bars, numeric light emitting diodes (LEDs), and/or one or more screens such as a liquid crystal display (LCD). In some embodiments,display210 may comprise a simple multicolored indicator light or set of lights, indicating an account status using one of a plurality of colors and/or an illumination pattern. In other embodiments,display210 may comprise a strip of indicator lights forming a progress/status bar to display progress toward a spending goal or debt limit. The indicator light strip may contain lights of various colors, or the entire strip may change colors, indicative of an account status or a threshold being crossed. In some embodiments,display210 may comprise an LCD (or other type of pixelated screen) to display a graphic or a short message including one or more lines of text, numbers, and symbols to provide account status.
• Processor220 may be one or more known processing devices, such as a microprocessor from the Pentium™ family manufactured by Intel™ or the Turion™ family manufactured by AMD™.Processor220 may constitute a single core or multiple core processors that executes parallel processes simultaneously. For example,processor220 may be a single core processor configured with virtual processing technologies. In certain embodiments,processor220 may use logical processors to simultaneously execute and control multiple processes.Processor220 may implement virtual machine technologies, or other known technologies to provide the ability to execute, control, run, manipulate, store, etc. multiple software processes, applications, programs, etc. In another embodiment,processor220 may include a multiple-core processor arrangement (e.g., dual, quad core, etc.) configured to provide parallel processing functionalities to allowstatus display110 to execute multiple processes simultaneously. One of ordinary skill in the art would understand that other types of processor arrangements could be implemented that provide for the capabilities disclosed herein.
• I/O devices230 may include one or more devices that allowstatus display110 to receive input fromuser130. I/O devices230 may include, for example, one or more buttons, switches, or a touchscreen panel. I/O devices230 may be manipulated byuser130 to activate/deactivatestatus display110, or to “silence” the account status indication, such as by turning offdisplay210 for a predetermined amount of time after manipulating I/O devices230.
• Transceiver240 may include one or more communication modules for establishing bidirectional wireless communication betweenstatus display110 andlocal network152. For example,transceiver240 may include circuitry and one or more antennas for communicating wirelessly withlocal network152 using a short range/near-field wireless communication protocol such as Bluetooth™, Bluetooth™ LE, WiFi, Zigbee, and Z-Wave.Transceiver240 may be configured to receive account information and settings, and to transmit data requests or requests to join a communication network during setup. In some embodiments,transceiver240 may establish communication withmobile device120,FSP server140, and/orthird party server160, either via a direct communication link, or vianetwork150, to receive account status information directly without the need fornetwork150. In such embodiments,transceiver240 may communicate using long range communication capabilities such as a cellular antenna.
• Memory250 may be a volatile or non-volatile, magnetic, semiconductor, tape, optical, removable, non-removable, or other type of storage device or tangible (i.e., non-transitory) computer-readable medium that stores account information, settings, and one or more programs for performing functions consistent with the methods disclosed herein. For example,memory250 may store one or more programs that, when executed, perform functions such as monitoring sensor data fromsensors260, sending network setup requests, receiving account status information updates (e.g., push updates), processing account status information, storing account status information, determining one or more indications associated with the account status information, and/or displaying the determined indication(s).
• In some embodiments,status display110 may contain one ormore sensors260 for collecting environmental, movement, and/or security data.Sensors260 may include, for example, ambient light sensors, motion detectors, and microphones.Processor220 may use data collected bysensors260 to control or modifystatus display110 functions. For example, in some embodiments, biometric data such as fingerprint scans may be used to authenticateuser130 and activatestatus display110. In some embodiments, ambient light, movement, and/or sound data may be monitored to activate and/or deactivatestatus display110. For example,processor220 may activatestatus display110 when the presence of a person is detected proximate tostatus display110, based on received movement and/or sound data.Processor220 may placestatus display110 into a “sleep” or standby mode when movement and/or sound is undetected for a predetermined period of time.
• In some embodiments,processor220 may automatically adjust the intensity of light emitted fromdisplay210 based on ambient light data sent fromsensors260. For example, ifsensor260 collects ambient light data indicating a dim or dark room,processor220 may reduce the brightness ofdisplay210 to conservebattery270 power and to provide a softer indication. In contrast,processor220 may increase the brightness ofdisplay210 whensensor260 detects a high amount of ambient light, to ensure thatuser130 is able to easily see the color and illumination pattern being displayed. By usingsensors260 to automate certain functions,status display110 may provide a more enjoyable and user-friendly experience.
• Battery270 may include a disposable or rechargeable battery suitable for powering the components ofstatus display110 for an extended period of time, to reduce the need to replace or recharge batteries often during substantially continuous operation. In some embodiments,battery270 may be replaced with a hard-wired power source, such as a power cord, to remove the need to replace or recharge batteries.
• FIG. 3 shows a diagram of an exemplarymobile device120, consistent with disclosed embodiments. As shown,mobile device120 may includedisplay310, I/O devices320,processor330,memory340 having stored thereondata360 and one ormore programs350, such asFSP app352, and further includingantenna370.
• Display310 may include one or more devices for displaying information, including but not limited to, liquid crystal displays (LCD), light emitting diode (LED) screens, organic light emitting diode (OLED) screens, and other known display devices.
• I/O devices320 may include one or more devices that allowmobile device120 to send and receive information. I/O devices320 may include, for example, a keyboard, buttons, switches, and/or a touchscreen panel. I/O devices320 may also include one or more communication modules (not shown) for sending and receiving information viaantenna370 from other components insystem100 by, for example, establishing wired or wireless connectivity betweenmobile device120 tonetwork150, by establishing direct wired or wireless connections betweenmobile device120 andFSP server140, or betweenmobile device120 andthird party server160. Direct connections may include, for example, Bluetooth™, Bluetooth LE™, WiFi, near field communications (NFC), or other known communication methods which provide a medium for transmitting data between separate devices.
• Processor(s)330 may be one or more known computing devices, such as those described with respect toprocessor220 inFIG. 2.
• Memory340 may be a volatile or non-volatile, magnetic, semiconductor, tape, optical, removable, non-removable, or other type of storage device or tangible (i.e., non-transitory) computer-readable medium that stores one or more program(s)350, such asFSP app352, anddata360.Data360 may include, for example,user130's personal information, account information, and display settings and preferences.
• Program(s)350 may include operating systems (not shown) that perform known operating system functions when executed by one or more processors. By way of example, the operating systems may include Microsoft Windows™, Unix™, Linux™, Apple™ operating systems, Personal Digital Assistant (PDA) type operating systems, such as Microsoft CE™, or other types of operating systems. Accordingly, disclosed embodiments may operate and function with computer systems running any type of operating system.Mobile device120 may also include communication software that, when executed by a processor, provides communications withnetwork150, such as Web browser software, tablet, or smart hand held device networking software, etc.Mobile device120 may be a device that executes mobile applications for performing operations consistent with disclosed embodiments, such as a tablet or mobile device.
• Program(s)350 may also include FSP app(s)352, such as an account information app, which when executed causesmobile device120 to perform processes related to providing account status information. For example, FSP app(s)352 may configuremobile device120 to perform operations including: activating and setting up anew status display110, receiving account information push updates fromFSP server140, sending account information requests toFSP server140, receiving account information updates fromFSP server140, processing received account information, and providing detailed account status information touser130 viadisplay310. In some embodiments,mobile device120 may receive encrypted account information fromFSP server140, and decrypt the account information before displaying ondisplay310.
• FIG. 4 shows a diagram of anexemplary FSP server140, consistent with disclosed embodiments. As shown,FSP server140 may include one ormore processor420, input/output (“I/O”)devices430,memory440 storingdata460 and programs450 (including, for example, server app(s)452 and operating system454), and adatabase470.FSP server140 may be a single server or may be configured as a distributed computer system including multiple servers or computers that interoperate to perform one or more of the processes and functionalities associated with the disclosed embodiments.
• Processor420 may be one or more known processing devices, such as a microprocessor from the Pentium™ family manufactured by Intel™ or the Turion™ family manufactured by AMD™.Processor420 may constitute a single core or multiple core processors that executes parallel processes simultaneously. For example,processor420 may be a single core processor configured with virtual processing technologies. In certain embodiments,processor420 may use logical processors to simultaneously execute and control multiple processes.Processor420 may implement virtual machine technologies, or other known technologies to provide the ability to execute, control, run, manipulate, store, etc. multiple software processes, applications, programs, etc. In another embodiment,processor420 may include a multiple-core processor arrangement (e.g., dual, quad core, etc.) configured to provide parallel processing functionalities to allowFSP server140 to execute multiple processes simultaneously. One of ordinary skill in the art would understand that other types of processor arrangements could be implemented that provide for the capabilities disclosed herein.
• FSP server140 may also include one or more I/O devices430 that may comprise one or more interfaces for receiving signals or input from devices and providing signals or output to one or more devices that allow data to be received and/or transmitted byFSP server140. For example,FSP server140 may include interface components, which may provide interfaces to one or more input devices, such as one or more keyboards, mouse devices, and the like, that enableFSP server140 to receive input from an employee of the financial service provider (not shown).
• FSP server140 may include one or more storage devices configured to store information used by processor420 (or other components) to perform certain functions related to the disclosed embodiments. In one example,FSP server140 may includememory440 that includes instructions to enableprocessor420 to execute one or more applications, such as server applications, an electronic transaction application, an account status application, network communication processes, and any other type of application or software known to be available on computer systems. Alternatively or additionally, the instructions, application programs, etc. may be stored in aninternal database470 or external storage (not shown) in direct communication withFSP server140, such as one or more database or memory accessible overnetwork150.Database470 or other external storage may be a volatile or non-volatile, magnetic, semiconductor, tape, optical, removable, non-removable, or other type of storage device or tangible (i.e., non-transitory) computer-readable medium.
• In one embodiment,FSP server140 may includememory440 that includes instructions that, when executed byprocessor420, perform one or more processes consistent with the functionalities disclosed herein. Methods, systems, and articles of manufacture consistent with disclosed embodiments are not limited to separate programs or computers configured to perform dedicated tasks. For example,FSP server140 may includememory440 that may include one ormore programs450 to perform one or more functions of the disclosed embodiments. Moreover,processor420 may execute one or more programs located remotely from accountinformation display system100. For example,FSP server140 may access one or more remote programs, that, when executed, perform functions related to disclosed embodiments.
• Programs450 stored inmemory440 and executed by processor(s)420 may include one or more server app(s)452 andoperating system454. Server app(s)452 may incorporate one or more financial services apps that cause processor(s)420 to execute one or more processes related to financial services provided to customers including, but not limited to, processing credit and debit card transactions, checking transactions, fund deposits and withdrawals, transferring money between financial accounts, lending loans, processing payments for credit card and loan accounts, and retrieving account information, processing account information to determine an account status, comparing multiple account statuses to determine an account status to display, and generating account status information for the determined status to display.
• Memory440 anddatabase470 may include one or more memory devices that store data and instructions used to perform one or more features of the disclosed embodiments.Memory440 anddatabase470 may also include any combination of one or more databases controlled by memory controller devices (e.g., server(s), etc.) or software, such as document management systems, Microsoft SQL databases, SharePoint databases, Oracle™ databases, Sybase™ databases, or other relational databases.
• FSP server140 may also be communicatively connected to one or more remote memory devices (e.g., remote databases (not shown)) throughnetwork150 or a different network. The remote memory devices may be configured to store information and may be accessed and/or managed byFSP server140. By way of example, the remote memory devices may be document management systems, Microsoft SQL database, SharePoint databases, Oracle™ databases, Sybase™ databases, or other relational databases. Systems and methods consistent with disclosed embodiments, however, are not limited to separate databases or even to the use of a database.
• FIG. 5 shows a flowchart of an exemplary status display setup process500. Process500 is described as performed primarily bymobile device120. In some embodiments, however,mobile device120,FSP server140, and/orstatus display110 may perform one or more disclosed steps. Furthermore, process500 is described as performed foruser130's account withFSP140. In some embodiments, however,status display110 may receive and display account information for an account held with a third party financial service provider, such as a bank that operatesthird party server160, using the methods discussed herein. In some embodiments,FSP server140 may receive account information for a plurality of accounts foruser130, including account information for accounts with the FSP and account information from one or more third party server(s)160, process the received account information to determine statuses for the plurality of accounts, and/or determine one or more statuses to display onstatus display110 based on the determined statuses and one or more rules.
• Disclosed embodiments provide an easy to use interface for displaying a substantially continuous account status without the need for cumbersome authentication and login steps. To associate the correct account status information with thestatus display110,status display110 may be configured during the first use, such as by performing status display set up process500. Setup process500 may begin instep502, wherestatus display110 connects to a network, such aslocal network152.Status display110 may include one or more buttons for activatingtransceiver240 and connecting tolocal network152. In some embodiments,status display110 may pair withmobile device120 via short range communication such as Bluetooth™, andmobile device120 may be used to configurestatus display110 including setting up preferences and connecting tolocal network152. Those of ordinary skill in the art will realize that certain aspects ofstep502 may be performed automatically bystatus display110 and/ormobile device120, and that certain aspects may require manual interaction byuser130. For example, in some embodiments,user130 may be required to place one or more ofstatus display110 ormobile device120 into a “pairing” mode. In some embodiments,status display110 and/ormobile device120 may initiate pairing mode automatically by wireless “handshake.” Furthermore, certain aspects of connectingstatus display110 tolocal network152 may be automated bystatus display110 and/orlocal network152, and certain aspects may require manual interaction byuser130, such as an input of a network passcode.
• Instep504,FSP server140 may receive account login information fromuser130, such as an account name or account number, and authentication information such as a password, personal identification (PIN) number, date of birth, social security number, and/or billing information. In some embodiments,FSP server140 may receive account login information fromuser130 viaFSP app352 onmobile device120. In some embodiments,FSP app352 may already have this information stored foruser130, and may re-request information for verifyinguser130's identity, for the purpose of unlocking one or more accounts for association withstatus display110.
• In step506, FSP server may receive account login information and verifyuser130's identity. Upon receiving the login and authentication information,FSP server140 may compare the information to one or more records stored indatabase470 to determine whetheruser130 is a current FSP customer and/or whetheruser130's identify is verified.
• In some embodiments,FSP app352 may also send collected login and authentication information to athird party server160 operated by another financial service provider, to verifyuser130's identity and allowFSP server140 and/orstatus display110 to receive account information from one or more accounts held by separate financial service providers.Third party server160 may authenticateuser130, and grantFSP server140 access touser130's account information held inthird party server160. Thereafter,FSP server140 may request, access, and/or receive account information for one or more ofuser130's accounts held by an institution other than FSP.
• In step508,FSP server140 may associatestatus device110 withuser130. In some embodiments,FSP server140 may store a network address such as an IP address, or an identification number forstatus display110 with information foruser130. Once associated,FSP server140 may automatically send future account status information to thecorrect status display110 without additional login steps or need forsubsequent user130 authentication.
• In step510,FSP server140 may receive a selection of accounts associated withuser130 to include in status update and display process600 (shown inFIG. 6). In some embodiments,FSP server140 may automatically select all accounts held by FSP and associated withuser130, and in otherembodiments FSP server140 may require manual selection of accounts. In some embodiments, the selection of accounts may include one or more accounts held by one or morethird party servers160.FSP server140 may send requests tothird party servers160 to access account information and/or receive push updates fromthird party servers160.
• In step512, in some embodiments,FSP server140 may receive one or more preferences fromuser130, to configure status display preferences. In some embodiments,FSP server140 may receive one or more preferences from, for example, a settings file stored locally inmemory340 ofmobile device120, inmemory440 ordatabase470 ofFSP server140, or accessed remotely vianetwork150. In some embodiments,mobile device120 may receive preferences via input fromuser130 using I/O devices320. Preferences may include, for example, a ranking of priority of a plurality of selected accounts (if multiple accounts became selected in step510), one or more thresholds or rules to apply to account information such as spending goals, spending limits, account balance thresholds, and other account information to include or exclude from status indication such as payment due dates, fraud alerts, overdraft alerts, or any potential account issues identified byFSP server140 or requested byuser130.FSP server140 may store the received preferences as rules to apply in process600 (described later with respect toFIG. 6).
• In some embodiments,FSP server140 may configurestatus display110 preferences by identifying one or more actions associated with the received preferences. For example,FSP server140 may identify fraud alerts and overdraft alerts as requiring immediate action, and configureFSP server140 to send push updates tostatus display110 immediately upon detecting fraudulent activity or an account overdraft on one or more ofuser130's accounts. In some embodiments,FSP server140 may receive user-defined amounts for spending limits and spending goals, to apply as rules for generating certain status indications. The number and type of preferences may vary depending on the needs ofuser130, the needs of the financial service provider, and/or the functions and capabilities ofFSP server140 andstatus display110.
• In step514,FSP server140 may complete process500 by transmitting the first account status information tostatus display110.FSP server140 may generate and transmit account status information by performing process600, described with respect toFIG. 6.
• FIG. 6 shows a diagram of anexemplary status display110 update and display process600, consistent with disclosed embodiments. In some embodiments, process600 may include analyzing account information for one or more accounts associated withuser130, such as account information identified in step510 of process500, which may be accessed atFSP server140 and/or received fromthird party servers160.
• Process600 begins instep602 whenFSP server140 receives information for the one or more accounts selected in process500. In some embodiments,FSP server140 may access account information stored inmemory440 ordatabase470, or access account information from a remote location.FSP server140 may also request and receive information for one or more accounts fromthird party servers160, or receive one or more push updates fromthird party servers160. Account information may include any data relevant to a status of an account including, for example, an account balance, remaining balance/credit, individual transaction amounts, payment due dates, overdraft notifications, and/or fraud notifications.FSP server140 may receive account information at predetermined intervals, such as every 15 minutes, every hour, every day, etc. At each interval,FSP server140 may generate a request for updated account information. In some embodiments,FSP server140 may receive push updates from a database or server having stored thereon updated account information. In some embodiments,FSP server140 may receive push updates outside of the normal intervals in urgent situations, such as when fraudulent activity is detected.
• Instep604,FSP server140processor420 may analyze the received account information. Analysis may include applying predefined rules, as well as preferences configured in step510, to the account information for each selected account, and determining a status for each account. In some embodiments,step604 may includesubsteps606,608, and/or610. Notably,processor420 may determine multiple statuses for each account, depending on the number of thresholds, rules, and types of information analyzed for each account, which collectively or individually may be referred to as “status indicators.”
• Insubstep606,processor420 may apply one or more thresholds to account information for each selected account. Thresholds may include predefined thresholds such as, for example, a credit limit for the account set by the FSP. Thresholds may also include one or more user-defined thresholds configured in step510 such as, for example, a personal spending limit, spending goal, or minimum desired account balance.
• Insubstep608,processor420 may check any due dates or deadlines noted in received account information. In some embodiments,processor420 may determine that a payment is due on an upcoming date, or that a promotional offer will expire on an upcoming date.
• Insubstep610,processor420 may check alert notifications in the received account information. For example, in some embodiments,processor420 may determine whether any fraud activity alerts are included in account information, as well as notifications from FSP regarding account information, account activity, warnings, or other informationalnotices warranting user130's attention.
• Based on the results fromsubsteps606,608, and610,FSP server140 may compile one or more statuses for each account (not shown in figures). Each status may have an assigned priority level or importance level determined, for example, based on predefined rules employed byFSP server140. For example, a status indicative of alert may have a high priority level and meritimmediate user130 attention, whereas a payment due in 10 days may have a low-mid priority level.FSP server140 may correlate different statuses to numeric priority levels, to rank/prioritize the statuses for each account (not shown in figures).
• In step612,FSP server140 may identify an account status to display onstatus display110. In some embodiments,FSP server140 may identify the status determined most urgent and/or time sensitive with respect to receiving attention fromuser130. For example, the identified status may be the status having the highest rank/priority level based on importance and urgency.
• In some embodiments,status display110 may include asimple display210, such as a single indicator light, and therefore may display only a single status at a time. In such embodiments,FSP server140 may determine the highest priority status among all statuses for all accounts, to display the “worst case scenario” of all accounts. For example, if five accounts are linked tostatus display110,FSP server140 may determine which status of the five accounts requires the most attention. For instance, if four of the five accounts have no alerts or notifications, and are considered to be “normal,” and the fifth account has a single notification pending,FSP server140 may identify the “notification” status as the selected status for displaying onstatus display110. In another instance, if three of the five accounts have “notification” statuses, one account has a “normal” status, and the fifth account has an “alert” status, thenFSP server140 may select the “alert” status for displaying on status display, as the “alert” status is most urgent and requires more immediate attention. As discussed in more detail later,FSP app352 onmobile device120 may provideuser130 with all account statuses and detailed information upon logging in. For example,user130 may notice the “alert” status indicated onstatus display110 andaccess FSP app352 onmobile device120 for the additional details.
• In other embodiments,status display110 may includemultiple displays210, enabling the display of multiple statuses simultaneously. Depending on the capabilities ofstatus display110,FSP server140 may identify one or more statuses for generating account status information. In embodiments wherestatus display110 is capable of indicating multiple account statuses,FSP server140 may select a quantity of the highest-ranked/prioritized statuses equal to the number of statuses thatstatus display110 can simultaneously provide.
• FSP server140 may also generate account status information for the identified account status (step not shown) for instructingstatus device110 regarding what indication to display. In some embodiments,FSP server140 may generate a simple alphanumeric code based on the identified account status and/or the status urgency or priority. By generating the account status information atFSP server140,status display110 does not need to receive detailed account information and analyze the information. Therefore, the present embodiments reduce the amount of processing power instatus display110, thereby also reducing power requirements.
• Instep614,FSP server140 may transmit the generated account status information tostatus display110 vianetwork150 andlocal network152.
• Instep616,FSP server140 may determine whether the next time interval is reached, and if not (“no” in step616), then instep616 loops until the next interval is reached. If the next time interval is reached (“yes” in step616), then process600 returns to step602, to receive updated account information, and repeat steps604-614 with the updated account information. In some embodiments, if a push update is received with account information corresponding to an urgent status, process600 may return to step602 before a next interval is reached, and repeat steps604-614 with the push update account information.
• Referring tostatus display110 inFIG. 6, in step618status display110 may receive updated account status information fromFSP server140, vialocal network152. In some embodiments,status display110 may communicate directly withFSP server140 and/orthird party server160 to receive account status information.
• Instep620,status display110 may store received account status information inmemory250. In some embodiments,processor220 may overwrite old data stored inmemory250 when updated account status information is received andmemory250 is full.
• Instep622,processor220 may determine an indication corresponding to the account status information.Memory250 may store instructions for a plurality of indications including instructions for illuminating different colored lights, instructions for displaying graphics, instructions for generating one or more sounds, and/or instructions for interfacing with one or more external devices via application programming interfaces (APIs, discussed in further detail later).Memory250 may also store a plurality of relationships associating the stored indications with different types of account status information. For example,memory250 may store associations between the alphanumeric codes received in the account status information to one or more stored indications. The stored relationships and indications may be preprogrammed and/or generated based on data identified in step510 of process500.
• Processor220 may determine, based on the stored relationships, which indication should be displayed for the received account status information. For example, if the account status information includes a “normal” account status for all accounts, a first stored relationship may associate a “normal” status with a steady green light indication. As another example, if the account status information includes an “alert” status for at least one account, a second stored relationship may associate an “alert” status with a red flashing light indication and/or an audible tone. As yet another example, if the account status information includes an intermediate status between “normal” and “alert,” such as a status indicating that a payment is coming due, a third stored relationship may associate the intermediate status with a pulsating yellow light indication. In some embodiments,FSP server140 may select a single status to include in the account status information, relievingstatus display110 of the task of selecting one from a plurality of statuses to display.
• In some embodiments, associated indications may include graphics, such as a check mark representing a “normal” status and an exclamation point representing an “alert” or “urgent” status. In other embodiments, associated indications may include one or more avatars, andmemory250 may store instructions for generating different expressions on the avatar corresponding to “normal,” “notification/warning,” and “alert/urgent” statuses.
• In some embodiments,memory250 may also store instructions for causingdisplay210 to produce different illumination patterns such as a steady illumination, a rapid flashing pattern, a variable flashing pattern such as a “staccato” pattern, and a gently pulsing pattern.Processor220 may select an illumination pattern corresponding to the urgency of the status. In some embodiments,processor220 may select a steady or gently pulsing pattern to use with a green light to indicate a “normal” status, select a gently pulsing or staccato pattern to use with a yellow light for a warning/notification status, and select a rapid flashing to use with a red light to indicate an “alert” or “urgent” status. Relationships between illumination patterns and urgency may be preprogrammed and stored inmemory250, and/or may be configured byuser130 during process500.
• Instep624,processor220 may activatedisplay210 to display the determined indication. In some embodiments,display210 may remain constantly activated, providing a constant ambient light or graphic indication thatuser130 may observe simply by glancing atstatus display110. In other embodiments,processor220 may receive data from one ormore sensors260, and automatically activatedisplay210 when a predetermined condition is satisfied, such as when movement or sound is detected proximate tostatus display110. In other embodiments,processor220 may activatedisplay210 upon receiving input fromuser130 via I/O devices230, such as whenuser130 presses a button onstatus display110.
• After activation,display210 may display the determined indication instep626. In embodiments that are not continuously active,step626 may last for a predetermined amount of time, after whichprocessor220 deactivatesdisplay210 until another activation is detected (steps not shown). In other embodiments,processor220 may deactivatedisplay210 based on input received fromuser130 via I/O devices230.
• In some embodiments, I/O devices230 may include a button for temporarily disablingdisplay210, in order to suppress or “snooze” the displayed indication for a predetermined period of time. Some embodiments ofstatus display110 may include a speaker to provide an audible indication in addition to or instead ofdisplay210, and I/O devices230 may include a button to temporarily mute the audible indication.
• In step628,processor220 may determine whether new account status information is received fromFSP server140, such as updated account status information for the next time interval, or a push update with an urgent/alert status. If new account status information is received (“yes” in step628), then process600 may return to step620, to store the new account status information and repeat steps622-626. If new account status information is not received (“no” in step628), then step628 may continue looping until new account status information is received.
• In some embodiments,FSP app352 onmobile device120 may provide additional account status information touser130. For example, upon noticing a yellow (e.g. “warning/notification”) or red (e.g. “alert/urgent”) indication,user130 may wish to know the reasons causing the warning or alert.User130 may launchFSP app352 onmobile device120, andmobile device120 may receive credentials (via, e.g., I/O320) to use in verifyinguser130's identity (steps not shown). AfterFSP app352 and/orFSP server140 verifiesuser130's identity,FSP app352 may provideuser130 with the same indication displayed onstatus display110 along with detailed information explaining what caused the status indication. For example,FSP app352 may display a flashing red light that matches the flashing red light onstatus display110, informuser130 about fraudulent activity detected in their account, and furtherprompt user130 to contact the FSP. In some embodiments wherestatus display110 is linked to multiple accounts,FSP app352 may display individual indicators and detailed status information for each account. By providing a simple and constant status indication onstatus display110,user130 remains informed of their general financial status without expending significant power or processing power, and without creating security risks associated with transmitting sensitive information. Furthermore, by providing detailed account status information upon request inFSP app352,user130 can retrieve detailed sensitive account information once they know their attention is needed.
• As discussed earlier, in some embodiments,status display110 is a small standalone device such as a magnetic button removably affixed to a home appliance such as a refrigerator.FIG. 7A shows an illustration ofstatus display110 formed as abutton magnet700 and affixed to a refrigerator.Button magnet700 may include a single indicator light as shown, or may include a plurality of lights or a graphic display for providing an indication of account status.
• In some embodiments,status display110 may be a module built into the housing of another household or office item, such as an alarm clock or a mirror.FIG. 7B shows an illustration ofstatus display110 formed as a module built into an alarm clock. As shown inFIG. 7B, the components ofstatus display110 are integrated within the housing of the alarm clock, with a display such as indicator light710 located in the clock face.
• FIG. 7C shows an illustration ofstatus display110 formed as a module built into a mirror. As shown inFIG. 7C, the components ofstatus display110 are integrated within the housing of the mirror, with a display such as indicator light720 located in the mirror glass.
• FIGS. 7A-7C are not meant to limit embodiments of the present disclosure in any way, and those of ordinary skill in the art will realize thatstatus display110 may be built into other types of devices such as, for example, a light fixture, a television, stereo system, etc. In some embodiments,status display110 may be configured to interact with other electronic devices and appliances in the home using APIs, such as a programmable home lighting system or programmable thermostat. For example,status display110 may instruct a home lighting system to illuminate one or more lights in a certain color and/or in a certain pattern based on account status information, similar to the functionality ofdisplay210 onstatus display110. In some embodiments,status display110 may be configured to control one or more appliances, such as by turning off a programmable thermostat when account status information indicates an overdraft or insufficient funds inuser130's account, to reduce costly heating and cooling bills. Various functionalities may be achieved using application program interfaces (APIs) betweenstatus display110 and communicating household appliances, and the functions may be preprogrammed or setup and configured byuser130 during process500.
• The foregoing description has been presented for purposes of illustration. It is not exhaustive and is not limited to the precise forms or embodiments disclosed. Modifications and adaptations of the embodiments will be apparent from consideration of the specification and practice of the disclosed embodiments. For example, the described implementations include hardware, firmware, and software, but systems and methods consistent with the present disclosure can be implemented as hardware alone.
• Computer programs based on the written description and methods of this specification are within the skill of a software developer. The various programs or program modules can be created using a variety of programming techniques. For example, program sections or program modules can be designed in or by means of Java, C, C++, assembly language, or any such programming languages. One or more of such software sections or modules can be integrated into a computer system, non-transitory computer-readable media, or existing communications software.
• Moreover, while illustrative embodiments have been described herein, the scope includes any and all embodiments having equivalent elements, modifications, omissions, combinations (e.g., of aspects across various embodiments), adaptations or alterations based on the present disclosure. The elements in the claims are to be interpreted broadly based on the language employed in the claims and not limited to examples described in the present specification or during the prosecution of the application, which examples are to be construed as non-exclusive. Further, the steps of the disclosed methods can be modified in any manner, including by reordering steps or inserting or deleting steps. It is intended, therefore, that the specification and examples be considered as exemplary only, with a true scope and spirit being indicated by the following claims and their full scope of equivalents.

Claims (21)

1. A display device for providing an account status, comprising:

a processor;

a display;

a transceiver; and

a memory having stored thereon instructions that, when executed by the processor, configure the processor to:

establish a connection with a service provider over a communication network via the transceiver to access account status information from the service provider for a first account associated with a user;

receive a Push update from the service provider via the connection, the Push update comprising a change in the account status information;

determine a visual indication associated with the received change in account status information; and

output, via the display, the determined visual indication.

2. The display device ofclaim 1, wherein the received account status information excludes sensitive information identifying the user or the first account.

3. The display device ofclaim 1, wherein the display comprises a multicolored light, and the determined visual indication comprises an illuminated color.

4. The display device ofclaim 1, wherein the display comprises a display screen, and the determined visual indication comprises an image.

5. (canceled)

6. The device ofclaim 1, further comprising at least one sensor, wherein the processor is configured to collect data from the at least one sensor and modify the determined visual indication outputted via the display based on the collected data.

7. The device ofclaim 6, wherein the at least one sensor includes a microphone.

8. The device ofclaim 6, wherein the at least one sensor includes an ambient light sensor.

9. A system for providing an account status, comprising:

a transceiver;

a memory; and

a processor coupled to the transceiver and configured to execute instructions stored in the memory to:

receive information for a first account associated with a user;

determine a status for the first account;

generate a status indicator based on the determined status, the status indicator comprising a visual representation of the status for the first account that excludes sensitive information that identifies the user or the first account; and

transmit, by the transceiver, the status indicator to a display device.

10. The system ofclaim 9, wherein the processor determines a status for the first account by at least one of comparing the received information to one or more thresholds or determining whether the received information contains any messages or alerts.

11. The system ofclaim 9, wherein the processor is further configured to receive information for a second account associated with the user.

12. The system ofclaim 11, wherein the account status information includes a single status for the first account and the second account, the single status representing the more urgent status of the first account or the second account.

13. The system ofclaim 9, further comprising at least one sensor, wherein the processor is configured to collect data from the at least one sensor and modify the status indicator outputted via the display.

14. The system ofclaim 13, wherein the at least one sensor includes a microphone.

15. The system ofclaim 13, wherein the at least one sensor includes an ambient light sensor.

16. A computer-implemented method of providing an account status, the method comprising:

accessing information from a database for a first account associated with a user;

determining an account status for the first account based on the received information;

generating, by the processor, a status indicator based on the determined account status, the status indicator excluding sensitive information that identifies the user or the first account; and

transmitting, by a transceiver, the status indicator to a display device.

17. The method ofclaim 16, wherein determining the account status comprises at least one of comparing the received information to one or more thresholds or determining whether the information contains any messages or alerts.

18. The method ofclaim 16, further comprising receiving information for a second account associated with the user.

19. The method ofclaim 18, wherein the status indicator includes a single status for the first account and the second account, the single status representing the more urgent status of the first account or the second account.

20. The method ofclaim 16, further comprising:

collecting data from at least one sensor; and

modifying the status indicator transmitted to the display device,

wherein the at least one sensor includes at least one of a microphone or an ambient light sensor.

21. The display device ofclaim 1, further comprising:

receive a second push update from the service provider via the connection, the second push update comprising a change in account status information of a second account associated with the user;

determine an urgency of the received change in the account status information of the first account and the second account;

determine a visual indication associated with the more urgent received change in account status information; and

output, via the display, the determined visual indication associated with the more urgent received change in account status information.

Images