Patent ID: 11922426
Assignee: CAPITAL ONE SERVICES, LLC
Field: IT methods for management (Electrical engineering)
Classification: CPC G | IPC G

Claim 0:
1. A transaction priority control system, comprising:
an account database storing transaction and account data for a plurality of user accounts, wherein each of the plurality of user accounts comprising an account associated with a user, transaction information including one or more transactions associated with the account, a balance associated with the account, a first predetermined amount, and a second predetermined amount;
a merchant database storing merchant information of a plurality of merchant accounts;
a server configured for data communication with user devices of the plurality of users, the account database and the merchant database, wherein the server comprises:
a transaction approval engine communicatively coupled to a prioritization engine; and
the prioritization engine comprising a predictive model, wherein the prioritization engine is communicatively coupled to the transaction approval engine, wherein the predictive model is a supervised learning model;
wherein, the prioritization engine is configured to:
monitor an account balance associated with a user account of the plurality of user accounts;
select one or more predictor variables based on data stored in the account database and in the merchant database, wherein the selected one or more predictive variables comprises a transaction type, a transaction amount, a transaction occurrence frequency and a merchant category code;
train the predictive model with the selected predictor variables using the transaction and account data;
based on the monitoring, determining whether the account balance of the user account is less than a first predetermined amount;
upon determining that the account balance is less than the first predetermined amount:
query the transaction information of the user account from the account database;
apply the predictive model to the transaction information of the user account;
determine, based on an analysis of the one or more predictor variables using the predictive model, one or more future transactions within a predetermined time period, wherein the determining the one or more future transactions further comprises:
identifying one or more future debit and credit transactions based on the transaction type, the transaction occurrence frequency and the merchant category code associated with each of the plurality of transactions;

determine a predicted future account balance associated with each of the one or more future debit transactions within the predetermined time period;
upon determining that the predicted future balance for a debit transaction of the one or more future debit transactions is less than the second predetermined amount, assign a priority score to the debit transaction to yield one or more debit transactions associated with one or more predicted future balance amounts below the second predetermined amount; and
send the one or more future debit transactions and the priority score corresponding to the each of the one or more future debit transactions to the transaction approval engine;

wherein, the transaction approval engine is configured to:
receive the one or more future debit transactions including the priority score corresponding to the each of the one or more future debit transactions; and
approve or deny a future debit transaction of the one or more future debit transactions based on the priority score and the user preference information;

wherein the server is configured to:
request a user preference information for the future debit transaction from a user device of the user, wherein the user device receives the user preference information from the user, via a user interface of the user device;
receive, from the user device, the user preference information of the user; and
send a notification message to the user device about the approval or denial of the future debit transaction;

wherein the transaction approval engine is further configured to:
transmit the one or more future debit transactions flagged for denial to the prioritization engine; and

wherein the prioritization engine is further configured to:
increase a priority score associated with the each of the one or more future debit transactions received from the transaction approval engine during a subsequent predetermined time period.