US 12,475,476 B2
Closed-loop environment for efficient, accurate, and secure transaction processing
Christopher Michael Petersen, Lakeway, TX (US); Jeffrey Scott Pittelkau, Montgomery, AL (US); Nikolais Linsteadt, Applegate, CA (US); Joseph Arthur Revnes, Atlanta, GA (US); Brian Daniel Cooper, Marietta, GA (US); William Matthau, Laguna Niguel, CA (US); Yamini Bistesh Sagar, Alpharetta, GA (US); Nicolas Frederic Cabrera, Atlanta, GA (US); Utkarsh Agarwal, Tucson, AZ (US); Tim Kuchlein, Cupertino, CA (US); Bharath Lakshmanan, San Ramon, CA (US); William Andrew Bryant, Alpharetta, GA (US); Stephen Paul Saucier, Atlanta, GA (US); Deepak Kumar, Marietta, GA (US); Anil Jaiswal, Marietta, GA (US); Byungkwon Jeon, Cumming, GA (US); and Balaji Devarasetty, Atlanta, GA (US)
Assigned to Bakkt Marketplace, LLC, Atlanta, GA (US)
Filed by Bakkt Marketplace, LLC, Atlanta, GA (US)
Filed on Jul. 16, 2021, as Appl. No. 17/378,185.
Claims priority of provisional application 63/116,964, filed on Nov. 23, 2020.
Prior Publication US 2022/0164815 A1, May 26, 2022
Int. Cl. G06Q 40/04 (2012.01); G06Q 30/0201 (2023.01); H04L 67/133 (2022.01)
CPC G06Q 30/0206 (2013.01) [G06Q 30/0201 (2013.01); G06Q 40/04 (2013.01); H04L 67/133 (2022.05)] 15 Claims
OG exemplary drawing
 
1. A computer-implemented method comprising:
generating and transmitting a first current pricing data application programming interface (API) request, wherein (i) the first current pricing data API request is associated with a first transaction request at a first timepoint and an internal user account identifiable by an internal account identifier, (ii) the first current pricing data API request indicates a digital asset associated with the first transaction request, and (iii) the first transaction request indicates a first number of digital asset units;
receiving a first current pricing data API response comprising first current pricing data;
providing the first current pricing data for display via a client device;
responsive to determining that a first configurable time period has elapsed:
generating and transmitting a second current pricing data API request, wherein the second current pricing data API request indicates the digital asset,
receiving a second current pricing data API response comprising second current pricing data, and
providing the second current pricing data for display via the client device;
receiving a second transaction request, wherein the second transaction request (i) is at a second timepoint, (ii) is associated with the internal user account identifiable by the internal account identifier, and (iii) indicates a second number of digital asset units;
responsive to the second transaction request, executing an off-chain digital asset transaction in real-time for the second transaction request within a second configurable time period, wherein the off-chain digital asset transaction for the second number of digital asset units is between a central operating account and the internal user account, and wherein the off-chain digital asset transaction is executed in response to a predicted increase in demand by a machine learning model trained with a digital asset transaction dataset;
dynamically providing a notification of execution of the off-chain digital asset transaction;
generating an updated digital asset transaction dataset based on the digital asset transaction dataset and the off-chain digital asset transaction, wherein the machine learning model is retrained with the updated digital asset transaction dataset;
generating and storing an account balance data object for the off-chain digital asset transaction; and
executing an on-chain digital asset transaction with a third number of digital asset units, wherein executing the on-chain digital asset transaction comprises generating and committing an on-chain transaction record data object associated with the central operating account to a distributed ledger,
wherein (a) the on-chain digital asset transaction is executed prior to receiving the first transaction request and the second transaction request, and (b) the third number of digital asset units is determined based at least in part on a digital asset unit balance associated with the central operating account.