Systems and methods for generating travel recommendations
US-2017193550-A1 · Jul 6, 2017 · US
US11182756B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11182756-B2 |
| Application number | US-201816107571-A |
| Country | US |
| Kind code | B2 |
| Filing date | Aug 21, 2018 |
| Priority date | Aug 21, 2018 |
| Publication date | Nov 23, 2021 |
| Grant date | Nov 23, 2021 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Provided, in an aspect, is a method for improved management of transaction data from a financial services computer network. The method includes receiving details for a first purchase, detecting that the first purchase is a trigger purchase, obtaining secondary details for the first purchase, receiving details for a later-made second purchase and additional purchases made between the first purchase and second purchase, and determining that the first purchase and the second purchase belong to the same experience set and that the additional intervening purchases do not belong to the same experience set as the first purchase and the second purchase.
Opening claim text (preview).
What is claimed is: 1. A computer-implemented method for improved management of transaction data from a financial services computer network, the method comprising: receiving, from the financial services computer network by a computer system comprising one or more processors, details for a first purchase with a merchant made by a user on a start date, the details including a merchant category code (MCC) and a merchant name associated with the merchant; detecting, by the computer system and without user input, that the first purchase is a trigger purchase by: identifying the merchant name as being one of a pre-determined set of merchant names associated with an activity or event that occurs on a later date from a respective financial transaction, wherein the pre-determined set of merchant names was generated via a machine learning algorithm trained on a database of user transactions, wherein the trigger purchase is identified as being associated with a respective activity or event to occur on a target date later than the start date; in response to detecting the trigger purchase, generating, by the computer system and without user input, an experience set based on the trigger purchase, wherein the experience set reflects the event and the trigger purchase is part of the experience set; obtaining, by the computer system, secondary details for the trigger purchase from a data source external to the financial services computer network, wherein the secondary details for the trigger purchase identify the target date; receiving, by the computer system from the financial services computer network, details for a second purchase made by the user on the target date; receiving, by the computer system, details for one or more other purchases made after the trigger purchase and before the second purchase; determining, by the computer system, that the second purchase is part of the experience set by comparing the details for the second purchase with at least one of the details for the trigger purchase or the secondary details for the trigger purchase; determining by the computer system, that the one or more other purchases are not to be part of the experience set by comparing the details for the one or more other purchases with at least one of the details for the trigger purchase or the secondary details for the trigger purchase; storing, by the computer system, the experience set to a database; and causing, by the computer system, information about the experience set to be displayed, the displayed information including information about the trigger purchase and information about the second purchase, and not including the details about the one or more other purchases. 2. The method of claim 1 , further comprising receiving details for one or more additional purchases made after the second purchase, and categorizing the one or more additional purchases as part of the experience set. 3. The method of claim 2 , further comprising determining that each of the additional purchases is related to the trigger purchase by comparing each of the additional purchase details with the first purchase details, with the first purchase secondary details, or with both the first purchase details and the first purchase secondary details. 4. The method of claim 3 , wherein the trigger purchase secondary details further comprise an end date after which no purchases are categorized as part of the experience set. 5. The method of claim 1 , wherein the trigger purchase details and the second purchase details are received concurrently with each other. 6. The method of claim 1 , wherein the trigger purchase details and the second purchase details are received separately and in real time as each of the first purchase and the second purchase is made. 7. The method of claim 1 , wherein the trigger purchase secondary details are obtained via email scraping. 8. The method of claim 1 , further comprising transmitting, by the computer system, a prompt for display on a computing device in response to detecting that the trigger purchase is a trigger purchase. 9. The method of claim 8 , further comprising: receiving, by the computer system, a response to the prompt; and grouping the trigger purchase and the second purchase into the experience set based at least in part on the response to the prompt. 10. A computer-implemented method for improving categorization of transactions by money-management software, the method comprising: receiving, by a computer system comprising one or more processors, attributes relating to a first transaction made on a first date by a user from a financial services computer network, the attributes including a merchant category code (MCC); detecting, by the computer system and without user input, that the first transaction is a trigger transaction by: identifying the MCC as being one of a pre-determined set of MCCs associated with an activity or event that occurs on a later date from a respective financial transaction, wherein the pre-determined set of merchant names was generated via a machine learning algorithm trained on a database of user transactions, the database of user transaction comprising a history of transactions of the user; wherein the trigger transaction is identified as being associated with an event to occur on a second date later than the first date based on the MCC; in response to detecting the trigger transaction, generating, by the computer system and without user input, an experience set based on the trigger transaction, wherein the experience set reflects the event and the first transaction is part of the experience set; obtaining, by the computer system, forecast data for the first transaction from a forecast agent, wherein the forecast data identifies the second date; receiving, by the computer system after a period encompassing a plurality of unrelated transactions, attributes relating to a second transaction made on the second date; determining, by the computer system, that the second transaction is part of the experience set by comparing the forecast data to the attributes relating to the second transaction; determining, by the computer system, that the unrelated transactions are not part of the experience set by comparing the forecast data to attributes relating to the unrelated transactions; storing, by the computer system, the experience set to a database, and causing, by the computer system, information about the experience set to be displayed, the displayed information including information about the first transaction and the second transaction, and not including information about any of the unrelated transactions. 11. The computer-implemented method of claim 10 , further comprising confirming the first transaction as a trigger transaction based on user input. 12. The computer-implemented method of claim 10 , wherein the forecast data further comprise a place. 13. The computer-implemented method of claim 10 , further comprising modifying the forecast data based on user input. 14. The computer-implemented method of claim 10 , further comprising causing a confirmation to be displayed after the second transaction. 15. The computer-implemented method of claim 10 , further comprising causing a reminder to be displayed before the second date. 16. The computer-implemented method of claim 10 , further comprising acquiring a choice from a user regarding the second transaction, and determining that the second transaction is related to the first transaction based on the choice. 17. The computer-implemented method of claim 10 , further comprising generati
Remote banking, e.g. home banking · CPC title
involving remote charge determination or related payment systems · CPC title
Credit schemes, i.e. "pay after" · CPC title
Visualization; Browsing · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.