# US 12,002,036 B2 · Enhancing merchant databases using crowdsourced browser data > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,002,036 B2 - Document ID: US12002036B2 - Status: Granted - Kind: B2 - Application number: 17/831,766 - Filed: 2022-06-03 - Published: 2022-09-15 - Granted: 2024-06-04 - Earliest claimed: 2020-04-29 - Assignees: Capital One Services, LLC - Applicants: Capital One Services, LLC - Inventors: Abdelkader M'Hamed Benkreira; Michael Mossoba; Joshua Edwards - Web page: https://patentgrep.com/patent/US12002036B2 ## CPC - G06Q 20/382: {insuring higher security of transaction} - G06F 9/44526: {Plug-ins; Add-ons} - G06F 16/955: using information identifiers, e.g. uniform resource locators [URL] - G06Q 20/102: {Bill distribution or payments} - G06Q 20/384: {using social networks} - G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract Systems as described herein may enhance merchant databases using crowdsourced browser data. An electronic payment server may receive cache information associated with the first transaction from a browser extension. The electronic payment server may retrieve a transaction record for a second transaction in a transaction database, wherein the first transaction matches with the second transaction. The electronic payment server may update a merchant record in a private merchant database with a friendly merchant name based on the cache information. Upon determining that the merchant record in the private merchant database exceeds a threshold confidence level, the merchant record may be promoted to a trustworthy database, and the friendly merchant name may be presented to a user device. ## Claims ### Claim 1 A computer-implemented method comprising: installing a browser extension to a first user device; receiving, from the browser extension and by an electronic payment server, information associated with a transaction conducted by a user via the browser extension, wherein the information comprises a trustworthy merchant name, and a user identifier associated with the transaction; updating, by the electronic payment server, a merchant record in a private merchant database with the trustworthy merchant name based on a translation from a merchant identifier in a transaction record to the trustworthy merchant name in the information; determining, by the electronic payment server, a confidence level of the merchant record based on a number of merchant records in the private merchant database sharing an association between the merchant identifier and the trustworthy merchant name; based on a determination that the confidence level exceeds a threshold level, promoting by the electronic payment server, the merchant record to a trustworthy database; causing display of the trustworthy merchant name on a second user device; determining, via a browser installed with the browser extension, that the user navigates to a website that is associated with a merchant; storing information associated with a second transaction in a local cache of the first user device; and based on a determination that the user has navigated away from the website without completing a checkout process, deleting the information associated with the second transaction from the local cache. ### Claim 2 (depends on 1) The computer-implemented method of claim 1, wherein determining the confidence level comprises: determining the confidence level based on a number of merchant records in the private merchant database sharing an association between the merchant identifier and the trustworthy merchant name. ### Claim 3 (depends on 1) The computer-implemented method of claim 1, wherein the browser extension performs operations comprising: based on a determination that the user has successfully completed the checkout process associated with the transaction, sending the information associated with the transaction to the electronic payment server. ### Claim 4 (depends on 1) The computer-implemented method of claim 1, wherein the browser extension performs operations comprising: determining, based on the information associated with the transaction, an element in a Document Object Model indicating a completion of the checkout process. ### Claim 5 (depends on 1) The computer-implemented method of claim 1, wherein the browser extension performs operations comprising: determining, based on the information associated with the transaction, a specific term on the website that indicates a completion of the checkout process. ### Claim 6 (depends on 1) The computer-implemented method of claim 1, wherein the browser extension performs operations comprising: determining, based on the information associated with the transaction, a specific term in a Universal Resource Locator that indicates a completion of the checkout process. ### Claim 7 (depends on 1) The computer-implemented method of claim 1, wherein the information associated with the transaction comprises a first transaction amount and the transaction record comprises a second transaction amount. ### Claim 8 (depends on 7) The computer-implemented method of claim 7, further comprising: retrieving, by the electronic payment server, the transaction record from a transaction database based on: a payment account identifier in the transaction record matching the user identifier; and the first transaction amount matching the second transaction amount. ### Claim 9 (depends on 1) The computer-implemented method of claim 1, further comprising: prior to promoting the merchant record to the trustworthy database, causing display, by the electronic payment server, of the trustworthy merchant name to the first user device; and receiving, from the first user device, a confirmation on the trustworthy merchant name. ### Claim 10 (depends on 1) The computer-implemented method of claim 1, wherein the information comprises the trustworthy merchant name, a merchant Universal Resource Locator, a merchant social media profile, and merchant contact information. ### Claim 11 An electronic payment system comprising: one or more processors; and memory storing instructions that, when executed by the one or more processors, cause the electronic payment system to: install a browser extension to a first user device; receive, from the browser extension, information associated with a transaction conducted by a user via the browser extension, wherein the information comprises a trustworthy merchant name, and a user identifier associated with the transaction; update a merchant record in a private merchant database with the trustworthy merchant name based on a translation from a merchant identifier in a transaction record to the trustworthy merchant name in the information; determine a confidence level of the merchant record based on a number of merchant records in the private merchant database sharing an association between the merchant identifier and the trustworthy merchant name; based on a determination that the confidence level exceeds a threshold level, promote the merchant record to a trustworthy database; cause display of the trustworthy merchant name on a second user device; determine, via a browser installed with the browser extension, that the user navigates to a website that is associated with a merchant; store information associated with a second transaction in a local cache of the first user device; and based on a determination that the user has navigated away from the website without completing a checkout process, cause to delete the information associated with the second transaction from the local cache. ### Claim 12 (depends on 11) The electronic payment system of claim 11, wherein the instructions when executed by the one or more processors, cause the electronic payment system to: determine the confidence level based on a number of merchant records in the private merchant database sharing an association between the merchant identifier and the trustworthy merchant name. ### Claim 13 (depends on 11) The electronic payment system of claim 11, wherein the instructions when executed by the one or more processors, cause the browser extension to: based on a determination that the user has successfully completed the checkout process associated with the transaction, send the information associated with the transaction to the electronic payment system. ### Claim 14 (depends on 11) The electronic payment system of claim 11, wherein the information associated with the transaction comprises a first transaction amount and the transaction record comprises a second transaction amount. ### Claim 15 (depends on 14) The electronic payment system of claim 14, wherein the instructions when executed by the one or more processors, cause the electronic payment system to: retrieve the transaction record from a transaction database based on: a payment account identifier in the transaction record matching the user identifier; and the first transaction amount matching the second transaction amount. ### Claim 16 (depends on 11) The electronic payment system of claim 11, wherein the instructions when executed by the one or more processors, cause the electronic payment system to: prior to promoting the merchant record to the trustworthy database, causing display of the trustworthy merchant name to the first user device; and receive, from the first user device, a confirmation on the trustworthy merchant name. ### Claim 17 (depends on 11) The electronic payment system of claim 11, wherein the information comprises the trustworthy merchant name, a merchant Universal Resource Locator, a merchant social media profile, and merchant contact information. ### Claim 18 One or more non-transitory media storing instructions that, when executed by one or more processors, cause the one or more processors to perform steps comprising: installing a browser extension to a first user device; receiving, from the browser extension, information associated with a transaction conducted by a user via the browser extension, wherein the information comprises a trustworthy merchant name, and a user identifier associated with the transaction; updating a merchant record in a private merchant database with the trustworthy merchant name based on a translation from a merchant identifier in a transaction record to the trustworthy merchant name in the information; determining a confidence level of the merchant record based on a number of merchant records in the private merchant database sharing an association between the merchant identifier and the trustworthy merchant name; based on a determination that the confidence level exceeds a threshold level, promoting the merchant record to a trustworthy database; and causing display of the trustworthy merchant name on a second user device; determining, via a browser installed with the browser extension, that the user navigates to a website that is associated with a merchant; storing information associated with a second transaction in a local cache of the first user device; and based on a determination that the user has navigated away from the website without completing a checkout process, deleting the information associated with the second transaction from the local cache. ### Claim 19 (depends on 18) The non-transitory media of claim 18, wherein the instructions when executed by the one or more processors, cause the one or more processors to further perform steps comprising: determining the confidence level based on a number of merchant records in the private merchant database sharing an association between the merchant identifier and the trustworthy merchant name. ### Claim 20 (depends on 18) The non-transitory media of claim 18, wherein the information comprises the trustworthy merchant name, a merchant Universal Resource Locator, a merchant social media profile, and merchant contact information.