# US 12,602,725 B2 · Secure identifier integration > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,602,725 B2 - Document ID: US12602725B2 - Status: Granted - Kind: B2 - Application number: 19/312,035 - Filed: 2025-08-27 - Published: 2025-12-11 - Granted: 2026-04-14 - Earliest claimed: 2023-03-24 - Assignees: TRETE Inc. - Applicants: TRETE Inc. - Inventors: Damien Patton - Web page: https://patentgrep.com/patent/US12602725B2 ## CPC - G06Q 40/04: Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange - G06F 16/215: Improving data quality; Data cleansing, e.g. de-duplication, removing invalid entries or correcting typographical errors - G06F 16/2358: {Change logging, detection, and notification (replication G06F16/27)} - G06F 16/2379: {Updates performed during online database operations; commit processing} - G06F 16/275: {Synchronous replication} - G06Q 20/02: involving a neutral party, e.g. certification authority, notary or trusted third party [TTP] - G06Q 20/065: {using e-cash} - G06Q 20/363: {with the personal data of a user} - G06Q 20/3674: {involving authentication} - G06Q 20/381: {Currency conversion} - G06Q 20/3829: {involving key management} - G06Q 20/389: {Keeping log of transactions for guaranteeing non-repudiation of a transaction} - G06Q 20/401: {Transaction verification} - G06Q 20/42: Confirmation, e.g. check or permission by the legal debtor of payment - G06Q 30/0613: {using intermediate agents} - G06Q 40/06: Asset management; Financial planning or analysis - H04L 9/3239: {involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD} - H04L 9/50: {using hash chains, e.g. blockchains or hash trees} - H04L 67/1097: for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS] - G06F 16/2365: {Ensuring data consistency and integrity} - G06F 16/27: Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor - G06Q 2220/00: Business processing using cryptography - G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract In certain aspects of the disclosure, a computer-implemented method includes creating a wallet for asset tokens and creating an account for a first user upon completion of user onboarding validation. The method includes associating the account with one of an individual and a business entity. The method includes initiating one of know-your-customer (KYC) for the individual and know-your-business (KYB) for the business entity. The method includes enabling the first user to access and make transactions using the wallet. ## Claims ### Claim 1 A computer-implemented method comprising: electronically onboarding an individual as a user of a trading system via a know-your-customer (KYC) protocol, including: establishing a dynamic security object model describing run-time data object properties of account object records governing access and privileges for secure exchange of tokenized assets; accessing the dynamic security object model; verifying an identity of the individual; and in response to and upon verifying the identity of the individual, automatically creating an individual user account corresponding to the individual with appropriate permission level security based on the established dynamic security object model, including automatically creating a digital wallet at the trading system and associating the individual user account with the digital wallet; electronically onboarding a business entity as a user of the trading system via a know-your-business (KYB) protocol, including: verifying an identity of the business entity and that the individual is authorized to act on behalf of the business entity; in response to and upon verifying the identity of the business entity and that the individual is authorized to act on behalf of the business entity, automatically: creating a business entity account corresponding to the business entity with appropriate permission level security based on the dynamic security object model, including automatically creating a business digital wallet at the trading system and associating the business entity account with the business digital wallet; and linking the individual user account to the business entity account; and authorizing the individual user account to act on behalf of the business entity account with respect to one or more operations at the trading system; subsequent to onboarding both the individual and the business entity: receiving a request from the individual user account to participate in a transaction on behalf of the business entity, the transaction defining a token transfer; confirming that token transfer is included in the one or more operations; and permitting the individual user account to transfer a token between the business digital wallet and another digital wallet of another account as part of the transaction in view of the confirmation. ### Claim 2 (depends on 1) The method of claim 1, further comprising validating business entity documentation indicating the individual is authorized to act on behalf of the business entity prior to authorizing the individual user account to act on behalf of the business entity account. ### Claim 3 (depends on 1) The method of claim 1, wherein permitting the individual user account to transfer a token between the business digital wallet and another digital wallet of another account comprises permitting the individual user account to transfer a token between the business digital wallet and another business digital wallet of another business entity. ### Claim 4 (depends on 1) The method of claim 1, further comprising: accessing transaction data indicative of completing the token transfer; and updating fractional ownership interests in an asset within an electronic capitalization table, in view of the token transfer and based on the transaction data. ### Claim 5 (depends on 1) The method of claim 1, further comprising: digitally preserving evidence of the token transfer transaction completion in a private mutable ledger and a public immutable ledger, including: recording transaction data in the private mutable ledger; and semi-redundantly synchronizing the public immutable ledger with the private mutable ledger including recording a subset of the transaction data in the public immutable ledger. ### Claim 6 (depends on 1) The method of claim 1, wherein authorizing the individual user account to act on behalf of the business entity account with respect to one or more operations comprises authorizing the individual user account to act on behalf of the business entity with respect to one or more of: initiating KYB, tokenizing business entity assets, claiming tokens, custodying tokens in the business digital wallet, or facilitating business entity transactions, at the trading system. ### Claim 7 (depends on 1) The method of claim 1, wherein authorizing the individual user account to act on behalf of the business entity account with respect to one or more operations comprises authorizing the individual user account to act on behalf of the business entity with respect to one or more of: buying tokens for the business entity, selling tokens for the business entity, auditing the business entity, reporting on the business entity, or viewing the business entity account information, at the trading system. ### Claim 8 (depends on 1) The method of claim 1, wherein linking the individual user account to the business entity account comprises linking the individual user account to the business entity account as a founder of the business entity. ### Claim 9 (depends on 1) The method of claim 1, further comprising prior to the individual acting on behalf of the business entity: presenting an account selector at a user interface, the account selector providing a selection between the individual user account and the business entity account; receiving a selection of the business entity account via the account selector presented at the user interface; and in response to the received selection of the business entity account, filtering out the individual user account from presented information associated with the business entity account at the user interface. ### Claim 10 (depends on 9) The method of claim 9, wherein receiving a request from the individual user account to participate in a transaction on behalf of the business entity comprises receiving the request from the individual user account to participate in a transaction on behalf of the business entity through the user interface after filtering out the individual user account. ### Claim 11 A computer system comprising: a processor; and system memory coupled to the processor and storing instructions configured to cause the processor to: electronically onboard an individual as a user of a trading system via a know-your-customer (KYC) protocol, including: establish a dynamic security object model describing run-time data object properties of account object records governing access and privileges for secure exchange of tokenized assets; access the dynamic security object model; verify an identity of the individual; and in response to and upon verifying the identity of the individual, automatically create an individual user account corresponding to the individual with appropriate permission level security based on the dynamic security object model, including automatically creating a digital wallet at the trading system and associating the individual user account with the digital wallet; electronically onboard a business entity as a user of the trading system via a know-your-business (KYB) protocol, including: verify an identity of the business entity and that the individual is authorized to act on behalf of the business entity; in response to and upon verifying the identity of the business entity and that the individual is authorized to act on behalf of the business entity, automatically: create a business entity account corresponding to the business entity with appropriate permission level security based on the dynamic security object model, including automatically creating a business digital wallet at the trading system and associating the business entity account with the business digital wallet; and link the individual user account to the business entity account; and authorize the individual user account to act on behalf of the business entity account with respect to one or more operations at the trading system, including granting the individual user account access to the business digital wallet; subsequent to onboarding both the individual and the business entity: receive a request from the individual user account to participate in a transaction on behalf of the business entity, the transaction defining a token transfer; confirm that token transfer is included in the one or more operations; and permit the individual user account to transfer a token between the business digital wallet and another digital wallet of another account as part of the transaction in view of the confirmation. ### Claim 12 (depends on 11) The system of claim 11, further comprising instructions configured to cause the processor to validate business entity documentation indicating the individual is authorized to act on behalf of the business entity prior to authorizing the individual user account to act on behalf of the business entity account. ### Claim 13 (depends on 11) The system of claim 11, wherein instructions configured to cause the processor to permit the individual user account to transfer a token between the business digital wallet and another digital wallet of another account comprise instructions configured to cause the processor to permit the individual user account to transfer a token between the business digital wallet and another business digital wallet of another business entity. ### Claim 14 (depends on 11) The system of claim 11, further comprising instructions configured to cause the processor to: access transaction data indicative of completing the token transfer; and update fractional ownership interests in an asset within an electronic capitalization table, in view of the token transfer and based on the transaction data. ### Claim 15 (depends on 11) The system of claim 11, further comprising instructions configured to cause the processor to: digitally preserve evidence of the token transfer transaction completion in a private mutable ledger and a public immutable ledger, including: record transaction data in the private mutable ledger; and semi-redundantly synchronize the public immutable ledger with the private mutable ledger including recording a subset of the transaction data in the public immutable ledger. ### Claim 16 (depends on 11) The system of claim 11, wherein instructions configured to cause the processor to authorize the individual user account to act on behalf of the business entity account with respect to one or more operations comprise instructions configured to cause the processor to authorize the individual user account to act on behalf of the business entity with respect to one or more of: initiating KYB, tokenizing business entity assets, claiming tokens, custodying tokens in the business digital wallet, or facilitating business entity transactions, at the trading system. ### Claim 17 (depends on 11) The system of claim 11, wherein instructions configured to cause the processor to authorize the individual user account to act on behalf of the business entity account with respect to one or more operations comprise instructions configured to cause the processor to authorize the individual user account to act on behalf of the business entity with respect to one or more of: buying tokens for the business entity, selling tokens for the business entity, auditing the business entity, reporting on the business entity, or viewing the business entity account information, at the trading system. ### Claim 18 (depends on 11) The system of claim 11, wherein instructions configured to cause the processor to link the individual user account to the business entity account comprise instructions configured to cause the processor to link the individual user account to the business entity account as a founder of the business entity. ### Claim 19 (depends on 11) The system of claim 11, further comprising instructions configured to cause the processor to prior to the individual acting on behalf of the business entity: present an account selector at a user interface, the account selector providing a selection between the individual user account and the business entity account; receive a selection of the business entity account via the account selector presented at the user interface; and in response to the received selection of the business entity account, filter out the individual user account from presented information associated with the business entity account at the user interface. ### Claim 20 (depends on 19) The system of claim 19, wherein instructions configured to cause the processor to receive a request from the individual user account to participate in a transaction on behalf of the business entity comprise instructions configured to cause the processor to receive the request from the individual user account to participate in a transaction on behalf of the business entity through the user interface after filtering out the individual user account.