Adjustment of knowledge-based authentication
US-2019259030-A1 · Aug 22, 2019 · US
US12332993B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12332993-B2 |
| Application number | US-202318545491-A |
| Country | US |
| Kind code | B2 |
| Filing date | Dec 19, 2023 |
| Priority date | May 7, 2021 |
| Publication date | Jun 17, 2025 |
| Grant date | Jun 17, 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.
Methods, systems, and apparatuses are described herein for improving the accuracy of synthetic authentication questions by analyzing third party account data. A request for access to a first account associated with a user may be received. The first account may be managed by a first organization. A transactions database might be queried for first account data. Second account data corresponding to a second account associated with the user might be received. That second account may be managed by a second organization different from the first organization. One or more second transactions, unique to the second account, may be identified. A synthetic transaction, configured to be different from transactions in the first account and the one or more second transactions, may be generated. An authentication question may be generated based on the synthetic transaction. Access to the first account might be provided based on a response to the authentication question.
Opening claim text (preview).
What is claimed is: 1. A method comprising: receiving, by a computing device, a request for access to a first account associated with a user; querying a transactions database for first account data corresponding to the first account, wherein the first account data indicates one or more first transactions conducted via a first payment method; receiving, from a second computing device, second account data corresponding to a second account associated with the user, wherein the second account data indicates one or more second transactions conducted via a second payment method; generating standardized merchant names by processing the second account data based on a format of the first account data; identifying, based on comparing the first account data and the processed second account data using the standardized merchant names, one or more second transactions, wherein the one or more second transactions are unique to the second account; generating, based on the first account data, a synthetic transaction not conducted by the first account or the second account, wherein the synthetic transaction is configured to be different from both the one or more first transactions and the one or more second transactions; and providing, based on a response to an authentication question associated with the synthetic transaction, access to the first account. 2. The method of claim 1 , wherein processing the second account data comprises: based on determining that a second format of the second account data does not indicate modification of the second account data, replacing one or more portions of the second account data. 3. The method of claim 1 , wherein generating the synthetic transaction comprises: identifying, based on the first account data, a merchant other than one or more merchants corresponding to the one or more second transactions unique to the second account, wherein the synthetic transaction corresponds to the merchant. 4. The method of claim 1 , wherein generating the synthetic transaction is further based on determining a pattern of transactions conducted by the first account. 5. The method of claim 1 , wherein receiving the second account data comprises: providing, to the second computing device, at least a portion of the first account data; and receiving, based on the first account data, the second account data. 6. The method of claim 1 , wherein receiving the second account data comprises: receiving, from the second computing device and in response to authentication credentials, the second account data. 7. The method of claim 1 , wherein processing the second account data comprises: based on determining that a second format of the second account data is different from a payment card industry standard, processing the second account data using a natural language processing algorithm, wherein the natural language processing algorithm is configured to modify the second format of the second account data based on the format of the first account data. 8. The method of claim 1 , wherein the first account data comprises a first list of transactions associated with the first account during a time period, and wherein receiving the second account data comprises: providing, to the second computing device, an indication of the time period, wherein the second account data comprises a second list of transactions associated with the second account during the time period. 9. The method of claim 1 , wherein the synthetic transaction is configured to be similar to one or more past transactions indicated by the first account data. 10. A computing device comprising: one or more processors; and memory storing instructions that, when executed by the one or more processors, cause the computing device to: receive a request for access to a first account associated with a user; query a transactions database for first account data corresponding to the first account, wherein the first account data indicates one or more first transactions conducted via a first payment method; receive, from a second computing device, second account data corresponding to a second account associated with the user, wherein the second account data indicates one or more second transactions conducted via a second payment method; generate standardized merchant names by processing the second account data based on a format of the first account data; identify, based on comparing the first account data and the processed second account data using the standardized merchant names, one or more second transactions, wherein the one or more second transactions are unique to the second account; generate, based on the first account data, a synthetic transaction not conducted by the first account or the second account, wherein the synthetic transaction is configured to be different from both the one or more first transactions and the one or more second transactions; and provide, based on a response to an authentication question associated with the synthetic transaction, access to the first account. 11. The computing device of claim 10 , wherein the instructions, when executed by the one or more processors, cause the computing device to process the second account data by causing the computing device to: based on determining that a second format of the second account data does not indicate modification of the second account data, replace one or more portions of the second account data. 12. The computing device of claim 10 , wherein the instructions, when executed by the one or more processors, cause the computing device to generate the synthetic transaction by causing the computing device to: identify, based on the first account data, a merchant other than one or more merchants corresponding to the one or more second transactions unique to the second account, wherein the synthetic transaction corresponds to the merchant. 13. The computing device of claim 10 , wherein the instructions, when executed by the one or more processors, cause the computing device to generate the synthetic transaction further based on determining a pattern of transactions conducted by the first account. 14. The computing device of claim 10 , wherein the instructions, when executed by the one or more processors, cause the computing device to receive the second account data by causing the computing device to: provide, to the second computing device, at least a portion of the first account data; and receive, based on the first account data, the second account data. 15. The computing device of claim 10 , wherein the instructions, when executed by the one or more processors, cause the computing device to receive the second account data by causing the computing device to: receive, from the second computing device and in response to authentication credentials, the second account data. 16. One or more non-transitory computer-readable media storing instructions that, when executed by one or more processors, cause a computing device to: receive a request for access to a first account associated with a user; query a transactions database for first account data corresponding to the first account, wherein the first account data indicates one or more first transactions conducted via a first payment method; receive, from a second computing device, second account data corresponding to a second account associated with the user, wherein the second account data indicates one or more second transactions conducted via a second payment method; generate standardized merchant names by processing the second account data based on a format of the first account data; identify,
Entity profiles · CPC title
for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32) · CPC title
Architecture, e.g. interconnection topology · CPC title
Processing or translation of natural language (natural language analysis G06F40/20; semantic analysis G06F40/30) · CPC title
Querying · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.