Enterprise reputations for uniform resource locators
US-2016380977-A1 · Dec 29, 2016 · US
US12340402B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12340402-B2 |
| Application number | US-202318329249-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jun 5, 2023 |
| Priority date | May 19, 2020 |
| Publication date | Jun 24, 2025 |
| Grant date | Jun 24, 2025 |
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.
The disclosed systems and methods may request a merchant identifier associated with a merchant from a third party, receive the merchant identifier, retrieve or receive a first uniform resource locator (URL) associated with the merchant, and store the merchant identifier and the first URL in a database. In response to a web browser extension detecting that a user is preparing to make an online purchase associated with the merchant, the system may receive an age request for an age of the merchant from a user device and identify the merchant identifier in the database based on a second URL included in the age request. The system may then request the age of the merchant from the database based on the merchant identifier, receive the age of the merchant from the third party, and transmit the age of the merchant to the user device for display.
Opening claim text (preview).
What is claimed is: 1. A system, comprising: one or more processors; and memory in communication with the one or more processors and storing instructions that, when executed by the one or more processors, are configured to cause the system to: request a merchant identifier associated with a merchant from a third party database; receive the merchant identifier associated with the merchant from the third party database; retrieve or receive a first uniform resource locator (URL) associated with the merchant; store the merchant identifier and the first URL in a first database to generate a first data entry for the merchant; in response to a web browser extension via a user device detecting that a useris preparing to make an online purchase based on a second URL, receive an age request from the user device for an age of the merchant, wherein the age request comprises the second URL; identify the merchant identifier in the first database based on the second URL; request the age of the merchant from the third party database based on the merchant identifier, wherein the age of the merchant represents how long the merchant has been in business as determined by identifying an earliest transaction associated with the merchant identifier; receive the age of the merchant from the third party database; and transmit the age of the merchant to the user device for display. 2. The system of claim 1 , wherein identifying the merchant identifier in the first database is based on matching or partially matching the first URL and the second URL, wherein the first database is a remote third party database. 3. The system of claim 1 , further comprising instructions that, when executed by the one or more processors, are configured to cause the system to: receive a date of creation associated with the second URL; determine that the second URL does not match the first URL; and in response to determining that the second URL does not match the first URL, transmit the second URL and the date of creation of the second URL to the first database to generate a second data entry for the merchant. 4. The system of claim 3 , further comprising instructions that, when executed by the one or more processors, are configured to cause the system to: cause the user device to display the date of creation of the second URL. 5. The system of claim 1 , wherein identifying the merchant identifier in the first database comprises extracting a first name of the merchant from the second URL and conducting a key word search of the first name against the first URL or a second name of the merchant stored in the first database. 6. The system of claim 1 , wherein detecting that a user is preparing to make an online purchase comprises detecting a URL shopping indicator in the second URL. 7. The system of claim 1 , wherein detecting that a user is preparing to make an online purchase comprises detecting URL query parameters in the second URL related to shopping or checkout, detecting document object model (DOM) elements related to shopping or checkout, conduct natural language parsing, or a combination thereof. 8. The system of claim 2 , further comprising instructions that, when executed by the one or more processors, are configured to cause the system to: receive a threshold age; determine whether the age of the merchant is older than the threshold age; when the age of the merchant is older than the threshold age, cause the user device to display the age of the merchant; and when the age of the merchant is less than the threshold age, cause the user device to display a confirmation message that at least partially blocks the user's view of a website and must be selected as an acknowledgement to exit. 9. A system, comprising: one or more processors; and memory in communication with the one or more processors and storing instructions that, when executed by the one or more processors, are configured to cause the system to: retrieve transaction data associated with a merchant; determine an age of the merchant by identifying an earliest transaction for the merchant in the transaction data, wherein the age of the merchant represents how long the merchant has been in business; store the age of the merchant and one or more names of the merchant in a database as a first data entry; in response to a web browser extension via a user device detecting that a user is preparing to make an online purchase based on a first uniform resource locator (URL), receive a request from the user device for the age of the merchant, wherein the request comprises the first URL; match the first URL to the one or more names of the merchant stored in the database to identify the associated age of the merchant; and transmit the identified age of the merchant to the user device for display. 10. The system of claim 9 , wherein detecting that a user is preparing to make an online purchase comprises detecting a URL shopping indicator in the first URL. 11. The system of claim 9 , wherein detecting that a user is preparing to make an online purchase comprises detecting URL query parameters in the first URL related to shopping or checkout, detecting document object model (DOM) elements related to shopping or checkout, natural language parsing, or a combination thereof. 12. The system of claim 9 , further comprising instructions that, when executed by the one or more processors, are configured to cause the system to: retrieve or receive a second URL associated with the merchant; retrieve or receive a date of creation associated with the first URL; determine that the second URL does not match the first URL; and in response to determining that the second URL does not match the first URL, (i) transmit the first URL and the date of creation of the first URL to the database to generate a second data entry for the merchant and (ii) cause the user device to display the date of creation of the first URL. 13. A system, comprising: one or more processors; and memory in communication with the one or more processors and storing instructions that, when executed by the one or more processors, are configured to cause the system to: receive a merchant identifier associated with a merchant from a third party database; retrieve or receive a first uniform resource locator (URL) associated with the merchant; in response to a web browser extension via a user device detecting that a user is preparing to make an online purchase based on a second URL, receive an age request from the user device for an age of the merchant, wherein the age request comprises the second URL; identify the merchant identifier in a first database based on the second URL; request the age of the merchant from the third party database based on the merchant identifier, wherein the age of the merchant represents how long the merchant has been in business as determined by identifying an earliest transaction associated with the merchant identifier; receive the age of the merchant from the third party database; and transmit the age of the merchant to the user device for display. 14. The system of claim 13 , wherein identifying the merchant identifier in the first database is based on matching or partially matching the first URL and the second URL, wherein the first database is a remote third party database. 15. The system of claim 13 , further comprising instructions that, when executed by the one or more processors, are configured to cause the system to: receive a date of creation associated with the second URL; determine that the second URL does not match the first URL; and in response to determining that t
Applying verification of the received information (cryptographic mechanisms or cryptographic arrangements for data integrity or data verification H04L9/32) · CPC title
for controlling access to devices or network resources · CPC title
Entity profiles · CPC title
Parsing · CPC title
Level alarms, e.g. alarms responsive to variables exceeding a threshold · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.