Systems and methods for managing a financial account in a low-cash mode
Abstract
A system for managing a financial account in a low cash mode. The system may include a memory storing instructions, and a processor configured to execute the instructions to perform operations. The operations may include providing an interface; providing a notification to a user when a balance in the first account is deemed to be in low cash mode; presenting, when the first account balance is deemed to be in low cash mode, an option for a transfer request; receiving, a selection of the option for the transfer request to connect the first account with a second account; transferring funds from the second account to the first account; notifying the user that funds have been transferred from the second account to the first account; and further notifying the user that the balance in the first account is greater than the threshold value.
Claims
exact text as granted — not AI-modifiedWhat is claimed is:
1. A system for managing a financial account, comprising:
a memory storing instructions;
a database, in electronic communication with the memory, configured to store information comprising:
financial account information associated with a financial account at a financial institution;
customer information for a customer associated with the financial account;
a mobile device unique identifier for a mobile device associated with the customer; and
an account balance associated with the financial account; and
at least one processor in electronic communication with the database, configured to execute the instructions to perform operations comprising:
providing for display, on a display of a mobile device, a setup dashboard configuration comprising a plurality of setup graphical user interfaces, including:
a first setup interface for receiving a first setting for a low cash mode threshold, wherein the first setup interface allows the user to set the low cash mode threshold;
a second setup interface for receiving a second setting for at least one default payment behavior when a financial account is in a low cash mode, wherein the second setting instructs the at least one processor whether to approve or deny check payments and automatic payments initiated before entering the low cash mode;
a third setup interface for receiving a third setting for enabling a geolocation alert service, the third setup interface consisting of options for geolocation based alerts;
a fourth setup interface displayed in response to selection of the selectable option for the geolocation alert service, the fourth setup interface including:
a manually add location entry field for receiving a fourth setting for a frequent locations list;
replacing the setup dashboard configuration with an account management dashboard configuration comprising one or more account management interfaces associated with processing a plurality of transactions while outside of the low cash mode;
determining a predicted balance of the financial account, by:
retrieving a current balance;
retrieving historical transaction data;
identifying one or more expected transactions based on the historical transaction data;
collecting geolocation data based on current and past geographic locations of the customer;
identifying one or more scheduled transactions; and
generating a predicted balance using a machine learning algorithm wherein the customer's current balance, the customer's historical transaction data, the customer's geolocation data, and the customer's scheduled transactions are inputs for the machine learning algorithm;
determining whether the financial account is in the low cash mode by:
comparing the current balance and the predicted balance to the low cash mode threshold; and
determining that the current balance or the predicted balance is below the low cash mode threshold;
responsive to determining that the financial account is in the low cash mode:
disabling and replacing the account management dashboard configuration with a low cash mode dashboard configuration comprising one or more low cash mode user interfaces different from the setup user interfaces and different from the account management user interfaces, wherein the low cash mode user interfaces comprise:
an indication that the financial account is in the low cash mode;
a set of electronic transaction controls restricted to account funding controls;
one or more default payment controls for processing previously-scheduled automatic payments while the account is in the low-cash mode;
wherein the processor permits a customer to navigate only within the low cash mode dashboard configuration for performing a limited set of electronic banking operations associated with the set of electronic transaction controls and the one or more default payment controls;
determining a geolocation alert, wherein the geolocation alert is determined by obtaining a geographic position of the mobile device, determining whether the geographic position is associated with a merchant, and if the geographic location is associated with a merchant, providing, in at least one of the low cash mode user interfaces, an indication that the customer account is in low cash mode; and
determining whether the merchant is included in the frequent locations list, and if the merchant is included in the frequent locations list, providing, in at least one of the low cash mode user interfaces, an option to disable a smart lock mode for a financial card associated with the financial account.
2. The system of claim 1 , wherein the low cash mode threshold comprises a negative current balance.
3. The system of claim 1 , wherein the low cash mode threshold comprises a predetermined amount.
4. The system of claim 1 , wherein the low cash mode threshold comprises a predetermined percentage of a regularly occurring deposit.
5. The system of claim 1 , wherein the at least one processor is configured to execute the instructions to perform further operations comprising:
determining the account is in the low cash mode by:
determining whether the customer performed a transaction with an online merchant; and
determining that the predicted account balance is negative based on an amount of the transaction.
6. The system of claim 1 , wherein the at least one processor is configured to execute the instructions to perform further operations comprising:
determine the account is in the low-cash mode when at least one of the following occurs:
the system predicts, via the at least one processor, that the account balance after processing a pending transaction is negative based on an amount of the pending transaction;
the system determines, via the at least one processor, that the account balance after processing a scheduled payment is negative based on amount of the scheduled payment;
the system determines, via the at least one processor, that the customer enters a predetermined time period; or
the system determines, via the at least one processor, that a geographic location of the customer corresponds with a geographic location of a merchant with whom the customer has a history of transactions that would cause the account balance to become negative.
7. The system of claim 6 , wherein the at least one processor is configured to execute the instructions to perform further operations comprising:
determine the predetermined time period based on at least one of:
scheduled transactions;
reoccurring transactions;
analysis of historical data; or
relation of current time to an upcoming event.
8. The system of claim 1 , wherein the at least one processor is configured to transmit a notification from the server to the user when the account enters the low cash mode, where the notification comprises at least one of an email, a text message, a voice call, a push notification through an application on a mobile device, a social media alert, an alert through wearable technology, or an alert through a device connected to a network.
9. The system of claim 8 , wherein the at least one processor is further configured to transmit, via the mobile device, a second notification from the server to the customer when the account exits the low-cash mode.
10. A method for managing a financial account, comprising:
providing for display, on a display of a mobile device, a setup dashboard configuration comprising a plurality of setup graphical user interfaces, including:
a first setup interface for receiving a first setting for a low cash mode threshold, wherein the first setup interface allows the user to set the low cash mode threshold;
a second setup interface for receiving a second setting for at least one default payment behavior when a financial account is in a low cash mode, wherein the second setting instructs at least one processor whether to approve or deny check payments and automatic payments initiated before entering the low cash mode;
a third setup interface for receiving a third setting for enabling a geolocation alert service, the third setup interface consisting of options for geolocation based alerts;
a fourth setup interface displayed in response to selection of the selectable option for the geolocation alert service, the fourth setup interface including:
a manually add location entry field for receiving a fourth setting for a frequent locations list;
replacing the setup dashboard configuration with an account management dashboard configuration comprising one or more account management interfaces associated with processing a plurality of transactions while outside of the low cash mode;
determining a predicted balance of the financial account, by:
retrieving a current balance;
retrieving historical transaction data;
identifying one or more expected transactions based on the historical transaction data;
collecting geolocation data based on current and past geographic locations of the customer;
identifying one or more scheduled transactions; and
generating a predicted balance using a machine learning algorithm wherein the customer's current balance, the customer's historical transaction data, the customer's geolocation data, and the customer's scheduled transactions are inputs for the machine learning algorithm;
determining whether the financial account is in the low cash mode by:
comparing the current balance and the predicted balance to the low cash mode threshold; and
determining that the current balance or the predicted balance is below the low cash mode threshold;
responsive to determining that the financial account is in the low cash mode:
disabling and replacing the account management dashboard configuration with a low cash mode dashboard configuration comprising one or more low cash mode user interfaces different from the setup user interfaces and different from the account management user interfaces, wherein the low cash mode user interfaces comprise:
an indication that the financial account is in the low cash mode;
a set of electronic transaction controls restricted to account funding controls;
one or more default payment controls for processing previously-scheduled automatic payments while the account is in the low-cash mode;
wherein the processor permits a customer to navigate only within the low cash mode dashboard configuration for performing a limited set of electronic banking operations associated with the set of electronic transaction controls and the one or more default payment controls;
determining a geolocation alert, wherein the geolocation alert is determined by obtaining a geographic position of the mobile device, determining whether the geographic position is associated with a merchant, and if the geographic location is associated with a merchant, providing, in at least one of the low cash mode user interfaces, an indication that the customer account is in low cash mode; and
determining whether the merchant is included in the frequent locations list, and if the merchant is included in the frequent locations list, providing, in at least one of the low cash mode user interfaces, an option to disable a smart lock mode for a financial card associated with the financial account.
11. The method of claim 10 , wherein the low cash mode threshold comprises a negative current balance.
12. The method of claim 10 , wherein the low cash mode threshold comprises a predetermined amount.
13. The method of claim 10 , wherein the low cash mode threshold comprises a predetermined percentage of a regularly occurring deposit.
14. The method of claim 10 , wherein the account is determined to be in the low cash mode when the predicted balance is negative based on determining whether the customer performed a transaction with an online merchant; and determining that the predicted account balance is negative based on an amount of the transaction.
15. The method of claim 10 , wherein the account is determined to be in the low-cash mode when at least one of the following occurs:
the system predicts, via the at least one processor, based on an amount of a pending transaction, that the account balance after processing the pending transaction is negative;
the system determines, via the at least one processor, based on an amount of a scheduled payment that the account balance after processing the scheduled payment is negative;
the system determines, via the at least one processor, that a customer enters a predetermined time period; or
the system determines, via the at least one processor, that a geographic location of the customer corresponds with a geographic location of a merchant with whom the customer has a history of transactions that would cause the account balance to become negative.
16. The method of claim 15 , wherein the system determines the predetermined time period based on at least one of;
scheduled transactions;
reoccurring transactions;
analysis of historical data; or
relation of current time to an upcoming event.
17. The method of claim 10 , wherein the at least one processor is configured to transmit a notification from the server to the user when the account enters the low cash mode, where the notification comprises at least one of an email, a text message, a voice call, a push notification through an application on a mobile device, a social media alert, an alert through wearable technology, or an alert through a device connected to a network.
18. A non-transitory computer readable medium having stored instructions, which when executed, cause at least one processor to perform operations for managing a financial account, comprising:
providing for display, on a display of a mobile device, a setup dashboard configuration comprising a plurality of setup graphical user interfaces, including:
a first setup interface for receiving a first setting for a low cash mode threshold, wherein the first setup interface allows the user to set the low cash mode threshold;
a second setup interface for receiving a second setting for at least one default payment behavior when a financial account is in a low cash mode, wherein the second setting instructs at least one processor whether to approve or deny check payments and automatic payments initiated before entering the low cash mode;
a third setup interface for receiving a third setting for enabling a geolocation alert service, the third setup interface consisting of options for geolocation based alerts;
a fourth setup interface displayed in response to selection of the selectable option for the geolocation alert service, the fourth setup interface including:
a manually add location entry field for receiving a fourth setting for a frequent locations list;
replacing the setup dashboard configuration with an account management dashboard configuration comprising one or more account management interfaces associated with processing a plurality of transactions while outside of the low cash mode;
determining a predicted balance of the financial account, by:
retrieving a current balance;
retrieving historical transaction data;
identifying one or more expected transactions based on the historical transaction data;
collecting geolocation data based on current and past geographic locations of the customer;
identifying one or more scheduled transactions; and
generating a predicted balance using a machine learning algorithm wherein the customer's current balance, the customer's historical transaction data, the customer's geolocation data, and the customer's scheduled transactions are inputs for the machine learning algorithm;
determining whether the financial account is in the low cash mode by:
comparing the current balance and the predicted balance to the low cash mode threshold; and
determining that the current balance or the predicted balance is below the low cash mode threshold;
responsive to determining that the financial account is in the low cash mode:
disabling and replacing the account management dashboard configuration with a low cash mode dashboard configuration comprising one or more low cash mode user interfaces different from the setup user interfaces and different from the account management user interfaces, wherein the low cash mode user interfaces comprise:
an indication that the financial account is in the low cash mode;
a set of electronic transaction controls restricted to account funding controls;
one or more default payment controls for processing previously-scheduled automatic payments while the account is in the low-cash mode;
wherein the processor permits a customer to navigate only within the low cash mode dashboard configuration for performing a limited set of electronic banking operations associated with the set of electronic transaction controls and the one or more default payment controls;
determining a geolocation alert, wherein the geolocation alert is determined by obtaining a geographic position of the mobile device, determining whether the geographic position is associated with a merchant, and if the geographic location is associated with a merchant, providing, in at least one of the low cash mode user interfaces, an indication that the customer account is in low cash mode; and
determining whether the merchant is included in the frequent locations list, and if the merchant is included in the frequent locations list, providing, in at least one of the low cash mode user interfaces, an option to disable a smart lock mode for a financial card associated with the financial account.Join the waitlist — get patent alerts
Track US11915214B1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.