Multi-layered credit card with transaction-dependent source selection
US-2021201316-A1 · Jul 1, 2021 · US
US11748727B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11748727-B2 |
| Application number | US-202016904115-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jun 17, 2020 |
| Priority date | Jun 17, 2020 |
| Publication date | Sep 5, 2023 |
| Grant date | Sep 5, 2023 |
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.
A system includes an application programming interface, a database, and a server. The application programming interface can make recommendations to a user at a point of sale to display a recommended payment method from a set of payment methods associated with the user. The database can store past transactions for each payment method in the set of payment methods. The server can generate payment analytics by analyzing the past transactions in the database for each payment method. The server can determine potential benefits available to the user. The server can determine the recommended payment method by using the payment analytics and maximizing the potential benefits available to the user.
Opening claim text (preview).
What is claimed is: 1. A system, comprising: an application programming interface for making recommendations to a user at a point of sale to display a recommended payment method from a set of payment methods associated with the user, wherein the application programming interface stores information about the user and one or more predetermined recommended payment methods associated with one or more web sites in a cache; a database that stores past transactions for each payment method in the set of payment methods and a set of generic transactions; and a server that is configured to: receive a payment request from the point of sale; determine that the payment request attempts to use one of the payment methods associated with the user by comparing payment information included in the payment request with payment information associated with each of the respective payment methods; identify the payment request payment method based on comparison of payment information included in the payment request with payment information associated with each of the respective payment methods; train a predictive model using the information stored in the cache; filter one or more past transactions in the database for each payment method based on one or more expired time periods of potential benefits to the user to yield one or more filtered past transactions and one or more unwanted results, wherein: the one or more filtered past transactions correspond to one or more past transactions selected by the filter, and the one or more unwanted results correspond to one or more past transactions removed by the filter; generate payment analytics by using the predictive model to analyze the one or more filtered past transactions in the database for each payment method; determine potential benefits available to the user; determine the recommended payment method by using the payment analytics and maximizing the potential benefits available to the user; process the payment request using the payment request payment method if the recommended payment method is the same as the payment request payment method; and transmit to the point of sale an indication to be displayed to the user by the point of sale that the recommended payment method is different than the payment request payment method if the recommended payment method is the different than the payment request payment method; receive, from the point of sale, a user choice of a payment method from the set of payment methods; retrieve, from the database, one or more generic transactions from the set of generic transactions for each of the unwanted results; and retrain the predictive model based on the one or more filtered past transactions, the one or more generic transactions, and the user choice. 2. The system of claim 1 , wherein the recommended payment method includes a virtual number. 3. The system of claim 1 , wherein the set of payment methods is selected from one or more of: (i) a credit card, (ii) a bank account, (iii) cash, (iv) a check, or (v) a debit card. 4. The system of claim 1 , wherein the potential benefits available to the user are selected from one or more of: a number of reward points, cash back, a number of airline miles, a donation to a charity, or an interest rate. 5. The system of claim 4 , wherein the potential benefits available to the user are stored in a customer profile that is stored in the database. 6. The system of claim 1 , wherein the application programming interface receives session information about the user. 7. A method, comprising: receiving, by a server, a payment request from a point of sale; determining, by the server, that the payment request attempts to use a payment method selected from a set of payment methods associated with a user by comparing payment information included in the payment request with payment information associated with each of the respective payment methods; identifying, by the server, the payment request payment method based on comparison of payment information included in the payment request with payment information associated with each of the respective payment methods; training a predictive model using information about the user and one or more predetermined recommended payment methods associated with one or more websites; filtering one or more past transactions stored in a database for each payment method based on one or more expired time periods of potential benefits to the user to yield one or more filtered past transactions and one or more unwanted results, wherein: the one or more filtered past transactions correspond to one or more past transactions selected by the filter, and the one or more unwanted results correspond to one or more past transactions removed by the filter; generating, by the server, payment analytics by using the predictive model to analyze the one or more filtered past transactions stored in the database for each payment method; determining, by the server, potential benefits available to the user; determining, by the server, the recommended payment method by using the payment analytics and maximizing the potential benefits available to the user; processing, by the server, the payment request using the payment request payment method if the recommended payment method is the same as the payment request payment method; transmitting, by the server to the point of sale, an indication to be displayed to the user by the point of sale that the recommended payment method is different than the payment request payment method if the recommended payment method is the different than the payment request payment method; receiving, from the point of sale, a user choice of a payment method from the set of payment methods; retrieving, from the database, one or more generic transactions from a set of generic transactions for each of the unwanted results; and retraining the predictive model based on the one or more filtered past transactions, the one or more generic transactions, and the user choice. 8. The method of claim 7 , wherein the server is in data communication with an application programming interface for making recommendations to the user at the point of sale to display the recommended payment method. 9. The method of claim 7 , wherein the set of payment methods is selected from one or more of: (i) a credit card, (ii) a bank account, (iii) cash, (iv) a check, or (v) a debit card. 10. The method of claim 7 , wherein the potential benefits available to the user are selected from one or more of: a number of reward points, cash back, a number of airline miles, a donation to a charity, or an interest rate. 11. The method of claim 7 , further comprising generating a virtual number for the recommended payment method. 12. The method of claim 11 , further comprising displaying a virtual number option pop-up to the user. 13. The method of claim 11 , wherein the virtual number is limited to use with a particular vendor. 14. A non-transitory computer-accessible medium having stored thereon computer-executable instructions for making a recommendation to a user at a point of sale, wherein upon execution by a computer arrangement comprising a processor, the instructions cause the computer arrangement to perform procedures comprising: receiving a payment request from the point of sale; determining that the payment request attempts to use a payment method selected from the a set of payment methods associated with the user by comparing payment information included in the payment request with payment information associated with each of the respective payment methods; identifying the payment request payment method base
comprising interface for record bearing medium or carrier for electronic funds transfer or payment credit · CPC title
Machine learning · CPC title
characterised in that multiple accounts are available, e.g. to the payer · CPC title
Payment using discounts or coupons (relating to marketing G06Q30/02) · CPC title
Keeping log of transactions for guaranteeing non-repudiation of a transaction · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.