US11823121B2ActiveUtilityA1

Systems and methods for processing, securing, and communicating industrial commerce transactions

85
Assignee: INXEPTION CORPPriority: Apr 25, 2019Filed: Apr 27, 2020Granted: Nov 21, 2023
Est. expiryApr 25, 2039(~12.8 yrs left)· nominal 20-yr term from priority
G06Q 10/087G06F 16/1837G06Q 20/0658G06Q 10/0633H04L 9/3239G06Q 20/389H04L 2463/102H04L 63/102G06Q 20/0655G06Q 20/203G06Q 20/3674G06Q 20/38215H04L 9/50
85
PatentIndex Score
4
Cited by
13
References
14
Claims

Abstract

Methods, systems, apparatus, and computer program products related to a digital business management system for business transactions are provided. In an example embodiment, the digital business management system includes receiving a transaction data object generated as a part of a transaction event executed via an external commerce channel to be posted to a ledger, wherein the transaction data object comprises one or more metadata tags classifying the transaction event. The system further comprises generating an immutable ledger entry, parsing the transaction data object to identify the one or more metadata tags for storage in association with the transaction event, identifying a match between the one or more metadata tags received from the external commerce channel and one or more master metadata tags stored in the ledger and associated with a data object profile, and updating the data object profile by associating the immutable ledger entry with the data object profile.

Claims

exact text as granted — not AI-modified
The invention claimed is: 
     
       1. A system comprising:
 a non-transitory computer readable storage medium storing a copy of a decentralized blockchain, the decentralized blockchain being maintained at a plurality of computing devices; 
 and one or more processors, configured to, with the non-transitory computer readable storage medium: 
 receive, at a network hub and via a communication application program interface of a third-party application, a transaction dataset for a transaction performed using the third-party application, wherein the transaction dataset for the transaction comprises one or more metadata tags classifying the transaction and a transaction price for an item exchanged as part of the transaction; 
 convert the transaction price into a payment token amount that is payable via payment tokens that are usable as surrogate payment data for fiat currency; 
 generate a first block of the decentralized blockchain to include the transaction dataset for the transaction, wherein the first block, after being generated, is immutable; 
 receive, at the network hub, a security token from an embedded-secure element (eSE) of a client device engaged with the third-party application; 
 in response to authentication of the security token at the decentralized blockchain:
 transfer, via the blockchain from a first digital wallet associated with the client device to a second digital wallet, one or more blockchain-secured payment tokens in the payment token amount, and 
 generate, by the network hub at the decentralized blockchain, a second block of the decentralized blockchain to include a record of the transfer of the one or more blockchain-secured payment tokens from the first digital wallet to the second digital wallet; and 
 
 facilitate exchange of the transferred one or more blockchain-secured payment tokens into fiat currency after completion of the transaction. 
 
     
     
       2. The system of  claim 1 , wherein the one or more processors are further configured to, with the non-transitory computer readable storage medium:
 standardize the transaction dataset into a format compatible with a profile that includes a transaction history of previous transactions performed using the third-party application and/or one or more additional third-party applications. 
 
     
     
       3. The system of  claim 1 , wherein the one or more processors are further configured to, with the non-transitory computer readable storage medium:
 subscribe to the communication application program interface of the third-party application to receive transaction data updates. 
 
     
     
       4. The system of  claim 1 , wherein the one or more metadata tags comprise product inventory information, product order information, order date and time information, or buyer information. 
     
     
       5. The system of  claim 1 , wherein the third-party application operates on a compiled code base or repository that is separate and distinct from that which supports the system. 
     
     
       6. A computer-implemented method comprising:
 providing a decentralized blockchain maintained at a plurality of computing devices; 
 receiving, at a network hub and via a communication application program interface of a third-party application, a transaction dataset for a transaction performed using the third-party application, wherein the transaction dataset for the transaction comprises one or more metadata tags classifying the transaction and a transaction price for an item exchanged as part of the transaction; 
 converting the transaction price into a payment token amount that is payable via payment tokens that are usable as surrogate payment data for fiat currency; 
 generating a first block of the decentralized blockchain, to include the transaction dataset for the transaction, wherein the first block, after being generated, is immutable; 
 receiving, at the network hub, a security token from an embedded-secure element (eSE) of a client device engaged with the third-party application; 
 in response to authenticating the security token at the decentralized blockchain:
 transferring, via the blockchain from a first digital wallet associated with the client device to a second digital wallet, one or more blockchain-secured payment tokens in the payment token amount, and 
 generating, by the network hub at the decentralized blockchain, a second block of the decentralized blockchain to include a record of the transfer of the one or more blockchain-secured payment tokens from the first digital wallet to the second digital wallet; and 
 
 facilitating exchange of the transferred one or more blockchain-secured payment tokens into fiat currency after completion of the transaction. 
 
     
     
       7. The computer-implemented method of  claim 6 , further comprising:
 standardizing the transaction dataset into a format compatible with a profile that includes a transaction history of previous transactions performed using the third-party application and/or one or more additional third-party applications. 
 
     
     
       8. The computer-implemented method of  claim 6 , further comprising:
 subscribing to the communication application program interface of the third-party application to receive transaction data updates. 
 
     
     
       9. The computer-implemented method of  claim 6 , wherein the one or more metadata tags comprise product inventory information, product order information, order date and time information, or buyer information. 
     
     
       10. The computer-implemented method of  claim 6 , wherein the third-party application operates on a compiled code base or repository that is separate and distinct from that which supports the digital business management system. 
     
     
       11. A computer program product comprising:
 a non-transitory computer readable medium storing a copy of a decentralized blockchain, the decentralized blockchain being maintained at a plurality of computing devices, wherein the non-transitory computer readable medium further stores computer program instructions, when executed by a processor, cause the processor to: 
 receive, at a network hub and via a communication application program interface of a third-party application, a transaction dataset for a transaction performed using the third-party application, wherein the transaction dataset for the transaction comprises one or more metadata tags classifying the transaction and a transaction price for an item exchanged as part of the transaction; 
 convert the transaction price into a payment token amount that is payable via payment tokens that are usable as surrogate payment data for fiat currency; 
 generate a first block of the decentralized blockchain to include the transaction dataset for the transaction, wherein the first block, after being generated, is immutable; 
 receive, at the network hub, a security token from an embedded-secure element (eSE) of a client device engaged with the third-party application; 
 in response to authentication of the security token at the decentralized blockchain:
 transfer, via the blockchain from a first digital wallet associated with the client device to a second digital wallet, one or more blockchain-secured payment tokens in the payment token amount, and 
 generate, by the network hub at the decentralized blockchain, a second block of the decentralized blockchain to include a record of the transfer of the one or more blockchain-secured payment tokens from the first digital wallet to the second digital wallet; and 
 
 facilitate exchange of the transferred one or more blockchain-secured payment tokens into fiat currency after completion of the transaction. 
 
     
     
       12. The computer program product of  claim 11 , wherein the computer program instructions when executed by a processor, further cause the processor to:
 standardize the transaction dataset into a format compatible with a profile that includes a transaction history of previous transactions performed using the third-party application and/or one or more additional third-party applications. 
 
     
     
       13. The computer program product of  claim 11 , wherein the computer program instructions when executed by a processor, further cause the processor to:
 subscribe to the communication application program interface of the third-party application to receive transaction data object updates. 
 
     
     
       14. The computer program product of  claim 11 , wherein the one or more metadata tags comprise product inventory information, product order information, order date and time information, or buyer information.

Cited by (0)

No later patents cite this yet.

References (0)

No backward citations on record.