# US 2026/0065368 A1 · Settlement and approval service

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2026/0065368 A1
- Document ID: US20260065368A1
- Status: Published application
- Kind: A1
- Application number: 19/385,513
- Filed: 2025-11-11
- Published: 2026-03-05
- Earliest claimed: 2023-03-24
- Assignees: TRETE Inc.
- Applicants: TRETE Inc.
- Inventors: Damien Patton; Christian Gratton
- Web page: https://patentgrep.com/patent/US20260065368A1

## 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

A system and method for determining whether to throttle or kill a sale of shares of an asset using a settlement approval service, including querying, by a settlement approval service, a transfer agent whether a buyer of shares of an asset is approved; querying, by the settlement approval service, a transfer agent whether a seller of shares of the asset is approved; based on the buyer and the seller being approved, querying, by the settlement approval service, the transfer agent as to whether the shares offered for sale are valid; and based on determining, by the settlement approval service, that the shares are valid, approving, by the settlement approval service, the sale of shares of the asset.

## Claims

### Claim 1

A trading system computer-implemented method comprising:
concurrently with processing transaction flows settling transactions, updating and maintaining a set of security action triggers that, when triggered, subject pre-settlement private credit transactions to one or more supplemental security actions, including:
tracking order frequency, transaction attributes, and user attributes based on a set of factors corresponding to private credit transactions,
wherein the set of factors include: (1) a plurality of “inside” factors and (2) a plurality of “outside” factors;
continually and automatically checking for a one or more “inside” factors impacting private credit transactions, the one or more “inside” factors included in the plurality of “inside” factors;
continually and automatically checking for a one or more “outside” factors impacting private credit transactions, the first “outside” factor included in the plurality of “outside” factors;
identifying a factor, from among: the one or more “inside” factors and the one or more “outside” factors, is occurring;
determining that the identified factor impacts pre-settlement private credit transactions associated with specified transaction data in view of the tracked transaction and user attributes; and
responsive to determining that the identified factor impacts pre-settlement private credit transactions associated with the specified transaction data, setting a flag denoting that pre-settlement private credit transactions associated with the specified transaction data are subject to the one or more supplemental security actions prior to settlement; and
concurrently with processing transaction flows settling transactions and concurrently with updating and maintaining the set of security action triggers, reviewing a private credit transaction in response to triggering a security action trigger, including:
monitoring flow of a “live” private credit transaction, the “live” private credit transaction being pre-settlement and including live transaction data defining exchange of shares in a private credit asset between a buyer of the shares and a seller of the shares; and
matching the live transaction data with the specified transaction data; and
in response to matching the live transaction data with the specified transaction data automatically:
interrupting flow of the “live” private credit transaction from progressing towards settlement; and
while interrupted, subjecting the “live” private credit transaction to the one or more supplemental security actions triggered in view of the set flag, the one or more supplemental security actions handling any transaction irregularities associated with the identified factor; and
(1) allowing the flow of the “live” private credit transaction to resume and the “live” private credit transaction to progress towards settlement subsequent to completion of the one or more supplemental security actions or (2) preventing the flow of the “live” private credit transaction and stopping the “live” private credit transaction from settling based on the one or more supplemental security actions.

### Claim 2 (depends on 1)

The method of claim 1, wherein identifying a factor comprises identifying a factor creating transaction ambiguity; and
wherein subjecting the “live” private credit transaction to the one or more supplemental security actions comprises pausing the “live” private credit transaction until the transaction ambiguity is resolved.

### Claim 3 (depends on 1)

The method of claim 1, wherein setting the flag comprises setting the flag indicating pre-settlement transactions including transaction data associated with one or more of: the buyer, the seller, or the shares in the private credit asset, are to be throttled for manual inspection prior to settlement; and
wherein subjecting the “live” private credit transaction to the one or more supplemental security actions comprises pausing the “live” private credit transaction for manual inspection prior to settlement responsive to the live transaction data matching with the specified transaction data.

### Claim 4 (depends on 3)

The method of claim 3, further comprising while the “live” private credit transaction is paused:
receiving approval from a manual review of the “live” private credit transaction; and
responsive to the approval, allowing progression of the “live” private credit transaction to settlement.

### Claim 5 (depends on 3)

The method of claim 3, further comprising while the “live” private credit transaction is paused:
receiving disapproval from a manual review of the “live” private credit transaction; and
responsive to the disapproval, canceling the “live” private credit transaction.

### Claim 6 (depends on 1)

The method of claim 1, wherein setting the flag comprises setting the flag indicating pre-settlement private credit transactions including transaction data associated with one or more of: the buyer, the seller, or the shares in the private credit asset, are to be killed prior to settlement; and
wherein preventing the flow of the “live” private credit transaction and stopping the “live” private transaction from settling comprises automatically killing the “live” private credit transaction prior to settlement responsive to the live transaction data matching with the specified transaction data.

### Claim 7 (depends on 6)

The method of claim 6, further comprising subsequent to killing the “live” private credit transaction:
reverting a capitalization table to a prior version from before the “live” private credit transaction started; and
re-listing the shares in the private credit asset for sale.

### Claim 8 (depends on 1)

The method of claim 1, wherein matching the live transaction data with the specified transaction data comprises a microservice matching the live transaction data with the specified transaction data.

### Claim 9 (depends on 1)

