Techniques for utilizing a predictive model to cache processing data
Abstract
Embodiments of the invention are directed to systems and methods for utilizing a cache to store historical transaction data. A predictive model may be trained to identify particular identifiers associated with historical data that is likely to be utilized on a particular date and/or within a particular time period. The historical data corresponding to these identifiers may be stored in a cache of the processing computer. Subsequently, an authorization request message may be received that includes an identifier. The processing computer may utilize the identifier to retrieve historical transaction data from the cache. The retrieved data may be utilized to perform any suitable operation. By predicting the data that will be needed to perform these operations, and preemptively store such data in a cache, the latency associated with subsequent processing may be reduced and the performance of the system as a whole improved.
Claims
exact text as granted — not AI-modified1 .- 20 . (canceled)
21 . A computer-implemented method, comprising:
transmitting, by a computing device to a server computer, an authorization request message for a transaction associated with an account; thereby causing the server computer to:
determine whether historical transaction data associated with the account is stored in a cache, wherein the historical transaction data is stored in the cache based upon an identified one or more accounts from a plurality of accounts, the one or more accounts predicted as being likely to be utilized to conduct one or more transactions within a future time period using a predictive model,
when the historical transaction data is stored in the cache, retrieve the historical transaction data associated with the account from the cache, and
when the historical transaction data is not stored in the cache, obtain the historical transaction data associated with the account from a historical transaction database;
receiving, by the computing device from the server computer, an authorization response message based upon the historical transaction data; and completing the transaction based on the authorization response message.
22 . The method of claim 21 , wherein:
the predictive model is trained based at least in part on historical transaction data associated with the plurality of accounts.
23 . The method of claim 22 , wherein:
the historical transaction data identifies a number of the plurality of accounts that have historically been utilized within a particular historical time period.
24 . The method of claim 23 , wherein:
the number of the plurality of accounts are determined to have conducted over a threshold percentage of transactions occurring within the particular historical time period.
25 . The method of claim 21 , wherein:
the predictive model is trained utilizing unsupervised machine learning techniques.
26 . The method of claim 21 , wherein the server computer further:
obtains, from a data store, a portion of the historical transaction data, the portion of the historical transaction data corresponding to transactions conducted utilizing the one or more accounts over a second time period; and storing, at the server computer, the portion of the historical transaction data within the cache.
27 . The method of claim 26 , wherein:
identifying the one or more accounts, obtaining the portion of the historical transaction data, and storing the portion of the historical transaction data, are performed in response to receiving the authorization request message.
28 . The method of claim 26 , wherein:
identifying the one or more accounts, obtaining the portion of the historical transaction data, and storing the portion of the historical transaction data, are performed periodically.
29 . The method of claim 21 , wherein the server computer further:
updates the historical transaction data with transaction data associated with the authorization request message, wherein the predictive model is updated based at least in part on the historical transaction data as updated.
30 . The method of claim 21 , wherein:
in response to receiving the authorization request message, the server computer utilizes the historical transaction data to calculate a risk score for the authorization request message, the authorization response message comprising the risk score.
31 . The method of claim 21 , wherein the predictive model is trained on the historical transaction data to utilize a season, holiday information corresponding to transaction dates, and demographic information associated with an account holder to identify the accounts that are likely to be utilized within the future time period.
32 . A system comprising:
a computing device comprising:
a processor, and
a non-transitory computer-readable medium, the non-transitory computer-readable medium comprising code, executable by the processor, for implementing a method comprising:
transmitting, to a server computer, an authorization request message for a transaction associated with an account, and receiving, from the server computer, an authorization response message based upon historical transaction data associated with the account; and the server computer in communication with the computing device, and programmed to:
determine whether the historical transaction data associated with the account is stored in a cache, wherein the historical transaction data is stored in the cache based upon an identified one or more accounts from a plurality of accounts, the one or more accounts predicted as being likely to be utilized to conduct one or more transactions within a future time period using a predictive model,
when the historical transaction data is stored in the cache, retrieve the historical transaction data associated with the account from the cache, and
when the historical transaction data is not stored in the cache, obtain the historical transaction data associated with the account from a historical transaction database.
33 . The system of claim 32 , wherein:
the predictive model is trained based at least in part on historical transaction data associated with the plurality of accounts.
34 . The system of claim 33 , wherein:
the historical transaction data identifies a number of the plurality of accounts that have historically been utilized within a particular historical time period; and the number of the plurality of accounts are determined to have conducted over a threshold percentage of transactions occurring within the particular historical time period.
35 . The system of claim 33 , wherein the server computer is further programmed to:
in response to receiving the authorization request message, utilize the historical transaction data to calculate a risk score for the authorization request message, the authorization response message comprising the risk score.
36 . The system of claim 32 , wherein the server computer is further programmed to:
obtain, from a data store, a portion of the historical transaction data, the portion of the historical transaction data corresponding to transactions conducted utilizing the one or more accounts over a second time period; and store, at the server computer, the portion of the historical transaction data within the cache.
37 . The system of claim 32 , wherein the server computer is further programmed to:
update the historical transaction data with transaction data associated with the authorization request message, wherein the predictive model is updated based at least in part on the historical transaction data as updated.
38 . The system of claim 32 , wherein the server computer further programmed to:
update the historical transaction data with transaction data associated with the authorization request message, wherein the one or more accounts are identified from the plurality of accounts subsequent to the historical transaction data being updated with the transaction data.
39 . The system of claim 32 , wherein the server computer is further programmed to delete, from the cache, another portion of the historical transaction data.
40 . The system of claim 39 , wherein the predictive model is trained on the historical transaction data to utilize a season, holiday information corresponding to transaction dates, and demographic information associated with an account holder to identify the accounts that are likely to be utilized within the future time period.Cited by (0)
No later patents cite this yet.
References (0)
No backward citations on record.