US 11,973,745 B2
Performing concealed transactions using a zero-knowledge data management network
Brett Shockley, Bonita Springs, FL (US); Alexander John Shockley, Palo Alto, CA (US); Michael Joseph Frendo, Boulder, CO (US); Shmuel Shaffer, Palo Alto, CA (US); Kenneth Keiter, Denver, CO (US); and James M. Behmke, Pembroke, MA (US)
Assigned to Journey.ai, Denver, CO (US)
Filed by Journey.ai, Denver, CO (US)
Filed on Dec. 4, 2019, as Appl. No. 16/703,855.
Claims priority of provisional application 62/852,850, filed on May 24, 2019.
Claims priority of provisional application 62/775,302, filed on Dec. 4, 2018.
Prior Publication US 2020/0226592 A1, Jul. 16, 2020
Int. Cl. G06Q 20/40 (2012.01); G06F 3/06 (2006.01); G06F 21/60 (2013.01); G06F 21/62 (2013.01); G06F 21/64 (2013.01); G06Q 20/38 (2012.01); H04L 9/06 (2006.01); H04L 9/08 (2006.01); H04L 9/14 (2006.01); H04L 9/30 (2006.01); H04L 9/32 (2006.01); H04L 9/40 (2022.01)
CPC H04L 63/0471 (2013.01) [G06F 3/062 (2013.01); G06F 3/0655 (2013.01); G06F 3/067 (2013.01); G06F 21/602 (2013.01); G06F 21/62 (2013.01); G06F 21/645 (2013.01); G06Q 20/38215 (2013.01); G06Q 20/3829 (2013.01); G06Q 20/383 (2013.01); G06Q 20/401 (2013.01); H04L 9/0643 (2013.01); H04L 9/0819 (2013.01); H04L 9/0825 (2013.01); H04L 9/083 (2013.01); H04L 9/0833 (2013.01); H04L 9/0891 (2013.01); H04L 9/14 (2013.01); H04L 9/30 (2013.01); H04L 9/3218 (2013.01); H04L 9/3236 (2013.01); H04L 9/3242 (2013.01); H04L 9/3247 (2013.01); H04L 9/3263 (2013.01); H04L 9/3265 (2013.01); H04L 9/3268 (2013.01); H04L 63/0421 (2013.01); H04L 63/0442 (2013.01); H04L 63/083 (2013.01); H04L 63/101 (2013.01); H04L 63/102 (2013.01)] 8 Claims
OG exemplary drawing
 
1. A method for providing secure financial transactions between a buyer and a seller, the method comprising:
obtaining, by a storage server in a network via one or more communication interfaces, financial account identification information of the buyer, wherein the financial account identification information of the buyer is encrypted by a public key of the buyer such that the storage server and the seller have no access to read the financial account identification information of the buyer,
wherein the storage server comprises the one or more communication interfaces being configured to communicate data over links in the network, a memory being configured to store software programs and data structures, one or more processors being configured to execute the software programs and manipulate the data structures, the one or more communication interfaces, the memory, and the one or more processors being interconnected by a system bus;
obtaining, by the storage server via the one or more communication interfaces, financial account identification information of the seller, wherein the financial account identification of the seller is encrypted by a public key of the seller such that the storage server and the buyer have no access to read the financial account identification information of the seller;
obtaining, by the storage server via the one or more communication interfaces, an invoice for a financial transaction between the buyer and the seller, the invoice indicating a financial value to transfer from the financial account identification information of the buyer to the financial account identification information of the seller, wherein the storage server has no access to read the invoice, wherein the invoice is encrypted;
obtaining, by the storage server via the one or more communication interfaces, a buyer-based rekeying key generated using a private key of the buyer and a public key of a financial institution associated with the financial account identification information of the buyer such that the storage server has no access to the private key of the buyer;
obtaining, by the storage server via the one or more communications interfaces, a seller-based rekeying key generated using a private key of the seller and the public key of the financial institution associated with the financial account identification information of the buyer such that the storage server has no access to the private key of the seller;
obtaining, by the storage server via the one or more communication interfaces, an authorization from the buyer for the transaction, the authorization signed with the private key of the buyer;
encrypting, by the storage server, the financial account identification information of the buyer using the buyer-based rekeying key, thereby generating a re-encrypted financial account identification information of the buyer;
encrypting, by the storage server, the financial account identification information of the seller using the seller-based rekeying key, thereby generating a re-encrypted financial account identification information of the seller;
encrypting, by the storage server, the invoice using one of either the buyer-based rekeying key or the seller-based rekeying key, thereby generating a re-encrypted invoice; and
providing, from the storage server via the one or more communication interfaces, in response to the authorization, the re-encrypted financial account identification information of the buyer, the re-encrypted financial account identification information of the seller, the buyer-based rekeying key, the seller-based rekeying key, and the re-encrypted invoice to a financial institution associated with the financial account identification information of the buyer, hereinafter collectively “the provided data”, the provided data being in a format such that the only the financial institution has access to read the provided data to complete the financial transaction.