The method of claim 1, wherein setting a flag comprises setting a flag applicable to a group of transactions.

### Claim 10 (depends on 1)

The method of claim 1, wherein identifying a factor comprises detecting an event through an Application Programming Interface (API).

### Claim 11

A trading system comprising:
a processor;
system memory coupled to the processor and storing instructions configured to cause the processor to:
concurrently with processing transaction flows settling transactions, update and maintain a set of security action triggers that, when triggered, subject pre-settlement private credit transactions to one or more supplemental security actions, including:
track order frequency, transaction attributes, and user attributes based on a set of factors,
wherein the set of factors include: (1) a plurality of “inside” factors and (2) a plurality of “outside” factors;
continually and automatically check for a one or more “inside” factors impacting private credit transactions, the one or more “inside” factors included in the plurality of “inside” factors;
continually and automatically check one or more “outside” factors impacting private credit transactions, the one or more “outside” factors included in the plurality of “outside” factors;
identify a factor, from among: the one or more “inside” factors, the first “outside” factor, and the second “outside” factor, is occurring;
determine that the identified factor impacts pre-settlement private credit transactions associated with specified transaction data in view of the tracked transaction and user attributes; and
responsive to determining that the identified factor impacts pre-settlement private credit transactions associated with the specified transaction data, set a flag denoting that pre-settlement private credit transactions associated with the specified transaction data are subject to the one or more supplemental security actions prior to settlement; and
concurrently with processing transaction flows settling transactions and concurrently with updating and maintaining the set of security action triggers, review a private credit transaction in response to triggering a security action trigger, including:
monitor flow of a “live” private credit transaction, the “live” private credit transaction being pre-settlement and including live transaction data defining exchange of shares in a private credit asset between a buyer of the shares and a seller of the shares; and
match the live transaction data with the specified transaction data; and
in response to matching the live transaction data with the specified transaction data automatically:
interrupt flow of the “live” private credit transaction from progressing towards settlement; and
while interrupted, subject the “live” private credit transaction to the one or more supplemental security actions triggered in view of the set flag, the one or more supplemental security actions handling any transaction irregularities associated with the identified factor; and
(1) allow the flow of the “live” private credit transaction to resume and the “live” private transaction to progress towards settlement subsequent to completion of the one or more supplemental security actions or (2) prevent the flow of the “live” private credit transaction and stopping the “live” private credit transaction from settling based on the one or more supplemental security actions.

### Claim 12 (depends on 11)

The system of claim 11, wherein instructions configured to cause the processor to identify a factor comprise instructions configured to cause the processor to identify a factor creating transaction ambiguity; and
wherein instructions configured to cause the processor to subject the “live” private credit transaction to the one or more supplemental security actions comprise instructions configured to cause the processor to pause the “live” private credit transaction until the transaction ambiguity is resolved.

### Claim 13 (depends on 11)

The system of claim 11, wherein instructions configured to cause the processor to set the flag comprise instructions configured to cause the processor to set the flag indicating pre-settlement private credit transactions including transaction data associated with one or more of: the buyer, the seller, or the shares in the private credit asset, are to be throttled for manual inspection prior to settlement; and
wherein instructions configured to cause the processor to subject the “live” private credit transaction to the one or more supplemental security actions comprise instructions configured to cause the processor to pause the “live” private credit transaction for manual inspection prior to settlement responsive to the live transaction data matching with the specified transaction data.

### Claim 14 (depends on 13)

The system of claim 13, further comprising instructions configured to cause the processor, while the “live” private credit transaction is paused, to:
receive approval from a manual review of the “live” private credit transaction; and
responsive to the approval, allow progression of the “live” private credit transaction to settlement.

### Claim 15 (depends on 13)

The system of claim 13, further comprising instructions configured to cause the processor while the “live” private credit transaction is paused, to:
receive disapproval from a manual review of the “live” private credit transaction; and
responsive to the disapproval, cancel the “live” private credit transaction.

### Claim 16 (depends on 11)

The system of claim 11, wherein instructions configured to cause the processor to set the flag comprise instructions configured to cause the processor to set the flag indicating pre-settlement private credit transactions including transaction data associated with one or more of: the buyer, the seller, or the shares in the asset, are to be killed prior to settlement; and
wherein instructions configured to cause the processor to prevent the flow of the “live” private credit transaction and stopping the “live” private credit transaction from settling comprise instructions configured to cause the processor to kill the “live” private credit transaction prior to settlement responsive to the live transaction data matching with the specified transaction data.

### Claim 17 (depends on 16)

The system of claim 16, further comprising instructions configured to cause the processor to subsequent to killing the “live” private credit transaction:
revert a capitalization table to a prior version from before the “live” private credit transaction started; and
re-list the shares in the private credit asset for sale.

### Claim 18 (depends on 11)

The system of claim 11, wherein instructions configured to cause the processor to match the live transaction data with the specified transaction data comprise a microservice configured to match the live transaction data with the specified transaction data.

### Claim 19 (depends on 11)

The system of claim 11, wherein instructions configured to cause the processor to set a flag comprise instructions configured to cause the processor to set a flag applicable to a group of transactions.

### Claim 20 (depends on 11)

The system of claim 11, wherein instructions configured to cause the processor to identify a factor comprise instructions configured to cause the processor to detect an event through an Application Programming Interface (API).
