Patent Grant
11935019
The disclosed embodiments relate to systems and methods for providing financial services, more particularly, providing customers the options to manage their financial accounts when their account balance is low, and additionally, to an application that provides comprehensive transactional services for customers managing their financial accounts in a low cash mode.
Financial service providers are rapidly expanding the use of mobile services and mobile applications. Currently, most financial service providers provide mobile banking services which allow customers to perform basic functions and transactions remotely, for example, by using an application on a mobile device such as a cell phone or a tablet having an online web interface. Mobile banking allows customers to manage their money without visiting a physical brick and mortar branch bank location. Customers may check account balances, pay bills, transfer funds, send money to others, deposit checks, receive customer support, apply for loans, receive alerts, apply for credit cards, manage benefits, manage credit/debit cards, review transactions, open new accounts, and perform many other banking services on a mobile application on a mobile device without travelling to a physical location. The financial services providers provide these functions to customers electronically via an application without the need for in-person teller services.
While these banking functions are useful for enabling funds to be electronically transferred without the need for paper checks or teller support, they are limited to certain transactions. Moreover, these exemplary banking functions are further limited when a user or customer's account balance is low or falls beneath a predetermined threshold dollar value (e.g. $25). As a result, what is needed is an online banking application that provides customers the ability to manage their financial accounts and perform banking operations when their account balance is low. In particular, what is needed is a mobile banking application that provides options for a user operating in a low cash mode, provides alerts to customers when they enter low cash mode, and prevents overdraft once a low cash mode is reached. Additionally, what is needed are preventive options, such as providing personal loans, transferring funds, facilitating automatic and manual transfers, cancelling transactions including cancellation of pending Automated Clearing House (“ACH”) (or pending checks that will generate the overdraft(s)), and accelerating pending ACH/payroll deposits.
Furthermore, what is needed is a mobile application that provides tiered overdraft fees based on the extent to which an account is negative, incorporates synthetic data and machine learning into an ACH and analytics, provides mobile network transfers (for added data protection), incorporates machine learning algorithms for learning customer transaction tendencies, provides fraud protection features in a mobile application specifically relating to the issues of a low cash mode and/or overdraft scenario, and integrates a low cash mode into a separate virtual wallet application. What is needed is a link between a customer's virtual wallet and a customer's social media (such as, a Facebook account), providing a notification channel to customers in order to provide an alert that a purchase will overdraft an account before a purchase is made while a customer's account is in low cash mode. What is needed is an overall increase in efficiency in providing financial services through automation, including, for example, through automated balance confirmation.
Moreover, what is needed is a mobile application that provides an automatic card lock feature that activates automatically when an account enters low cash mode with an option that allows a user to turn off within the application. What is further needed is an automatic card lock feature that activates automatically when an account enters a low cash mode based on a predicted balance (e.g., a payment or direct deposit scheduled for tomorrow) as well as based on a customer's current balance. What is needed is the ability for a customer to select and switch between overdraft protection features (e.g., pay, cancel, protection through loans or transfers and accelerated ACH/payroll deposits) on a mobile application without the need for bank intervention. What is needed is a mobile application that provides customers the option to pay some, but not all, transactions that would overdraft an account (such an application would also facilitate the customer's ability to prioritize transactions and potentially delay the payment of some transactions and would differentiate point of sale transactions from ACH transactions, checks, and scheduled payments).
Additionally, what is needed is a mobile application that enables a customer to approve or deny spending for an entire day while an account is in low cash mode or while a card lock feature is activated, a mobile application that provides an alert notifying a customer of the ability to approve or deny spending for a day, and that provides an alert for a customer to configure how an account can spend for the day. Further, what is needed is a mobile application that provides a debit card smart lock feature, with a threshold that may be different from a low cash mode threshold and that can be disabled in a mobile application, that automatically prevents a customer from using the locked card when a customer's balance falls below a set threshold value, and allows a customer to manually or automatically draw funds from a second account when a first account has insufficient funds.
Furthermore, what is needed is a feature that allows a user to block certain mobile application functionality from a web application when a customer's phone is lost or stolen. Further, what is needed is a mobile application that displays the amount of (specified) time a customer has to cure an overdraft (such as a grace period), which may help customers who otherwise don't handle money or time well to remember to cure an overdraft, that notifies a customer at predetermined times during an overdraft grace period using push notifications to a user's phone or messages to the user, which may also help customers remember to cure an overdraft, and that personalizes a grace period based on customer characteristics.
What is needed are personalizing characteristics that may include offering a customer more or less time for larger or smaller overdraft amounts, offering a customer a longer grace period if their balance is ordinarily high, offering a customer a longer grace period if a customer is in good standing with a bank, as indicated, for example, by more debit card use, higher average balance, or higher direct deposits. Personalizing characteristics that are needed may also include extending a grace period if a customer makes a payment for less than an overdraft fee, offering a customer a fixed amount of overdraft time per month that may be spread over the month, or offering a customer a longer or shorter grace period over time. If, for example, a customer overdrafts once with a grace period of 48 hours, the next overdraft may have a grace period of 24 hours. If, for example, a customer does not overdraft for several months, a customer may earn additional grace period time. Personalizing characteristics that are needed may further include carrying a customer's extra grace period time over from month to month, with a cap on the total overdraft time available, giving customers a bucket of accrued grace period time that they can add to their current grace period to cash out the accrued time, offering a customer a grace period as a reward/relationship benefit as a part of a package, and/or selling a customer additional grace period time by which to cure a negative balance.
Furthermore, what is needed is a mobile application that allows a customer to dynamically set reminders to make a scheduled payment later or to set a reminder to make the payment later, that updates other applications, focusing on the ability to automatically reschedule payments on behalf/invocation of a virtual wallet calendar, that charges a customer a negative balance fee instead of a transactional/per item fee for insufficient funds, that recommends cancelling particular scheduled payments but proceeding with others in a way that minimizes/prevents overdraft or prevents other fees, and that prevents a given customer's balance to drop below a given tolerance value by allowing a customer to choose certain scheduled payments to process and rendering the remaining payments no longer actionable.
Moreover, what is needed is a mobile application that provides a predictive cash flow feature, which uses machine learning to predict a customer's expenses and alerts a customer to potential periods during which a customer will have a low or negative balance, and a predictive cash mode feature that allows a customer to manually add payments flagged by a predictive cash mode to help prevent a low or negative balance. What is also needed is a mobile application that links a customer's account to social media to facilitate communication with a customer by, for example, sending a message to a customer through Facebook Messenger, that uses geolocation technology to alert a customer who is entering a store that the customer's account is in low cash mode, that provides a feature to include spouses or joint users, so that a joint user on a customer's account is also notified when another joint user arrives at a geographic location, such as a store while the associated account is in low cash mode, that turns on this feature at a predicted danger day or at particular high-risk stores for the customers, and that obtains the customer's consent for the use of this feature.
Finally, what is needed is a mobile application that allows a user to designate particular transactions or locations to process even while in a low cash mode (for example, a customer may want the ability to buy groceries, even while in low cash mode), and that provides a user-friendly graphical user interface of a low cash mode feature.
One aspect of the present disclosure is directed to a system for managing a financial account in a low cash mode. The system may include at least one processor; and at least one memory configured to execute the instructions to perform operations. The operations may include providing an interface accessible via a user device registered with a first account; providing, via the interface, a notification to a user when a balance in the first account is less than a threshold value; presenting, when the first account balance is less than a threshold value, an option for a transfer request; receiving, via the interface, a selection of the option for the transfer request to connect the first account with a second account; transferring cash, based on the request, from the second account to the first account; notifying, via the interface, the user that cash has been transferred from the second account to the first account; and further notifying, via the interface, the user that the balance in the first account is greater than the threshold value.
Another aspect of the present disclosure is directed to a method for managing a financial account in a low cash mode. The method may perform operations including providing an interface accessible via a user device registered with a first account; providing, via the interface, a notification to a user when a balance in the first account is less than a threshold value; presenting, when the first account balance is less than a threshold value, an option for a transfer request; receiving, via the interface, a selection of the option for the transfer request to connect the first account with a second account; transferring cash, based on the request, from the second account to the first account; notifying, via the interface, the user that cash has been transferred from the second account to the first account; and further notifying, via the interface, the user that the balance in the first account is greater than the threshold value.
Yet another aspect of the present disclosure is directed to a non-transitory computer-readable medium. The non-transitory computer readable medium may perform a method for managing a financial account in a low cash mode. The method may perform operations including providing an interface accessible via a user device registered with a first account; providing, via the interface, a notification to a user when a balance in the first account is less than a threshold value; presenting, when the first account balance is less than a threshold value, an option for a transfer request; receiving, via the interface, a selection of the option for the transfer request to connect the first account with a second account; transferring cash, based on the request, from the second account to the first account; notifying, via the interface, the user that cash has been transferred from the second account to the first account; and further notifying, via the interface, the user that the balance in the first account is greater than the threshold value.
Aspects of the present disclosure may include systems, methods, and computer readable media for providing notifications to a customer, the operations comprising associating the customer with an account, associating the account with a mobile device, determining an account balance of the account, and determining, based on the account balance, whether the account is deemed to be in a low cash mode state. The operations may further comprise providing, via the mobile device, a notification to the customer when the account enters the low-cash mode state and providing, via the mobile device, a notification to the customer when the account enters the low-cash mode state.
Aspects of the present disclosure may additionally include systems, methods, and computer readable media for preventing an account from entering a low cash mode state, the operations comprising associating the customer with an account, associating the account with a mobile device, determining an account balance of the account, and determining, based on the account balance, whether the account is deemed to be in a low cash mode state. The operations may further comprise providing, via the mobile device, a notification to the customer when the account enters the low-cash mode state and providing, via the mobile device, a notification to the customer when the account enters the low-cash mode state.
Aspects of the present disclosure may additionally include systems, methods, and computer readable media for preventing an account from entering a low cash mode state, the operations comprising associating the customer with an account, associating the account with a mobile device, determining an account balance of the account, and predicting, as a result of an initiated transaction, that the initiated transaction will result in the first account entering the low cash mode state. The operations may further comprise providing, via the mobile device, a notification to the customer when the account is predicted to enter the low-cash mode state and presenting, with the notification, options to the customer to manage the first account while the first account is predicted to enter the low cash mode state.
Aspects of the present disclosure may additionally include systems, methods, and computer readable media for preventing an account from entering a low cash mode state, the operations comprising associating a customer with a first account, associating the customer with a second account, linking the second account with the first account, determining a first account balance of the first account, and determining, based on the first account balance, whether the first account is deemed to be in the low cash mode state. The operations may further comprise transferring, automatically, when the first account is deemed to be in the low cash mode state, funds from the second account into the first account, processing the initiated transaction, and presenting a notification to the customer.
Aspects of the present disclosure may additionally include systems, methods, and computer readable media for determining a negative balance fee, the operations comprising associating a customer with a first account, determining a first account balance of the first account, and assessing, when the first account balance is negative, the negative balance fee.
Aspects of the present disclosure may additionally include systems, methods, and computer readable media for generating synthetic data, the operations comprising associating a customer with an account, storing data associated with the account, applying machine learning to the data to generate synthetic field-level data, and substituting the synthetic field-level data in place of field-level data associated with the account in an Automated Clearing House transaction or a mobile network transfer.
Aspects of the present disclosure may additionally include systems, methods, and computer readable media for analyzing historical data, the operations comprising associating a customer with an account, storing data associated with the account, applying machine learning to the data to determine transaction tendencies, and using the transaction tendencies to predict an account balance.
Aspects of the present disclosure may additionally include systems, methods, and computer readable media for presenting and using account management options, the operations comprising associating a customer with an account, providing options for managing the account, and implementing the selected options.
Aspects of the present disclosure may additionally include systems, methods, and computer readable media for integrating social media and financial services, the operations comprising associating a customer with a first account at a financial institution, associating the customer with a social media account, linking the first account with the social media account, determining a first account balance of the first account, determining, based on the first account balance, whether the first account is deemed to be in a low cash mode state, and providing a notification to the customer when the first account is deemed to be in the low cash state.
Aspects of the present disclosure may additionally include systems, methods, and computer readable media for integrating social media and financial services the operations comprising associating a customer with a first account at a financial institution, associating the customer with a social media account, presenting an option for the customer to grant the financial institution permission to link the first account and the social media account, receiving permission to link the first account and the social media account, receiving permission to link the first account and the social media account, and linking the first account with the social media account. The operations may further comprise determining a first account balance of the first account, determining, based on the first account balance, whether the first account is deemed to be in a low cash mode state, and providing a notification to the customer when the first account is deemed to be in the low cash mode state using the social media account.
Aspects of the present disclosure may additionally include systems, methods, and computer readable media for preventing a negative account balance, the operations comprising associating a customer with an account at a financial institution, associating the account with a mobile device, determining a first account balance of the first account, determining, based on the first account balance, whether the first account is deemed to be in a low cash mode state, identifying a potential purchase and a potential purchase amount, determining, based on the potential purchase amount and the first account balance, whether the potential purchase will result in a negative first account balance, providing a notification to the customer that the potential purchase will result in a negative first account balance.
Aspects of the present disclosure may additionally include systems, methods, and computer readable media for preventing a negative account balance, the operations comprising associating a customer with an account at a financial institution, associating a customer with an account at a financial institution, determining a first account balance of the first account, determining, based on the first account balance, whether the first account is deemed to be in a low cash mode state, receiving a request for transfer of funds from a transaction initiated by the card, and denying the request for monetary transfer while the first account is deemed to be in the low cash mode state.
Aspects of the present disclosure may additionally include systems, methods, and computer readable media for predicting low-cash mode state, the operations comprising associating a customer with a first account, storing financial history data associated with the customer, accessing non-financial data, analyzing the financial history data and the non-financial data, determining, a future account balance of the first account, based on scheduled transactions, the financial history data, and the non-financial data, and determining whether the first account is deemed to be in the low-cash mode state based on the future account balance.
Aspects of the present disclosure may additionally include systems, methods, and computer readable media for avoiding negative account balance, the operations comprising providing an interface accessible via a user device associated with a first account, associating a customer with the first account at a financial institution, determining a first account balance of the first account, determining, based on the first account balance, whether the first account is less than a threshold value, providing, via the interface, a notification to the customer when the first account balance is less than the threshold value, and providing, via the interface, a notification to the customer when the first account balance is less than the threshold value.
Aspects of the present disclosure may additionally include systems, methods, and computer readable media for avoiding negative account balance, the operations comprising associating a customer with a first account, determining a first account balance of the first account, determining, based on the first account balance, whether the first account is deemed to be in a low cash mode state, providing a notification to the customer when the first account is deemed to be in the low cash mode state, and presenting, with the notification, options to the customer to manage the first account while the first account is deemed to be in the low cash mode state.
Aspects of the present disclosure may additionally include systems, methods, and computer readable media for managing accounts, the operations comprising associating a customer with an account, determining an account balance of the account, determining, based on the account balance, whether the account is deemed to be in a low cash mode state, determining whether smart lock is activated, providing a first notification to the customer when the account is deemed to be in the low cash mode state, providing a second notification to the customer when smart lock is activated, and presenting, with the first notification, at least one option to the customer to manage the first account.
Aspects of the present disclosure may additionally include systems, methods, and computer readable media for managing accounts, the operations comprising associating a customer with an account, associating a card with the account, determining whether smart lock is activated, receiving a request to transfer funds from a transaction initiated by the card, and denying, when smart lock is activated, the request.
Aspects of the present disclosure may additionally include systems, methods, and computer readable media for preventing fraudulent transactions, the operations comprising associating a customer with an account, associating the account with a mobile device, receiving a request to disable a function in an application on the mobile device, and processing the request.
Aspects of the present disclosure may additionally include systems, methods, and computer readable media for managing a negative account balance, the operations comprising associating a customer with an account, determining an account balance of the account, determining, based on the account balance, whether the account balance is negative, and displaying a time remaining until a negative balance fee is assessed.
Aspects of the present disclosure may additionally include systems, methods, and computer readable media for managing a negative account balance, the operations comprising associating a customer with an account, determining an account balance of the account, determining, based on the account balance, whether the account balance is negative, providing a first notification to the customer when the account balance is negative, and providing, after a specific amount of time, a second notification to the customer when the account balance is negative.
Aspects of the present disclosure may additionally include systems, methods, and computer readable media for generating a personalized grace period, the operations comprising associating a customer with an account at a financial institution, determining an account balance of the account, determining, based on the account balance, whether the account balance is negative, providing a first notification to the customer when the account balance is negative, determining the personalized grace period, and displaying, the personalized grace period to the customer.
Aspects of the present disclosure may additionally include systems, methods, and computer readable media for providing reminder notifications to a customer, the operations comprising associating a customer with an account at a financial institution, determining an account balance of the account, determining, based on the account balance, whether the account balance is negative, providing a first notification to the customer when the account balance is negative, and providing an option for the customer to receive a second notification while the account balance remains negative.
Aspects of the present disclosure may additionally include systems, methods, and computer readable media for calendar-based transaction management, the operations comprising associating a customer with an account at a financial institution, providing a calendar-based interface for the account, wherein a transaction is represented by a location on a calendar corresponding to a date associated with the transaction, assigning a date for processing the transaction based on the location of the representation on the calendar, changing the date for processing the transaction in response to receiving customer input moving the representation of the transaction on the calendar, and processing the transaction on the date for processing the transaction.
Aspects of the present disclosure may additionally include systems, methods, and computer readable media for determining a negative balance fee, the operations comprising associating a customer with a first account, determining a first account balance of the first account, and assessing, once during a period of time when the first account balance is negative, the negative balance fee.
Aspects of the present disclosure may additionally include systems, methods, and computer readable media for providing recommendations for managing an account in a low-cash mode state, the operations comprising associating a customer with an account at a financial institution, determining an account balance of the account, storing financial history data associated with the customer, accessing non-financial data, analyzing the financial history data and the non-financial data, determining, a future account balance of the account, based on the account balance, scheduled transactions, the financial history data, and the non-financial data, and determining whether the first account is deemed to be in the low-cash mode state based on the future account balance.
Aspects of the present disclosure may additionally include systems, methods, and computer readable media for maintaining an account above a low balance threshold, the operations comprising associating a customer with an account at a financial institution, receiving the low balance threshold from the customer, determining an account balance of the account, determining, based on the account balance, whether the account balance is less than the low balance threshold, providing a notification to the customer when the account balance is deemed to be less than the low balance threshold, and presenting, with the notification, options to the customer to manage the account while the account balance is less than the low balance threshold.
Aspects of the present disclosure may additionally include systems, methods, and computer readable media for predicting cash flow, the operations comprising associating a customer with an account at a financial institution, storing financial history data associated with the customer, storing account history data associated with the account, storing aggregated data associated with other customers and other accounts, accessing non-financial data, analyzing by machine learning the financial history data, the account history data, the aggregated data, and the non-financial data, and determining a future account balance of the account, based on scheduled transactions, the financial history data, the account history data, the aggregated data, and the non-financial data. The operations may further comprise determining whether the first account is deemed to be in the low-cash mode state based on the future account balance and determining a danger time period associated with the future account balance and the low cash mode state.
Aspects of the present disclosure may additionally include systems, methods, and computer readable media for preventing a negative account balance, the operations comprising associating a first customer with an account at a financial institution, associating a second customer with the account, associating the first customer with a mobile device, determining an account balance of the account, and determining, based on the account balance, whether the account is deemed to be in a low cash mode state. The operations may further comprise determining, via the mobile device, a location of the first customer, determining if the location of the first customer is associated with a location of a merchant, and providing, when the location of the first customer is associated with the location of a merchant and the account is deemed to be in the low cash mode state, a notification to the first customer and the second customer.
Aspects of the present disclosure may additionally include systems, methods, and computer readable media for preventing a negative account balance, the operations comprising associating a customer with an account at a financial institution, determining an account balance of the account, determining, based on the account balance, whether the account is deemed to be in a low cash mode state, activating, when the account is deemed to be in the low cash mode state, smart lock, providing a first notification to the customer when the account is deemed to be in the low cash mode state, providing a second notification to the customer when smart lock is activated, and presenting, with the second notification, at least one option to the customer to manage the account.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only, and are not restrictive of the disclosed embodiments as claimed.
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate disclosed embodiments and, together with the associating a card with the first account description, serve to explain the disclosed embodiments. In the drawings:
The following detailed description refers to the accompanying drawings. Wherever possible, the same reference numbers are used in the drawings and the following description to refer to the same or similar parts. While several illustrative embodiments are described herein, modifications, adaptations and other implementations are possible. For example, substitutions, additions, or modifications may be made to the components illustrated in the drawings, and the illustrative methods described herein may be modified by substituting, reordering, removing, or adding steps to the disclosed methods. Accordingly, the following detailed description is not limited to the disclosed embodiments and examples. Instead, the proper scope is defined by the appended claims.
As used herein, low-cash mode may be used to refer to a state of an account held by a customer at a financial service provider when the financial service provider determines that the account has insufficient funds to handle a transaction without resulting in a negative balance, that the account has a negative balance, that the account balance may be negative as a result of scheduled or predicted future transactions, or that the account balance has fallen below a predetermined threshold value.
In some embodiments, system environment 100 may include one or more networks 102. Network 102 may comprise any computer networking arrangement used to exchange data. For example, network 102 may be the Internet, a private data network, a virtual private network (VPN) using a public network, and/or other suitable connections that enable the components of system environment 100 to send and acquire information. Network 102 may also include a public switched telephone network (“PSTN”) and/or a wireless network such as a cellular network, wired Wide Area Network, Wi-Fi network, and/or another known wireless network (e.g., WiMAX) capable of bidirectional data transmission.
Each network 102, financial institution 106, and third-party service provider 110 may also include one or more local networks (not shown). A local network may be used to connect the components of
In some embodiments, system environment 100 may include one or more user devices 108. User device 108 may be one or more of a desktop computer, a laptop, a tablet, a smartphone, a multifunctional watch, a pair of multifunctional glasses, a tracking device, or any suitable device with computing capability. User device 108 may comprise a memory, a processor, and/or other specialized hardware that is configured to execute one or more methods of the disclosed embodiments. User device 108 may have an online banking or financial account management application installed thereon, which may enable user device 108 to communicate with, for example, with financial institution 106 and/or third-party service provider 110 via network 102 and/or a local network. Additionally, user device 108 may connect to financial institution 106 and/or third-party service provider 110 through use of web browser software via network 102 and/or a local network. Finally, user device 108 may provide a graphical user interface 118 to enable users to view data from the user device 108 generated by an application thereon and obtained over network 102 from one or more of financial institution 106 and/or third-party service provider 110.
In some embodiments, one or more of financial institution 106, third-party service provider 110, and/or network 102 may include one or more databases. Database may include one or more memory devices that store information. By way of example, databases may include Oracle™ databases, Sybase™ databases, or other relational databases or non-relational databases, such as Hadoop sequence files, HBase™, or Cassandra™. The databases or other files may include, for example, data and information related to the source and destination of a network request, the data contained in the request, etc. Systems and methods of disclosed embodiments, however, are not limited to separate databases. Database may include computing components (e.g, database management system, database server, etc.) configured to acquire and process requests for data stored in memory devices of database and to provide data from database.
In some embodiments, one or more of financial institution 106, third-party service provider 110, and/or network 102 may include one or more cloud services. Cloud service may include a physical and/or virtual storage system associated with cloud storage for storing data and providing access to data via a public network such as the Internet. Cloud service may include cloud services such as those offered by, for example, Amazon®, Apple®, Cisco®, Citrix®, IBM®, Joyent®, Google, Microsoft®, Rackspace®, Salesforce.com®, and Verizon®/Terremark®, or other types of cloud services accessible via network 102. In some embodiments, cloud service comprises multiple computer systems spanning multiple locations and having multiple databases or multiple geographic locations associated with a single or multiple cloud storage service(s). As used herein, cloud service refers to physical and virtual infrastructure associated with a single cloud storage service and may manage and/or store data.
In some embodiments, one or more of financial institution 106, third-party service provider 110, and/or network 102 may include one or more servers or clusters of servers. Servers or clusters of servers may be located in the same data center or different physical locations. Multiple servers and clusters may be formed as a grid to share resources and workloads. Each server and/or cluster may include a plurality of linked nodes operating collaboratively to run various applications, software modules, analytical modules, rule engines, etc. Each node may be implemented using a variety of different equipment, such as a supercomputer, personal computer, a server, a mainframe, a mobile device, or the like. In some embodiments, the number of servers and/or server duster may be expanded or reduced based on workload. In some embodiments, one or more components of system environment 100 may be placed behind a load balancer to support high availability and ensure real-time (or near real-time) processing of optimal decision predictions.
In some embodiments, one or more of financial institution 106, third-party service provider 110, and/or network 102 may include one or more computing systems that are configured to execute software instructions stored on one or more memory devices to perform one or more operations consistent with disclosed embodiments. For example, a financial institution 106 may include memory devices storing data and software instructions and processors configured to use the data and execute the software instructions to perform server-based functions and operations known to those skilled in the art. Financial institution 106 may also include one or more general-purpose computers, mainframe computers, or any combination of these types of components. In some embodiments, financial institution 106 may have an application installed thereon to perform processes that are consistent with disclosed embodiments.
In some embodiments, one or more of financial institution 106, third-party service provider 110, and/or network 102 may include devices configured as a particular apparatus, system, or the like based on the storage, execution, and/or implementation of the software instructions that perform operations consistent with disclosed embodiments. Devices of financial institution 106 may be standalone or may be part of a subsystem included in a larger system. For example, financial institution 106 may include distributed servers that are remotely located and communicate over a network (e.g., WAN and/or a local network) or a dedicated network.
In some embodiments, one or more of financial institution 106, third-party service provider 110, and/or network 102 may include or may access one or more storage devices configured to store data and/or software instructions used by one or more processors to perform operations consistent with disclosed embodiments. For example, financial institution 106 may include memory configured to store one or more software programs that perform several functions when executed by a processor. The disclosed embodiments are not limited to separate programs or computers configured to perform dedicated tasks. For example, financial institution 106 may include memory that stores a single program or multiple programs. Additionally, one or more of financial institution 106, third-party service provider 110, and/or network 102 may execute one or more programs located remotely. For example, financial institution 106 may access one or more remote programs stored in memory included with a remote component that, when executed, perform operations consistent with disclosed embodiments. For example, financial institution 106 may exchange data and interact with systems, devices, and programs of third-party service provider 110 and/or hardware and software of user device 108. In certain aspects, one or more of financial institution 106, third-party service provider 110, and/or network 102 may include server software that generates, maintains, and provides services associated with user accounts.
Financial institution 106 in system environment 100 may include any entity that generates, provides, manages, and/or maintains financial service accounts 130, etc., for customers. Financial institution 106 may include a retail and commercial bank, internet bank, credit union, savings and loan association, investment bank or company, brokerage firm, and/or another financial institution known by those of skill in the art. Financial institution 106 may provide and maintain one or more financial service accounts 130 for an account owner. The one or more accounts 130 may include, among others types, a checking account, a savings account, certificate of deposit account, money market account, brokerage account, investment retirement account (IRA), 401(k) account, line of credit, and/or any other financial account known by those of skill in the art. System environment 100 may include more than one financial institution 106 with one or more financial accounts 130, a single financial institution 106 with two or more financial accounts 130, or any other combination thereof. In the context of the disclosed embodiments, the present embodiments include multiple accounts, including at least a first account and second account, including those situated in one or more financial institutions, owned by one or more account owners, and of one or more account type.
Each financial account 130 in system 100 may have differing or overlapping account ownership and access privileges. For example, the financial accounts 130 may be individual accounts, joint accounts, payable-on-death accounts, joint account with rights of survivorship, accounts in trust, or any other type of account ownership known by those of skill in the art. For example, an individual account may include a singular account owner. A joint account may include two or more account owners with equal access to funds and information related to the account Accounts in trust may be controlled by a designated trustee for the benefit of another account owner, who may have limited access or control over the trust account. It is not desired to limit the type of financial account 130 used in the present embodiments.
Third-party service provider 110 may be any company, organization, or entity that may enable, monitor, coordinate, and/or control access and provide information to different account owners of different financial accounts 130 in system environment 100. Third-party service provider 110 may communicate with one or more financial institutions 110 and one or more customers via one or more user devices 108 and enable access to account information and manage access rights to different financial accounts 130. Third-party service provider 110 may serve as an information clearinghouse or intermediary between financial institution 106 and user device 108. For example, account owners may grant third-party service provider 110 access to certain information for financial accounts 130 maintained by one or more financial institution 106. Financial institution 106 may securely publish data to third-party service provider 110 for particular financial accounts whose owners have granted access, and particular data from those accounts, over a secure protocol or public or private network, and third-party service provider 110 may control access to the information between different account owners. In one embodiment, account owner of financial account 130 may grant access to information from the account, whereby financial institution 106 enables third-party service provider 110 to access account data via an application programming interface (API) or other means, and share data with an owner of another financial account. The two accounts are thereby linked by third-party service provider 110 having access to certain data in each account and publishing that data to the different account owners. This enables, for instance, an owner of a first account to see transactions in a second account. Certain personal and financial data may be obfuscated or not shared by third-party service provider 110, or financial institution 106 may not provide such information, upon request and based on the scope of access enabled by an account owner. These data sharing functions may also be carried out, in certain embodiments, by one or more financial institution 106 directly with account owners and without third-party service provider 110.
As will be discussed in greater detail below, account owners may establish rules to transfer money from a first account to a second account (or a third account) based on activity in the first account. Account owners may also establish rules to transfer money from a second account to a first account (or a third account) based on activity in the second account. Rules may be established and stored in an account owner's financial account 130 by financial institution 106, in a service account 140 of third-party service provider 110, or both. Rules may be established by account owners via graphical user interface 118 of user device 108 for, among other things, determining when to transfer funds, determining how much to transfer, and determining what restrictions are placed on transferred funds, transfer amounts, and transfer rates.
One or more financial institutions 106 and/or one or more third-party service providers 110 may host a web application. API, web site, or similar interface that is accessible over network 102 to account owners via user device 108. The interface may be hosted on one or more web servers and operate in a client-server model with user device 108, while obtaining information, including account information, from service provider 110 and/or financial institution 106. Via user device 108, an account owner may view graphical user interface 118 on user device 108. Graphical user interface 118 may provide account owners with the ability to view financial account information of another account, for example, another account owner's account. Graphical user interface 118 may also provide an interface enabling the disclosed functions herein, including, among other things, authorizations to transfer cash and/or funds (assets), authorizations to share information and connect and/or link financial accounts, establish rules for transferring cash and/or funds (assets) between linked accounts, and track and monitor transfers and the status of financial accounts.
System for Low-Cash Mode
As disclosed herein, low-cash mode may be used to refer to a state of an account held by a customer at a financial service provider when the financial service provider determines that the account has insufficient funds to handle a transaction without resulting in a negative balance, that the account has a negative balance, that the account balance may be negative as a result of scheduled or predicted future transactions, or that the account balance has fallen below a predetermined threshold value.
Consistent with the present embodiments, financial institution 106, 116 may provide the customer at user device 118 with options to manage accounts 131, 132 in low cash mode including methods, systems, and features disclosed herein which provide the customer the ability to at least increase the balance of accounts 131, 132 (e.g. personal loan, transfer of cash and/or funds), approve or deny individual transactions, lock a card associated with accounts 131, 132, or prevent spending in order to avoid a negative account balance. Additionally, methods, systems, and features disclosed herein may provide the customer the ability to prioritize payments, cancel transactions, manage the amount of a negative balance or length of time carrying a negative balance in order to minimize negative balance fees, select repayment options when an overdraft cannot be avoided, and other options and features which the customer can select in order to avoid or minimize a negative account balance.
System for Alerting to Customers when Entering/Exiting Low-Cash Mode
Consistent with disclosed embodiments, a financial institution may provide a notification to a customer when an account associated with the customer enters low cash mode in the form of an alert. The notification may be triggered when an account balance is negative; when an account balance falls below a predetermined threshold; during a particular time of the month that is determined based on scheduled reoccurring transactions such as direct deposits and automatic billing as well as analysis of historical data; determined based on transaction date related to upcoming holidays, birthdays, anniversaries, or calendared special occasions; triggered when a customer is interacting with a merchant online; or determined based on geographic location of a customer or merchant. The notification may be delivered to the customer as an email, text message, voice call, alert through an application on a mobile phone, social media alert, alert through a mobile device, alert through wearable technology, alert through a device connected to the internet, or other methods for instantaneously alerting a customer.
The notification may further include information relating to any negative balance fees to be assessed if the negative balance is not cured and a period of time to cure negative balance. In some embodiments, the negative balance fees may be tiered based on, for example, the extent to which the account is negative or the length of time the account balance is negative.
Consistent with disclosed embodiments, financial institution may also provide a notification to a customer when the account associated with the customer is no longer in low cash mode. The notification may be triggered when a customer cures a negative balance; when the account balance is greater than a predetermined threshold balance; a particular time of the month is past; a time period related to upcoming holidays, birthdays, anniversaries, or calendared special occasions has past; or the financial institution determines the customer is no longer in danger of incurring a negative balance based on a change in geographic location of a customer. The notification may be delivered to the customer as an email, text message, voice call, alert through a mobile banking application, social media alert, alert through a mobile device or mobile device application, alert through wearable technology, alert through a device connected to the internet, or other means for instantaneously providing an alert to the customer.
As shown in
At step 1708, financial institution 106 may determine, based on the account balance, whether the account is deemed to be in a low-cash mode state, as disclosed herein. At step 1710, if the account is deemed to be in a low-cash mode state, financial institution 106 may provide a notification to the customer that the account is deemed to be in a low-cash mode state. At step 1712, financial institution 106 may present options to manage the account while the account is in the low-cash mode state.
System for Preventing Overdraft
Consistent with disclosed embodiments, the financial institution may offer customers various options to avoid negative account balances and associated negative balance fees. The financial institution may offer the customers options disclosed herein including, for example, the ability to transfer money between accounts, the ability to cancel pending transactions or payments, the ability to obtain a loan, or the ability to accelerate ACH transactions or payroll deposits. These options may be offered to the customers by the financial institution through various methods, including through an application on a mobile device. In some embodiments, these options may be selectable by the customer and implemented automatically, without any action or intervention by the financial institution.
Consistent with disclosed embodiments, the financial institution may present the option to the customer of obtaining or applying for a personal loan in order to avoid a negative account balance. Financial institution may present this option to the customer with a preapproved amount and an interest rate for immediate approval and deposit of the amount into the account. Additionally or alternatively, the customer may choose to customize the terms of the loan, subject to approval by the financial institution.
In
In
In
Additionally or alternatively, the preventative options may further include the ability to accelerate pending ACH deposits or a regularly scheduled deposit including, for example, a payroll deposit. The financial institution may accelerate the deposits by expediting processing, providing the funds as a loan from the financial institution for little or no cost as a loan for the amount of the future deposit, waiting to process withdrawals until the deposit has been processed, or other means known in the art used to accelerate deposits.
At step 1810, financial institution 106 may determine, based on the first account balance, whether the account is deemed to be in a low-cash mode state, as disclosed herein. At step 1812, if the account is deemed to be in a low-cash mode state, financial institution 106 may automatically transfer funds from the second account to the first account. The amount of funds transferred may be preselected by the customer or determined by financial institution 106. Additionally or alternatively, the amount of funds transferred may be sufficient such that the first account is no longer deemed to be in the low-cash mode state or sufficient to prevent a negative first account balance.
At step 1814, financial institution 106 may provide a notification to the customer that the first account is deemed to be in a low-cash mode state, that funds were automatically transferred from the second account, the amount of funds transferred from the second account, a current first account balance, and/or options for managing the first account while in the low-cash mode state.
System for Tiered Overdraft Fees
In other embodiments, a financial institution may charge a negative balance fee when a transaction results in a negative account balance. In some embodiments, the financial institution may assess the negative balance fees using a tier system. The tiered negative balance fees may be based on, for example, the extent to which the account is negative with higher fees for larger negative amounts as compared to smaller negative amounts or based on historical data associated with the account.
System for Synthetic Data and Machine Learning
Consistent with disclosed embodiments, the financial institution may include data privacy and security measures in order to protect transaction, account, and customer data. Financial institution may use, for example, encryption/decryption, tokenization/detokenization, masking, obfuscation, or other methods for protecting data. Additionally or alternatively, financial institution may employ artificial intelligence or machine learning algorithms to protect transaction, account, and customer data. The artificial intelligence or machine earning algorithms may also be used to generate synthetic data or artificial data stored in a data platform to be substituted for transmitted data or for fields in transmitted data that are deemed sensitive by the costumer or financial institution.
System for Fraud Protection Features
Consistent with disclosed embodiments, financial institution may integrate fraud protection features with the features associated with an account in low-cash mode. Fraud protection features may include security questions, multi-factor authentication, password standards, alerts associated with suspicious activity, and any other feature or service intended to prevent, detect, or resolve fraud. Password standards may include minimum password requirements such as length or character requirements.
Security questions may include a set of questions and answers wherein the customer or account holder provides answers to questions when creating an account. The customer-provide answers to the questions are stored by the financial institution and used to verify the identity of the customer. The questions and answers are setup such that only the customer should be able to provide the specific answer to the specific questions. The financial institution may prompt a customer for the answers to security questions when the customer attempts to login to the account from a computer or mobile device not previously associated with the account.
In one example, multi-factor authentication may include, when a customer logs into an account, generating a one-time passcode such as a random string of characters and sending the one-time passcode to a device (e.g., as a text message, email, or voice call), prompting the customer for entry of one-time passcode, validating the entered passcode, and permitting access to the account.
At step 2008, financial institution 106 may prompt for entry of the one-time passcode. At step 2010, financial institution 106 may receive entry of the passcode. At step 2012, financial institution 106 may validate the passcode received in order to ensure that the passcode received matches the one-time passcode that was generated and sent. At step 2014, if the received passcode is validated, then financial institution 106 may grant the customer access to the account.
System for Integration with PNC Virtual Wallet
Consistent with disclosed embodiments, the financial institution may provide options allowing customers to perform actions relating to low cash mode through a website, a mobile version of a website, an application or a micro-application on a mobile device, or through an ancillary application, such as a budgeting or money-management application, for example PNC Mobile Wallet®.
System for Linking with Virtual Wallet and Social Media
In some embodiments, the financial institution may urge or permit customers to link financial accounts with social media accounts. The link between accounts may provide financial institution with access to information gathered by the social media account and associated applications. The link may also provide another channel for financial institution to send alerts or messages to a customer. For example, a customer could receive a message via a social network instant or direct message that the account has entered low cash mode.
Additionally or alternatively, the financial institution may provide a customer with the option to associate a social media account associated with the customer with a financial account. The financial institution may then interact with the customer using the notifications and infrastructure provided by the social media platform. For example, the financial institution may provide a notification that an account associated with a user has entered low cash mode using Facebook Messenger or Twitter Direct Message. The financial institution may also access or analyze data associated with a customer's social media profile, presence, usage, activity, connections, or other social media data.
System for Pre-Purchase Alerts
Consistent with disclosed embodiments, the financial institution may provide a notification to a customer that a pending, scheduled, or anticipated purchase or transaction will result in a negative account balance before the purchase or transaction is made. For example, a financial institution may notify a customer that a transaction associated with an item placed in a virtual shopping cart while visiting an online merchant would result in a negative balance. In another embodiment the financial institution may use historical data associated with a customer to predict and notify a customer that an anticipated transaction will result in a negative balance. The financial institution may further anticipate transactions based on the time of the day, month, or year; a geographic location associated with a merchant; a geographic location associated with the customer; or other indicators associated with the customer and spending an amount greater than a current balance.
At step 2308, financial institution 106 may determine, based on the account balance, whether the account is deemed to be in a low-cash mode state, as disclosed herein. At step 2310, financial institution may identify a potential purchase and the amount of the potential purchase. At step 2312, financial institution 106 may, based on the account balance and potential purchase amount, determine a potential account balance. At step 2314, financial institution 106 may provide a notification to the customer. The notification may include a predicated account balance, options to prevent a negative balance, options to avoid the account entering the low-cash mode state, or additional information and options for managing the account as disclosed herein.
System for Overall Increased Efficiency of Transactions
Implementation of the disclosed embodiments may result in overall increased efficiency of transactions by financial institution 106. The increased efficiency may result from at least improved capability to transfer funds between accounts, automation of high demand or regularly occurring tasks/queries such as balance confirmation, by storing and displaying more information in the same place, by providing quicker searching of transaction data, providing additional avenues for communicating with customers, providing more effective avenues for communicating with customers, and other features discussed below which improve functionality for the customers or financial institution 106. Additionally or alternatively, the disclosed embodiments may increase customer satisfaction with the financial institution and improve customer loyalty.
System for Automatic Card Lock
Consistent with disclosed embodiments, when an account associated with a customer enters low cash mode, the financial institution may disable, reject, or block transactions initiated by a credit or debit card associated with the account. The notification (disclosed above) may inform the customer that an account has entered low cash mode and that any card associated with the account has been locked. The financial institution may provide the customer with the ability to choose the option to have the financial institution of automatically locking any card when the associated account enters low cash mode. The financial institution may also provide the customer with the ability to unlock a card that has been locked due to the account's entry into low cash mode. These options and functionality may be provided by the financial institution through a mobile application or web-based interface.
At step 2408, financial institution 106 may determine, based on the account balance, whether the account is deemed to be in a low-cash mode state, as disclosed herein. At step 2410, financial institution may receive a transaction initiated by the card associated with the account. At step 2412, if the account is deemed to be in a low-cash mode state, financial institution 106 may automatically deny the transaction initiated by the card.
System for Low-Cash Mode Based on Predicted Balance
Consistent with disclosed embodiments, the financial institution may determine that an account is in low cash mode based on a predicted balance. The predicted balance may be determined by comparing historical transaction data with current transaction data and predicting a future balance by manipulating the current balance based on expected transactions, deposits, and withdrawals. In some embodiments, the financial institution may apply artificial intelligence or machine learning algorithms to historical data associated with a customer or account in order to learn and predict transactions and spending tendencies and thereby generate a predicted balance.
At step 1910, financial institution 106 may determine, based on a predicted first account balance, whether the first account will enter a low-cash mode state, as disclosed herein. At step 1912, if the account is predicted to enter the low-cash mode state, financial institution 106 may automatically transfer funds from the second account to the first account. The amount of funds transferred may be preselected by the customer or determined by financial institution 106. Additionally or alternatively, the amount of funds transferred may be sufficient such that the first account is no longer predicted to enter the low-cash mode state or sufficient to prevent a negative first account balance.
At step 1914, financial institution 106 may provide a notification to the customer that the first account is predicted to enter the low-cash mode state, that funds were automatically transferred from the second account, the amount of funds transferred from the second account, a current first account balance, and/or options for managing the first account while in the low-cash mode state.
System for Selecting Overdraft Protection Features
In the disclosed embodiments regarding payment designation options, the financial institution may offer such options through various methods, including through an application on a mobile device. In some embodiments, these options may be selectable by the customer and implemented automatically without any action or intervention by the financial institution (e.g., without approval of the selected features by the financial institution).
At step 2608, financial institution 106 may determine, based on the account balance, whether the account is deemed to be in a low-cash mode state, as disclosed herein. At step 2610, if the account is deemed to be in a low-cash mode state, financial institution 106 may provide a notification to the customer that the account is deemed to be in a low-cash mode state. At step 2612, financial institution 106 may present options to manage the account while the account is in the low-cash mode state.
System for Customer Management of Transactions
In some embodiments, financial institution may provide options to the customer with an account in low cash mode to select which transactions to approve while other transactions are canceled or delayed. The options presented by the financial institution may also allow the customer to select an order of the transactions for processing, resulting in a prioritization of processing transactions. The customer may further select payments to delay until the occurrence of an event, such as a deposit, or for a specified length of time. The financial institution can vary the options presented based on the origin of an individual transaction, for example presenting the option to cancel some transactions while others can only be delayed. Different transaction origins may include point of sale transactions, ACH transactions, checks, scheduled payments, or any other method of initiating a transfer of funds into or out of an account.
In some embodiments the financial institution may offer a customer the option to designate payments for processing or non-processing after a payment transaction has occurred. A financial institution may, for example, receive data indicating that a payment transaction between a merchant and a customer account has occurred while the customer account is in low cash mode, and may offer the customer the option of designating that payment transaction for processing. In some embodiments, financial institution may additionally offer the customer the option to designate future payments from that merchant or location as payments which should be processed while the customer account is in low cash mode.
In other embodiments, financial institution may offer customers the option to designate payments to be delayed or canceled while the associated account in operating in low cash mode. In some embodiments, payments may not be available to be designated for processing during low cash mode unless criteria set by the financial institution or the customer are met. For example, the financial institution may not allow any payments to be designated for processing if the customer account is in delinquency, has a balance above or below a threshold, has an overdraft or penalty fee outstanding, or has a customer account history consistent with other groups of customer accounts. As another illustrative example, the customer account may be associated with parental controls or a controlling agent. The financial institution may withhold offering the customer designation options or may offer the customer the designation options but prevent the customer from making designations unless the financial institution has received an authorization from the customer's parent or controlling agent.
System for Account Management Over a Time Period
Consistent with disclosed embodiments, financial institution may provide a customer with the option to approve or deny processing or initiation of transactions for a period of time, such as an entire day (as discussed above). Alternatively, the financial institution may provide the customer the ability to review options associated with individual transactions. In one embodiment, the financial institution may provide a notification to the customer (as disclosed herein) that presents the option to the customer to approve or deny spending for the day.
In another embodiment, financial institution may provide a notification to the customer (as disclosed herein) that prompts the customer to configure how an account can spend for a specified period of time, such as a day. The notification may direct the customer to open an application on a mobile device where the financial institution presents options for processing transactions associated with an account within the specified period of time.
At step 2706, financial institution 106 may determine, based on the account balance, whether the account is deemed to be in a low-cash mode state, as disclosed herein. At step 2708, financial institution 106 may determine whether smart lock is activated or designated to be activated when the account is deemed to be in the low-cash mode state. At step 2710, financial institution 106 may provide a notification to the customer. The notification provided in step 2710 may include multiple notifications. Additionally or alternatively, the notification may include information relative to the low-cash mode state and/or options to manage the account.
System for Smart Lock
Consistent with disclosed embodiments, the financial institution may provide an option for a customer to lock a card associated with an account. When a card is locked, the financial institution will cancel or decline transactions associated with the card. The lock may be initiated automatically when the balance of the account falls below a predetermined threshold. Additionally or alternatively, the financial institution may present the customer with the option to lock a card through an interface such as an application on a mobile device. The predetermined threshold for locking the card may or may not be different for the threshold triggering low cash mode for the same account. The financial institution may select a default predetermined value for locking the card or, alternatively, present the customer with the ability to set the predetermined threshold for locking the card. The financial institution may present the customer with the option to unlock a card associated with a card through an interface such as an application on a mobile device. As shown in
At
At step 2806, financial institution 106 may determine, based on the account balance, whether the account is deemed to be in a low-cash mode state, as disclosed herein. At step 2808, financial institution 106 may determine whether smart lock is activated or designated to be activated when the account is deemed to be in the low-cash mode state. At step 2810, financial institution 106 may receive a request or initiation of a card transaction. At step 2812, if smart lock is activated, financial institution 106 may deny the card transaction. At step 2814, financial institution may provide a notification to the customer, as disclosed herein.
System for Overdraft Protection—Additional Accounts
Consistent with present embodiments, a financial institution may present a customer with the option to transfer funds from a different account into an account in low cash mode or into an account to prevent the account from entering low cash mode. Upon entry of an account into low cash mode or in order to prevent an account from entering low cash mode, the financial institution may automatically transfer funds from a predetermined account into an account in low cash mode. The predetermined account may be a different account owned by the same customer in the same financial institution, owned by a different customer in the same financial institution, owned by the same customer in a different financial institution, owned by a different customer in a different financial institution, or any other financial institution account previously linked with the customer's account currently in low cash mode (as discussed below). The predetermined account may also be a credit card or similar line of credit wherein the balance of the transaction is posted to the credit card or similar account automatically instead of resulting in a negative balance for the account in low cash mode.
In some embodiments, the financial institution may provide customers the option to draw on funds located in an alternative account for a transaction when an account is in low cash mode or when the transaction will result in the account entering low cash mode. In response to an alert provided by the financial institution, the financial institution may provide the customer with the ability to select an alternative account associated with the customer from which to draw funds for the transaction. The alternative account may be a checking account, savings account, line of credit, or any other account associated with the customer. Additionally or alternatively, the financial institution may provide the option for a customer to preselect an alternative account associated with the customer from which to automatically draw funds when the account is in low cash mode or when the transaction will result in the account entering low cash mode.
The ability to monitor transactions in first account 131 from second account 132 enables the owner of second account 132 to verify certain deposits, whether transferred cash and/or funds are maintained for a period of time, and to monitor and track savings (and transferred funds) in first account 131. In the present embodiment, automatic electronic transfers may be made from second account 132 to first account 131 based on activity in first account 131. For example, when first account 131 enters a low cash mode, or when an account balance in first account 131 drops beneath a predetermined threshold value, electronic transfers may be made from second account 132 to first account 131 automatically. Alternatively, electronic transfers may be made manually based on user interaction via a graphical user interface. A predetermined threshold value may be a static value (e.g. $25) or alternatively, may represent, a dynamic percentage value (e.g. a percentage value of a total account balance) that may change over time. In the present embodiment, the owner of second account 132 may be provided information, including transaction details and periodic statements, related to activity in first account 131. The owner of second account 132 may then verify that rules are being applied correctly and that transferred funds to first account 131 are transferred and maintained according to preset rules governing the funds transfer. Particular rules with respect to transfers will be discussed below.
At step 1604, financial institution 106 may transmit a notification to a user when the first account is deemed to be in a low-cash mode state based on a balance in the first account, as disclosed herein. In some embodiments, the first account is deemed to be in the low-cash mode state when the first account balance is less than or equal to a predetermined percentage of a total amount of funds stored in the first account.
At step 1606, financial institution 106 may display, when the first account balance is less than a threshold value, an option to transfer funds into the first account. Financial institution 106 may determine, before transferring funds, that the second account has sufficient funds to transfer the desired amount of funds to the first account without resulting in a negative account balance in the second account.
At step 1608, financial institution 106 may receive, via the interface, a selection of the option for the transfer request to connect the first account with a second account. Financial institution 106 may request authorization, prior to transferring the funds, to initiate the transfer of funds from the second account to the first account. Financial institution 106 may include a stored amount identifier, an indication of sufficient funds in the second account, and a request for authorization to transfer the funds from the second account to the first account based on the stored amount identifier. In some embodiments, financial institution 106 may determine that the second account has insufficient funds to transfer funds to the first account, and notify, via the interface, the user that funds has not been transferred from the second account to the first account.
At step 1610, financial institution 106 may transfer funds, based on the request, from the second account to the first account. Financial institution 106 may store a date identifier associated with the transferred cash, the date identifier indicating a deposit date for transfer into the first account. Financial institution 106 may provide, via an interface accessible via a user device registered with the second account, a fee indication specifying a fee associated with the transfer request from the second account. Financial institution 106 may provide via an interface accessible via a user device registered with the second account, a notification indicating the amount of funds transferred from the second account to the first account.
At step 1612, financial institution 106 may transmit a notification, via the interface, to the user that funds have been transferred from the second account to the first account. At step 1614, financial institution 106 may transmit an additional notification, via the interface, to the user that the first account is not longer deemed to be in the low-cash mode state based on the new first account balance. Other notifications not shown, and consistent with this disclosure, may be contemplated.
System for Disabling Features
Consistent with disclosed embodiments, the financial institution may provide the option for a customer to disable some or all functionality of an application on a mobile device. The financial institution may present this option when a customer indicates via phone call, web interface, or visit to a branch location that a mobile device associated with the customer has been lost, misplaced, or stolen.
At
System for Displaying a Grace Period
As shown in
System for Automatic Reminder Notifications
Consistent with the present embodiment, the financial institution may provide a notification to a customer during a grace period as a reminder to cure the negative balance. The financial institution may provide the notifications to the customer at predetermined times. The times may be predetermined by the financial institution or set by the customer. The times may relate to the amount of time remaining to cure the negative balance or the amount of time the balance has been negative. The financial institution may provide notifications such as a push notification on a mobile device associated with the customer, an SMS notification, an email notification, a voice call, a notification through a social media account associated with the customer, or any other notification intended to reach the customer.
System for Personalized Grace Periods
Consistent with the present embodiment, financial institution may also personalize a grace period for individual customers based on characteristics associated with the customer. In one embodiment, the financial institution may determine the length of a grace period based on the overdraft amount. For example, the financial institution may determine a shorter grace period for a small overdraft amount while determining a longer grace period for a larger overdraft amount. In another example, the financial institution may determine a longer grace period for a small overdraft amount while determining a shorter grace period for a larger overdraft amount.
In another embodiment, financial institution may determine the length of a grace period based on historical account data. The financial institution may determine a longer grace period if the historical account data indicates that the account balance consistently remains above a predetermine threshold.
In another embodiment, financial institution may determine the length of a grace period based on a customer's status with the financial institution. Financial institution 106 may determine longer a grace period for a customer in good standing with the financial institution. Financial institution 106 may also consider factors such as debit card use, average balance, direct deposit amounts, timing of regularly occurring or historical transactions, or any other indicator of high activity/volume with the financial institution when the financial institution determines if a customer is in good standing.
In another embodiment, financial institution may determine the length of a grace period based on a customer's actions within the grace period. For example, financial institution 106, may determine to increase the length of a grace period if the customer takes action to cure a negative balance within a grace period but does not fully cure a negative balance.
In another embodiment, financial institution may determine a fixed amount of time to be used as a grace period before an account balance is negative. The fixed amount of time may be available for use by a customer throughout a time period such as a month. The fixed amount of time the financial institution determines as a grace period could then be instituted by the customer when an account has a negative balance. Financial institution would then refrain from assessing a negative balance fee while grace period remains. When the grace period runs out, if the customer has not cured the negative balance, then the financial institution may assess a negative balance fee. If the customer cures the negative balance before the grace period ends, then the financial institution may refrain from assessing a negative balance fee and the remaining grace period time may be remain available for use by the customer. The grace period may run during single instance of a negative account balance or across multiple instances of negative account balance by the customer within the time period.
In another embodiment, financial institution may determine a fixed amount of time to be used as a grace period based on historical data associated with a customer. Financial institution may determine the time to be used by the customer as a grace period, for example, based on a number of historical occurrences of a negative balance. In one embodiment, the fixed amount of time to be used as a grace period is shorter when the customer has historical occurrences of a negative balance. In another example, the fixed amount of time to be used as a grace period is longer when the customer has greater amounts of time between historical occurrences of a negative balance.
In another embodiment, financial institution may determine a fixed amount of time to be used as a grace period on a reoccurring basis for example, monthly or annually. Financial institution may further allow time allocated as a grace period to be saved, compiled, accumulated, or carried over so that the customer continues to build a reserve of time to be used as a grace period when an account balance is negative. However, financial institution may set a maximum amount of time to be saved, compiled, accumulated, or carried over as a grace period. The financial institution may also implement other measures to limit the accumulation of total grace period. For example, the time allotted as a grace period may expire if unused for length of time (such as one year).
In another embodiment, financial institution may allocate a fixed amount of time to be used as a grace period as an incentive. The incentive may be given by the financial institution periodically, such as on the anniversary of the customer's relationship with the financial institution or may be included as an incentive within a package when a customer purchases a product from financial institution. Additionally or alternatively, the time to be used as a grace period may be given as an incentive for referrals by a customer, rewarding the customer and a new customer invited by the customer with time to be used as a grace period when the new customer opens an account with financial institution based on an invitation from the customer. In another embodiment, financial institution may offer to sell more time to be used as a grace period to the customer. Financial institution may allow the customer to purchase additional grace period time.
System for Customized Reminder Notifications
in some embodiments, financial institution may present an option to the customer to allow the customer to dynamically set reminders within an interface related to the financial institution so that the financial institution provides notifications to the customer reminding the customer to cure a negative account balance. Financial institution may suggest time or increments for the reminder notifications. Financial institution may also permit customers to select reminders that are regularly occurring or persistent until the negative account balance is cured. Financial institution may further permit customers to select the timing, time increments, consistency, or manner of reminder notifications.
System for Integration with PNC Virtual Wallet Calendar
In other embodiments, financial institution may provide the customer with an option to view past, present, and future transactions on a calendar interface, for example the PNC Virtual Wallet Calendar. When an account enters low cash mode, the financial institution may provide customers with the option to allow the financial institution to automatically reschedule payments in order to prevent or cure a negative balance. The financial institution may automatically reschedule transactions by applying machine learning or artificial intelligence algorithms to the calendared transactions.
System for Time Period-Based Negative Balance Fees
In some embodiments, the financial institution may provide a negative balance fee as a substitute for a transactional fee when a customer account has insufficient funds. For example, the financial institution may provide the customer with the option of electing to pay a flat fee for every predetermined period of time in which the customer's account has a negative balance. In some embodiments the period of time is not predetermined or may be dynamically adjusted to suit the customer based on the customers data or the customer account's historical data.
System for Recommendations Based on Scheduled Payments
Consistent with disclosed embodiments, the financial institution may provide a notification to a customer that a pending, scheduled, or anticipated purchase or transaction will result in a negative account balance before the purchase or transaction is made. For example, a financial institution may notify a customer that a transaction associated with an item placed in a virtual shopping cart while visiting an online merchant would result in a negative balance. In another embodiment the financial institution may use historical data associated with a customer to predict and notify a customer that an anticipated transaction will result in a negative balance. The financial institution may further anticipate transactions based on the time of the day, month, or year; a geographic location associated with a merchant; a geographic location associated with the customer; or other indicators associated with the customer and spending an amount greater than a current balance.
System for Maintaining a Minimum Threshold Value
In some embodiments, the financial institution may provide the customer an option of setting a low balance threshold. The low balance threshold represents a maximum negative balance after the customer account enters low cash mode. In electing to set a low balance threshold, the customer can prevent negative balances from decreasing beyond a negative amount set as the negative balance threshold. This provides the customer with peace of mind that a negative balance will not exceed the customer's ability repay and also has the benefit of assisting the financial institution in assessing a financial risk profile associated with the customer. The low balance threshold may include providing the customer with the ability to selectively choose one or more scheduled payments for processing. Once the customer indicates that selection of scheduled payments for processing is complete, the financial institution may render remaining scheduled payments unactionable. Unactionable payments cannot be cancelled or modified by a customer but may be cancelled or modified by the financial institution.
The low balance threshold may be dynamic and automatically set as a function of various factors, such as the customer's age, income, credit score, financial history, or other factors relevant to the customer's likelihood of repaying a negative balance. In some embodiments, the low balance threshold is set by an agreement between the customer and the financial institution. The low balance threshold may also be set by the financial institution, allowing a customer to choose among scheduled payments for processing but preventing the customer from changing the low balance threshold amount.
In some embodiments, the financial institution may provide the customer an option of setting a low balance threshold. The low balance threshold represents a maximum negative balance after the customer account enters low cash mode. In electing to set a low balance threshold, the customer can prevent negative balances from decreasing beyond a negative amount set as the negative balance threshold. This provides the customer with peace of mind that a negative balance will not exceed the customer's ability repay and also has the benefit of assisting the financial institution in assessing a financial risk profile associated with the customer. The low balance threshold may include providing the customer with the ability to selectively choose one or more scheduled payments for processing. Once the customer indicates that selection of scheduled payments for processing is complete, the financial institution may render remaining scheduled payments unactionable. Unactionable payments cannot be cancelled or modified by a customer but may be cancelled or modified by the financial institution.
The low balance threshold may be dynamic and automatically set as a function of various factors, such as the customer's age, income, credit score, financial history, or other factors relevant to the customer's likelihood of repaying a negative balance. In some embodiments, the low balance threshold is set by an agreement between the customer and the financial institution. The low balance threshold may also be set by the financial institution, allowing a customer to choose among scheduled payments for processing but preventing the customer from changing the low balance threshold amount.
At step 3008, financial institution 106 may determine, based on the account balance and low balance threshold, whether the account is less than the low balance threshold. At step 3010, financial institution 106 may provide a notification to the customer, as disclosed herein. At step 3012, financial institution 106 may present options to manage the account while the account balance is less than the low balance threshold.
System for Predictive Cash Flow
Consistent with disclosed embodiments, the financial institution may apply artificial intelligence or machine learning algorithms to historical data stored in a data platform and associated with a customer or account in order to learn and predict transactions and spending tendencies. The historical data may additionally include data available through the customer's social media account(s). Financial institution 106 may further provide notifications or recommendations based on the predicted transactions or spending tendencies.
In some embodiments, the financial institution may provide the customer with a predictive cash flow feature. The predictive cash flow feature may use one or more of the customer's financial history, the customer account history, and aggregated data from other customers and customer accounts to create one or more predictions. The one or more predictions may include time periods or amounts related to a customer's financial status, and may include time periods when a customer is more likely to enter low cash mode. The predictive cash flow feature may, by way of illustrative example, analyze a customer's financial history and determine patterns corresponding to when the customer's account receives deposits or when the customer makes expenditures. Through this analysis, the predictive cash flow feature may determine probabilities for a customer account entering low cash mode and, when a probability is within certain range, notify a customer of a prediction. The predictive cash flow feature may similarly provide the customer with a prediction corresponding to a high likelihood of a low customer account balance or negative balance.
In some embodiments, the predictive cash flow feature incorporates machine learning to create more accurate predictions. For example, the financial institution may apply machine learning or artificial intelligence algorithms to evaluate historical predictions and their accuracy in comparison to actual customer account status. The predictive cash flow feature may then adjust data inputs used for predictions that were historically less accurate and leave unmodified data inputs used for predictions that were historically accurate. In addition, the predictive cash flow feature may create predictions for the purpose of evaluating and enhancing future predictions without sending the predictions to a customer. This enables the predictive cash flow feature to continually improve the accuracy of predictions while providing a customer with the most accurate predictions.
In some embodiments the predictive cash flow feature incorporates data received and stored by the financial institution as well as data received from third parties. Data received from third parties may enable the financial institution to create more holistic and accurate predictions by incorporating more data into its analysis. Data included in the predictive cash flow feature may include non-financial data, such as calendar data, weather data, or other types of data associated with or correlating to financial behavior.
In some embodiments, the predictive cash flow feature allows a customer the ability to manually add payments to be analyzing or given greater weight in generating predicative cash flows.
At step 3112, financial institution 106 may analyze by machine learning the financial history data, the account history data, the non-financial data and the aggregated data. At step 3114, financial institution 106 may determine a future account balance of the account based on the analysis performed in step 3114. At step 3116, financial institution 106 may determine, based on the future account balance, whether the first account will enter a low-cash mode state, as disclosed herein. At step 3118, financial institution may determine a danger time period for the customer or the account, as disclosed herein.
System for Communication Through Social Media
In some embodiments, the financial institution may urge or permit customers to link financial accounts with social media accounts. The link between accounts may provide financial institution with access to information gathered by the social media account and associated applications. The link may also provide another channel for financial institution to send alerts or messages to a customer. For example, a customer could receive a message via a social network instant or direct message that the account has entered low cash mode.
Additionally or alternatively, the financial institution may provide a customer with the option to associate a social media account associated with the customer with a financial account. The financial institution may then interact with the customer using the notifications and infrastructure provided by the social media platform. For example, the financial institution may provide a notification that an account associated with a user has entered low cash mode using Facebook Messenger or Twitter Direct Message. The financial institution may also access or analyze data associated with a customer's social media profile, presence, usage, activity, connections, or other social media data.
At step 2208, financial institution 106 may receive permission to link the account at financial institution 106 associated with the customer with the social media account associated with the customer. At step 2210, financial institution may link the account at financial institution 106 associated with the customer with the social media account associated with the customer.
At step 2212, financial institution 106 may determine an account balance of the account. At step 2214, financial institution 106 may determine, based on the account balance, whether the account is deemed to be in a low-cash mode state, as disclosed herein. At step 2216, if the account is deemed to be in a low-cash mode state, financial institution 106 may provide a notification to the customer that the account is deemed to be in a low-cash mode state via the social media account associated with the customer.
System for Geolocation Based Alerts
In some embodiments, financial institution may offer customers the option to designate payments based on a user's location (as discussed herein). A customer may, for example, use a mobile device that is associated with a customer account. The mobile device may have a GPS or be otherwise configured with location services to determine the location of the mobile device. When the mobile device determines that the location of the mobile device is within a predetermined distance from a merchant while the customer's account is in low cash mode, the mobile device may provide a notification to the customer and provide the customer with the option of designating the merchant for payment processing during low cash mode.
In some embodiments, financial institution may offer a geolocation alert service. The geolocation alert service includes a customer carrying a mobile device with a global positioning system or other location services. The mobile device may determine a location of the mobile device and communicate the location to the financial institution or to a mobile application associated with the financial institution. The financial institution, either through its own servers or through the mobile application, may determine whether the location is associated with a merchant and whether the customer account associated with the mobile device is low cash mode. If the financial institution determines that the customer account is in low cash mode and the location is associated with a merchant, the financial institution may notify the customer that the customer account is in low cash mode. The financial institution may provide such notification by, for example, sending a text message to a phone number associated with the customer account, sending an email to an email address associated with the customer account, sending a push notification to the mobile device via the mobile application, and/or any other notification disclosed herein.
In some embodiments, the geolocation alert service may similarly notify the customer when the customer account is within a certain range of the threshold for entering low cash mode. For example, the financial institution may notify the customer that the customer's account is within a specified dollar amount of entering low cash mode when the customer carries their mobile device to a merchant.
In some embodiments, the financial institution may notify more than one customer associated with a customer account when the customer account is in low cash mode and the location is associated with a merchant. For example, when one of multiple customers associated with an account enters a location associated with a merchant, the financial institution may notify all associated customers that the customer account is in low cash mode and that one of the customers is entering a merchant. This is particularly useful in joint accounts where one joint account holder would otherwise be able to spend while the customer account is in low cash mode without the knowledge of the other joint account holder. In some embodiments, the financial institution may allow customers to set parental controls or designate one or more controlling agents so that notifications are sent to one or more parents or controlling agents.
In some embodiments, the geolocation alert service may be enabled based on predicted danger conditions. One or more customers, parents, or controlling agents may, for example, may determine a danger condition under which they will be notified through the geolocation alert service. The danger condition may be any condition that is predicted to result in a high financial risk or a high risk of a customer account entering low cash mode. For example, the danger condition may be the mobile device entering a location associated with a merchant known for selling high-value products. Under such a danger condition, the geolocation alert service would assist customers with taking informed and financially responsible actions by notifying them when they could end up spending a high amount of money and thereby cause a customer account to enter low cash mode.
Other examples of danger conditions include merchants determined to be disreputable, merchants with high interest rates, merchants at which the customer account has previously entered low cash mode, merchants at which other customer accounts have entered low cash mode, a time or time period associated with impulsive buying or other customer accounts entering low cash mode, and a time or time period associated with a customer's regular income receipt.
In some embodiments, the financial institution may request or require the consent of the customer to enable the geolocation alert service. The financial institution may, by way of example, request permission from a customer to enable the geolocation alert service when a customer installs the mobile application on a mobile device, or the financial institution may require the consent of the customer to enable the geolocation alert service and accept various terms upon installation of the mobile application.
At step 3210, financial institution 106 may determine an account balance of the account. At step 3212, financial institution 106 may determine, based on the account balance, whether the account is deemed to be in a low-cash mode state, as disclosed herein.
At step 3214, financial institution may determine the location of the first customer via the first device. At step 3216, financial institution may determine if the location of the first customer is associated with a merchant. At step 3218, financial institution may provide a notification to the first customer, the second customer, or both, as disclosed herein.
At step 3316, financial institution 106 may analyze by machine learning the financial history data, the account history data, the aggregated data and the non-financial data. At step 3318, financial institution 106 may determine a future account balance of the account based on the analysis performed in step 3316. At step 3320, financial institution 106 may determine, based on the future account balance, whether the first account will enter a low-cash mode state, as disclosed herein.
At step 3322, financial institution may determine the location of the first customer via the first device. At step 32163324 financial institution may determine if the location of the first customer is associated with a merchant. At step 3326, financial institution may provide a notification to the first customer, the multiple customers, or both, as disclosed herein.
At step 3416, financial institution 106 may analyze by machine learning the financial history data, the account history data, the aggregated data and the non-financial data. At step 3418, financial institution 106 may determine a future account balance of the account based on the analysis performed in step 3416. At step 3420, financial institution 106 may determine, based on the future account balance, whether the first account will enter a low-cash mode state, as disclosed herein.
At step 3422, financial institution may determine the location of the first customer via the first device. At step 3424, financial institution may determine a danger condition. At step 3326, financial institution may provide a notification to the first customer, the multiple customers, or both, as disclosed herein.
Systems for Exemptions from Low-Cash Mode
In some embodiments, financial institution may provide the customer with one or more low cash mode payment recommendations (such as grocery recommendations as discussed herein). When additional payments are made by a customer whose account is in low cash mode, financial institution may use customer data, customer account data, financial institution data, third party data, or a combination thereof to determine an optimal way for the customer to schedule payments. For example, the financial institution may analyze the scheduled payments for the customer account and a fee schedule associated with the customer account and recommend which scheduled payments the customer should pay in order to minimize incurring fees. Low cash mode payment recommendations benefit the financial institution by providing customers with advice that may mitigate their risk profile to the financial institution and by increasing customer satisfaction with the financial institution. Low cash mode payment recommendations benefits customers by empowering them with information and flexibility while aiding their financial decisions when funds are insufficient and financial advice is needed most.
In some embodiments, financial institution may offer customers various options to process designated transactions for processing even while in low cash mode. For example, financial institution may offer customers the option to designate payments for processing that are made at a grocery store (as discussed above) even while in low cash mode. The financial institution may offer customers options to designate particular merchants or types of payments prior to or upon the customer's account entering low cash mode. Financial institution may also offer customers the option to designate particular merchants or types of payment while the customer's account is in low cash mode.
In some embodiments, financial institution may provide the customer with a list of merchants and the customer may select one or more merchants from the list. The financial institution will then process transactions initiated by the selected merchants while the associated account is in low cash mode. In some embodiments, financial institution provides the user with a list of types of payments and the user selects one or more types of payment from the list. The financial institution will then process transactions corresponding to the selected payments while the associated account in in low cash mode. The types of payment may include, for example, payment categories. The financial institution may obtain payment categories from a third party or determine such payment categories using financial data and historical financial transaction data associated with a particular merchant, payment amount, or time of payment.
Systems Providing User Interface
In some embodiments, as used herein, micro-applications may be used to implement a low cash mode of operation as displayed on a graphical user interface or webpage (as discussed above) or on a mobile device (as discussed below). For example, a low cash mode may be used to refer to when an account balance in a financial account drops beneath a predetermined threshold value, and additionally, to options presented by financial service provider 110 (e.g. personal loan, transfer of fund, and the like) when financial service provider 110 determines that an account has insufficient funds to handle a transaction without resulting in a negative balance.
In some embodiments, balance data for each of the three deposit accounts 322, 324 and for the credit account 326 may also be shown as part of webpage 302 as shown in
In some embodiments, a customer may be provided with a user interface. The user interface may provide the customer with a variety of notifications, such as notifications triggered when the customer's account enters or exits low cash mode as well as notifications providing education as to the features an options available for accounts in low cash mode. The user interface may also be configured to display a variety of settings, including display settings, notification settings, customer account settings, and low cash mode settings. In addition to displaying these settings, the user interface allows a user, which may or may not be the customer, to adjust these settings. By displaying the settings in an aesthetically pleasing and intuitive manner, a user may feel more informed and empowered to control their customer account and the functionality of low cash mode. In some embodiments, the user interface is customizable such that portions of the user interface may be rearranged according to the needs or preferences of the user. In some embodiments, the customizability of the user interface is reduced to promote uniformity of user experience across a variety of users.
The user interface may be provided on a variety of devices, such as mobile devices, tablets, laptops, desktop computers. Automated Teller Machines (ATMs), or other devices. Furthermore, the user interface may be provided for use by a single user or may be configured for use by more than one user, such as a user interface configured to provide access to many users at a publicly accessible device.
In some embodiments, the user interface comprises one or more panels. Each panel may include text or images to provide a user with account information, or provide a user with notifications regarding such account information. The account information may include low cash mode information associated with a customer account, such as a balance available to the user, current settings of low cash mode, funding options, fund transfer information, fund deposit information, time remaining until overdraft or other fees are incurred, overdraft or other fees being avoided by the user's actions or settings over various periods of time, current payment control settings, and payments available for viewing by a user. In some embodiments, the account information includes payment control information, such as protected balance, available balance, returned payments, payment schedules, and payment decision deadlines.
When a user interacts with one or more panels (for example by tapping, swiping, clicking with a cursor, or otherwise performing an action indicative of a user's choice), the user interface may change to include new or additional information displayed through the interface or provide a user with new or additional settings. For example, one panel may include information regarding a balance available through low cash mode. When the user interacts with the panel, the user interface may change to display more detailed information regarding the available balance, such as a transaction history or a detailed time stamp for when low cash mode was enabled. In some embodiments, one panel may include payment control notifications. When the user interacts with the panel, the user interface may change to display payment control information, settings, and/or choices. Such payment control choices may include, for example, buttons enabling the user to select payments the user does not want paid using the customer account.
While some features relating services, technologies, and features offered by a financial services provider have been described with respect to the above embodiments, it should be understood that they are not limited thereto, and that various other features may be included or featured. The accompanying figures are intended to provide exemplary views for purposes of explaining systems and methods described herein, and they are not intended to limit the scope of those features or interfaces.
In some embodiments, some or all of the logic for the above-described techniques may be implemented as a computer program, as an application, or as a plug-in module or sub-component of another application. The described techniques may be varied and are not limited to the examples or descriptions provided. In some examples applications may be developed for download to mobile communications and computing systems, e.g., laptops, mobile computers, tablet computers, smartphones, etc., being made available for download by the customer either directly from the device or through a website.
Moreover, while illustrative embodiments have been described herein, the scope thereof includes any and all embodiments having equivalent elements, modifications, omissions, combinations (e.g., of aspects across various embodiments), adaptations and/or alterations as would be appreciated by those in the art based on the present disclosure. For example, the number and orientation of components shown in the exemplary systems may be modified. Further, with respect to the exemplary methods illustrated in the attached drawings, the order and sequence of steps may be modified or combined, and/or steps may be added or deleted.
Thus, 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 will be apparent to those skilled in the art from consideration of the specification and practice of the disclosed embodiments. For example, while a financial institution may have been described herein as the entity managing and/or maintaining the financial accounts 130 and providing the graphical user interface 118 for user device 108, it is to be understood that, consistent with disclosed embodiments, another entity may provide such services in conjunction with or separate from a financial institution. For example, third-party service provider 110 may provide some or all of the above-described functions.
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. Accordingly, the examples presented herein are to be construed as non-exclusive. Further, the steps of the disclosed methods may be modified in any manner, including by reordering steps and/or inserting or deleting steps.
Furthermore, although aspects of the disclosed embodiments are described as being associated with data stored in memory and other tangible computer-readable storage mediums, one skilled in the art will appreciate that these aspects can also be stored on and executed from many types of tangible computer-readable media, such as secondary storage devices, like hard disks, floppy disks, or CD-ROM, or other forms of RAM or ROM. Accordingly, the disclosed embodiments are not limited to the above-described examples but, instead, are defined by the appended claims in light of their full scope of equivalents.
This application is a continuation of U.S. application Ser. No. 17/027,250, filed Sep. 21, 2020, which claims priority to Provisional U.S. Patent Application Ser. No. 62/983,572, filed Feb. 28, 2020, the disclosures of which are incorporated herein by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3626381 | Dubinsky et al. | Dec 1971 | A |
| 3702006 | Page | Oct 1972 | A |
| 4340879 | Laflamme | Jul 1982 | A |
| 5491795 | Beaudet et al. | Feb 1996 | A |
| 5644727 | Atkins | Jul 1997 | A |
| 5699528 | Hogan | Dec 1997 | A |
| 5734915 | Roewer | Mar 1998 | A |
| 5819236 | Josephson | Oct 1998 | A |
| 6373930 | McConnell et al. | Apr 2002 | B1 |
| 6535855 | Cahill et al. | Mar 2003 | B1 |
| 7140036 | Bhagavatula et al. | Nov 2006 | B2 |
| 7213266 | Maher et al. | May 2007 | B1 |
| 7624052 | Seaman et al. | Nov 2009 | B1 |
| 7681228 | Mizrah | Mar 2010 | B2 |
| 7765580 | Vandergeest et al. | Jul 2010 | B2 |
| 7937305 | Lego et al. | May 2011 | B1 |
| 8061592 | Clem et al. | Nov 2011 | B1 |
| 8065230 | Little | Nov 2011 | B1 |
| 8073472 | Thakur et al. | Dec 2011 | B1 |
| 8311935 | Balachandran et al. | Nov 2012 | B2 |
| 8374963 | Billman | Feb 2013 | B1 |
| 8380618 | Kazenas et al. | Feb 2013 | B1 |
| 8380623 | Ley et al. | Feb 2013 | B1 |
| 8423440 | Mackrell et al. | Apr 2013 | B1 |
| 8423452 | Ley et al. | Apr 2013 | B1 |
| 8458089 | Gareis | Jun 2013 | B1 |
| 8495384 | DeLuccia | Jul 2013 | B1 |
| 8504455 | Balestreire et al. | Aug 2013 | B1 |
| 8602296 | Velline et al. | Dec 2013 | B1 |
| 8606714 | Cameo et al. | Dec 2013 | B1 |
| 8676642 | Sheley | Mar 2014 | B1 |
| 8719132 | Diggdon et al. | May 2014 | B1 |
| 8856807 | Khapre et al. | Oct 2014 | B1 |
| 9047639 | Quintiliani et al. | Jun 2015 | B1 |
| 9552272 | Liang et al. | Jan 2017 | B1 |
| 9881296 | Paulin et al. | Jan 2018 | B1 |
| 9965808 | Kunz et al. | May 2018 | B1 |
| 10169812 | Bajgier et al. | Jan 2019 | B1 |
| 10169946 | Benkreira et al. | Jan 2019 | B1 |
| 10242402 | Soccorsy et al. | Mar 2019 | B1 |
| 10270808 | Sherif et al. | Apr 2019 | B1 |
| 10373131 | Hsieh et al. | Aug 2019 | B2 |
| 10373248 | Casey et al. | Aug 2019 | B1 |
| 10380659 | Benkreira et al. | Aug 2019 | B1 |
| 10395287 | Lowell et al. | Aug 2019 | B1 |
| 10402829 | Baar et al. | Sep 2019 | B1 |
| 10423947 | Baar et al. | Sep 2019 | B1 |
| 10462619 | Diaconu et al. | Oct 2019 | B2 |
| 10474736 | Stoica et al. | Nov 2019 | B1 |
| 10521796 | Newman et al. | Dec 2019 | B1 |
| 10599490 | Caraccioli | Mar 2020 | B1 |
| 10636087 | Bardouille et al. | Apr 2020 | B1 |
| 10665238 | Bermudez-Cisneros | May 2020 | B1 |
| 10755281 | Yip et al. | Aug 2020 | B1 |
| 10768952 | Watson et al. | Sep 2020 | B1 |
| 10805465 | Krebs et al. | Oct 2020 | B1 |
| 10878408 | Kurani et al. | Dec 2020 | B1 |
| 10909618 | Mortensen et al. | Feb 2021 | B1 |
| 10963589 | Fakhraie et al. | Mar 2021 | B1 |
| 10970778 | Starbuck et al. | Apr 2021 | B1 |
| 10977725 | Flowers et al. | Apr 2021 | B1 |
| 10984434 | Arya et al. | Apr 2021 | B1 |
| 10990980 | Reses et al. | Apr 2021 | B1 |
| 10992679 | Fakhraie et al. | Apr 2021 | B1 |
| 10997592 | Kurani | May 2021 | B1 |
| 11037167 | Duke et al. | Jun 2021 | B1 |
| 11079919 | Soccorsy | Aug 2021 | B1 |
| 11144989 | Bardouille et al. | Oct 2021 | B1 |
| 11270279 | Rozovski et al. | Mar 2022 | B1 |
| 11386223 | Fakhraie et al. | Jul 2022 | B1 |
| 11463576 | Gordon et al. | Oct 2022 | B1 |
| 11556936 | Fisher | Jan 2023 | B1 |
| 11574359 | Ball et al. | Feb 2023 | B1 |
| 20010037451 | Bhagavatula et al. | Nov 2001 | A1 |
| 20020026423 | Maritzen et al. | Feb 2002 | A1 |
| 20020029189 | Titus et al. | Mar 2002 | A1 |
| 20020082892 | Raffel et al. | Jun 2002 | A1 |
| 20020091635 | Dilip et al. | Jul 2002 | A1 |
| 20030043978 | Gallagher | Mar 2003 | A1 |
| 20030105692 | Gilbert et al. | Jun 2003 | A1 |
| 20030105707 | Audebert et al. | Jun 2003 | A1 |
| 20040039694 | Dunn | Feb 2004 | A1 |
| 20040098338 | Uehara et al. | May 2004 | A1 |
| 20040148517 | Banks-Binici et al. | Jul 2004 | A1 |
| 20040158521 | Newton et al. | Aug 2004 | A1 |
| 20050171811 | Campbell et al. | Aug 2005 | A1 |
| 20050211765 | Brown et al. | Sep 2005 | A1 |
| 20050263588 | Babi | Dec 2005 | A1 |
| 20060047588 | Lal et al. | Mar 2006 | A1 |
| 20060218006 | Malik | Sep 2006 | A1 |
| 20060235795 | Johnson et al. | Oct 2006 | A1 |
| 20070033103 | Collins et al. | Feb 2007 | A1 |
| 20070124358 | Levi et al. | May 2007 | A1 |
| 20070130065 | Staab et al. | Jun 2007 | A1 |
| 20070260562 | Hutson et al. | Nov 2007 | A1 |
| 20070283416 | Renaud | Dec 2007 | A1 |
| 20080010192 | Rackley, III | Jan 2008 | A1 |
| 20080040265 | Rackley, III et al. | Feb 2008 | A1 |
| 20080103970 | Books et al. | May 2008 | A1 |
| 20080168393 | Rosskopt | Jul 2008 | A1 |
| 20080298569 | Monk | Dec 2008 | A1 |
| 20080307220 | Campbell | Dec 2008 | A1 |
| 20090043604 | Jung et al. | Feb 2009 | A1 |
| 20090043699 | Elterich | Feb 2009 | A1 |
| 20090081989 | Wuhrer | Mar 2009 | A1 |
| 20090089205 | Bayne | Apr 2009 | A1 |
| 20090106365 | Drory et al. | Apr 2009 | A1 |
| 20090204538 | Ley et al. | Aug 2009 | A1 |
| 20090271287 | Halpern | Oct 2009 | A1 |
| 20090271315 | Hammad | Oct 2009 | A1 |
| 20090276839 | Peneder | Nov 2009 | A1 |
| 20090288012 | Hertel et al. | Nov 2009 | A1 |
| 20090313304 | Goodger et al. | Dec 2009 | A1 |
| 20100019030 | Monk | Jan 2010 | A1 |
| 20100023390 | Kim | Jan 2010 | A1 |
| 20100086112 | Jiang et al. | Apr 2010 | A1 |
| 20100100469 | Buchanan et al. | Apr 2010 | A1 |
| 20100153247 | DiPaolo et al. | Jun 2010 | A1 |
| 20100153260 | Moebs et al. | Jun 2010 | A1 |
| 20100199338 | Craddock et al. | Aug 2010 | A1 |
| 20100312700 | Coulter et al. | Dec 2010 | A1 |
| 20110076989 | Lynch | Mar 2011 | A1 |
| 20110125643 | Cameo et al. | May 2011 | A1 |
| 20110153447 | Thomas et al. | Jun 2011 | A1 |
| 20110161182 | Racco | Jun 2011 | A1 |
| 20110183745 | Gagner et al. | Jul 2011 | A1 |
| 20110194676 | Hogan et al. | Aug 2011 | A1 |
| 20110201408 | Gagner et al. | Aug 2011 | A1 |
| 20110208629 | Benefield et al. | Aug 2011 | A1 |
| 20110295731 | Waldron, III et al. | Dec 2011 | A1 |
| 20120046011 | Thakur et al. | Feb 2012 | A1 |
| 20120054093 | Schamer et al. | Mar 2012 | A1 |
| 20120130786 | Marshall | May 2012 | A1 |
| 20120130894 | Pendleton | May 2012 | A1 |
| 20120179604 | Blain et al. | Jul 2012 | A1 |
| 20120185843 | Burke et al. | Jul 2012 | A1 |
| 20120197743 | Grigg et al. | Aug 2012 | A1 |
| 20130013506 | Wiggins et al. | Jan 2013 | A1 |
| 20130036058 | Kelly et al. | Feb 2013 | A1 |
| 20130067328 | Salyards et al. | Mar 2013 | A1 |
| 20130080471 | Forte et al. | Mar 2013 | A1 |
| 20130103577 | Lawson et al. | Apr 2013 | A1 |
| 20130145148 | Shablygin et al. | Jun 2013 | A1 |
| 20130204862 | Marchiori | Aug 2013 | A1 |
| 20130212021 | Kingston et al. | Aug 2013 | A1 |
| 20130269014 | Gerber | Oct 2013 | A1 |
| 20130339188 | Mohamed et al. | Dec 2013 | A1 |
| 20130346177 | Jung et al. | Dec 2013 | A1 |
| 20130346302 | Purves et al. | Dec 2013 | A1 |
| 20140012746 | Hanson et al. | Jan 2014 | A1 |
| 20140032406 | Roach et al. | Jan 2014 | A1 |
| 20140038546 | Neal et al. | Feb 2014 | A1 |
| 20140067654 | Hansonj et al. | Mar 2014 | A1 |
| 20140081853 | Sanchez et al. | Mar 2014 | A1 |
| 20140082097 | Athale et al. | Mar 2014 | A1 |
| 20140089191 | Brown | Mar 2014 | A1 |
| 20140095392 | Rose et al. | Apr 2014 | A1 |
| 20140129303 | Aiglstorfer | May 2014 | A1 |
| 20140156785 | Kammula et al. | Jun 2014 | A1 |
| 20140164062 | Wen et al. | Jun 2014 | A1 |
| 20140164199 | Wilkes | Jun 2014 | A1 |
| 20140172695 | Kanjlia et al. | Jun 2014 | A1 |
| 20140180919 | Brown | Jun 2014 | A1 |
| 20140195422 | Zheng et al. | Jul 2014 | A1 |
| 20140214668 | Lotter et al. | Jul 2014 | A1 |
| 20140258088 | Belarj | Sep 2014 | A1 |
| 20140279332 | Poole | Sep 2014 | A1 |
| 20140279438 | Reiff et al. | Sep 2014 | A1 |
| 20140279460 | Weiss et al. | Sep 2014 | A1 |
| 20140279513 | Dodds-Brown et al. | Sep 2014 | A1 |
| 20140310153 | Patel | Oct 2014 | A1 |
| 20140358799 | Kingston et al. | Dec 2014 | A1 |
| 20150026025 | Calman et al. | Jan 2015 | A1 |
| 20150026026 | Calman et al. | Jan 2015 | A1 |
| 20150058219 | Grossman et al. | Feb 2015 | A1 |
| 20150067822 | Randall | Mar 2015 | A1 |
| 20150073952 | Ventura et al. | Mar 2015 | A1 |
| 20150073959 | Connors et al. | Mar 2015 | A1 |
| 20150081491 | Brereton et al. | Mar 2015 | A1 |
| 20150081495 | Randall | Mar 2015 | A1 |
| 20150095216 | Van Heerden et al. | Apr 2015 | A1 |
| 20150100442 | Van Heerden et al. | Apr 2015 | A1 |
| 20150100443 | Van Heerden et al. | Apr 2015 | A1 |
| 20150106267 | Lee | Apr 2015 | A1 |
| 20150112870 | Nagasundaram et al. | Apr 2015 | A1 |
| 20150127530 | Wick et al. | May 2015 | A1 |
| 20150143256 | Panchawagh-Jain et al. | May 2015 | A1 |
| 20150161576 | Keen | Jun 2015 | A1 |
| 20150178693 | Solis | Jun 2015 | A1 |
| 20150178725 | Poetsch | Jun 2015 | A1 |
| 20150193774 | Wetzel | Jul 2015 | A1 |
| 20150193866 | Van Heerden et al. | Jul 2015 | A1 |
| 20150193867 | Del Vecchio et al. | Jul 2015 | A1 |
| 20150193868 | Del Vecchio et al. | Jul 2015 | A1 |
| 20150193869 | Del Vecchio et al. | Jul 2015 | A1 |
| 20150206252 | Rephlo et al. | Jul 2015 | A1 |
| 20150220923 | Vasant Akole et al. | Aug 2015 | A1 |
| 20150227869 | Saraf et al. | Aug 2015 | A1 |
| 20150262182 | Gervais et al. | Sep 2015 | A1 |
| 20150262183 | Gervais et al. | Sep 2015 | A1 |
| 20150278796 | Jiang et al. | Oct 2015 | A1 |
| 20150302444 | Sundaresan | Oct 2015 | A1 |
| 20150339641 | Krietzman et al. | Nov 2015 | A1 |
| 20150350457 | Lauer | Dec 2015 | A1 |
| 20150379072 | Dirac et al. | Dec 2015 | A1 |
| 20150379644 | Danielak et al. | Dec 2015 | A1 |
| 20160019536 | Ortiz et al. | Jan 2016 | A1 |
| 20160042405 | Zeng et al. | Feb 2016 | A1 |
| 20160048842 | Trivedi et al. | Feb 2016 | A1 |
| 20160063478 | Koeppel et al. | Mar 2016 | A1 |
| 20160078503 | Wang | Mar 2016 | A1 |
| 20160162923 | Meier | Jun 2016 | A1 |
| 20160180315 | Kanamori | Jun 2016 | A1 |
| 20160180316 | Wang et al. | Jun 2016 | A1 |
| 20160189123 | Lucia Specogna et al. | Jun 2016 | A1 |
| 20160203483 | Bridgewater et al. | Jul 2016 | A1 |
| 20160225278 | Leddy | Aug 2016 | A1 |
| 20160247233 | Page | Aug 2016 | A1 |
| 20160104237 | Kanjlia et al. | Oct 2016 | A1 |
| 20160300204 | Guido et al. | Oct 2016 | A1 |
| 20160328692 | Camps et al. | Nov 2016 | A1 |
| 20160328698 | Kumaraguruparan et al. | Nov 2016 | A1 |
| 20160343075 | Chandler | Nov 2016 | A1 |
| 20170004506 | Steinman et al. | Jan 2017 | A1 |
| 20170011398 | Narisimhan | Jan 2017 | A1 |
| 20170011399 | Steinlicht et al. | Jan 2017 | A1 |
| 20170032343 | Kurniadi et al. | Feb 2017 | A1 |
| 20170046651 | Lin et al. | Feb 2017 | A1 |
| 20170046688 | Pande | Feb 2017 | A1 |
| 20170061535 | Williams | Mar 2017 | A1 |
| 20170063735 | Gillespie et al. | Mar 2017 | A1 |
| 20170063840 | Krishnaia | Mar 2017 | A1 |
| 20170076377 | Myers | Mar 2017 | A1 |
| 20170083930 | Nagaraj et al. | Mar 2017 | A1 |
| 20170091765 | Lloyd et al. | Mar 2017 | A1 |
| 20170132719 | Rogers | May 2017 | A1 |
| 20170154351 | Venugopalan et al. | Jun 2017 | A1 |
| 20170163471 | Zheng | Jun 2017 | A1 |
| 20170178110 | Swanson et al. | Jun 2017 | A1 |
| 20170178113 | Mugford et al. | Jun 2017 | A1 |
| 20170178131 | Fernandez et al. | Jun 2017 | A1 |
| 20170178135 | Bull et al. | Jun 2017 | A1 |
| 20170193501 | Cole et al. | Jul 2017 | A1 |
| 20170195993 | Cole et al. | Jul 2017 | A1 |
| 20170243028 | LaFever et al. | Aug 2017 | A1 |
| 20170293972 | van Bemmelen | Oct 2017 | A1 |
| 20170300895 | Shanmugam | Oct 2017 | A1 |
| 20170300906 | Shanmugam | Oct 2017 | A1 |
| 20170315700 | Rolih et al. | Nov 2017 | A1 |
| 20170316506 | Lesner et al. | Nov 2017 | A1 |
| 20170323345 | Flowers et al. | Nov 2017 | A1 |
| 20170344985 | Weisser | Nov 2017 | A1 |
| 20170364919 | Ranganath et al. | Dec 2017 | A1 |
| 20180005229 | Grassadonia | Jan 2018 | A1 |
| 20180005323 | Grassadonia | Jan 2018 | A1 |
| 20180025421 | Schamer et al. | Jan 2018 | A1 |
| 20180026960 | Votaw et al. | Jan 2018 | A1 |
| 20180039791 | Beye et al. | Feb 2018 | A1 |
| 20180060843 | Maheshwari | Mar 2018 | A1 |
| 20180068294 | Melgar et al. | Mar 2018 | A1 |
| 20180082321 | Boccardi et al. | Mar 2018 | A1 |
| 20180114212 | Beck et al. | Apr 2018 | A1 |
| 20180165977 | Johansen et al. | Jun 2018 | A1 |
| 20180181966 | Rao et al. | Jun 2018 | A1 |
| 20180189829 | Patwardhan et al. | Jul 2018 | A1 |
| 20180197171 | Steinman et al. | Jul 2018 | A1 |
| 20180218366 | Storiale | Aug 2018 | A1 |
| 20180240108 | Boss et al. | Aug 2018 | A1 |
| 20180253727 | Ortiz et al. | Sep 2018 | A1 |
| 20180276287 | Kurian et al. | Sep 2018 | A1 |
| 20180335928 | Van Os et al. | Nov 2018 | A1 |
| 20180336543 | Van Os et al. | Nov 2018 | A1 |
| 20180336557 | Khurana et al. | Nov 2018 | A1 |
| 20180367526 | Huang et al. | Dec 2018 | A1 |
| 20190020651 | Soon-Shiong et al. | Jan 2019 | A1 |
| 20190037642 | Price et al. | Jan 2019 | A1 |
| 20190110188 | Dunjic et al. | Apr 2019 | A1 |
| 20190114702 | Nicholson et al. | Apr 2019 | A1 |
| 20190122307 | Sayed | Apr 2019 | A1 |
| 20190180524 | Palmer et al. | Jun 2019 | A1 |
| 20190197617 | Chopra | Jun 2019 | A1 |
| 20190205872 | Tourne et al. | Jul 2019 | A1 |
| 20190207754 | Lyer et al. | Jul 2019 | A1 |
| 20190251249 | Sprague et al. | Aug 2019 | A1 |
| 20190259095 | Templeton | Aug 2019 | A1 |
| 20190295158 | Wu | Sep 2019 | A1 |
| 20190303924 | Knorr | Oct 2019 | A1 |
| 20190311566 | Benkreira et al. | Oct 2019 | A1 |
| 20190325442 | Norman et al. | Oct 2019 | A1 |
| 20190325448 | Barakat et al. | Oct 2019 | A1 |
| 20190354979 | Crawford | Nov 2019 | A1 |
| 20190355063 | Probetts | Nov 2019 | A1 |
| 20190355464 | Brownfield | Nov 2019 | A1 |
| 20190377864 | Mossoba et al. | Dec 2019 | A1 |
| 20190385223 | Sharma | Dec 2019 | A1 |
| 20190392441 | Lee et al. | Dec 2019 | A1 |
| 20200065809 | Elfeky | Feb 2020 | A1 |
| 20200074565 | Dotter | Mar 2020 | A1 |
| 20200090261 | Tumulty, II et al. | Mar 2020 | A1 |
| 20200104845 | Riechers et al. | Apr 2020 | A1 |
| 20200105254 | Sarir et al. | Apr 2020 | A1 |
| 20200111494 | Lau et al. | Apr 2020 | A1 |
| 20200120049 | Galloway | Apr 2020 | A1 |
| 20200126087 | Benkreira et al. | Apr 2020 | A1 |
| 20200126135 | Venuraju et al. | Apr 2020 | A1 |
| 20200175566 | Bender et al. | Jun 2020 | A1 |
| 20200211013 | Franceschi | Jul 2020 | A1 |
| 20200242232 | Mechani | Jul 2020 | A1 |
| 20200265457 | Miller et al. | Aug 2020 | A1 |
| 20200286093 | Agrawal et al. | Sep 2020 | A1 |
| 20200302425 | Artemiw et al. | Sep 2020 | A1 |
| 20200342379 | Phillips et al. | Oct 2020 | A1 |
| 20200349642 | Kumar et al. | Nov 2020 | A1 |
| 20200380528 | Ganapathy et al. | Dec 2020 | A1 |
| 20200394638 | Mcleod et al. | Dec 2020 | A1 |
| 20200402155 | Kurian et al. | Dec 2020 | A1 |
| 20210019718 | Moskowitz et al. | Jan 2021 | A1 |
| 20210019755 | Omojola et al. | Jan 2021 | A1 |
| 20210019822 | Edwards et al. | Jan 2021 | A1 |
| 20210042723 | Walters | Feb 2021 | A1 |
| 20210042724 | Rathod | Feb 2021 | A1 |
| 20210073906 | Bailey | Mar 2021 | A1 |
| 20210082043 | Kanjlia et al. | Mar 2021 | A1 |
| 20210110373 | Bhusri et al. | Apr 2021 | A1 |
| 20210110470 | Schamer et al. | Apr 2021 | A1 |
| 20210125287 | Fasoli et al. | Apr 2021 | A1 |
| 20210133869 | Brock et al. | May 2021 | A1 |
| 20210182850 | Morse et al. | Jun 2021 | A1 |
| 20210217104 | Phillips et al. | Jul 2021 | A1 |
| 20210241333 | Lindsey et al. | Aug 2021 | A1 |
| 20220005036 | Reses et al. | Jan 2022 | A1 |
| 20220084134 | Brock et al. | Mar 2022 | A1 |
| 20220114602 | Horn, III et al. | Apr 2022 | A1 |
| 20220319283 | Misra et al. | Oct 2022 | A1 |
| 20230049204 | Reses et al. | Feb 2023 | A1 |
| Number | Date | Country |
|---|---|---|
| WO-2011112752 | Sep 2011 | WO |
| WO 2014071261 | May 2014 | WO |
| WO 2015192208 | Dec 2015 | WO |
| WO-2017072647 | May 2017 | WO |
| Entry |
|---|
| “Impacts of Overdraft Programs on Consumers”, Jun. 2012, Available At: https://www.govinfo.gov/content/pkg/FR-2012-02-28/pdf/2012-4576.pdf (Year: 2012). |
| “Overdraft Protection: Opt-In Requirements and Related Marketing Issues”, OCC Bulletin 2010-15, Apr. 12, 2010 Available at: https://www.occ.treas.gov/news-issuances/bulletins/2010/bulletin-2010-15.html (Year: 2010). |
| “PNC Financial (PNC) Removes NSF Fees for Consumer Accounts”, Zacks Equity Research, Yahoo Finance, Aug. 15, 2022, 3 pages. |
| “PNC Launches Low Cash Mode(SM) to Address $17 Billion in Industry Overdraft Fees”, The PNC Financial Services Group, Inc., Apr. 13, 2021, 5 pages. |
| “Protecting Consumers from Abusive Overdraft Fees”, Feb. 2009, Available At: https://www.govinfo.gov/content/pkg/CHRG-111shrg56975/pdf/CHRG-111shrg56975.pdf (Year: 2009). |
| 12 CFR 230—Truth In Savings (Regulation DD), Jan. 1, 2012. Available at: https://www.govinfo.gov/content/pkg/CFR-2012-title12-vol4/xml/CFR-2012-title12-vol4-part230.xml (Year: 2012). |
| Ameris Bank, “Advanced Login Authentication”, 2016, Available at: https://www.amerisbank.com/AmerisBank/media/Documents/Advanced-Login-Authentication.pdf (Year: 2016). |
| Cocheo, Steve, “How PNC Adapted Its Virtual Wallet to Solve Overdraft Complaints”, The Financial Brand, Aug. 25, 2021, 8 pages. |
| Digital Identity Guidelines, NIST 800-63-3, 2017, Available at: https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-63-3.pdf (Year: 2017). |
| FAQs on FFI EC Guidance on Authentication in an Internet Banking Environment, Aug. 2015. Available at: https://www.ffiec.gov/pdf/authentication_faq.pdf. (Year: 2015). |
| FDIC Law, Regulations, Related Acts, 6000—Consumer Protection, Jun. 30, 2016, 23 pages. Available at https://www.ecfr.gov/current/title-12/chapter-X/part-1005/subpart-A?toc=1 (Year: 2016, updated for 2023). |
| FDIC, “Overdraft Payment Programs and Consumer Protection”, 2010. Available at: https://www.fdic.gov/news/financial-institution-letters/2010/fil10081.pdf (Year: 2010). |
| Hrushka, Anna, “PNC's ‘low cash mode’ gives users 24-hour overdraft buffer”, Bankingdive, Apr. 13, 2021, 3 pages. |
| Online Banking Enhanced Authentication, 2014, Available at: https://www.eecu.org/EECU/media/pdfs/ EECU-enhanced-authentication-FAQ.pdf (Year: 2014). |
| Personal knowledge questions for fallback authentication: Security questions in the era of Facebook, 2008, Available at: http://cups.cs.cmu.edu/soups/2008/proceedings/p13Rabkin.pdf (Year: 2008). |
| PNC Bank, “Online Bill Pay”, 2013. Available at: https://content.pncmc.com/live/pnc/SCT/pdfs/Online_Bill_Pay.pdf (Year: 2013). |
| Prior, Jon, “How PNC responded to customers' complaints about overdraft fees”, American Banker, Apr. 13, 2021, 5 pages. |
| Sabatini, Patricia, “Sick of overdraft fees? Pittsburgh's larges bank has a uniquie answer”, Pittsburgh Post-Gazett, Apr. 14, 2021, 2 pages. |
| Tompor, Susan, “Banks, credit unions making changes on how sky-high overdraft fees are handled”, Detroit Free Press, Jun. 11, 2021, 9 pages. |
| UNFCU Digital Banking, 2018, Available at: https://digital.unfcu.org/Apps/Content/Assets/Custom/UNFCU_Digital_Banking_Guide.pdf (Year 2018). |
| United One Credit Union, 2016, Available at: https://www.unitedone.org/files/unitedone/1/file/How%20to%20Reset%20IB%20Security%20Questions.pdf (Year: 2016). |
| “Text and Email Alerts”, PNC Bank, 2013. Available at: https://content.pncmc.com/live/pnc/SCT/pdfs/Text_Email_Alerts.pdf (Year: 2013). |
| “Consumers and Mobile Financial Services”, Federal Reserve, 2016. Available at: https://www.federalreserve.gov/econresdata/consumers-and-mobile-financial-services-report-201603.pdf (Year: 2016). |
| “U.S. Bank ReliaCard”, 2019. Available at: https://uidd.delawareworks.com/Content/USB-ReliaCard%20FAQ.pdf (Year: 2019). |
| “Stack Views.” Jun. 17, 2019. Developer. Apple.com https://developer.apple.com/library/archive/documentation/UserExperience/Conceptual/AutolayoutPG/LayoutUsingStackViews.html (Year: 2019). |
| “UIStackView”, Jul. 25, 2019. https://developer.apple.com/documentation/uikit/uistackview (Year: 2019). |
| Chowdhury, Kunal. “Using StackPanel to define a stacked layout.” O'Reilly Learning Platform. Mastering Visual Studio. 2017 (Year: 2017). |
| “PCI DSS Quick Reference Guide: Understanding the Payment Card Industry Data Security Standard version 3.2.1”, Jul. 2018, 39 pages. Available at: https://listings.pcisecuritystandards.org/documents/PCI_DSS-QRG-v3_2_1.pdf (Year: 2018). |
| Congressional Research Service, “Data Protection Law: An Overview”, Mar. 2019, 79 pages. Available at: https://crsreports.congress.gov/product/pdf/R/R45631 (Year: 2019). |
| Number | Date | Country | |
|---|---|---|---|
| 62983572 | Feb 2020 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 17027250 | Sep 2020 | US |
| Child | 17367746 | US |
