Systems and methods for release platform operations

Description

"SYSTEMS AND METHODS FOR RELEASE PLATFORM OPERATIONS" CROSS-REFERENCE TO RELATED REQUESTS

[001] This application claims the benefit of U.S. Provisional Application No. 63 / 623,795, filed January 22, 2024, entitled “SYSTEMS AND METHODS FOR RELEASE PLATFORM OPERATIONS,” and U.S. Provisional Application No. 63 / 697,742, filed September 23, 2024, entitled “SYSTEMS AND METHODS FOR RELEASE PLATFORM OPERATIONS,” the contents of which are incorporated herein by reference in their entirety. TECHNICAL FIELD

[002] Aspects of this disclosure relate generally to the implementation of a release functionality and, more particularly, but not limited to, to systems and methods for implementing a release platform system. Some features may enable and provide greater security, greater data integrity and transparency, verification of information and / or documents, immutable records, decentralization, smart contracts, verification (e.g., enhanced verification), reduction of counterparty risk, efficient dispute resolution, data encryption, reduction of operational risk, traceability, or a combination of these factors. BACKGROUND

[003] In a conventional forward contract, a producer enters into a forward contract with a buyer, such as a contract to deliver a future commodity at a predetermined price on a specific date. The producer may need one or more resources (e.g., one or more inputs) to produce the output associated with the contract. For example, if the output is a commodity, such as an agricultural crop, the producer may need to acquire seeds, fertilizers, equipment, or a Petition 870250086483, dated 09 / 24 / 2025, p. 7 / 215 2 / 149 combination of these elements to produce the crop. The producer can purchase the resources from a supplier. In some situations, the producer may not have sufficient funds or credit to acquire the resources from the supplier. In these circumstances, the producer may offer a guarantee instrument, a payment assignment, or a combination of these mechanisms to the supplier. The guarantee instrument, the payment assignment, or both may be associated with or linked to the forward contract and allow the supplier to receive payment from the buyer for the resources acquired by the producer. The buyer may charge a fee, such as a percentage of the purchase price of the resources, and this fee may be deducted from the purchase price.

[004] The conventional forward contract process can present several flaws. For example, the supplier needs to verify the authenticity and validity of the forward contract between the producer and the buyer. Furthermore, the buyer may establish and / or adjust the rate to be deducted from the purchase price, and the producer / supplier may have little or no negotiating or demanding power. Another problem arises when the supplier needs to depend on the buyer to receive payment based on the delivery / receipt of the commodity. If the buyer does not make the payment to the supplier, the supplier will have to waste time and resources to receive the amount due. In addition, in some situations, multiple suppliers may execute various guarantee instruments and / or payment assignments in relation to the same forward contract, without the suppliers being aware of each other's existence.Another problem is that the signed forward contract, guarantee instrument, and / or payment assignment may be lost or misplaced, resulting in payment delays or default by the producer or supplier. Additionally, payments made based on the forward contract, guarantee instrument, and / or payment assignment may be processed by a bank (or banking system) that has little or no expertise. Petition 870250086483, dated 09 / 24 / 2025, page 8 / 215 3 / 149 knowledge about the underlying contractual obligations. Thus, the conventional term contract process can result in lack of data / information security and integrity, lack of transparency, fraud or failure to retain documents, high counterparty risks, expensive and time-consuming dispute resolution, lack of encryption and data protection, operational risks, lack of traceability, or a combination of these factors. SUMMARY

[005] The following summarizes some aspects of this disclosure to provide a basic understanding of the technology discussed. This summary is not a comprehensive overview of all the features covered by the disclosure, and is not intended to identify key or critical elements of all aspects of the disclosure, nor to delineate the scope of any or all aspects of the disclosure. Its sole purpose is to present some concepts from one or more aspects of the disclosure in a summarized form, as a prelude to the more detailed description that will be presented later.

[006] An innovative aspect of the subject described in this disclosure can be implemented in a method, performed by a first computing device, to implement a release service. The method includes obtaining the first contract data associated with a first contract between a first user and a second user. The method further includes verifying whether the first contract data associated with the first contract is valid based on a first entry received from a first device associated with the first user, a second entry received from a second device associated with the second user, or a combination of both. The method also includes, after verifying the first contract, sending a request to create, on an institutional server, a financial account associated with the first contract. The method includes storing, in a database, input information associated with a first entry related to the first contract. Petition 870250086483, dated 09 / 24 / 2025, page 9 / 215 4 / 149 Information from the first entry indicates the first user, the second user, the data from the first contract, the financial account, or a combination of these elements.

[007] Another innovative aspect of the subject described in this disclosure can be implemented in an electronic device, such as a server. The electronic device includes at least one processor and memory coupled to at least one processor. The memory stores processor-readable instructions that, when executed by at least one processor, cause the processor to obtain first-contract data associated with a first contract between a first user and a second user. The instructions, when executed by at least one processor, cause the processor to verify whether the first-contract data associated with the first contract is valid based on a first input received from a first device associated with the first user, a second input received from a second device associated with the second user, or a combination of both.The instructions, when executed by at least one processor, cause the processor, after verifying the first contract, to send a request to create, on an institutional server, a financial account associated with the first contract. The instructions, when executed by at least one processor, cause the processor to store, in a database, information from the first entry associated with a first entry related to the first contract. The information from the first entry indicates the first user, the second user, the data of the first contract, the financial account, or a combination of these elements.

[008] Another innovative aspect of the subject described in this disclosure can be implemented in a non-transient, computer-readable medium that stores instructions. The instructions, when executed by a processor, cause the processor to perform operations that include obtaining data from the first contract associated with a first contract between a first user and a second user. Petition 870250086483, dated 09 / 24 / 2025, page 10 / 215 5 / 149 The operations also include verifying whether the data of the first contract associated with the first contract is valid based on an initial entry received from a first device associated with the first user, a second entry received from a second device associated with the second user, or a combination of both. The operations also include, after verifying the first contract, sending a request to create, on an institutional server, a financial account associated with the first contract. The operations also include storing, in a database, information from the first entry associated with a first entry related to the first contract. The information from the first entry indicates the first user, the second user, the data of the first contract, the financial account, or a combination of these elements.

[009] Another innovative aspect of the subject described in this disclosure can be implemented in a method, performed by a first computing device, to implement a release service. The method includes identifying a financial account on an institution's server, the financial account associated with a first contract between a first user and a second user. The first user is the beneficiary of the financial account, and an entity associated with the first computing device has authority over the financial account. The method also includes identifying a transfer made to the financial account. The method further includes, after identifying the transfer, sending a request to the institution's server to perform one or more distributions from the financial account, the distributions being determined based on a first entry in a database.The first entry is associated with the first contract and indicates the first user, the second user, data from the first contract associated with the first user, the financial account, or a combination of these elements. The method also includes sending a notification indicating the first distribution to a first account associated with the first user. Petition 870250086483, dated 09 / 24 / 2025, page 11 / 215 6 / 149

[010] Another innovative aspect of the subject described in this disclosure can be implemented in an electronic device, such as a server. The electronic device includes at least one processor and memory coupled to at least one processor. The memory stores processor-readable instructions that, when executed by at least one processor, cause the processor to identify a financial account on an institution's server, the financial account associated with a first contract between a first user and a second user. The first user is the beneficiary of the financial account, and an entity associated with the electronic device has authority over the financial account. The instructions, when executed by at least one processor, also cause the processor to identify a transfer made to the financial account.The instructions, when executed by at least one processor, still cause the processor, after identifying the transfer, to send a request to the institution's server to perform one or more distributions of the financial account. These distributions are determined based on an initial entry in a database. The first entry is associated with the first contract and indicates the first user, the second user, data from the first contract associated with the first user, the financial account, or a combination of these elements. The instructions, when executed by at least one processor, also cause the processor to send a notification indicating the first distribution to a first account associated with the first user.

[011] Another innovative aspect of the subject described in this disclosure can be implemented in a non-transient, computer-readable medium that stores instructions. The instructions, when executed by a processor, cause the processor to perform operations that include identifying a financial account on an institution's server, the financial account associated with a first contract between a first user and a second user. The first user is the beneficiary of the account. Petition 870250086483, dated 09 / 24 / 2025, page 12 / 215 7 / 149 Financial and an entity associated with a central server has authority over the financial account. Operations also include identifying a transfer made to the financial account. Operations further include, after identifying the transfer, sending a request to the institution's server to perform one or more distributions from the financial account, with distributions determined based on an initial entry in a database. The initial entry is associated with the first contract and indicates the first user, the second user, data from the first contract associated with the first user, the financial account, or a combination of these elements. Operations also include sending a notification indicating the initial distribution to a first account associated with the first user.

[012] Another innovative aspect of the subject described in this disclosure can be implemented in a system. The system includes a release server configured to obtain first-contract data associated with a first contract between a first user and a second user. The release server is also configured to verify that the first-contract data associated with the first contract is valid based on a first entry received from a first device associated with the first user, a second entry received from a second device associated with the second user, or a combination of both. The release server is further configured to, after verifying the first contract, send a request to create, on an institutional server, a financial account associated with the first contract. The release server is configured to store, in a database, information from the first entry associated with the first contract.The information in the first entry indicates the first user, the second user, the data of the first contract, the financial account, or a combination of these elements. In some implementations, the system that includes the release server also includes a central server, the institution's server, the database, or a... Petition 870250086483, dated 09 / 24 / 2025, page 13 / 215 8 / 149 combination of these elements.

[013] Some details associated with the implementations are described above, and others are described below. Other aspects, features, and implementations of this disclosure will become apparent to a person of average skill in the field by reviewing the following description of specific and exemplary implementations of this disclosure in conjunction with the accompanying figures. Although the features of this disclosure may be described in relation to particular implementations and figures below, all implementations of this disclosure may include one or more of the advantageous features described herein. In other words, although one or more implementations may be described as having particular advantageous features, one or more of these features may also be used in accordance with the various implementations of the disclosure described herein.Similarly, although exemplary implementations may be described below as implementations of devices, systems, or methods, such exemplary implementations may be implemented in various devices, systems, and methods. Other implementations, advantages, and features of the present disclosure will become apparent after reviewing the entire application, including the following sections: Brief Description of the Drawings, Detailed Description, and the Claims. BRIEF DESCRIPTION OF THE DRAWINGS

[014] A further understanding of the nature and advantages of the present disclosure can be obtained by reference to the following drawings. The following drawings illustrate, by way of example and not limitation. In the attached figures, similar components or features may have the same reference label.

[015] Figure 1A is a block diagram of an example of a release system according to one or more aspects. Petition 870250086483, dated 09 / 24 / 2025, page 14 / 215 9 / 149

[016] Figure 1B is a block diagram of another example of a release system according to one or more aspects.

[017] Figure 2 is a flow diagram illustrating an example of a process that supports the operation of a release system according to one or more aspects.

[018] Figures 3-8 are exemplary graphical user interface (GUI) diagrams to illustrate the operation of a release system according to one or more aspects.

[019] Figure 9 is a flow diagram illustrating another example of a process that supports the operation of a release system according to one or more aspects.

[020] Figures 10-17 are exemplary GUI diagrams to illustrate the operation of a release system according to one or more aspects.

[021] Figures 18-23 illustrate operations of a release system according to one or more aspects.

[022] Figure 24 is a block diagram of an example of a release system according to one or more aspects.

[023] Figure 25 is a block diagram of an example system according to one or more aspects.

[024] Figure 26 is a flow diagram illustrating another example of a process that supports the operation of a release system according to one or more aspects.

[025] Figure 27 is a ladder diagram illustrating an example of operations associated with a release system according to one or more aspects.

[026] Figure 28 is a ladder diagram illustrating an example of operations associated with a release system according to one or more Petition 870250086483, dated 09 / 24 / 2025, page 15 / 215 10 / 149 aspects.

[027] Figure 29 is a flow diagram of an example of a server process that supports the operation of a release system according to one or more aspects.

[028] Figure 30 is a flow diagram of another example of a server process that supports the operation of a release system according to one or more aspects.

[029] Figures 31-37 are exemplary GUI diagrams to illustrate the operation of a release system according to one or more aspects.

[030] Figure 38 is a block diagram of an example database of a release system according to one or more aspects.

[031] Similar numbers and reference designations in the various figures indicate similar elements. DETAILED DESCRIPTION

[032] Several aspects of the disclosure are described more fully below with reference to the accompanying drawings. This disclosure can, however, be carried out in several different ways and should not be interpreted as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided so that this disclosure is comprehensive and complete, and to fully convey the scope of the disclosure to those skilled in the field. Based on the teachings described herein, a person skilled in the field will be able to perceive that the scope of the disclosure aims to cover any aspect of the disclosure presented herein, whether implemented independently or combined with any other aspect of the disclosure. For example, an apparatus can be implemented or a method can be practiced using any number of the aspects presented herein.Furthermore, the scope of the disclosure aims to cover such apparatus or method practiced using another structure, functionality or framework and. Petition 870250086483, dated 09 / 24 / 2025, p. 16 / 215 11 / 149 functionality beyond or distinct from the various aspects of the disclosure presented here. Any aspect of the disclosure presented here may be materialized by one or more elements of a claim.

[033] This disclosure provides computer-readable systems, devices, methods, and media for implementing a clearing system, such as a transient payment account system. The clearing system (e.g., the transient payment account system) is configured to operate with a financial institution, such as a banking system. For example, the clearing system may interact with the financial institution to provide services associated with a business chain, such as an agribusiness chain. In some implementations, the clearing system may be configured to enhance the settlement of forward contracts through dynamic account creation, secure user authentication, and efficient financial transactions, leveraging both banking infrastructure and innovative technological solutions.

[034] In some implementations, the clearing system includes a clearing server that is configured to verify multiple users and confirm an agreement between two or more of those users. The clearing server can generate an entry in a database based on the confirmed agreement. For example, the database might include a blockchain ledger, and the clearing server might create an entry in the blockchain ledger. In some implementations, the clearing server generates a smart contract based on the agreement, and the smart contract is stored as part of the entry. The clearing server might also initiate the creation of a financial account (e.g., a trust account) at a financial institution, such as a bank. In some implementations, the clearing server might provide the user with the option to select which financial institution (among several financial institutions) to use to create the financial account.The financial account may be associated with the agreement (for example). Petition 870250086483, dated 09 / 24 / 2025, page 17 / 215 12 / 149 example, the entry on the blockchain). The financial account can receive funds associated with the agreement, and the clearing server can initiate a disbursement of funds to one or more of the multiple users. For example, the clearing server can determine one or more disbursements based on the entry on the blockchain.

[035] In some implementations, the clearing system includes a central server. The central server may be part of the clearing server or may be distinct from it. The central server is configured to provide a payment service associated with the transaction. For example, the central server may establish a transfer account (e.g., a payment transit account) that is configured to receive funds (e.g., a payment) associated with the agreement (e.g., the entry into the blockchain). The central server may provide the funds to the financial account and may initiate one or more distributions of the funds from the financial account to one or more user accounts of the multiple users. In some implementations, the central server is also configured to determine and / or deduct one or more fees associated with the funds received in the transfer account.Fees may include a service fee, a regulatory fee, or a combination thereof, by way of illustrative, but not limiting, examples.

[036] In some implementations, a clearing system (e.g., clearing server and / or central server) can provide a technical solution for large financial institutions to manage loans and disbursements associated with agreements, such as forward contracts, with greater security, improved success rate, and / or greater visibility compared to other systems. For example, the clearing system can limit or resolve problems associated with conventional forward contracts, such as counterparty and default risks, fees, lack of transparency, etc. Additionally, or alternatively, in some implementations, the clearing system may include a platform for Petition 870250086483, dated 09 / 24 / 2025, page 18 / 215 13 / 149 self-service (e.g., a third-party platform) in which there is limited interaction with a financial institution. Although there is limited interaction, the financial institution may have greater and more reliable visibility into the underlying transaction, for example, knowing who the parties and / or counterparties are in one or more agreements.

[037] In addition, or alternatively, in some implementations, the clearing system may be configured to provide document management services, contract management services, or a combination thereof. The clearing system may be configured to register users and store user data, store account data (e.g., bank account data), classify and / or store document / agreement data, link different stored data, and generate and store executable applications (e.g., smart contracts). The data stored by the clearing server may be stored in a database and, optionally, may be stored immutably. The database may include a ledger, such as a blockchain.In some implementations, the clearing server is configured to receive document data from users, where the documents have different data formats, different document types, different data item types, different data encodings, or a combination thereof. The clearing system can be configured to store the received document data (e.g., in its original format) and generate standardized document data for use in smart contract generation. To illustrate, the clearing system can be configured to identify data items (e.g., information) included in the received documents and standardize the data items (e.g., the different formats, the different document types, the different data item types, the different data encodings, or a combination thereof) to facilitate the generation and / or storage of standardized document data. The clearing system can be... Petition 870250086483, dated 09 / 24 / 2025, page 19 / 215 14 / 149 is configured to facilitate data access and sharing of original document data and standardized document data. In some implementations, the clearing server may also receive user inputs that include or indicate data items that can also be stored in the database in a standardized format. Based on the standardized data (e.g., standardized document data and / or standardized input data) stored in the database, the clearing system can generate one or more smart contracts.

[038] In addition, or alternatively, the clearing system can be configured to receive sensor data from one or more sensors, such as sensors related to an agribusiness supply chain, which have different sensor data formats, different sensor data types, different sensor data encodings, or a combination thereof. The clearing system can be configured to store the received sensor data (e.g., in the original format) and generate standardized sensor data for use as input in one or more smart contracts.To illustrate, the compensation system can be configured to identify sensor data items (e.g., information) included in the sensor data and generate standardized sensor data (e.g., standardizing the different sensor data formats, the different sensor types, the different types of sensor data items, the different sensor data encodings, or a combination thereof) for storage. In some implementations, the standardized sensor data can be used as input to a smart contract to trigger the execution of at least one part of the smart contract.

[039] In addition, or alternatively, the clearing system and / or the database may include one or more application programming interfaces (APIs) that allow access (e.g., authorized or user-based access). Petition 870250086483, dated 09 / 24 / 2025, page 20 / 215 15 / 149 permissions) to the data stored in the database. In some implementations, the clearing system can be configured to identify a user and the user's authorization / access level. For example, different users may have different read / write access levels with respect to the database and / or the clearing system. The clearing system may generate data output for the user based on the user's authorization / access level. Thus, different users of the clearing system may receive different data from the clearing system based on the user's authorization / access level. In some implementations, a first user may request authorization or access to data associated with a second user, and / or the second user may grant the first user access to data associated with them.Additionally, or alternatively, the clearing system may send notifications to different users that include accessible data based on the authorization / access levels of the different users. In some examples, notifications may be based on an event, a status change, time-sensitive information, or a combination thereof. In some implementations, notifications (e.g., push notifications) may be sent to a user's device, such as a smartphone. Notifications may include one or more portions of the standardized data that the respective user is authorized to access. Furthermore, or alternatively, the clearing system may provide an application (e.g., a software application such as a mobile app or a desktop application) to a user's device to allow the user to securely access the clearing system.These applications can be configured to allow user access according to the user's authorization / access level.

[040] In some implementations, the compensation system is configured to generate one or more reports based on the data stored in the database. Petition 870250086483, dated 09 / 24 / 2025, page 21 / 215 16 / 149 data. For example, a report can be generated based on standardized data stored in the database. The report generated by the clearing system can be user-specific, transaction-specific, a regulatory report, a timeline report of events or actions associated with a user or transaction, or a combination thereof. The clearing system may also be able to determine (e.g., calculate) one or more metrics based on the standardized data. The metrics can be provided to one or more users and / or used by the clearing system or by a user to make a determination or selection. For example, the clearing system might select a rate for a user based on one or more metrics associated with the user, select a server to offer or provide to the user based on the metrics, or a combination thereof.

[041] Specific implementations of the subject described in this disclosure may be implemented to achieve one or more of the following technical advantages. In some respects, the techniques of this disclosure relating to clearing functionality offer the technical advantage of greater interoperability between devices, improved efficiency in data processing, data validation and integrity, and improved data security. For example, a clearing system may provide a process for user verification, agreement verification, standardization of data communication, rate calculation, data standardization / formatting and / or status information reporting, standardization of communication between devices of the clearing system, or a combination thereof.By standardizing the formatting, encoding, or both, of data related to an agreement, the clearing server can be configured to improve interoperability between devices associated with users who are parties to the agreement, thus improving data coordination between multiple devices and platforms without requiring specific hardware or software solutions. Petition 870250086483, dated 09 / 24 / 2025, page 22 / 215 17 / 149 targeted. In addition, the processes implemented by the compensation system can improve data processing efficiency, data integrity, data transparency, and / or data security.

[042] Furthermore, in some implementations, the clearing system may include or allow blockchain-enabled transparency, which can improve data integrity and increase trust in the automated execution of smart contracts. For example, the clearing system may include or match a white-label product that empowers participants in an existing advance payment contract (in any sector), increasing transparency for the bank and counterparties in a secure and permissioned manner. In some implementations, the clearing system is blockchain-enabled and integrated into the central banking system to boost operations.

[043] The clearing system can also offer a scalable solution. For example, the clearing system can be applied to existing small, medium, and large ecosystems with supply chains involving multiple participants where forward contracts are used. Furthermore, or alternatively, the clearing system can allow a trusted third-party institution, such as a central banking service, a payment system / service, or a combination thereof, to facilitate transactions, improving trust and reducing risks among participants, while facilitating lending opportunities by financial institutions, enhancing underwriting capabilities with the additional data provided by the solution, or a combination of these factors. Thus, the clearing system can also be configured to provide revenue opportunities.

[044] The compensation system can provide a variety of improvements, such as technological improvements, which increase transparency, reduce operating costs, improve data integrity, and increase security. Petition 870250086483, dated 09 / 24 / 2025, page 23 / 215 18 / 149 In general, they generate new data structures and leverage APIs (such as REST APIs or webhooks). The use of one or more APIs can provide standardized integration points and / or specify data formats or protocols that allow interoperability between different users / entities (e.g., different devices and / or different systems). Furthermore, or alternatively, the clearing system can be configured to integrate with financial institutions, allowing lending partners to have comprehensive visibility into transactions and contract details, increasing their ability to offer customized services. This integration can also allow lending partners to benefit from increased cash flow, providing more value and innovation to the agricultural industry and ultimately attracting new customers.In some implementations, the clearing system can guarantee the payment recipient certainty of receiving payment through the allocation of funds managed by the bank upon deposit into the payment clearing account. For sellers, the clearing system can facilitate loan applications for any user (e.g., sellers or buyers). To illustrate, the clearing system can facilitate loan applications for a user using projections of future income (after setting up the payment clearing account). Additionally, or alternatively, for buyers, the clearing system can streamline the payment process by automating distribution to multiple parties, simplifying the buyer's role.

[045] Referring to Figure 1A, a block diagram of an example of a clearing system 100 according to one or more aspects is shown. The system 100 includes user devices (such as a producer device 102, a buyer device 130 and a recipient device 140), a clearing server 116 (for example, a clearing platform) and a server of Petition 870250086483, dated 09 / 24 / 2025, page 24 / 215 19 / 149 institution 150. In some implementations, the system 100 may also include one or more banking devices (or servers), such as a first banking device 160, a second banking device 162, or a combination thereof. Note that in some implementations, the institution server 150 may be a banking device (e.g., a bank server). The producer device 102, the clearing server 116, the buyer device 130, the recipient device 140, the institution server 150, the first banking device 160, the second banking device 162, or a combination thereof may include or correspond to an electronic device, such as a server or computer, as illustrative and non-limiting examples. In some implementations, the institution server 150 may include or correspond to a financial institution, such as a bank.

[046] The producer device 102 includes a processing system. The processing system includes one or more processors 104 (collectively referred to as processor 104), one or more memories 106 (collectively referred to as memory 106), or a combination thereof. In addition, the producer device 102 includes a network interface 114. Although not depicted, the producer device 102 may include one or more input / output (I / O) devices, such as a mouse, touch screen, keyboard, monitor, other interface, or a combination thereof, configured to receive input from a user, provide output to the user, or both. Different device and / or computer architectures may be used to implement the producer device 102, and the producer device 102 is not limited to a specific architecture, provided that the hardware implementing the producer device 102 supports the compensation system functions described herein.

[047] The 104 processor may include a central processing unit (CPU) or microprocessor, a graphics processing unit (GPU), Petition 870250086483, dated 09 / 24 / 2025, page 25 / 215 20 / 149 microcontroller or a combination thereof, programmed to perform the functions of the manufacturer's device 102. The implementations described herein are not restricted by the architecture of processor 104, provided that processor 104, directly or indirectly, supports the operations described. Processor 104 may be a single component or multiple components that execute the various logical instructions described, such as instructions 108. This disclosure is not restricted by the architecture of processor 104, provided that processor 104 supports modules, configurations, or operations as described herein.Furthermore, as will be understood by those with experience in the field, a “module” may include an application-specific integrated circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or grouped) that executes one or more software or firmware applications, a combinational logic circuit, and / or other suitable components that provide the described functionality. In some implementations, a module is a standalone hardware or software component that interacts with a larger system. Alan Freedman, The Computer Glossary 268 (8th ed. 1998).

[048] Memory 106 includes or is configured to store instructions 108 and / or contract information 110. Instructions 108 may include or correspond to object code, source code, firmware, or combinations thereof that, when executed by processor 104, cause the execution of operations as described in this disclosure. Contract information 110 may include or correspond to a contract (e.g., a forward contract), a purchase agreement, a pledge instrument, a payment reassignment, or a combination thereof. In some implementations, contract information 110 may be associated with a contract (e.g., a forward contract) for the exchange of a good (e.g., an object, product, commodity, etc.) or a service. As illustrative, but not limiting, examples, the good (e.g., a commodity) may include corn, wheat, coffee, soybeans, Petition 870250086483, dated 09 / 24 / 2025, page 26 / 215 21 / 149 apples, bananas, meat, pigs, cows, earth, gravel, fabric, clothing, corn, oats, paddy rice, rapeseed, soybean meal, soybean oil, milk, cocoa, coffee C, cotton No. 2, sugar No. 11, sugar No. 14, frozen concentrated orange juice, adzuki beans, an energy resource (e.g., petroleum, coal, gas) or any other type of commodity.

[049] Network interface 114 can be adapted to connect producer device 102 to a network 164, which may be one or more local area networks (LANs), wide area networks (WANs), and / or the Internet. Therefore, in some implementations, producer device 102 can be accessed via an online portal. In some implementations, network interface 114 includes a transceiver configured to send and receive signals, such as electronic signals. Although described as a transceiver, network interface 114 may alternatively include a receiver, a transmitter, or both. In some implementations, network interface 114 includes a wireless interface, such as a long-range interface (LoRa), a Wi-Fi interface (e.g., an IEEE 802.11 interface), a cellular interface, a Bluetooth interface, a Bluetooth Low Energy (BLE) interface, a Zigbee interface, another type of low-power network interface, or similar.

[050] The 116 clearing server (also referred to as a management server) can be associated with a platform, such as a platform configured to perform one or more functions. For example, the 116 clearing server can be configured to provide supply chain digitization (e.g., digitizing supply chain information). To further illustrate, as an illustrative and non-limiting example, the 116 clearing server can facilitate transactions between farmers, buyers, and financial institutions. Through the use of smart contracts and blockchain, the 116 clearing server automates transactions, ensuring that the parties Petition 870250086483, dated 09 / 24 / 2025, page 27 / 215 22 / 149 fulfill their contractual obligations in a transparent and secure manner. In some implementations, the clearing server 116 may include or communicate with a payment service, such as a payment microservice, which includes a platform agnostic to the platform of a financial institution (e.g., the financial institution associated with the institution server 150). In other implementations, the platform associated with the payment service is included in or controlled / managed by the financial institution associated with the institution server 150. The payment service (such as a payment microservice) may be configured to accommodate payments such as traditional fiat currencies, cryptocurrencies, stablecoins, Central Bank Digital Currencies (CBDCs), and / or tokenized assets.

[051] In some examples, the payment service may be a central payment service-based system (e.g., a central payment microservice-based system), in which the central system may enable a variety of functionalities, such as allowing a client / user to authorize the clearing server 116 to operate on one or more (or all) of that client's bank resources, thus allowing the clearing server 116 to view or access balances and / or transactions, and / or issue outbound transfers. The central system may also utilize one or more application programming interfaces (APIs) that allow the clearing server 116 to perform operations for near real-time fund transfers and / or high-value transactions. The central system may include or correspond to the central server 250 (e.g., a payment server or a transaction server) described further below, at least with reference to FIG. 1B.In some implementations, the entity that operates / administers the central system is a different entity from the entity that operates the clearing server 116.

[052] In addition, the 116 clearing server can be configured to reduce fraud and increase trust associated with transactions managed by Petition 870250086483, dated 09 / 24 / 2025, page 28 / 215 23 / 149 Clearing Server 116. To illustrate, by using a blockchain to record transactions (as described below), each step of the transaction is immutably recorded, significantly reducing the possibility of fraud. This increases trust between all parties / users, from producers to banks and buyers, as illustrative, non-limiting examples. Clearing Server 116 can also improve liquidity and access to credit for one or more users of Clearing Server 116. For example, Clearing Server 116 allows producers (e.g., farmers) to sell their products efficiently and access faster payments, improving liquidity.Furthermore, the 116 clearing server facilitates access to credit by providing a lender (e.g., a recipient associated with the 140 recipient device) with verifiable and transparent data from one or more transactions (e.g., agricultural transactions), thereby increasing the likelihood of lenders granting credit or speeding up the process of such transactions. The 116 clearing server can operate in conjunction with one or more 150 institution servers (e.g., financial institutions) to enable access to a financial institution via the 116 clearing server. For example, the 116 clearing server can perform or facilitate the management of trust accounts, user authentication, and bank account verification, all performed in accordance with the financial institution's local rules and regulations.

[053] The clearing server 116 includes a processing system composed of one or more processors 119 (collectively referred to as processor 118), one or more memories 120 (collectively referred to as memory 120), or a combination thereof. In addition, the clearing server 116 includes a network interface 129. Although not shown, the clearing server 116 may include one or more input / output (I / O) devices, such as a mouse, keyboard, touch screen, monitor, other type of interface, or a Petition 870250086483, dated 09 / 24 / 2025, page 29 / 215 24 / 149 combination thereof, configured to receive input from a user and provide output to the user. Different server and computer architectures can be used to implement the 116 clearing server, and the 116 clearing server is not limited to a specific architecture, provided that the hardware implementing the 116 clearing server supports the management system functions described herein. For example, the 116 clearing server may include one or more servers, a decentralized platform, or a cloud computing platform configured to perform operations or execute the steps described herein.

[054] The processor 118, memory 120 and network interface 129 of the clearing server 116 may correspond (i.e., be analogous) to the processor 104, memory 106 and network interface 114 of the producer device 102. Thus, the processor 118, memory 120 and network interface 129 may include similar or identical features to those described with reference to the processor 104, memory 106 and network interface 114.

[055] Memory 120 can be configured to store instructions 122, participant information 124 (e.g., user information, bank account information, etc.), a database 126, an API 128, or a combination of these elements. In some implementations, the instructions 122, participant information 124, database 126, API 128, or a combination thereof may be stored externally (i.e., remotely) from the clearing server 116. The instructions 122 may include or correspond to object code, source code, firmware, or combinations thereof that, when executed by the processor 118, cause the processor 118 to perform operations in accordance with the aspects of this disclosure as described herein.

[056] Participant information 124 may include data associated with or corresponding to one or more users or entities, such as a producer, a Petition 870250086483, dated 09 / 24 / 2025, page 30 / 215 25 / 149 buyer, a recipient, an institution, a bank, a central entity, or a combination thereof. For example, participant information 124 may store producer data associated with or corresponding to a producer device operator or owner 102. As another example, participant information 124 may store buyer data associated with a buyer device operator or owner 130. As yet another example, participant information 124 may store recipient data associated with a recipient device operator or owner 140.

[057] In some implementations, for a user or entity, participant information 124 includes or indicates a name, company, date of birth, nationality, government identification number, CPF / CNPJ, email address, telephone number, fax number, address, account information, sustainability information, or a combination thereof. Account information may include or indicate a bank account, the name of the bank providing the bank account, a routing number associated with a third-party bank account, the type of bank account, the name of the bank account holder, or a combination thereof. Sustainability information may include or indicate sustainable agricultural practices, certifications or sustainable metrics (e.g., organic standards, carbon footprint), environmental, social, and governance (ESG) indicators, or a combination thereof.

[058] The 126 database can store a 127 ledger, as one or more data structures and / or a blockchain-based ledger. The 127 ledger (e.g., the blockchain ledger) can be a secure data structure that allows users of a distributed computing system to trust the accuracy of the data included in the blockchain ledger. For example, the 127 ledger (e.g., the blockchain ledger) is a data structure stored using storage resources of the distributed computing system. The ledger Petition 870250086483, dated 09 / 24 / 2025, page 31 / 215 26 / 149 Ledger 127 (e.g., the blockchain ledger) may include a record or history of transactions facilitated by clearing server 116. API 128 may include one or more interfaces. Although database 126 and ledger 127 are described as being included in clearing server 116, in other implementations, database 126 and ledger 127 may be separate from clearing server 116 and accessible by it. For example, database 126 and ledger 127 may be included on the same remote server, distinct from clearing server 116. As another example, database 126 may be included on a first remote server and ledger 127 may be included on a second remote server. In some implementations, database 126 (e.g., ledger 127) indicates or records one or more transactions (e.g., payments, transfers, disbursements, etc.).) associated with a contract between multiple users. An example of database 126 is described later, at least with reference to FIG. 38.

[059] API 128 may include one or more interfaces that enable communication or interfacing with the clearing server 116 by other devices or applications. For example, API 128 (or the various interfaces) may be accessible by one or more devices, such as the producer device 102, the clearing server 116, the debtor device 130, the receiver device 140, the institution server 150, the first banking device 160, the second banking device 162, a central server (as described, at least with reference to FIG. 1B), or a combination thereof. In some implementations, the clearing server 116 and / or the database 126 may include API 128 or an interface layer that provides the user or entity with the ability to access at least a portion of the database 126.For example, API 128 or the interface layer can provide read-only access or limited write / execute transaction privileges to the user or entity. Petition 870250086483, dated 09 / 24 / 2025, page 32 / 215 27 / 149

[060] The receiver device 140 includes a processing system composed of one or more processors 142 (collectively referred to as processor 142), one or more memories 144 (collectively referred to as memory 144), or a combination of these components. In addition, the receiver device 140 includes a network interface 148.

[061] Processor 142, memory 144, and network interface 148 may correspond to (i.e., be analogous to) processor 104, memory 106, and network interface 114, respectively, of producer device 102. Thus, processor 142, memory 144, and network interface 148 may include similar or the same characteristics described with reference to processor 104, memory 106, and network interface 114, respectively. Processor 142 may be configured to execute instructions 146 stored in memory 144 to perform one or more operations described in this document.

[062] The institution's server 150 includes a processing system that includes one or more processors 152 (collectively referred to as processor 152), one or more memories 154 (collectively referred to as memory 154), or a combination thereof. In addition, the institution's server 150 includes a network interface 159.

[063] Processor 152, memory 154, and network interface 159 may correspond to (i.e., be analogous to) processor 104, memory 106, and network interface 114, respectively, of producer device 102. Thus, processor 152, memory 154, and network interface 159 may include similar or the same features described with reference to processor 104, memory 106, and network interface 114, respectively. Processor 152 may be configured to execute instructions 156 stored in memory 154 to perform one or more operations described herein. Memory 154 may also include or store account information 158, such as one or more Petition 870250086483, dated 09 / 24 / 2025, p. 33 / 215 28 / 149 financial accounts (e.g., a trust account).

[064] In some implementations, the institution server 150 includes or supports one or more APIs. Each of the one or more APIs may allow another device, such as the release server 116, to interact with the institution server 150. For example, the one or more APIs may include a first API to allow the release server 116 to create a new bank account (e.g., to declare payments) and obtain the account details. The one or more APIs may also additionally or alternatively include a second API to allow another device to transfer funds from another bank account to an account on the institution server 150. The one or more APIs may further additionally or alternatively include a third API to allow another device (e.g., the release server 116 or a user device) to obtain notifications of any deposit into an account on the institution server 150.One or more APIs may additionally or alternatively include a fourth API to allow another device (for example, the release server 116 or a user device) to transfer money from an account on the institution server 150 to another account on the institution server 150 or to another financial institution.

[065] The first banking device 160, the second banking device 162, or both, may include one or more components as described herein with reference to the institution's server 150. In some implementations, the first banking device 160 and / or the second banking device 162 include, respectively, one or more servers, a decentralized platform, or a cloud computing platform. In addition, or alternatively, the first banking device 160, the second banking device 162, or both, may be configured to perform one or more operations described herein with reference to the institution's server 150. In some implementations, the first banking device 160 is associated with a first account owned by the same entity. Petition 870250086483, dated 09 / 24 / 2025, page 34 / 215 29 / 149 that owns or operates the offtaker device 130. For example, an offtaker associated with the offtaker device 130 may have a first account with an entity (e.g., a bank or financial institution) associated with the first banking device 160. Additionally, or alternatively, the second banking device 162 may be associated with a second account owned by the same entity associated with (e.g., owning or operating) the recipient device 140. For example, a recipient associated with the recipient device 140 may have a first account with an entity (e.g., a bank or financial institution) associated with the second banking device 162. In some implementations, the owner or operator of the offtaker device 130 additionally or alternatively has an account with the financial institution associated with (e.g., owning or operating) the institution server 150.In addition, or alternatively, the owner or operator of the recipient device 140 additionally or alternatively has an account with the institution associated with (e.g., owns or operates) the institution's server 150.

[066] The concepts described herein are not limited to the architecture of the producer device 102, the clearing server 116, the offtaker device 130, the recipient device 140, the institution server 150, the first banking device 160, the second banking device 162, a central server (as described with reference to FIG. 1B), or any combination thereof. Instead, the items mentioned are provided as examples of computing devices that can be adapted to perform the functions of the devices as described herein. In particular, any suitable processor-based device may be used, including, without limitation, personal digital assistants (PDAs), computers, laptops, tablet computers, smartphones, video game consoles, multiprocessor servers, and others, as illustrative and non-limiting examples. Furthermore, or alternatively, while the server of Petition 870250086483, dated 09 / 24 / 2025, page 35 / 215 30 / 149 compensation 116 and the institution server 150 are illustrated as physically distinct systems; in some implementations, compensation server 116 and institution server 150 may be implemented in a single system that includes a processor (e.g., processor 118 and / or processor 152), a memory (e.g., memory 120 and / or memory 154), and a network interface (e.g., network interface 129 and network interface 159).

[067] Although described with a single institution server 150 interacting with clearing server 116, system 100 may include multiple institution servers (e.g., institution server 150) configured to interact with clearing server 116. To illustrate, each institution server of the multiple institution servers may be associated with a different institution (e.g., a different bank), and each respective institution server may be communicatively coupled to clearing server 116 (e.g., via network 164). In some implementations, institution server 150 may include one or more servers, a decentralized platform, or a cloud computing platform configured to perform operations or execute the steps described herein.

[068] Furthermore, the systems and methods of this disclosure can be implemented in application-specific integrated circuits (ASICs), very large-scale integrated circuits (VLSIs), or other circuits. Additionally, it should be understood that the devices described herein, or certain components thereof, may reside in, or be installed in, different locations within the system 100. In some implementations, the devices of the system 100 may include one or more servers, a decentralized platform, or a cloud computing platform configured to perform operations or execute the steps described herein. For example, the clearing server 116, the institution server 150, and / or a central server may include a cloud computing platform or a Petition 870250086483, dated 09 / 24 / 2025, page 36 / 215 31 / 149 decentralized platform. Thus, any of the devices in system 100 may include a purpose-built computing system designed, configured, or adapted to perform and / or initiate operations, functions, processes, and / or methods described herein and may be communicatively coupled to various end-user devices, which may be, for example, a computer, tablet, smartphone, or other similar end-user computing device, as illustrative and non-limiting examples. Users may interact with any of the devices in system 100 using a device via one or more networks, such as network 164, which may include one or more local intranets, LANs, WANs, virtual private networks (VPNs), and so forth.Communicative coupling between different devices in the 100 system can be provided by, for example, one or more wireless connections, a synchronous optical network connection (SONET), a digital line (T1, TN, E1 or E3), a Digital Data Service (DDS) connection, a DSL (Digital Subscriber Line) connection, an Ethernet connection, and so on, as illustrative and non-limiting examples.

[069] The 164 network, as a communication network, can facilitate data communication between the components of the 100 system. For example, the 164 network can facilitate data communication between the producer device 102, the clearing server 116, the buyer device 130, the recipient device 140, the institution server 150, the first banking device 160, the second banking device 162, a central server, or a combination thereof. The 164 network can include a wired network, a wireless network, or a combination thereof. For example, the 164 network can include any type of communication network, such as a direct PC-to-PC connection, a LAN, a WAN, a modem-to-modem connection, the Internet, intranet, extranet, cable transmission system, cellular communication network, any combination of the above, or any other communication network currently known or developed in the future, within which it allows Petition 870250086483, dated 09 / 24 / 2025, page 37 / 215 32 / 149 that two or more electronic devices communicate.

[070] In some implementations, the clearing server 116, or another server – for example, a central server 250, is associated with or hosts an application (also referred to here as an app), such as a mobile application and / or a web platform. The application includes a computer program configured to function as a user interface for one or more users to interact with and / or perform one or more operations with or via the clearing server 116. In implementations where the application includes a mobile application, at least part of it may be stored on a user's device and may be operable or available to the user in online mode.

[071] During the operation of system 100, the producer device 102 can log in to or access the clearing server 116. For example, a producer (e.g., an entity or individual) associated with the producer device 102 may have login credentials associated with a service provided by the clearing server 116, such as login credentials associated with a clearing service.

[072] Producer device 102 can send contract information 110 (e.g., contract data) to clearing server 116. The contract information 110 sent by producer device 102 may include or indicate contract information 110 stored on producer device 102, which may represent a contract (e.g., a forward contract) between the producer and a buyer (e.g., an offtaker). The offtaker may be an individual or an entity associated with offtaker device 130.

[073] In addition, or alternatively, the producer device 102 may request that the clearing server 116 initiate or request the institution server 150 to create an account associated with the producer, the contract information 110, or a combination thereof. In some implementations, the producer device Petition 870250086483, dated 09 / 24 / 2025, page 38 / 215 33 / 149 102 can indicate which financial institution (e.g., a bank) the account should be created for. For example, the producer's device 102 can indicate a financial institution where the producer already has an existing personal account. Additionally, or alternatively, the clearing server 116 can request that the producer's device 102 select the financial institution from among several financial institutions. Based on the request, the clearing server 116 can send an account request 172 to the institution's server 150. The account request 172 can include contract information 110, information (e.g., name, address, phone number, email address, etc.) about the producer, information (e.g., name, address, phone number, email address, etc.) about the offtaker, or a combination thereof.

[074] Based on account request 172, institution server 150 may generate or create a clearing account, such as a financial account (e.g., a custody account or a trust account). For example, institution server 150 may generate account information 158 associated with the clearing account. The account information 158 associated with the clearing account may include a clearing account ID 174. Institution server 150 may send account ID 174 to clearing server 116, producer device 102, or a combination thereof.

[075] Based on the receipt, by clearing server 116, of contract information 110, the request to create an account, the account ID 174, or a combination thereof, clearing server 116 may send a verification request 176 to the offtaker's device 130. Verification request 176 may request that the offtaker verify that it is a party to the contract associated with the contract information 110. In some implementations, the offtaker may be provided with an option to submit the contract information that is in its possession as part of the verification process. Petition 870250086483, dated 09 / 24 / 2025, page 39 / 215 34 / 149

[076] The offtaker device 130 may send a verification response 178 to the clearing server 116. The verification response 178 may include or indicate whether or not the offtaker verifies that it is a party to the contract associated with the contract information 110. Additionally, or alternatively, the verification response 178 (or an additional response / message) may include or indicate contract information that is in the offtaker's possession. In some implementations, the verification response 178 (or an additional response / message) may include or indicate an account acknowledgment indicating that the offtaker acknowledges that the account at the institution associated with the institution server 150 was established on behalf of the producer in relation to the contract information 110, to which the offtaker is a party.In some implementations, when clearing server 116 receives contract information 110 from producer device 102 and also receives contract information from offtaker device 130, clearing server 116 can perform a comparison to determine if the contract information 110 from producer device 102 and the contract information from offtaker device 130 match—that is, to determine if there is any discrepancy.

[077] Clearing server 116 can send a verification notification 180 to the producer device 102. The verification notification 180 can be sent based on and / or indicate the result of the verification response 178. In some implementations, clearing server 116 can also send the verification notification 180 to the institution server 150. The verification notification 180 can indicate that a valid contract (e.g., a futures contract) has been established between the producer and the offtaker, and that the offtaker will pay the producer through the financial account established (in relation to the contract) at the institution.

[078] Based on a valid and verified agreement, the producer may purchase or acquire one or more resources (e.g., one or more inputs) to produce a Petition 870250086483, dated 09 / 24 / 2025, page 40 / 215 35 / 149 Product associated with the agreement. The producer may purchase or acquire resources from a supplier (also called the recipient). However, instead of paying for the purchase of the resources in cash, the producer may offer a pledge instrument, a payment assignment, or a combination thereof, to the supplier, so that the supplier becomes the recipient of a portion of a payment (associated with the information in agreement 110) that the product taker makes to the producer through the institution. In some examples, the producer may purchase seeds, fertilizers, equipment (e.g., a tractor), or similar items to enable the production of the contracted product.In addition, or alternatively, the producer can obtain a loan and receive money from the recipient, and the producer can use the money to pay for agricultural labor (e.g., farm workers), logistics-related labor (e.g., a driver), an insurance product, or another product or service.

[079] Based on the pledge instrument, payment assignment, or a combination thereof, which the recipient receives from the producer, the recipient may need to be approved by the producer to receive the payment portion through the institution. In some implementations, the producer may initiate an approval process to allow the recipient to submit a request (e.g., an invoice) for payment. For example, producer device 102 may send the pledge instrument, payment assignment, or a combination thereof to clearing server 116 with respect to agreement information 110, account ID 174, or a combination thereof. Clearing server 116 may then send a notification to recipient device 140 to inform the recipient that they may submit a payment request for approval by the producer. The payment request by the supplier (e.g., the recipient) is described in more detail here.

[080] In some implementations, the recipient (using the device of Petition 870250086483, dated 09 / 24 / 2025, page 41 / 215 36 / 149 recipient 140) can initiate authorization and / or approval by the producer to receive the payment portion through the institution. To illustrate, recipient 140's device can access clearing server 116 and perform a search to identify the producer, the agreement information 110, the account ID 174, or a combination thereof, and authorize or approve a payment portion related to the agreement. In some implementations, recipient 140's device can send a request 182 (e.g., a search request) to clearing server 116 to initiate the search.

[081] Based on request 182, clearing server 116 can identify the producer, the producer's device 102, the agreement information 110, the account ID 174, or a combination thereof. Clearing server 116 can send the search result information to the recipient's device 140 to allow the recipient's device 140 to select a search result and request access to the agreement information 110.

[082] Recipient device 140 can send a request (for example, request 182 or another request) to clearing server 116 to access agreement information 110 based on the search result information. Based on the request from recipient device 140, clearing server 116 can send an access request to producer device 102.

[083] Producer device 102 may accept or reject the access request to grant access to agreement information 110 to the recipient (e.g., recipient device 140). If producer device 102 rejects the access request, producer device 102 may send a recipient denial of authorization to the clearing server 116. The recipient denial of authorization may include or indicate the reason for the rejection. Clearing server 116 may send at least part of the denial of authorization. Petition 870250086483, dated 09 / 24 / 2025, page 42 / 215 37 / 149 recipient to recipient device 140. Alternatively, producer device 102 may send recipient authorization 184 to clearing server 116 to approve access to settlement information 110. Clearing server 116 may notify recipient device 140 that access has been granted, and recipient device 140 may view settlement information 110.

[084] Once the recipient (e.g., recipient device 140) has access to the agreement information 110, recipient device 140 can send a payment request to the producer via clearing server 116. In some implementations, recipient device 140 can send document information 186, the request amount, the supplier account information (e.g., the recipient), or a combination thereof, to clearing server 116. Document information 186 may include or indicate the pledge instrument, the payment assignment, or a combination thereof. In some implementations, document information 186 may also include the request amount and / or a request for supplier approval.

[085] Note that different recipients may interact with the producer at different stages of the production and / or delivery of a commodity in association with the first agreement. To illustrate, a first recipient may sell seeds to the producer, a second recipient may provide planning services to the producer, a third recipient may sell fertilizer to the producer, a fourth recipient may spread the fertilizer, a fifth recipient may harvest the produced goods (e.g., an object, a product, a crop, a commodity, etc.), a sixth recipient may transport the goods, or a combination thereof, as illustrative and non-limiting examples. Each recipient may provide the respective documentary information to the clearing server 116, and the documentary information may be stored in the database 126. Petition 870250086483, dated 09 / 24 / 2025, page 43 / 215 38 / 149

[086] Based on the information in document 186, clearing server 116 can send an approval request to producer device 102. Producer device 102 can accept or reject the approval request. If producer device 102 rejects the approval request, producer device 102 can send a denial to recipient to clearing server 116. The denial to recipient can include or indicate the reason for the rejection. Clearing server 116 can send at least part of the denial to recipient, such as a denial indication, the reason for the denial, or both, to recipient device 140. Alternatively, producer device 102 can send an approval to recipient 188 (e.g., an approval message) to clearing server 116 to approve payment by institution server 150.Clearing server 116 can notify recipient device 140 that the recipient has been approved for payment by institution server 150. Additionally, clearing server 116 can send recipient information 190 to institution server 150. Recipient information 190 may include or indicate that the recipient is approved to receive at least a portion of the payment, the amount of the portion, the account information of the vendor (e.g., the recipient), or a combination thereof.

[087] Based on the information in agreement 110 and the performance (e.g., delivery) by the producer, the product taker may provide a payment to the clearing account on the institution's server 150. For example, the product taker's device 130 may initiate the first banking device 160 to send a transfer 192 (e.g., the payment) to the producer's clearing account on the institution's server 150. The payment may include traditional fiat currency, cryptocurrencies, stablecoins, Central Bank Digital Currencies (CBDCs), and / or tokenized assets. Petition 870250086483, dated 09 / 24 / 2025, page 44 / 215 39 / 149

[088] The server at institution 150 can receive transfer 192 and can hold the transfer amount (e.g., the payment). The server at institution 150 can send a transfer notification 194 to the clearing server 116. The transfer notification 194 can indicate that transfer 192 has been received by the server at institution 150 and is ready to be distributed.

[089] Clearing server 116 can access database 126 and determine or confirm how transfer 192 should be allocated between one or more parties, such as the producer, the recipient, the institution, an entity associated with clearing server 116, another entity, or a combination thereof. For example, clearing server 116 can confirm that the transfer corresponds to the agreement information 110, the account ID 174, the producer, the product recipient, or a combination thereof. In addition, or alternatively, as another example, clearing server 116 can determine one or more disbursements, such as a first part (e.g., a first amount) to be provided to an account associated with the producer, a second part (e.g., a second amount) to be provided to an account associated with the recipient, and a third part (e.g., a third amount) to be provided to an account associated with clearing server 116.Clearing server 116 can send a remittance request 196 to the institution server 150 in order to disburse one or more parts of the transfer 192.

[090] Based on the sending request 196, the institution's server 150 may disburse one or more parts of the transfer 192. For example, the institution's server 150 may disburse a first part of the transfer 192 to the account (e.g., the clearing account) associated with the producer, a second part of the transfer 192 to a second banking device 162 associated with the recipient, or a combination thereof. To illustrate, the institution's server 150 may send the second part as a disbursement 198 to the second device. Petition 870250086483, dated 09 / 24 / 2025, page 45 / 215 40 / 149 banking 162. In addition, or alternatively, the institution's server 150 may disburse a third party to an account corresponding to an entity associated with the clearing server 116. In some implementations, the third party may be associated with a fee (e.g., a service fee) for services rendered by the clearing server 116 in association with at least the agreement information 110 (e.g., the contract).

[091] After the disbursement of one or more parts of the transfer 192, the institution server 150 may send a confirmation message to the clearing server 116 to confirm that one or more parts of the transfer 192 have been disbursed based on the submission request 196. The clearing server 116 may update the database 126 based on or in response to the confirmation message.

[092] Note that clearing server 116 can update database 126 to reflect the different operations (e.g., disbursements) performed by clearing server 116 and / or information received or generated by clearing server 116. Additionally, or alternatively, clearing server 116 can send status change notifications to one or more parties / entities (e.g., the producer, the product taker, the recipient, the institution, etc.). Each party may be able to establish an account or credentials with clearing server 116 and view information that the party is authorized to see. For example, each party may be able to access a graphical user interface (GUI), such as a dashboard GUI, which provides information that the party is authorized to view. Examples of GUIs are described in more detail here, at least with reference to Figures 3-8 and 10-17.

[093] After the disbursements and after database 126 (e.g., ledger 127) is updated to reflect the disbursements, clearing server 116 can determine whether the settlement has been completed or satisfied based Petition 870250086483, dated 09 / 24 / 2025, page 46 / 215 41 / 149 in database 126. Based on the determination that the settlement has been concluded or satisfied, the clearing officer may request that the clearing account on the institution's server 150 be closed, that the information in the ledger 127 associated with the settlement be archived, or a combination thereof.

[094] In some implementations, system 100 can be configured for self-service contract management, integration with one or more additional services (e.g., one or more additional services provided by an entity associated with clearing server 116), a versatile implementation, API functionalities, or a combination thereof. Self-service contract management can allow counterparties to autonomously create, manage, and execute transaction contracts within the platform (e.g., clearing server 116). For example, the platform (e.g., clearing server 116) can serve as an entry point for a wider range of products and / or services, which can leverage critical supply chain data to improve or optimize payment clearing processes.For example, products and / or services may include or correspond to one or more products or services provided in association with a supply chain, such as an agribusiness supply chain. The one or more products or services may include or correspond to seed procurement and tracking, logistics management, inventory tracking and management, or a combination thereof, as illustrative and non-limiting examples. The versatile application / implementation of the platform can enable any entity (e.g., a company or an individual) involved in transactions with future payment receivables, regardless of location. The API-based platform functionalities can be designed to perform key functions through API integrations, including account creation for payment clearing, generation of deposit receipts, and real-time deposit notifications. Petition 870250086483, dated 09 / 24 / 2025, page 47 / 215 42 / 149 and exit payments, as described above.

[095] In some implementations, the clearing server 116 and / or the database 126 are configured to receive supply chain data, such as sensor data (e.g., Internet of Things (IoT) data) from one or more sensors. Collecting real-time data (e.g., from sensors on agricultural equipment, storage facilities, delivery trucks, etc.) provides transparent tracking and proof of the status of the goods (e.g., the status of a good associated with the agreement), which can prevent disputes over quantity or quality. In addition, or alternatively, sensor data can determine a characteristic of a good (e.g., a physical object), such as a commodity. Sensor data can be received by the clearing server 116 and / or the database 126 and can indicate one or more measurements, such as temperature, global positioning satellite (GPS) coordinate, color, water content, or other objective measurement.Furthermore, the sensor can generate signatures, or other types of data structures, that allow validating the accuracy of the sensor data. The sensor can send the sensor data and a signature generated by a sensor that generated the data. In some implementations, the sensor can send the sensor data and / or the signature along with or in association with an identifier of an agreement, such as a contract ID (e.g., a contract ID). The clearing server 116 and / or the database 126 can receive the sensor data and the signature, and validate, based on the signature, the accuracy of the former data. In this way, the system 100 can prevent fraud and / or incorrect data from being stored in the database 126.Furthermore, clearing server 116 and / or database 126 may receive and store, in database 126, sensor certification results, laboratory certification and / or test results, or a combination thereof, to ensure that the sensor data and / or merchandise meet the agreed standards of an agreement. Petition 870250086483, dated 09 / 24 / 2025, page 48 / 215 43 / 149

[096] In some implementations, sensor data, test data, or other data received by the clearing server 116 and / or database 126 may be stored in database 126. For example, such data may be stored in a respective entry or in an entry related to an agreement. To illustrate, the data from a first sensor may be stored in database 126 in an entry that corresponds to the first sensor. In some examples, a portion of the sensor data may be linked to an entry associated with an agreement. As another example, the received sensor data may include or indicate an identifier of an entry associated with an agreement and may be stored in that entry. If the sensor data is stored in the entry associated with the agreement, this data may be used to update the agreement status, which may trigger a partial payment or a final payment associated with the agreement.

[097] In some implementations, the clearing server 116 and / or the database 126 may be configured to receive data from a device associated with an authorized local representative. The authorized local representative may be authorized to monitor and / or verify farm conditions, crop conditions, commodity conditions, storage conditions, or a combination thereof. The information collected by the authorized local representative may be sent to the clearing server 116 to be stored in the database 126.

[098] In some implementations, the 116 clearing server includes a compliance module. Agricultural commodities are frequently traded internationally, which requires compliance with the regulations of various jurisdictions. The compliance module is configured to update information as laws and regulations change over time. The information in the compliance module can be applied to an agreement, Petition 870250086483, dated 09 / 24 / 2025, page 49 / 215 44 / 149 to the contract formation process, fee calculation, reporting operations, enforcement of attachments, dispute resolution or a combination thereof, based on a relevant country or region.

[099] In some implementations, the 116 clearing server allows adjustments to contract terms, volumes, or deadlines. For example, the 116 clearing server may enable a process for a user or entity associated with an agreement to request a modification to the agreement. The request may include a field to be modified, such as price, quantity, or delivery date, as illustrative and non-limiting examples. The 116 clearing server may obtain signatures from all parties impacted by the modification and record the modification and signatures in the entry associated with the agreement. Such information may be stored in the entry (e.g., in database 126) to track, verify, and authenticate amendments without compromising the integrity of the original contract.

[0100] In some implementations, the clearing server 116 may register one or more devices to communicate with the clearing server 116, the database 126, a central server (e.g., the central server 250 of FIG. 1B), or a combination thereof. For example, a system user 100, the clearing server 116 may register a device associated with or identified by the user. In some examples, the device is the producer device 102 associated with the producer. To register the device, the clearing server 116 may obtain (e.g., receive) a device identifier from the device. The clearing server 116 may generate a registered device ID, such as a unique identifier and / or a certificate, that is associated with the device. The clearing server 116 may store the registered device ID in the database 126.For example, the registered device ID, the device identifier, or both may be stored in database 126—for example, as part of the user information associated with the user. The clearing server 116. Petition 870250086483, dated 09 / 24 / 2025, page 50 / 215 45 / 149 can send the registered device ID to the device. In some implementations, the 116 clearing server may limit a user to registering a single device. Alternatively, a user may be able to register multiple devices with the 116 clearing server, and each device may receive a respective registered device ID that is unique to the device.

[0101] The user can use the device with the registered device ID to access (e.g., log in to) clearing server 116 and / or database 126. For example, during a login procedure performed with clearing server 116 using the device, the device can provide a copy of the registered device ID or a portion of the registered device ID, or a value generated based on the registered device ID, to clearing server 116. Additionally, or alternatively, the device can use the registered device ID to generate a value (e.g., a signature) for clearing server 116. In some implementations, the user's device can send to clearing server 116, as part of a device-to-clearing server 116 communication, at least a portion of the device ID and / or the value (e.g., the signature).In some implementations, each operation (e.g., read operation or write operation) performed between the clearing server 116 (or database 126) and the device can be logged (and indicate the logged device ID). The logged device ID portion and / or value can allow clearing server 116 to confirm the origin of the communication, preventing fraud or misuse of clearing server 116.

[0102] In some implementations, the clearing server 116 may define user rights based on whether or not the user accesses the clearing server 116 and / or the database 126 using a device with a registered device ID. For example, if the user performs a login operation on Petition 870250086483, dated 09 / 24 / 2025, page 51 / 215 46 / 149 clearing server 116 using a device with a registered device ID, the user may have full read and write permissions when using the device with the registered device ID. Alternatively, if the user performs a login operation on clearing server 116 using another device that does not have a registered device ID (for example, a device ID for a device linked to the user), the user may have reduced read and write permissions compared to the user's full read and write permissions. For example, when using the other device, the user may have full read permissions but no write permissions. As another example, the user may have reduced read permissions and may only be able to view documents or information provided by the user themselves. Furthermore, or alternatively, the user may not have write permissions while using the other device.In this way, the 116 clearing server can provide additional security and reduce fraud or unauthorized access to the system.

[0103] In some implementations, the clearing server 116 can facilitate the purchase of a property (e.g., a farm) by a user, such as the producer. To purchase the farm, the producer can provide an initial payment (for the purchase), which is a portion of the purchase price and is paid to the seller of the property. Traditionally, a buyer of agricultural land (e.g., the producer) would make an agreement with the seller to pay the remainder of the purchase price based on revenue from future crops. Such an arrangement might cover multiple crops, requiring detailed tracking of crop sales and revenue allocation by the producer for the benefit of the seller. Alternatively, the producer could obtain a loan (e.g., a mortgage) from the financial institution (associated with the institution server 150) to pay the remainder or the entirety of the purchase price to the seller.The producer can then make regular payments (e.g., monthly) to the financial institution or can enter into an arrangement to pay the remainder. Petition 870250086483, dated 09 / 24 / 2025, p. 52 / 215 47 / 149 of the loan based on future crop revenue from the property.

[0104] In some of these implementations, the 116 clearing server may allow the buyer (e.g., the producer) to obtain a bank loan from a financial institution (e.g., a bank or lender) for at least part of the purchase price of the property. The financial institution becomes both the property security holder and a recipient (e.g., a beneficiary of the buyer) within the clearing platform supported by the 116 clearing server. The 116 clearing server can be configured to automatically designate the financial institution as the beneficiary (or designate based on the buyer's selection of the financial institution as the beneficiary) of the crop proceeds generated on the farmland, where the land crop purchase contracts utilize the 116 clearing server.

[0105] In some of these implementations, the 116 clearing server may allow the buyer to request and / or obtain the loan from the financial institution through interactions with the 116 clearing server. Because the 116 clearing server offers a transparent and automated mechanism for tracking and directing crop proceeds, the financial institution (e.g., the bank) can streamline the credit analysis process by reducing the number of requirements and simplifying collateral verification. Consequently, a loan provided through the use of the 116 clearing server may be less complex to obtain than a traditional loan process (e.g., a traditional loan application process).This increased efficiency benefits all parties: the seller receives payment more predictably, the buyer enjoys a smoother financing experience, and the lender gains greater visibility and reduced risk through real-time data tracking provided by the 116 clearing server.

[0106] In some implementations, the compensation server 116 may Petition 870250086483, dated 09 / 24 / 2025, page 53 / 215 48 / 149 aggregate data on contracts, payment milestones, and pledge instruments, thus offering real-time dashboards and historical summaries. These descriptive analyses allow stakeholders to monitor key performance indicators (KPIs) and generate periodic reports. Historical summaries and reports can be generated in a standardized format. The standardized format of these historical summaries and / or reports allows this information to be accessed via an API. In some implementations, the 116 clearing server may include a predictive modeling engine that uses machine learning (e.g., artificial intelligence (AI)) to predict crop yields, identify potential defaults, and provide risk scores.The predictive modeling engine (e.g., an AI component) can also detect anomalies (e.g., irregular pawn patterns, abnormal payment delays) by comparing real-time data with historical patterns.

[0107] For example, with reference to FIG. 1B, a block diagram of another example of a clearing system 200, according to one or more aspects, is shown. Compared to system 100, system 200 includes a central server 250, in addition to the components of system 100. The central server 250 may include one or more servers, a decentralized platform, or a cloud computing platform. In some implementations, the central server 250 (e.g., a central banking server) is configured to provide one or more processing services, such as one or more payment processing services, as described further below. System 200 includes the producer device 102, the clearing server 116 (e.g., a clearing platform), the taker device 130, the recipient device 140, the institution server 150, and the central server 250.In addition, the 200 system may include the first banking device 160, the second banking device 162, or... Petition 870250086483, dated 09 / 24 / 2025, page 54 / 215 49 / 149 both.

[0108] Although central server 250 is described as separate from clearing server 116, in other implementations, clearing server 116 may include at least part or all of central server 250. For example, one or more operations described with reference to central server 250 may be performed by clearing server 116. In addition, or alternatively, one or more operations described with reference to clearing server 116 may be performed by central server 250. Note that each of the clearing servers 116 and central server 250 is separate from the institution server 150.

[0109] The central server 250 (also referred to as a facilitation server, administration server, processing server, or monitoring server) can be configured to perform one or more operations associated with the administration or monitoring of a financial account (e.g., a trust account) created within a financial institution (FI), such as a financial institution associated with the institution server 150. In some implementations, the financial account may be a digital account, a transit account (or a trust account) designated to receive a payment that will be distributed according to the terms of an agreement (e.g., a contract). The financial account may be configured to hold funds on behalf of a beneficiary, may be linked to a master account associated with a user, and / or may be programmatically controlled by the clearing server 116 (and / or the central server 250).In some implementations, the financial account can be configured to receive funds via a credit card transaction. The central server 250 can also be configured to register one or more participants / users, register one or more parties / entities associated with a participant or user, perform or coordinate intermediate transactions and / or a final settlement of payments. Petition 870250086483, dated 09 / 24 / 2025, page 55 / 215 50 / 149 coordinate or request the closing of a financial account, or a combination thereof. In some implementations, the central server 250 provides efficient integration between the clearing server 116 and the institution server 150 to ensure secure and transparent transactions that comply with regulations, thus maximizing efficiency and customer satisfaction. In some implementations, the central server 250 can be configured to interact with a financial institution (e.g., the institution server 150). For example, the central server 250 can be configured to perform or facilitate operations previously performed on Payment Transit Accounts (which may also be referred to as pass-through accounts) before final settlement in a financial account at a financial institution.

[0110] The central server 250 includes a processing system comprising one or more processors 252 (collectively referred to as processor 252), one or more memories 254 (collectively referred to as memory 254), or a combination thereof. In addition, the central server 250 includes a network interface 259.

[0111] Processor 252, memory 254, and network interface 259 may correspond to (i.e., be analogous to) processor 104, memory 106, and network interface 114 of producer device 102, respectively. Thus, processor 252, memory 254, and network interface 259 may include similar or the same characteristics described with reference to processor 104, memory 106, and network interface 114, respectively. Processor 252 may be configured to execute instructions 256 stored in memory 254 to perform one or more operations described in this context.

[0112] In some implementations, processor 252 includes one or more modules, such as the tariff module 253, the customer manager 255, and the account manager 257. Although described as modules, in some implementations, the module Petition 870250086483, dated 09 / 24 / 2025, page 56 / 215 51 / 149 of tariffs 253, the customer manager 255 and the account manager 257 may be associated with the execution of instructions 256 (e.g., code) that cause the processor 252 to perform one or more operations described with reference to the tariffs module 253, the customer manager 255, the account manager 257, or a combination thereof.

[0113] The 253 pricing module (also referred to as the fees module) is configured to control the different fees applied to transactions in the 200 system. For example, the 253 pricing module can be configured to calculate the fees associated with a transaction based on a pricing policy (e.g., a service fee) and / or local regulations (e.g., tariffs), ensuring that all fees are correctly applied before proceeding to settlement. In some implementations, the 253 pricing module may allow the central server 250 (and / or the authorization server 116 via central server 250) to flexibly establish and adjust service costs according to market and operational needs. Furthermore, the 253 pricing module can provide users, such as the producer, buyer, and / or receiver, with a clear and detailed view of the fees applied to their transactions, which helps maintain customer trust and satisfaction.

[0114] The 255 customer manager is configured to act or operate as a central record holder for all participants and help manage user data, such as producers (e.g., farmers), buyers (e.g., purchasers), recipients (e.g., creditors), etc. The 255 customer manager can support supplementary registration, links, and socioeconomic information and corporate structures of companies and groups involved in contracts, which supports processes such as KYC (Know Your Customer) and credit assessment, as well as helping to achieve compliance and security in transactions. In some implementations, the 255 customer manager is configured to support the Petition 870250086483, dated 09 / 24 / 2025, page 57 / 215 52 / 149 Customer identification and verification (e.g., KYC operations), which may be performed in association with or in partnership with a government-approved ID system, an e-KYC portal, a financial institution with which the user has an existing account, or a combination of these elements. In some examples, the institution server 150 may be configured to provide an API for user verification, such as verifying users using login credentials associated with the financial institution linked to the institution server 150. To illustrate, the authorization server 116 or the central server 250 may access the institution server 150 via the API to perform user verification.Furthermore, or alternatively, the 255 customer manager can facilitate the collection, verification, and management of customer data, ensuring that all parties involved in transactions (e.g., sender, recipient, and assignee) are properly authenticated and comply with current regulations. In some implementations, the 255 customer manager can offer personalized services to a user, such as automatic notifications about transaction status and payment reminders. For example, the 255 customer manager can be configured to notify a user about any deposits received into accounts linked to or associated with the user.

[0115] Account Manager 257 is configured to perform one or more operations to create a transaction account, monitor or initiate one or more financial transactions, or a combination of these operations. For example, Account Manager 257 can be configured to perform account creation and administration. To illustrate, Account Manager 257 (e.g., Central Server 250) can automate the creation and / or configuration of financial accounts, such as trust accounts (in a financial institution) and other necessary accounts. In some implementations, Account Manager 257 can be configured to allow a user to identify a primary user account, such as an account to which everyone Petition 870250086483, dated 09 / 24 / 2025, page 58 / 215 53 / 149 The remaining unallocated funds at the end of a contract and owed to the user will be transferred. The 257 account manager can also perform ongoing management of a financial account (e.g., a trust account), such as balance monitoring and verification of suspicious activity. Additionally, or alternatively, the 257 account manager can perform transaction pre-processing (e.g., before settlement at a financial institution), where preliminary checks are carried out to ensure the compliance and accuracy of the amounts to be transferred. In some implementations, the 257 account manager is configured to ensure that funds are correctly distributed among participants after the completion of transactions on the platform, following the terms established by a contract (e.g., a smart contract).

[0116] In some implementations, the central server 250 can be configured to access the database 126 and / or the ledger 127. To illustrate, the central server 250 (e.g., processor 252) may include a blockchain mechanism configured to access the database 126 and / or the ledger 127. The database 126 and / or the ledger 127 used by the clearing server 116 and / or the central server 250 can enable system 200 (or system 100) to provide a robust, performant, scalable, and integrated solution that automates monetization, clearing, and financial flow processes, meeting the specific needs of a sector or industry (e.g., the agricultural sector) and beyond, while improving the efficiency, security, and transparency of financial transactions.Database 126 and / or ledger 127 can enable and support the maintenance (e.g., by clearing server 116 and / or central server 250) of a clear contractual chain of ownership for traceability and accessibility of all transaction and change histories.

[0117] Clearing server 116 and / or central server 250 can be configured to provide financial account management (e.g., management of Petition 870250086483, dated 09 / 24 / 2025, page 59 / 215 54 / 149 fiduciary accounts) and rule-based transfers. One or more APIs may be used and / or developed with respect to integration aspects so that the clearing server 116 and / or the central server 250 interact or operate with each other, with the institution server 150, with the ledger 127, or a combination thereof. In some implementations, system devices 200 may interact to perform user authentication, in which a secure user authentication process is validated by the financial institution (e.g., the institution server 150). The user authentication process may be integrated with a financial institution API (e.g., the institution server 150) for seamless user verification.Furthermore, or alternatively, the 200 system can be configured to perform automated management of transit accounts, in which accounts that will hold funds on behalf of a beneficiary are created programmatically and can be operated programmatically on behalf of the beneficiary through the 200 system. An additional aspect may include the possibility of marking accounts as excluded so that they can no longer receive funds – for example, once a contract is concluded. The 200 system (e.g., clearing server 116 and / or central server 250) can enable or support fund acceptance and notification capabilities, in which accounts are authorized to receive funds from any institution within a banking system (e.g., a national banking system), accompanied by webhooks or events that trigger the execution of rules based on predefined parameters.Some aspects may include the creation of a QR code, such as a PIX code (PIX is a real-time payment system), to streamline the payment process, allowing a person or entity sending or transferring money to make payments more efficiently. The 116 clearing server and / or the 250 central server may also be able to automate the release of funds. For example, the 116 clearing server and / or the 250 central server. Petition 870250086483, dated 09 / 24 / 2025, page 60 / 215 55 / 149 may be able to send user-authorized transfer instructions to send money to any platform participant or to any account in the banking system.

[0118] During the operation of system 200, a user, such as a producer, a buyer, a recipient, or another user, may register with the clearing server 116. For example, the user (e.g., the producer) may send user information 240 from the producer's device 102 to the clearing server 116. User information 240 may include contact information (e.g., name, address, telephone number, email address), identification information (e.g., driver's license number, passport number, military identification number, state or federal ID number, etc.), business information (e.g., company name, business address, business telephone number, business registration number, etc.), bank account information (e.g., bank name, account number, branch number, balance, deposit amount, account opening date), or a combination of these data.Clearing server 116 can store user information 240, or a portion thereof, in database 126. For example, clearing server 116 can store contact information, identification information, business information, or a combination thereof in a first part of database 126, and can store bank account information in a second part of database 126. In some implementations, the first part of the database and the second part of database 126 are separate databases, entries, or data structures. The portion of user information 240 stored in the first part of database 126 can be linked to the other portion of user information 240 stored in the second part of database 126, such as by linking one or more fields from the database parts, including a pointer to another database part in the stored data. Petition 870250086483, dated 09 / 24 / 2025, page 61 / 215 56 / 149 in a different part of the database, or something similar. In some implementations, the clearing server 116 records the producer, the buyer, the recipient, or a combination thereof.

[0119] To register (e.g., onboard) the user, clearing server 116 may verify user 240 information. For example, clearing server 116 may perform or initiate a verification process, such as a Know Your Customer (KYC) process, which may enable regulatory compliance (e.g., with an anti-money laundering law), minimize the risk of fraud or criminal activity, or a combination of both. The verification process may verify user 240 information using trusted information, such as government records. To illustrate, to verify user 240 information, a KYC resource on an external device, such as the institution's server 150 or another server that provides KYC processing, may be used to perform the KYC processing. In some implementations, the KYC resource on the external device may be accessible via an API of the external device (e.g., the institution's server 150).

[0120] To verify user 240's information, clearing server 116 can generate and / or send a user 242 verification request to another device. The user 242 verification request can include some or all of user 240's information. In some implementations, clearing server 116 sends the user verification request to the KYC resource on the external device (e.g., the institution server 150). In other implementations, clearing server 116 sends the user 242 verification request to the central server 250 (e.g., the client manager 255), and the central server 250 (e.g., the client manager 255) sends a request (which includes the user 242 verification request or a part thereof) to the external device (e.g., the institution server 150). Petition 870250086483, dated 09 / 24 / 2025, page 62 / 215 57 / 149

[0121] Clearing server 116 receives a verification response from user 246 from another device based on the verification process. For example, clearing server 116 may receive the verification response from user 246 from the external device (e.g., the institution's server 150) and / or from the central server 250. Clearing server 116 can determine whether the user has been verified or not based on the verification response from user 246. If the verification response from user 246 indicates that user 240's information has not been verified, the user may not be registered with clearing server 116 and / or further verification processing may be performed with the user to correct one or more deficiencies indicated by the verification response from user 246. If the verification response from user 246 indicates that user 240's information has been verified, the user may be registered with clearing server 116.In some implementations, clearing server 116 may inform the user that they have been verified. In implementations where central server 250 sends the request to the external device to verify the user, central server 250 may receive the user verification response 246 from the external device and determine whether the user has been verified or not based on the user verification response 246, and client manager 255 may store an indication in database 126 or memory 254 that the user is registered. Additionally, or alternatively, clearing server 116 may send an indicator to central server 250 (e.g., to client manager 255) indicating that the user is registered.

[0122] In some implementations, the 116 clearing server can determine if the user has a bank account that they can use to send or receive funds. If the user has a bank account, the 116 clearing server can confirm the bank account by initiating one or more deposits into the account and requesting the deposit amounts from the user. If the user provides the amount(s) Petition 870250086483, dated 09 / 24 / 2025, page 63 / 215 58 / 149 correct deposit(s), clearing server 116 confirms the bank account. If the user does not have a bank account, clearing server 116 may direct the user to establish a bank account with a financial institution. In some implementations, clearing server 116 may facilitate the process for the user to open a bank account with a financial institution associated with the institution's server 150.

[0123] After the user is verified and registered on the clearing server 116, the user, as the buyer, provides the contract information 110 to the clearing server 116. The contract information 110 may be associated with or correspond to a contract (e.g., a purchase or sale transaction) of goods and / or services. For example, the contract may be associated with the sale of a future commodity (e.g., a crop) from a producer to an offtaker. As another example, the contract may be associated with the sale of equipment to another party, such as the offtaker or the recipient. In another example, the producer may purchase equipment or materials from a company, such as an agricultural company, and payment is to be made after or at the time of delivery of the equipment or material to the producer.

[0124] Clearing server 116 can confirm the existence of the contract associated with the contract information 110. For example, clearing server 116 can perform one or more operations as described herein, at least with reference to FIG. 1A. To illustrate, clearing server 116 can confirm the contract with each party involved in the agreement. In some implementations, if one of the contract parties is not registered with clearing server 116, clearing server 116 can perform one or more operations to register the respective party (e.g., the respective user), as described herein.

[0125] Based on confirmation of the contract associated with the information from Petition 870250086483, dated 09 / 24 / 2025, page 64 / 215 59 / 149 contract 110, the clearing server 116 stores the contract in database 126. For example, clearing server 116 may store the contract 110 information in a third party (e.g., an entry or data structure) of database 126, and the contract 110 information stored in this third party of database 126 may be linked or associated with the first party of database 126, which stores contact information, identification information, business information, or a combination thereof. Additionally, or alternatively, clearing server 116 may generate an entry (associated with the contract) in the ledger 127 (e.g., a blockchain). Note that the ledger 127, as a permissioned or public blockchain, may include immutable records, such as records that utilize or leverage cryptographic hashing, block linking, or a combination of both.Cryptographic hashing uses cryptographic hash functions (e.g., the Secure Hash Algorithm (SHA)-256) to generate unique hashes for each block. Any alteration to the block's data changes the corresponding block hash, signaling that the block has been tampered with. Block linking is used so that each block contains the hash of a previous block in the blockchain, creating a chain. Thus, altering a single block requires recalculating the links for all subsequent blocks, which is a computationally prohibitive task. In implementations that include the use of blockchain, the decentralized and cryptographic nature of the blockchain can reduce the risk of document loss or manipulation due to the immutability of records. Furthermore, cryptographic mechanisms (e.g., hashing and / or digital signatures) can be used to verify the authenticity and provenance of the document.Storing contract information, document information, assignment information, etc., in the database in an immutable manner can provide tamper-proof records with dates and timestamps, allowing real-time access and preventing fraud. The ability to access the... Petition 870250086483, dated 09 / 24 / 2025, page 65 / 215 60 / 149 database 126 and receiving real-time access can foster trust between different users and between users and the entities that operate the clearing server 116 and the institution's server 150.

[0126] The ledger entry 127 associated with the contract may include or indicate the contract information 110, user information, contact information (e.g., name, address, telephone number, email address), identification information (e.g., driver's license number, passport number, military ID number, state or federal ID number, etc.), business information (e.g., company name, company address, company telephone number, company registration number, etc.), banking information (e.g., bank name, account number, routing number, balance amount, deposit amount, account opening date), or a combination of these data, for each user associated with the contract. In addition, or alternatively, the ledger entry 127 may include a smart contract generated by the clearing server 116 based on the contract – i.e., the contract information 110.The smart contract can be configured to release payments to the supplier upon proof of delivery of goods or completion of certain milestones. For example, clearing server 116 might receive verifiable data (e.g., from a sensor) that is recorded in database 126 and associated with the first contract. The verifiable data (e.g., sensor data) might indicate that goods have been delivered and one or more characteristics of the goods. Based on the verifiable data, the smart contract can determine that one or more conditions of the first contract have been met and can authorize the disbursement of funds from the financial account.

[0127] In some implementations, clearing server 116 may send an indication of the ledger entry 127 to central server 250 (e.g., account manager 257). Central server 250 (e.g., account manager 257) Petition 870250086483, dated 09 / 24 / 2025, page 66 / 215 61 / 149 accounts 257) can then access ledger entry 127 to read or write to the entry. For example, central server 250 can send a database access request 248 to clearing server 116 in order to access the entry. Additionally, central server 250 (e.g., account manager 257) can receive verified user data from account manager 255, such as user data for one or more users associated with the contract.

[0128] In some implementations, the fee module 253 may determine one or more fees based on the ledger entry 127, and the one or more fees may be represented by fee information 249. The fees represented by fee information 249 may include a service fee, a regulatory fee, or a combination thereof, as illustrative and non-limiting examples. The fee module 253 may provide fee information 249 to the account manager 257, the clearing server 116, the database 126, or a combination thereof. In some implementations, the fee module 253 sends fee information 249 to the account manager 257, and the account manager 257 updates the ledger entry 127 with the fee information 249 using the database access request 248.In some implementations, clearing server 116 or central server 250 is configured to generate or provide payment status information associated with the contract (e.g., ledger entry 127). Payment status information may include or indicate an amount paid, an amount due, a payer, a beneficiary, fee information 249 (e.g., a service fee or regulatory fee), a payment due date, a contract ID, a contract status, or a combination thereof, as illustrative and non-limiting examples.

[0129] In some implementations, the clearing server 116 may receive an additional contract related to the original contract (for example, the entry Petition 870250086483, dated 09 / 24 / 2025, page 67 / 215 62 / 149 in ledger 127). For example, the additional contract may include or correspond to an assignment, an assignment contract, a pledge instrument, a payment reassignment, or a combination thereof, which is related to the original contract. Clearing server 116 may confirm the existence of the additional contract, as described herein, at least with reference to Figure 1A. Furthermore, clearing server 116 may update the entry in ledger 127 and / or send an indication to central server 250 (e.g., account manager 257). In some of these implementations, central server 250 may update the rate information 249 associated with the contract based on receipt of the additional contract notification. For example, account manager 257 may have the rate manager (e.g., rate module 253) determine the updated rate information.

[0130] Clearing server 116 can send an account request 172 to central server 250, to institution server 150, or to a combination of both. Account request 172 can ask central server 250, institution server 150, or both, to open one or more accounts associated with the contract (for example, the ledger entry 127). In some implementations, clearing server 116 sends account request 172 to central server 250, and central server 250 sends at least part of the account request to institution server 150. For example, account manager 257 can send account request 172 (or another request based on account request 172) to institution server 150.

[0131] Central server 250 may, based on account request 172, establish a transfer account (e.g., a payment transit account) that is associated with the contract (and / or the ledger entry 127). The transfer account may have a transfer account ID, such as an account number, a routing number, a code, a barcode, a QR code, or Petition 870250086483, dated 09 / 24 / 2025, p. 68 / 215 63 / 149 a combination of these. In addition, or alternatively, the institution's server 150 may, based on account request 172, establish a financial account, such as a trust account, that is associated with the contract (and / or the ledger entry 127). The financial account may include or correspond to the account information 158 of FIG. 1A. The financial account may include a financial account ID, such as an account number, a code (e.g., a QR code), or a combination thereof, and the institution's server 150 may send such information to the central server 250, the clearing server 116, or both.

[0132] In some implementations, the transfer account (e.g., the payment transit account) is configured to settle payments and receipts through a bank account and then apply them to a specific bank account during bank statement processing. For example, a transfer 292 (e.g., a payment) associated with the contract may be initiated by a payer, and the transfer account may receive the payment from a payer's account and apply the payment to the financial account on the institution's server 150.

[0133] Clearing server 116 may receive account ID 174 from central server 250, institution server 150, or both. Account ID 174 may include or indicate account information for the transfer account, the financial account, or both. In some implementations, account ID 174 includes a code (e.g., a QR code) that corresponds to the transfer account or the financial account. Clearing server 116, central server 250, or both may send the QR code to one or more users associated with the contract (e.g., ledger entry 127).

[0134] In some implementations, after the opening of the transfer account, the financial account, or both, the clearing server 116 and / or the central server 250 can monitor transactions associated with the account. Petition 870250086483, dated 09 / 24 / 2025, page 69 / 215 64 / 149 transfer, to the financial account or both. In addition, or alternatively, the clearing server 116 and / or the central server 250 may communicate with one or more user devices, such as the producer's device 102, the buyer's device 130 or the recipient's device 140, to provide information associated with the contract (e.g., the ledger entry 127), such as a status update. For example, a user may use a user application (e.g., a web platform or a mobile application) associated with the clearing server 116 or the central server 250 to access the user's account and obtain the information associated with the contract, such as the account status or status update.

[0135] Central server 250 can receive or identify transfer 292 (e.g., a payment) associated with the contract. In some implementations, transfer 292 is received by central server 250, which manages the receipt of transfer 292 into the transfer account, as well as managing the sending of transfer 292 from the transfer account to the financial account on institution server 150. For example, a payment processing part of central server 250 might receive transfer 292 associated with the transfer account and provide an amount to the financial account on institution server 150. The amount provided might be equal to the value of transfer 292 less one or more fees associated with the contract (e.g., ledger entry 127).In other implementations, central server 250 identifies that transfer 292 occurred in the financial account on institution server 150 based on access to the financial account on institution server 150.

[0136] Central server 250 can determine one or more distributions (e.g., account and amount) associated with the funds in the financial account. For example, central server 250 (e.g., account manager 257) can determine the distributions based on database 126 (e.g., the ledger entry). Petition 870250086483, dated 09 / 24 / 2025, page 70 / 215 65 / 149 127). To illustrate, based on the transfer account and / or the financial account, the central server 250 can identify the ledger entry 127 and access that entry. The central server 250 (e.g., the account manager 257) can generate distribution information 260 indicating the distributions and send this distribution information 260 to the institution's server 150 so that the funds from the financial account are distributed. In some implementations, the central server 250 can confirm that the funds have been distributed and / or send a notification to one or more users informing them that the funds have been distributed. Additionally, or alternatively, the central server 250 (e.g., the account manager 257) can update the ledger entry 127 to indicate the completion of one or more distributions.

[0137] Clearance server 116 and / or central server 250 (e.g., account manager 257) may determine that the settlement has been completed. For example, central server 250 (e.g., account manager 257) may access the ledger entry 127 and determine that all user accounts have been settled and that no further payments are pending. Based on the determination that the settlement has been completed, clearance server 116 and / or central server 250 (e.g., account manager 257) may send a closing request 262 to the institution server 150 to close the financial account. Additionally, or alternatively, based on the determination that the settlement has been completed, central server 250 may close the transfer account – for example, so that the transfer account can no longer receive payments.In addition, clearance server 116 and / or central server 250 (e.g., account manager 257) can identify or designate the ledger entry 127 as filed.

[0138] In some examples of system 200 operation, a user (e.g., a producer) can carry out a purchase / sale transaction of equipment or supplies. To illustrate, an agricultural company (the recipient) Petition 870250086483, dated 09 / 24 / 2025, page 71 / 215 66 / 149 can sell equipment (such as a tractor) or supplies to another company (the producer). Payment is due upon delivery of the equipment / supplies and is managed through a financial account provided by the financial institution associated with the institution's server 150. The clearance server 116, operating in conjunction with the central server 250, can be positioned as a configured third party to facilitate and monitor the transaction process.

[0139] To facilitate and monitor the transaction process, clearance server 116 can perform an integration operation with a user, such as the producer associated with the producer device 102, the recipient associated with the recipient device 140, or both. Clearance server 116 (or central server 250) can utilize a Know Your Customer (KYC) process to ensure regulatory compliance and minimize risks. For example, clearance server 116 can notify central server 250 to perform the KYC process for the user, and central server 250 (e.g., customer manager 255) can perform the KYC processing using a KYC resource located on an external device, such as the institution server 150. In some implementations, customer manager 255 can be used to centrally register qualified and validated participants, corresponding profile information, connections, and specific parameters.As part of the integration, the user can designate or create a primary account, such as a bank account under the user's control. In some implementations, the user can choose to create a primary account at a financial institution associated with the institution server 150, and the clearance server 116 can facilitate or assist in opening the primary account.

[0140] The producer and the recipient may enter into a sales contract that includes a promissory note. Clearance server 116 (or central server 250) may digitally register and store the contract in the ledger 127, ensuring easy Petition 870250086483, dated 09 / 24 / 2025, page 72 / 215 67 / 149 Access and management of agreed terms. For example, the 116 clearance server may receive a copy of the contract from one of the producers or the recipient, and the 116 clearance server may confirm the contract with the other. In some implementations, a back-office team (e.g., support team associated with an entity that provides services related to the 116 clearance server) may assist the producer and / or the recipient in verifying the documents related to the contract and help obtain digital signatures through a 116 clearance server application used by the producer and / or the recipient. The 116 clearance server may generate (e.g., automatically or manually) a smart contract (e.g., executable code) based on the contract terms.

[0141] Central server 250 can create a payment transit account on the central server 250 itself to manage transactions and payments. Additionally, or alternatively, central server 250 (e.g., account manager 257) can initiate or request the institution server 150 to open a financial account (e.g., a trust account) associated with the contract. For example, account manager 257 can ensure that all account parameters are correctly configured by the institution server 150 before opening the financial account. In some implementations, the payment transit account and / or the financial account can be opened after the contract is confirmed by the producer and the recipient.

[0142] In some implementations, the producer may finance part of the payment through another party (e.g., an assignee), such as a financial institution. In these implementations, a payment assignment agreement may be established between the producer, the recipient, and the assignee, allowing part of the payment to be transferred directly to the assignee from the financial account. The central server 250 may subsequently initiate the distribution of Petition 870250086483, dated 09 / 24 / 2025, page 73 / 215 68 / 149 funds using account manager 257 (e.g., the account management module) to cause the execution of final settlement operations in the financial institution's financial accounts.

[0143] Release server 116 can facilitate the issuance of the credit assignment notice and the payment assignment agreement. For example, release server 116 can ensure that these documents are prepared, reviewed, and stored in the ledger 127 (e.g., a Blockchain system), as well as coordinate the obtaining of digital signatures through the release server 116 application.

[0144] Before settlement in the financial account, central server 250 can monitor preparatory transactions, applying fee module 253 (e.g., a fee module) to calculate and charge any associated fees, such as performing the reservation of funds and any fees for the operation or services provided by the release server 116, the central server 250, or a combination thereof.

[0145] Throughout the process, the producer (a user) and / or the recipient can use the release server application 116 to track the transaction status, verify documents, and / or communicate with the release server support team 116. In addition, the central server 250 can provide, through the release server 116 and / or the release server application 116, all transaction information and real-time (or near real-time) operation and rate statements.

[0146] After delivery of the equipment / supply, payment can be initiated by the producer via the producer device 102 and processed by the central server 250. The central server 250 can ensure that funds are transferred from the producer's account to the financial account at the financial institution. The payment is then distributed from the financial account to the recipient and, if applicable, to the assignee, as per the established agreements. Petition 870250086483, dated 09 / 24 / 2025, page 74 / 215 69 / 149

[0147] After payments are finalized and obligations are fulfilled (for example, the completion of a contract / agreement), central server 250 coordinates the closing of the financial account with the financial institution, ensuring that all final steps are properly documented and filed.

[0148] In the examples described above, at least with reference to system 200 of FIG. 2, the central server 250 can advantageously ensure that the necessary funds are available and reserved for the transaction before settlement by the financial institution. Furthermore, or alternatively, the central server 250 can ensure that all transactions meet the criteria established in the contract and that all necessary authorizations have been obtained. In this way, the central server 250 enables efficient, secure, and transparent management of complex transactions, maximizing operational efficiency and customer satisfaction. The clearing server 116 and / or the central server 250 simplifies the management of complex financial transactions and offers a robust platform for the continuous innovation of secure data structures, providing traceable and verifiable actions in relation to contracts and agreements.

[0149] In some implementations, the clearing server 116 and / or its application may provide or support dynamic user profiles and control panels that allow users to select and change profiles dynamically based on actions performed within the system 100 or 200. Additionally, or alternatively, the clearing server 116 and / or its application may provide or support document management and comparison, including functionalities for uploading, scanning, and comparing documents using optical character recognition (OCR) technology, supporting a variety of document types and formats, including the Portable File Format (PDF).

[0150] In some implementations, system 100 or 200 may include or utilize a payment platform (for example, a payment platform). Petition 870250086483, dated 09 / 24 / 2025, page 75 / 215 70 / 149 instant), such as PIX. In certain implementations, this payment platform may include or correspond to the central server 250. It is worth noting that PIX is an instant payment platform that operates in Brazil, allowing merchants to receive funds in real time, without the need for intermediaries. The instant payment platform (e.g., PIX) can be used as a transfer mechanism, linking a unique key (e.g., a PIX key) to an account to simplify transactions. The central server 250 (or clearing server 116) can be configured to generate, at the time of creation of transit accounts, a random key (e.g., a unique key, such as a PIX key) for the account, this key being registered for receiving and executing payments. For example, the random key may include a QR code.

[0151] In some implementations, the central server 250 or the clearing server 116 may be configured to manage contractual disputes. For example, the central server 250 or the clearing server 116 may include functionalities to flag disputes and notify all parties involved. In certain implementations, the clearing server 116 is configured to initiate an arbitration process or a dispute resolution process associated with the controversy. The arbitration or dispute resolution process may access, rely on, or interpret information contained in the database 126 to quickly provide an enforceable decision.

[0152] In case of dispute, fund transfers from the financial account (e.g., the transit account) may be restricted (e.g., limited to an undisputed portion or a percentage of the total contract value) or prohibited by clearing server 116 or central server 250. In other implementations, all payments from the financial account (e.g., the transit account) may be suspended or placed on hold by the server of Petition 870250086483, dated 09 / 24 / 2025, page 76 / 215 71 / 149 clearing 116 or by the central server 250 until the dispute is resolved. Based on the resolution of the dispute, the funds may be transferred back from the account according to the original agreement or according to a new dispute resolution agreement. This resolution agreement may be received by the clearing server 116 and stored in the database 126.

[0153] In some implementations, users or operators of systems 100 or 200 may have distinct access levels within the system. Different access levels may cater to different management hierarchies within a financial institution or organization, ensuring compliance with financial regulations. Various access levels may correspond to different parties involved in agreements, different types of devices used to access the clearing server 116, associations with financial entities or intermediaries, other characteristics, or a combination of these factors. In some implementations, each access level may allow access to a subset of documents or privileges, with the lowest level providing only permission to view certain documents, such as the contract, while higher levels allow approving payments, adding parties to agreements, confirming accounts, among other actions.

[0154] In some implementations of systems 100 or 200, the clearing server 116 can be configured to generate, based on one or more entries in database 126, historical data associated with a user, such as the first user (e.g., the producer) or the second user (e.g., the buyer), or with an entity. The historical data may include an aggregation of data from one or more entries, the result of one or more analyses of those entries, or a combination of these elements. Based on the historical data, the user information associated with it, or a combination of these factors, the clearing server 116 can determine one or more related metrics. Petition 870250086483, dated 09 / 24 / 2025, page 77 / 215 72 / 149 to the user. These metrics may include a risk score (e.g., a liability score) associated with the user, the on-time delivery rate, the number of defaults, the total volume of products sold or received by the user, one or more quality indicators of the products produced by the user, or a combination of these factors. In some implementations, historical data and / or metrics may follow a standardized format, or the 116 clearing server may generate a report (e.g., a standardized report) containing this data, metrics, or a combination thereof.In addition, or alternatively, the clearing server 116 may provide the historical data, metrics, user information, a user rating, or a corresponding report to another entity, such as the user himself, another user, the central server 250, a financial institution, or another entity (e.g., an insurance provider, a vendor, a lender, etc.). For example, the clearing server 116 and / or the database 126 may include an API or allow API calls that enable a user or entity to access the historical data, metrics, user information, user rating, or a corresponding report, in a standardized data format and / or structure.In some implementations, historical data, metrics, and / or user ratings may be updated periodically, whether hourly, daily, monthly, quarterly, annually, based on the completion of a contract, randomly, or through a combination of these criteria.

[0155] In some implementations, the 116 settlement server may use historical data, metrics, risk score, user information, or a combination of these elements to determine one or more fees associated with the user (e.g., the first or second user). For example, the lower the risk score, the lower the fee. As another example, the risk score may be used as a weighting value applied to a standard fee for Petition 870250086483, dated 09 / 24 / 2025, page 78 / 215 73 / 149 determine the rate for a user. Another example would be that frequent users of one or more services provided by the 116 settlement server may have their service rate reduced. Additionally, or alternatively, the 116 settlement server may, for at least one service in a set of services, determine the respective rate based on metrics associated with the user and send, to a user's device, an indication of the service and the respective rate. In some examples, the service may be an insurance product, such as an insurance product associated with the first contract.

[0156] In some implementations, settlement server 116 may request or allow a user to provide insurance information associated with a contract to be registered in database 126. The insurance information may indicate, for a contract (e.g., a contract), how premiums are calculated and distributed. In some implementations, settlement server 116 may also obtain and store meteorological data (e.g., sensor data) that may be sent along with an insurance claim.

[0157] In some implementations, the 100 or 200 system may support decentralized or consortium governance, such as formal processes for proposing and voting on updates that ensure inclusive oversight. In these cases, the 100 or 200 system may include a governance layer that records proposals and votes on the chain (e.g., in blockchain entries), specifying how decisions affect the code or parameters of the smart contract. Additionally, or alternatively, farmers' cooperatives, individual users, provider associations, and / or industry regulators may act in an advisory or auditing role, having oversight (e.g., ledger auditing, recommending rate changes, or mediating high-level disputes) associated with the 100 or 200 system.

[0158] In some implementations, a server (for example, the server of Petition 870250086483, dated 09 / 24 / 2025, page 79 / 215 74 / 149 compensation 116) includes at least one processor (e.g., processor 118) and one memory (e.g., memory 120) coupled to at least one processor. The memory stores processor-readable instructions that, when executed by at least one processor, cause the processor to retrieve first contract data (e.g., contract information 110) associated with a first contract between a first user and a second user. The instructions, when executed by the processor, also cause the processor to verify whether the first contract data associated with the first contract is valid based on a first input received from a first device (e.g., producer device 102) associated with the first user, a second input received from a second device (e.g., taker device 130) associated with the second user, or a combination of both.The instructions, when executed by the processor, also cause the processor, after verifying the first contract, to send a request (e.g., account request 172) to create, on an institution server (e.g., institution server 150), a financial account (e.g., represented by account information 158) associated with the first contract. The instructions, when executed by the processor, cause the processor to store, in a database (e.g., database 126), information from the first entry associated with the first contract. The information from the first entry indicates the first user, the second user, the data from the first contract, the financial account, or a combination of both.

[0159] In some implementations, a server (e.g., central server 250) includes at least one processor (e.g., processor 252) and a memory (e.g., memory 254) coupled to at least one processor. The memory stores processor-readable instructions that, when executed by at least one processor, cause the processor to perform an action. Petition 870250086483, dated 09 / 24 / 2025, page 80 / 215 75 / 149 identifies a financial account (e.g., represented by account information 158) on an institution server (e.g., institution server 150). The financial account is associated with a first contract between a first user and a second user. The first user is the beneficiary of the financial account, and an entity associated with a central server (e.g., central server 250) has agency over the financial account. The instructions, when executed by the processor, also cause the processor to identify a transfer (e.g., transfer 292) made to the financial account. The instructions, when executed by the processor, cause the processor, after identifying the transfer, to send a request to the institution server (e.g., represented by disbursement information 260) to make one or more disbursements from the financial account.The disbursement(s) is / are determined based on an initial entry in a database (e.g., database 126). The initial entry is associated with the first contract and indicates the first user, the second user, the data of the first contract (e.g., the information of contract 110) associated with the first user, the financial account, or a combination of both. The instructions, when executed by the processor, cause the processor to send a notification indicating the initial disbursement to a first account associated with the first user.

[0160] In some implementations, a system includes a clearing server (e.g., clearing server 116) configured to obtain first-contract data (e.g., contract information 110) associated with a first contract between a first user and a second user. The clearing server is also configured to verify that the first-contract data associated with the first contract is valid based on a first input received from a first device (e.g., producer device 102) associated with the first user, and a second input received from a second device. Petition 870250086483, dated 09 / 24 / 2025, page 81 / 215 76 / 149 device (e.g., buyer device 130) associated with the second user, or a combination of both. The clearing server is further configured to, after verification of the first contract, send a request (e.g., account request 172) to create, on an institution server (e.g., institution server 150), a financial account (e.g., represented by account information 158) associated with the first contract. The clearing server is configured to store, in a database (e.g., database 126), information from the first entry in a first entry associated with the first contract. The first entry information indicates the first user, the second user, the data of the first contract, the financial account, or a combination of both.In some implementations, the system that includes the clearing server also includes a central server (e.g., central server 250), the institution's server, the database, or a combination of these elements.

[0161] The 100 or 200 system provides an ecosystem and supports a process for managing the clearing of payments between parties in a secure and transparent manner, which reduces fraud, improves efficiency, and provides secure communication. To illustrate, the 100 or 200 system can support a payment process and / or payment solution with security and compliance aspects. For example, the 126 database can allow sensitive contract terms, pledge records, payment details, or a combination thereof to remain confidential. As another example, the 100 or 200 system can use end-to-end encryption and robust key management, specifying how different stakeholders are granted role-based permissions to access the clearing server platform 116 and / or the 126 database.Thus, the 100 or 200 system offers a technical advantage by providing a verifiable, transparent, secure, and equitable technological solution in order to mitigate and resolve. Petition 870250086483, dated 09 / 24 / 2025, page 82 / 215 77 / 149 problems with improper data handling and record keeping, uncertainty in payments, hidden liens, fraud and the like.

[0162] In addition, or alternatively, system 100 or 200 may comply with relevant regulations and security protocols to protect the funds and personal information of one or more users. For example, system 100 or 200 may provide an auditable trail of contractual events and payment flows that ensures compliance with local or international regulations (e.g., anti-money laundering, financial reporting). To illustrate, the clearing server 116 may designate authorized regulators to access the database 126 and / or may generate reports to meet statutory requirements.

[0163] One or more devices in the 100 or 200 system may implement security features through software and using processes in accordance with the Information Security Policies for all roles and positions necessary to ensure secure operation. In some implementations, the 100 or 200 system adopts a zero-trust security posture. In addition, or alternatively, the 100 or 200 system may implement a continuous compliance process that automatically analyzes, notifies, and configures resources to comply with security policies.

[0164] In some implementations, one or more devices of the 100 or 200 system may be implemented using a cloud-based infrastructure. For example, one or more devices of the 100 or 200 system may have an infrastructure that is cloud-based, such as infrastructures supported by AWS Data Centers, which adhere to guidelines and regulations. For example, the cloud-based infrastructure may follow the guidelines and regulations of a financial banking system (e.g., the Brazilian banking system). Additionally, or alternatively, the 100 or 200 system may allow for new or other parties. Petition 870250086483, dated 09 / 24 / 2025, page 83 / 215 78 / 149 utilize system 100 or 200 without jeopardizing existing contractual relationships. For example, system 100 or 200 may implement a microservices or modular approach, allowing each microservice or modular component (e.g., a payment service, an identity verification service, a contract authentication / validation service, or an arbitration service) to function independently but integrate seamlessly.

[0165] System 100 or 200 may store a minimum set of data so that sufficient information is available to personalize and monitor service quality and execute the business logic of System 100 or 200 functionalities, as well as comply with local regulations such as Personally Identifiable Information (PII), Know Your Customer (KYC) compliance, Anti-Money Laundering (AML) compliance, and similar requirements. Data, such as customer or transaction data, from System 100 or 200 may be encrypted (e.g., encrypted by AWS) during transit and while stored. Additionally, or alternatively, data may also be stored in a repository due to compliance or regulatory needs.

[0166] System 100 or 200 may have offline capabilities for a user entry point. For example, one or more devices or applications of System 100 or 200 may have a monolithic application (e.g., offline-first data capture applications that do not rely on a server). When offline capabilities are not required, an application may leverage Kubernetes-based microservices with auto-scaling and micro frontends for scalable and fast-response functionality. Additionally, or alternatively, System 100 or 200 may provide offline mobile or SMS-based solutions that can capture transactions locally and synchronize later. For example, a mobile device, such as Producer 102's device, could log data from Petition 870250086483, dated 09 / 24 / 2025, page 84 / 215 79 / 149 events that are cryptographically signed and temporarily stored, then synchronized with the database 126 and / or the clearance server 116 as soon as connectivity is restored on the mobile device.

[0167] System 100 or 200 (e.g., System 100 or 200 infrastructure) can guarantee ownership of data from different parties / entities, such as data belonging to a financial institution (e.g., Banco do Brasil) and / or data managed by the clearance server 116, regardless of each organization's existing infrastructures. System 100 or 200 (e.g., System 100 or 200 infrastructure) can adhere to security and compliance standards, including a zero-trust security posture and continuous compliance monitoring, such as with Prisma Cloud support. System 100 or 200 (e.g., System 100 or 200 infrastructure) can include or have access to Blockchain technology to enhance the security and transparency of transactions. In some implementations, Blockchain technology may include or host the ledger 127.In addition, or alternatively, system 100 or 200 (for example, clearance server 116, central server 250 or institution server 150) may provide a web platform accessible via a desktop computer or mobile device.

[0168] System 100, as described with reference to FIG. 1A, and / or System 200, as described with reference to FIG. 1B, offers several advantages. One such advantage may include providing access to verified and secure contract-related data for additional parties in future obligations. Another advantage may include blockchain-enabled solutions. For example, System 100 or 200 may incorporate blockchain technology to further enhance the system's capabilities, leveraging key features such as: immutable records, decentralization, transparency, smart contracts, verification (e.g., enhanced verification), reduced counterparty risk, efficient dispute resolution. Petition 870250086483, dated 09 / 24 / 2025, page 85 / 215 80 / 149 dispute resolution, data encryption, operational risk reduction, traceability, or a combination of all of these. Furthermore, through collaboration with the institution's server 150 (e.g., a financial institution) and adherence to stringent security and compliance standards, the system 100 or 200 can improve the technical field of clearance systems and significantly enhance clearance capabilities within a business chain (e.g., the agribusiness chain), offering a robust, secure, and user-friendly platform for all stakeholders.

[0169] The use of blockchain can provide security, privacy, reliability, immutability, trust, or a combination of these elements. In terms of security, a blockchain architecture is fully encrypted and includes multiple layers of security, making it future-proof, which makes it an advantageous technology for contract management and settlement. In terms of privacy, a forward contract can include sensitive information, and the contract owner has granular control over who and when another person can view and / or access the documents. Regarding reliability, the ability of a smart contract to automatically execute ensures that the contract rules are applied, helping to reduce and / or eliminate fraud. In terms of immutability, any changes to an account or the terms of the contract are recorded in an immutable ledger, which can enable greater trust and visibility.Regarding trust, each of the properties of security, privacy, reliability, and / or immutability increases trust in the platform. Furthermore, the use of the platform promotes transparency in the intentions and actions of users, increasing trust between the parties involved.

[0170] Another advantage of the 100 or 200 system, such as the 126 database, may include improved data security and entry tracking due to the use of immutable records, such as records that utilize or leverage cryptographic hashing, block linking, or a combination of these techniques. Cryptographic hashing utilizes cryptographic hash functions (e.g., the algorithm Petition 870250086483, dated 09 / 24 / 2025, page 86 / 215 81 / 149 Secure Hash (SHA)-256) is used to generate unique hashes for each block. Any alteration to the block's data changes its hash, signaling tampering. Block linking is used so that each block contains the hash of its predecessor, creating a chain. Altering a single block requires recalculating all subsequent blocks, a computationally prohibitive task.

[0171] Another advantage of the 100 or 200 system, such as the 126 database, can include decentralization, such as a distributed ledger, node consensus, or a combination of these techniques. The distributed ledger is configured to maintain the record through a network of nodes, thus eliminating single points of failure and decentralizing control. Node consensus implements consensus mechanisms, such as Proof of Work or Proof of Stake, for transaction validation, thus ensuring that no single entity controls the state of the ledger.

[0172] Another advantage of the 100 or 200 system, such as the 126 database, may include transparency, such as a public ledger, an audit history, or a combination of these features. The public ledger may allow all network participants to view the ledger, ensuring transparency in transactions and balances. The audit history may maintain or provide a complete, verifiable, and immutable history of transactions (e.g., all transactions), accessible for auditing and verification.

[0173] Another advantage of the 100 or 200 system, such as the 126 database, may include the use of smart contracts, such as self-executing contracts, event-triggered execution, or a combination of these features. Self-executing contracts can encode the contract terms into programmable scripts, called smart contracts, which are automatically executed based on predefined criteria, minimizing manual intervention and errors. Event-triggered execution triggers the execution of the contract based on predefined events, ensuring the timely and objective fulfillment of the contract. Petition 870250086483, dated 09 / 24 / 2025, page 87 / 215 82 / 149

[0174] Another advantage of the 100 or 200 system may include verification (e.g., enhanced verification), such as digital signature, entity identity verification, or a combination of these features. Digital signatures are configured to employ cryptographic signatures, allowing parties to sign transactions and documents in a verifiable manner. Entity identity verification integrates advanced identity verification protocols to authenticate users and counterparties.

[0175] Another advantage of the 100 or 200 system may include reduced counterparty risks, such as custody mechanisms, real-time reconciliation, or a combination of these features. Custody mechanisms use smart contracts to hold funds in custody, releasing them only when the contract terms are properly met. Real-time reconciliation ensures the immediate and transparent recording of transactions, mitigating delays and discrepancies.

[0176] Another advantage of the 100 or 200 system may include efficient dispute resolution, such as an immutable audit log. The immutable audit log can provide an indisputable record of transactions and interactions, simplifying dispute resolution.

[0177] Another advantage of the 100 or 200 system may include data encryption, such as end-to-end encryption, secure channels, or a combination thereof. End-to-end encryption can protect data in transit and at rest using cryptography such as Advanced Encryption Standards (AES) and / or Rivest-Shamir-Adleman (RSA). Secure channels can establish encrypted communication channels for data exchange, preserving confidentiality and integrity.

[0178] Another advantage of the 100 or 200 system may include reduced operational risk as a result of automated processing, continuous monitoring, or a combination thereof. Automated processing may Petition 870250086483, dated 09 / 24 / 2025, page 88 / 215 83 / 149 Automate routine tasks and compliance checks, reducing human error and operational inefficiencies. Continuous monitoring can implement real-time monitoring systems and alerts to quickly identify and mitigate risks.

[0179] Another advantage of the 100 or 200 system may include traceability, such as timestamping, chain of custody, or a combination thereof. Timestamping may include recording the exact time and sequence of transactions, providing a clear and traceable timeline. Chain of custody may maintain a transparent and traceable record of ownership and asset transfers throughout the asset's entire lifecycle.

[0180] Referring to FIG. 2, a flow diagram illustrating an example process 210 supporting the operation of a settlement system according to one or more aspects is presented. The operations of process 210 may be performed by a device or system, such as system 100 or 200. Additionally, or alternatively, the device or system may include or correspond to a settlement platform. In some implementations, the settlement platform includes or corresponds to a server, such as settlement server 116 described above with reference to FIGs. 1A or 1B and / or central server 250 described above with reference to FIG. 1B.

[0181] In block 202, the settlement platform receives login information from a producer. For example, settlement server 116 might receive login information from producer device 102. Producer device 102 might be associated with the producer. In some implementations, the producer might not have an account or login information established with the settlement platform. In such cases, the producer might establish the account or login information with the settlement platform beforehand or as part of a login process for the producer to access the settlement platform. Petition 870250086483, dated 09 / 24 / 2025, page 89 / 215 84 / 149

[0182] In block 204, the settlement platform receives a request to create a settlement account. For example, settlement server 116 might receive the request from producer device 102. In some implementations, the request is received from the producer (e.g., producer device 102). The settlement account (e.g., a financial account) might be an account held or managed by an institution, such as an institution associated with institution server 150. In some implementations, the settlement account might be associated with the producer, an agreement (e.g., agreement information), or a combination of these elements. The agreement information might include or correspond to agreement information 110. In some implementations, the request to create the settlement account might be received via a graphical user interface (GUI), as described later, at least with reference to FIG. 3.In addition, or alternatively, the settlement platform may receive a request to create a financial account (also referred to in this document as a trust account, transfer account, transit account, or transit account) that is maintained or managed by the central server 250.

[0183] In some implementations, in block 206, the settlement platform receives the settlement information. For example, settlement server 116 may receive settlement information 110. In some implementations, the settlement information may be received as part of (e.g., included with) the request to create the settlement account, after the request to create the settlement account. In some implementations, the settlement information may be received via a graphical user interface (GUI), as described later, at least with reference to FIG. 3.

[0184] In block 208, the settlement platform sends an account reservation request based on receiving the request to create the settlement account. For example, settlement server 116 might send the request to Petition 870250086483, dated 09 / 24 / 2025, pp. 90 / 215 85 / 149 account 172 to institution server 150 and / or central server 250. In some implementations, the account reservation request is sent via an API from institution server 150. The account reservation request may cause institution server 150 to generate an account for the producer that is associated with agreement information 110. Based on the account reservation request, institution server 150 may generate account information (e.g., the account number).

[0185] In block 211, the settlement platform sends a deal verification request based on receipt of deal information (e.g., based on deal information indicating that an entity, such as a buyer, has entered into a deal with the producer). For example, settlement server 116 might send verification request 176 to purchasing device 130. Purchasing device 130 might be associated with a buyer who is linked to the producer based on deal information 110. In some implementations, the deal verification request includes or indicates at least part of the deal information 110. In some implementations, the deal verification request might be sent based on input received through a graphical user interface (GUI), such as a GUI described with reference to FIG. 3 or FIG. 4.

[0186] In block 212, the settlement platform receives a verification response based on the submission of the agreement verification request. For example, settlement server 116 may receive verification response 178 from buyer device 130. In some implementations, the verification response validates the agreement information 110, which was provided to settlement server 116 by the producer. Additionally, or alternatively, the verification response may include agreement information held by the buyer. Based on the agreement information received from buyer device 130, settlement server 116 may compare the agreement information received from the buyer's device. Petition 870250086483, dated 09 / 24 / 2025, pp. 91 / 215 86 / 149 producer 102 and the agreement information received from the buyer's device 130. In some implementations, the verification response may be received via a graphical user interface (GUI), as described further below with reference to FIG. 5.

[0187] In some implementations, in block 214, the settlement platform receives an account acknowledgment. For example, settlement server 116 may receive account acknowledgment from the buyer (e.g., buyer device 130), indicating that the buyer acknowledges that the account at the institution was established on behalf of the producer in relation to the settlement information 110. In some implementations, account acknowledgment may be received via a graphical user interface (GUI), as described further below with reference to FIG. 6.

[0188] In block 216, the settlement platform sends an active account notification. For example, settlement server 116 may send verification notification 180 to producer device 102. Additionally, or alternatively, settlement server 116 may send a similar or the same notification to buyer device 130, institution server 150, or both. In some implementations, the notification may be sent via communication such as email, text message, or an automated phone call, or the notification may be received via a graphical user interface (GUI), such as a GUI described later with reference to FIG. 7.

[0189] In block 218, the settlement platform generates a control panel. For example, settlement server 116 may generate a control panel for the producer, which includes information associated with the account at the institution, the contract, or a combination of both. In some implementations, the control panel may include or correspond to a graphical user interface (GUI), such as a GUI described later with reference to FIG. 8. Petition 870250086483, dated 09 / 24 / 2025, page 92 / 215 87 / 149

[0190] FIGS. 3-8 are example diagrams of graphical user interfaces (GUIs) to illustrate the operation of a settlement system according to one or more aspects. FIGS. 3-8 may include or correspond to one or more GUIs associated with process 210. One or more of these GUIs may be generated by the settlement server 116 and / or displayed by another device, such as the producer device 102 or the buyer device 130, respectively. In some implementations, the settlement server 116 may receive information from the database 126 and / or the central server 250 so that one or more of the GUIs in FIGS. 38 are generated.

[0191] FIG. 3 shows an example of a GUI 300 for initiating a settlement account. During the setup of a settlement account, a user, such as the producer, can fill in information associated with a contract, such as a forward contract. The information may include the buyer's email address, the contract value, and the expected payment date. Additionally, or alternatively, the producer can upload an existing contract (e.g., contract information 110) to initiate the process of creating a payment settlement account (i.e., a settlement account). For example, the producer uploads the contract that was executed with the buyer to the platform in order to initiate the process of creating a dedicated payment settlement account for the specific contract.Based on the uploaded forward contract, the institution associated with institutional server 150 can reserve a payment settlement account number that is associated with the producer, the forward contract, or a combination thereof.

[0192] FIG. 4 shows an example of a GUI 400 to indicate that the producer is awaiting verification from the buyer. For example, the producer may be on hold, waiting for the buyer to confirm the validity of the contract and the commitment to pay the settlement bill when settling the contract. Petition 870250086483, dated 09 / 24 / 2025, page 93 / 215 88 / 149 At this point, the producer is in a waiting period, as action from the buyer is required for the process to continue. During this waiting period (if the action is taking too long), the producer can send a reminder to the buyer. The reminder may include or correspond to verification request 176 of FIG. 1A.

[0193] FIG. 5 shows an example of GUI 500 to allow the buyer to verify the contract, for example, a forward contract. For example, verifying the contract via GUI 500 may result in the generation or transmission of verification response 178 from FIG. 1A. GUI 500 can provide the buyer with the ability to verify and validate whether this is a real contract and / or whether the buyer is one of the parties to the contract. For example, the buyer may receive a request to verify the authenticity of the contract (e.g., the forward contract). The verification process can be done manually by the buyer, viewing the contract and verifying the contract based on the observation.Alternatively, the verification process can be performed automatically if the buyer is able to send a copy of the contract (in the buyer's possession), so that a service running (e.g., in the background) can compare the sent contract with the contract provided by the producer to determine if the contracts match. In some examples, the service may be provided by the 116 settlement server. In some implementations, the comparison may be performed between the two contracts to verify the terms. For example, a file match or an OCR match may be performed to determine if the contract sent by the buyer matches the form of the contract provided by the producer. As another example, if the contract is sent by the producer, the buyer can manually review the contract and indicate whether the contract is verified—that is, whether a valid agreement exists between the producer and the buyer.

[0194] FIG. 6 shows an example of a GUI 600 for assigning payment in association with the settlement account. For example, the buyer Petition 870250086483, dated 09 / 24 / 2025, page 94 / 215 89 / 149 may acknowledge and agree to pay the producer's dedicated settlement account when settling the forward contract via GUI 600. In other words, the buyer acknowledges and agrees to pay the settlement account associated with the producer and / or the contract when settling the contract. This acknowledgment may be legally binding.

[0195] FIG. 7 shows an example of a GUI 700 to indicate that the settlement account configuration is complete and linked to the contract, for example, the forward contract. For example, the producer can access and review the GUI 700 after the buyer has verified the agreement and agreed to assign the payment. In some implementations, the institution may also have visibility over the transaction.

[0196] FIG. 8 shows an example of an 800 dashboard GUI. The 800 dashboard GUI can correspond to a graphical interface through which the producer can review the status of one or more settlement accounts. The 800 dashboard GUI can allow the producer to have complete, real-time data on the settlement account for payments, loans, and disbursements. Although the 800 dashboard GUI is described with reference to the producer, similar dashboard GUIs can also be generated for the buyer, the recipient, another beneficiary, another entity, etc.

[0197] FIG. 9 is a flow diagram illustrating another example of a 900 process that supports the operation of a settlement system in one or more respects. The operations of the 900 process may be performed by a device or system, such as system 100 or system 200. In addition, or alternatively, the device or system may include or correspond to a settlement platform. In some implementations, the settlement platform includes or corresponds to settlement server 116 described above with reference to FIGS. 1A or 1B, or to central server 250 of FIG. 1B. In some implementations, one or more operations described with reference to the 900 process may occur Petition 870250086483, dated 09 / 24 / 2025, pages 95 / 215 90 / 149 after one or more operations performed as described with reference to process 210 of FIG.

[0198] In block 902, the settlement platform receives a fetch request from a recipient. For example, settlement server 116 might receive a fetch request from recipient device 140. In some implementations, the fetch request might be received via a graphical user interface (GUI), such as a GUI described later with reference to FIG. 10.

[0199] In block 904, the settlement platform receives an access request from the recipient. For example, settlement server 116 might receive request 182 from recipient device 140. In some examples, the access request is received after the search results are provided to the recipient based on the search request, and the access request indicates one of the search results that was selected for access by the recipient. In some implementations, the access request might be received via a graphical user interface (GUI), such as a GUI described later with reference to FIG. 11.

[0200] In block 906, the settlement platform sends an access request to the producer. For example, settlement server 116 might send an access request to producer device 102. The access request sent to the producer might indicate or correspond to a document, agreement, file, data entry, or something similar, which is indicated by the access request received from the recipient. In some implementations, the access request might be sent via communication, such as email, text message, or an automated phone call, or it might be received via a graphical user interface (GUI), such as a GUI described later with reference to FIG. 12. Petition 870250086483, dated 09 / 24 / 2025, pp. 96 / 215 91 / 149

[0201] In block 910, the settlement platform receives an access response from the producer. For example, settlement server 116 might receive recipient authorization 184 from producer device 102. The access response might indicate whether the producer grants access to the requested item to the recipient. In some implementations, the access response might be received via a graphical user interface (GUI), such as a GUI described later with reference to FIG. 12.

[0202] In block 912, the settlement platform receives document information from the recipient. For example, settlement server 116 might receive document information 186 from recipient device 140. In some implementations, document information might be received via a graphical user interface (GUI), such as a GUI described later with reference to FIGS. 13 or 14.

[0203] In block 914, the settlement platform sends an approval request to the producer. For example, settlement server 116 might send the approval request to producer device 102. The approval request might indicate a request for the producer to approve or verify one or more documents represented by the document information received from the recipient. In some implementations, the approval request might be sent via communication, such as email, text message, or automated phone call, or it might be received via a GUI, such as a GUI described later with reference to FIG. 15.

[0204] In block 916, the settlement platform receives an approval response from the producer. For example, settlement server 116 might receive approval from recipient 188 from producer device 102. The approval response may indicate whether one or more documents represented by the document information received from the recipient have been approved by the producer. In some Petition 870250086483, dated 09 / 24 / 2025, page 97 / 215 In 92 / 149 implementations, the approval response can be received via a GUI, such as the GUI described later with reference to FIG. 15.

[0205] In block 918, the settlement platform sends an approval response notification to the recipient, the institution, or both. For example, settlement server 116 might send recipient information 190 to recipient device 140, institution server 150, or both. The approval response indicates whether the producer has approved one or more documents represented by the document data received from the recipient. In some implementations, the notification might be sent via communication such as email, text message, or automated phone call, or it might be received via a GUI, such as a GUI described later with reference to FIG. 16.

[0206] In block 920, the settlement platform generates a dashboard. For example, settlement server 116 might generate a dashboard for the producer that includes account-associated information (associated with the producer or contract information 110) at the institution, an account-associated with the recipient, or a combination of both. In some implementations, the dashboard might include or correspond to a GUI, such as a GUI described later with reference to FIG. 17.

[0207] FIGS. 10-17 and 31-37 are example GUI diagrams to illustrate the operation of a settlement system according to one or more aspects. FIGS. 10-17 may include or correspond to one or more GUIs associated with process 900. One or more of these GUIs may be generated by the settlement server 116, generated by the central server 250, and / or displayed by another device, such as the producer device 102 or the buyer device 130.

[0208] FIG. 10 illustrates an example of a GUI 1000 for searching for information associated with a producer. For example, the recipient can search for a contract (e.g., a futures contract) using the producer's CNPJ or name via GUI 1000. The search results can Petition 870250086483, dated 09 / 24 / 2025, pp. 98 / 215 93 / 149 allow the recipient to send a request to the producer to obtain permission to access and view the details of the future contract.

[0209] FIG. 11 illustrates an example of a GUI 1100 to indicate that the taker is on hold awaiting the producer's response to the request for permission to access information on a futures contract. While the hold is indicated by GUI 1100, the recipient can also send a reminder to the producer to remind them to review the pending request.

[0210] FIG. 12 illustrates an example of a GUI 1200 to allow the producer to approve a request for access to a specific futures contract. For example, the producer receives the request and decides whether to approve or deny the request to view the contract information (e.g., futures contract information) of the taker via the GUI 1200.

[0211] FIG. 13 illustrates an example of a 1300 GUI to allow the recipient to upload supporting documents and / or request payment. For example, after the recipient gains access to view the contract (e.g., the future contract), the 1300 GUI allows the recipient to submit supporting documents and request payment when the associated dedicated clearing account is funded—for example, when the borrower makes the payment. Additionally, the recipient can view contract details such as the payment date, expected payment amounts, etc., via the 1300 GUI. The recipient can select submit in the 1300 GUI and then be placed on hold while awaiting the producer to verify and validate the information in the producer's process flow.

[0212] FIG. 14 illustrates an example of a GUI 1400 to indicate that the recipient is on hold awaiting a decision from the producer to approve a payment request (for the recipient) from the clearing account at the time of payment to the taker. While the hold is indicated by GUI 1400, the Petition 870250086483, dated 09 / 24 / 2025, page 99 / 215 94 / 149 recipient can send a reminder to the producer via GUI 1400.

[0213] FIG. 15 illustrates an example of a GUI 1500 that allows the producer to make a decision on the recipient's payment request. The producer can view the documents that the recipient has sent and the payment request, through the GUI 1500, to decide whether to validate or reject the payment.

[0214] FIG. 16 illustrates an example of GUI 1600 to inform the recipient that the payment request has been approved. Thus, GUI 1600 represents that the recipient has an active pending release, which will occur when the contract is settled. To illustrate, when the buyer makes the payment to the clearing account (for the producer and associated with the contract) at the institution, the recipient will receive a portion of the payment.

[0215] FIG. 17 illustrates an example of a 1700 dashboard GUI. The 1700 dashboard GUI can correspond to an interface through which the recipient can review the status of one or more clearing accounts. The 1700 dashboard GUI can allow the recipient to have complete, real-time data on disbursements. It is worth noting that the 1700 dashboard GUI can also allow the recipient to manage other payment receipts from different participants.

[0216] FIG. 31 illustrates an example of a GUI 3100 for displaying an agreement. The GUI 3100 may include a first part that displays (e.g., presents) agreement data, such as agreement information 110 (e.g., agreement data), received from a first user. The agreement data may be associated with a first agreement between the first user and a second user. The GUI 3100 may include a second part that indicates information to be collected from the displayed (e.g., presented) agreement data.

[0217] FIG. 32 illustrates an example of a GUI 3200 for displaying information collected from an agreement. The GUI 3200 may include or correspond to the GUI 3100 after the information has been collected from the agreement data, which is presented in Petition 870250086483, dated 09 / 24 / 2025, pages 100 / 215 95 / 149 a first part of GUI 3200, and populated in a second part of GUI 3200. In some implementations, some of the information in the second part of GUI 3200 may be generated by a server (e.g., clearing server 116). For example, the server may obtain user information from a database, such as database 126, which is populated in the second part of GUI 3200. Additionally, or alternatively, the server may generate a unique ID, such as a contract number, to identify and / or track the agreement between the first user and the second user. GUI 3200 may allow a user to edit the information displayed in the second part.

[0218] FIG. 33 illustrates an example of a GUI 3300 for displaying another agreement. The other agreement, as a second agreement, can be generated based on a first agreement (for example, the information from agreement 110), such as the agreement described with reference to FIGS. 31 or 32. The second agreement, which is displayed in the GUI 3300, can be between the first user, the second user, and an entity (for example, a bank) that provides a financial account associated with the first agreement. The second agreement can indicate that the entity will provide the financial account and that the first and second users agree to use the financial account in association with the first agreement.

[0219] FIG. 34 illustrates an example of a 3400 GUI for displaying the status of a contract. For example, the contract status may be represented by the agreement information 110. In some implementations, the contract status displayed or summarized in the 3400 GUI may indicate the status of the financial account (e.g., a transit account), the contract parties, a commodity associated with the contract, the price and method of payment, and one or more beneficiaries (e.g., recipients). The contract parties may include a seller (e.g., the producer) and a buyer (e.g., the offtaker). The contract party relating to the price and method of payment may be associated with an additional agreement between Petition 870250086483, dated 09 / 24 / 2025, pp. 101 / 215 96 / 149 The buyer, the seller, and an entity (e.g., a bank) that provides a financial account associated with the contract. This additional agreement may indicate that the entity will provide the financial account and that the first and second users agree to use the financial account in association with the contract. In some implementations, the portion of the contract summary relating to price and payment method may indicate the execution status of the additional agreement. Additionally, or alternatively, the portion of GUI 3400 that indicates beneficiaries may indicate the status or amount to be paid to one or more of the indicated beneficiaries. A pending approval status may indicate that the beneficiary has not yet been authorized or that an invoice (e.g., document 186 information) has not yet been approved. Selecting a beneficiary using GUI 3400 may provide an additional GUI with specific information about the selected beneficiary.

[0220] FIG. 35 illustrates an example of GUI 3500 for displaying an invoice. For example, the invoice may include or correspond to the information in document 186. GUI 3500 may include a first part that displays or shows the invoice, such as the information in document 186, received from a beneficiary (e.g., a recipient). The invoice may be associated with an agreement, such as an agreement represented by the information in agreement 110. GUI 3500 may also include a second part that indicates the information to be collected from the displayed invoice.

[0221] FIG. 36 illustrates an example of a 3600 GUI for displaying information collected from an invoice. The 3600 GUI may include or correspond to the 3500 GUI after the information is collected from the invoice, displayed in a first part of the 3600 GUI, and populated in a second part of the 3600 GUI. In some implementations, some of the information in the second part may be generated by a server (e.g., settlement server 116). For example, the server may obtain user information from a database, such as database 126, for display in the second part of the 3600 GUI. Petition 870250086483, dated 09 / 24 / 2025, pp. 102 / 215 97 / 149

[0222] FIG. 37 illustrates an example of a 3700 GUI for presenting a user control panel associated with one or more contracts. In some implementations, the 3700 GUI is associated with a first user, such as a producer (e.g., seller). For each contract, the 3700 GUI may allow additional information to be presented or retrieved related to the respective contract. For example, as shown in FIG. 37, contract AD-G3918 has four documents, which include a user identity information document, a sales invoice, a loan document, and a purchase agreement (PCA), and one or more of these documents may be selected via the 3700 GUI to cause the selected document to be displayed.

[0223] With reference to FIGS. 18-23, FIGS. 18-23 illustrate operations of system 100 (e.g., a settlement system) and / or system 200, according to one or more aspects. For example, each system in FIGS. 18-23 may include or correspond to system 100 or 200. It is worth noting that, with reference to FIGS. 18-23, in some implementations, settlement server 116 may include central server 250. Alternatively, with reference to FIGS. 18-23, in some implementations, one or more operations described with reference to settlement server 116 may alternatively be performed by central server 250, which is separate from settlement server 116.

[0224] FIG. 18 is an example of an 1800 system with an architecture that shows one or more communication channels according to one or more aspects. The 1800 system includes settlement server 116 and institution server 150. Based on technical feasibility, an encrypted communication channel via Secure Sockets Layer (SSL) for communications sent to or received by settlement server 116 can occur over the Internet or through a secure IPSec virtual private network (VPN), adding an extra layer of security. In some implementations, one or more endpoint calls may also be protected. Petition 870250086483, dated 09 / 24 / 2025, pp. 103 / 215 98 / 149 by authentication flows established on the server side (e.g., the institution server 150) and implemented on the client side (e.g., the settlement server 116). An authentication flow may be associated with a machine-to-machine authorization pattern (“M2M Oauth2”), an API token, etc.

[0225] In some implementations, settlement server 116 may receive and store users 1810 (e.g., user information), such as user information 240, associated with the user. Additionally, or alternatively, users 1810 may be stored in database 126. Settlement server 116 may validate the user based on users 1810. To validate the user, settlement server 116 may perform a credential validation and authentication operation 1830, in which settlement server 116 provides at least a portion of users 1810 to the institution server 150 for authentication / validation by an authentication system 1852 of the institution server 150.In some implementations, the institution's server authentication system 1852 may include or correspond to a KYC service and / or may be configured to confirm / authenticate a user's financial account at the financial institution associated with the institution's server 150 or a financial account at another financial institution.

[0226] FIG. 19 is an example of a 1900 system with an architecture for destination bank account verification, according to one or more aspects. The 1900 system includes settlement server 116 and institution server 150. In some implementations, the 1900 system has already registered (e.g., authenticated) a user, as described with reference to FIG. 18. In FIG. 19, the 1900 system is configured to perform a destination bank account registration process where funds will be disbursed to the authenticated user after the funds are received into a financial account (e.g., a trust account). For example, a participant (e.g., a creditor, a recipient, an assignee, Petition 870250086483, dated 09 / 24 / 2025, pp. 104 / 215 99 / 149 etc.) of an agreement can be identified to receive funds from the financial account. In some implementations, the participant who will receive the funds may be registered as a user of settlement server 116, directly or indirectly.

[0227] To enable the participant to receive the funds, the settlement system 116 determines or identifies that a destination bank account associated with the participant needs to be specified. The settlement server 116 can receive the user's bank account information 1910 (e.g., destination bank account information), and this user bank information 1910 can be linked to users 1810. The bank information 1910 can indicate the user's destination account. In some implementations, the destination bank account is required to be included in a specific national banking system. The settlement server 116 can validate the destination bank account using an account validation point 1952 from the institution's server 150.For example, settlement server 116 can initiate a destination account registration operation 1930 via account validation point 1952, as an HTTPS account validation point, to validate whether the user has control over the account indicated by the bank information 1910. An example of a system for validating the account is described here with reference to FIG. 20.

[0228] Based on a validated account, settlement server 116 can store linked bank information 1910 and users 1810 in a permissioned blockchain 1927. The permissioned blockchain 1927 may include or correspond to the ledger 127. Access to the permissioned blockchain 1927 can be performed based on a data hash validation operation.

[0229] FIG. 20 is another example of a 2000 system with an architecture for verifying a destination bank account or transferring funds, according to one or more aspects. The 2000 system includes settlement server 116 and institution server 150. Settlement server 116 can perform an operation Petition 870250086483, dated 09 / 24 / 2025, pp. 105 / 215 100 / 149 of destination account registration 2011, initiating one or more microdeposit transfers 2010 — for example, the settlement server may indicate the number of microdeposits to be transferred, the value of each microdeposit, or a combination thereof. The settlement server 116 may access the funds transfer point 2012 of the institution server 150 to perform the microdeposit transfers 2010 to the bank account identified by the user. In some implementations, microdeposit transfers 2010 may be deposited into the bank account from an account owned by an entity that operates the settlement server 116.

[0230] Settlement server 116 can perform a microdeposit value creation operation 2013 that generates microdeposit information 2020, which is stored in database 126. The microdeposit information 2020 can be linked to the bank account (represented by bank account information 1910) to which the microdeposit was made. Additionally, settlement server 116 can perform a notification operation 2014, in which the server notifies the user about microdeposits (e.g., microdeposit transfers 2010). In some implementations, the notification operation 2014 can generate a callback URL that is provided to the user to allow them to enter the amounts that were deposited into the identified bank account. Settlement server 116 receives user input 2030 via the callback URL, and this user input 2030 indicates the value of the microdeposits.The value of microdeposits can be stored as 2021 URL token information, which is compared with 2020 microdeposit information. If the value indicated by the 2021 URL token information matches the value indicated by the 2020 microdeposit information, the 116 settlement server performs an account validation operation and validates the user's bank account.

[0231] The 2100 system, as illustrated in FIG. 21, includes the server of Petition 870250086483, dated 09 / 24 / 2025, pp. 106 / 215 101 / 149 settlement 116 and the institution's server 150. After a contract (e.g., a forward contract) is negotiated and established between the participants, a settlement account (e.g., a financial account) needs to be created where funds from the participant(s) with payment responsibility can be deposited, based on the nature of the relationship with the participant(s). From this account, the smart contract code will settle and disburse the funds according to the established rules.

[0232] Settlement server 116 can receive contract information 2110 associated with a user's contract. To illustrate, after negotiating and establishing (approving) a forward contract between participants, the forward contract can be registered on settlement server 116, so that contract information 2110 represents the forward contract. In some implementations, contract information 2110 may include or correspond to contract information 110. Contract information 2110 may be linked to users 1810. Settlement server 116 can perform a contract registration and approval operation 2120 to confirm that contract information 2110 is authentic, as described at least with reference to FIG. 1A. In some implementations, contract information 2110 may indicate the status of a contract, an alteration (e.g., a timestamp) of a status change, or a combination of these elements.

[0233] Furthermore, after the contract information 2110 is authenticated / validated, settlement server 116 can initiate or request the creation of the financial account with institution server 150. For example, settlement server 116 can access a financial account creation point 2122 from institution server 150 to have institution server 150 create a financial account 2124 on institution server 150. Settlement server 116 can store financial account information 2112 that indicates financial account 2124. Petition 870250086483, dated 09 / 24 / 2025, pp. 107 / 215 102 / 149 The financial account information 2112 may be linked to the contract information 2110, to users 1810, or to both.

[0234] Financial account information 2112, contract information 2110 and users 1810 (e.g., participants) are also recorded as one or more entries, and this information is stored on permissioned blockchain 1927 (e.g., ledger 127).

[0235] FIG. 22 is an example of a 2200 system with an architecture for executing the flow of funds, according to one or more aspects. The 2200 system includes the clearing server 116, the institution server 150 and the buyer device 130.

[0236] In some implementations, a buyer (associated with buyer device 130) can make a payment to financial account 2124. Institution server 150 can send an indication (e.g., a signal or an event) to clearing server 116 that the payment (e.g., funds) has been deposited into financial account 2124.

[0237] Clearing server 116 can receive the indication and determine a disbursement amount from financial account 2124 to a destination bank account. The destination bank account can be determined or identified based on the information from bank account 1910. The disbursement amount may include one or more amounts for different accounts of different users, based on the execution of the smart contract. In other words, based on one or more terms of the term contract (e.g., represented by the information from agreement 2110), one or more portions (or the entirety) of the payment may be allocated for distribution by clearing server 116 according to the smart contract (i.e., disbursed according to the established rules). In some implementations, clearing server 116 (or central server 250) may determine an order (e.g., a release order) in which the funds are Petition 870250086483, dated 09 / 24 / 2025, pp. 108 / 215 103 / 149 transferred to one or more parties. Clearing server 116 may perform a settlement execution operation and perform one or more payment execution operations that are sent to institution server 150. Institution server 150 may disburse the funds, via a funds transfer endpoint of institution server 150, from financial account 2124 to the destination accounts identified by clearing server 116 and associated with the payments received from clearing server 116.

[0238] FIG. 23 presents an example of a 2300 system with an architecture for user authentication. As shown in FIG. 23, the clearing server 116 (or the central server 250) is configured to operate with an OAuth2 flow available on the institution server 150. In some implementations, the clearing server 116 (or the central server 250) includes an API (for example, API 128) to authenticate a user accessing the clearing server 116. A user can access the clearing server 116 and be received in the application, being directed to an OAuth2 portal on the institution server 150. The institution server 150 authenticates the user and provides output indicating whether the user has been authenticated. If the output indicates that the user has been authenticated—for example, that the user authenticated as an existing user—the user is logged in by the clearing server 116.Otherwise, if the output indicates that the user has not been authenticated, the clearing server 116 launches (or allows the user to launch) an onboarding wizard to register the user in a user database. In some implementations, the system operations 2300 of FIG. 23 may be performed in conjunction with one or more system operations 1800 of FIG. 18. Additionally, or alternatively, the system operations 2300 of FIG. 23 may be performed before one or more system operations 1900 of FIG. 19.

[0239] FIG. 24 is a block diagram of an example of a system Petition 870250086483, dated 09 / 24 / 2025, pp. 109 / 215 104 / 149 2400 according to one or more aspects. The 2400 system includes a blockchain system, a payment system, a central system (e.g., the 250 central server), a user interface, and external services.

[0240] The blockchain system is configured to perform or provide contract storage. For example, the blockchain system may include or correspond to the 127 ledger. The document storage provided by the blockchain system may allow for the verification of one or more documents, such as document verification by one or more entities or systems.

[0241] The user interface may include or correspond to a device interface, such as the producer device 102, the buyer device 130, or the recipient device 140. The user interface may include or utilize a web platform or a mobile application to interact with one or more systems. For example, the user interface may allow the respective device to interact with the release server 116. In some implementations, the user interface may allow the respective device to send a request to another device or system, such as the payment system. In some of these implementations, the request may be sent directly to the payment system or to the payment system via the release server 116 and / or the central system (e.g., the central server 250).

[0242] The payment system includes or is configured to process payments and apply one or more fees. For example, the payment system may be configured to receive and process one or more payments. The payment system's fee application may be configured to determine and / or apply fees, which may be charged to the same financial account(s) as the processed payments. In some implementations, the fee may include a fee associated with the use of the release server 116 or a tariff (calculated by the tariff module 253). Petition 870250086483, dated 09 / 24 / 2025, pages 110 / 215 105 / 149

[0243] The central banking system, such as the central server 250, includes the fee module 253, the customer manager 255, and the account manager 257. The customer manager 255 can be configured to perform KYC verification using the KYC verification provided by external services. The account manager 257 can be configured to perform one or more operations with respect to a financial institution (e.g., institution server 150) using the banking integration of external services.

[0244] External services may include KYC verification and bank integration. Bank integration may allow the central banking system to interact with (e.g., integrate operations with) a financial institution, such as the institution 150 server. In some implementations, external services may be included or provided by the institution 150 server.

[0245] In some implementations, prior to settlement in a financial account at the financial institution, one or more operations / transactions may be performed by the central banking system (e.g., the central server 250). For example, one or more operations / transactions may include a funds reservation operation, in which the central banking system ensures that funds are available and reserved for a transaction. The operations / transactions may include an intermediate clearing operation, in which the central banking system processes any necessary financial clearing between related accounts according to smart contracts, thus preparing the amounts for final settlement.In addition, or alternatively, operations / transactions may include validations and authorizations, in which the central banking system ensures that transactions meet the criteria established in smart contracts and that all necessary authorizations have been obtained.

[0246] FIG. 25 is a block diagram of an example of a 2500 system according to one or more aspects. The 2500 system includes the settlement server. Petition 870250086483, dated 09 / 24 / 2025, pages 111 / 215 106 / 149 116, the central server 250 and the institution's server 150.

[0247] Settlement server 116 includes components or modules configured to enable or perform back-office operations, KYC integration, or a combination of both. The back-office can be configured to assist the user in obtaining documents and / or storing documents on a blockchain (e.g., ledger 127). Registered contracts can be provided or accessed from central server 250 (e.g., account manager 257). KYC integration can be configured to perform one or more integration operations associated with a user. KYC integration may include verifying and registering a user on central server 250 (e.g., customer manager 255). Settlement server 116 may also include or support a user application to enable and / or facilitate user interaction with central server 250 (e.g., account manager 257).

[0248] Central server 250 includes fee module 253, customer manager 255, and account manager 257. Fee module 253 is configured to apply or determine fees or charges associated with payments, transfers, or disbursements. Fee module 253 can indicate the value of a fee or charge to account manager 257. Customer manager 255 can be configured to provide customer data (e.g., user or participant data) to account manager 257. Account manager 257 is configured to create and manage accounts. For example, account manager 257 can be configured to initiate the creation of one or more financial accounts by institutional server 150. Institutional server 150 is configured to manage one or more financial accounts.

[0249] In some implementations, a cloud-based service (for example, an AWS cloud service, as a non-limiting example) may host web and mobile applications associated with the settlement server 116. The cloud-based service may also include or support a payment system and a system Petition 870250086483, dated 09 / 24 / 2025, pages 112 / 215 107 / 149 of blockchain. The payment system may include fee application, payment processing, or a combination of both. The blockchain system (e.g., the ledger 127) may include or support document verification, contract storage, transaction history data, or a combination of these elements. The cloud-based service may also include or support the central server 250 (e.g., a central banking system) which includes the customer manager 255, the account manager 257, the fee module 253, or a combination of these components. In some implementations, the payment system, the blockchain system, or both may be accessible or integrated within the central banking system.In addition, or alternatively, the central server 250 can be configured to access one or more external services, such as a KYC verification service, a financial institution (e.g., the institutional server 150), or other similar services.

[0250] FIG. 26 is a flow diagram that illustrates another example of a 2600 process that supports the operation of a settlement system according to one or more aspects. The operations of the 2600 process can be performed by a device or system, such as system 100 or 200. In addition, or alternatively, the device or system may include or correspond to a settlement platform. In some implementations, the settlement platform includes or corresponds to the settlement server 116 described above with reference to FIG. 1.

[0251] Process 2600 can be performed on or by system 100 or 200, as illustrative and non-limiting examples. In some implementations, process 2600 represents a process from opening a financial account with a financial institution to closing the financial account. The operations of process 2600 can be performed by one or more devices, one or more servers, one or more entities, or a combination thereof.

[0252] In block 2602, process 2600 includes conducting KYC onboarding. Petition 870250086483, dated 09 / 24 / 2025, pages 113 / 215 108 / 149 and customer verification. For example, settlement server 116, main server 250, institution server 150, external services, or a combination thereof, may perform KYC onboarding and customer verification.

[0253] In block 2604, process 2600 includes the registration of a user using / with the customer management module. For example, the customer management module may include or correspond to customer manager 255.

[0254] In block 2606, process 2600 includes the receipt and storage of a contract and a promissory note on a blockchain. For example, the blockchain may include or correspond to ledger 127 or a blockchain system.

[0255] In block 2608, process 2600 optionally includes the provision of assistance by a back office (e.g., an agent, employee, administrator, or other authorized user) associated with settlement server 116. For example, settlement server 116 can be configured to allow or provide assistance to one or more users regarding the registration and / or provision of documents, such as a contract and / or promissory note.

[0256] In block 2610, process 2600 includes the creation of a payment transit account. For example, settlement server 116 and / or central server 250 can create a payment transit account for a user. To illustrate, settlement server 116 and / or central server 250 can generate a payment transit account for a user and can manage the account using account manager 257. In some implementations, the operations in block 2610 are optional.

[0257] In block 2612, process 2600 includes the opening of a bank account via central server 250 (e.g., a central banking service). For example, central server 250 (or settlement server 116 via central server 250) may open a bank account with a financial institution. Petition 870250086483, dated 09 / 24 / 2025, pages 114 / 215 109 / 149 (for example, the institution's server 150). The settlement server 116 and / or the central server 250 may have authority over the bank account associated with the contract.

[0258] In block 2614, process 2600 includes the receipt of a payment assignment contract. For example, settlement server 116 may receive the assignment contract. The assignment contract may be stored on the blockchain in association with a contract, one or more accounts, and / or one or more users. Additionally, or alternatively, the assignment contract may be provided to or accessible from central server 250.

[0259] In block 2616, process 2600 includes performing transaction monitoring and applying fees. For example, settlement server 116 and / or central server 250 may monitor one or more transactions and apply the fee. Additionally, in block 2618, process 2600 includes using the application (APP) to monitor the financial account. For example, a user of a device, such as producer device 102, buyer device 130, or recipient device 140, may monitor their respective financial account.

[0260] In block 2620, process 2600 includes the initiation of payment processing. For example, payment processing may be initiated based on the detection of a transfer (e.g., transfer 192) of funds. In some implementations, payment processing may be performed by a third party that receives a payment (e.g., transfer 192) to be provided to a financial account, such as that of the producer associated with producer device 102. In block 2622, process 2600 includes the transfer of funds to the financial account.

[0261] In block 2624, process 2600 includes payment execution and settlement. For example, settlement server 116 and / or central server 250 may determine one or more rates or fees, identify users or individuals. Petition 870250086483, dated 09 / 24 / 2025, pages 115 / 215 110 / 149 who are to receive the funds according to a smart contract and / or documents, or a combination of these factors, and the funds may be deposited into the accounts of identified users or individuals, with fees being deducted from the financial account. After payment and settlement of funds from the financial account to one or more other accounts, in block 2626, process 2600 includes the closing of the financial account.

[0262] FIG. 27 is a ladder diagram illustrating an example of a 2700 system supporting the operation of a settlement system in one or more respects. The 2700 system may include or correspond to the 100 or 200 system. The 2700 system includes the settlement server 116, a user device 2701, the central server 250, the institution server 150, and the ledger 127 (e.g., a blockchain). The user device 2701 may include or correspond to a user, such as a user of the producer device 102, the buyer device 130, or the recipient device 140 (i.e., a user of the user device 2701 may include or correspond to a user of the producer device 102, the buyer device 130, or the recipient device 140).Note that one or more of the operations described in relation to user device 2701 may be performed through settlement server 116 and / or central server 250, such as through communications between user device 2701 and the respective server, interactions with one or more APIs supported by the respective server, or something similar. The operations shown in the ladder diagram may be associated with a process from KYC onboarding to the final closing of a financial account.

[0263] Settlement server 116 performs KYC onboarding and verification with user device 2701 (e.g., a user) on 2702. User device 2701 (e.g., the user) is registered with the server's client manager 255 (e.g., a client management module). Petition 870250086483, dated 09 / 24 / 2025, pages 116 / 215 111 / 149 central 250. In 2706, the user's device 2701 (e.g., the user) stores a contract and / or a promissory note in the ledger 127 (e.g., a blockchain).

[0264] Settlement server 116 can optionally provide back-office team assistance to a user of user device 2701, on 2708. Back-office team assistance can provide support or guidance to the user of user device 2701 to perform one or more operations, such as uploading documents, signing documents, setting up one or more accounts, etc.

[0265] User device 2701 creates a payment transit account with central server 250, in 2710. The payment transit account can allow central server 250 to initiate a transfer of funds from a financial account at a financial institution or to another account at the same or another financial institution. In 2712, user device 2701 can open a financial account (e.g., a trust account) at a financial institution associated with institution server 150. For example, the financial account can be opened via central server 250. Additionally, or alternatively, user device 2701 can establish a configuration in an account management module (e.g., 257) of central server 250, in 2714. The configuration in the account management module can link the payment transit account and the financial account.In 2716, user device 2701 provides a payment assignment contract to central server 250 and / or settlement server 116. In some implementations, information (e.g., identification information) from the payment transit account, financial account, payment assignment contract, or a combination thereof may be stored in the ledger 127 (e.g., a blockchain).

[0266] Settlement server 116 can provide documents to user device 2701, where the documents are issued and stored in ledger 127 Petition 870250086483, dated 09 / 24 / 2025, pages 117 / 215 112 / 149 (for example, a blockchain), in 2718. Thus, a user of the device of user 2701 can have complete transparency over the documents and obligations related to a financial account associated with the user.

[0267] Central server 250 can monitor transactions and / or the application of fees associated with a payment system and / or financial account, in 2720. For example, central server 250 can perform monitoring to determine if funds (e.g., a payment) have been deposited into the financial account. Additionally, or alternatively, central server 250 can apply a fee, deducting a charge from the funds in the financial account. Furthermore, in 2722, the user of user device 2701 can use an application (e.g., an application supported by settlement server 116) to monitor the user's payment transfer account, the financial account associated with the contract, documents, balances, or a combination of these elements.

[0268] User device 2701 can initiate a payment and processing associated with the contract and / or financial account in 2724. For example, if the user is a buyer (offtaker), the buyer can initiate a payment to a producer's financial account. In 2726, the user of user device 2701 transfers funds to the financial account. In some implementations, funds can be transferred from a financial institution associated with the user to the financial account that is managed by a financial institution associated with institution server 150. In some implementations, the financial institution associated with the user and the financial institution associated with institution server 150 may be the same financial institution or different financial institutions.

[0269] In 2728, central server 250 may initiate the distribution of payment from the financial account based on and / or in accordance with the assignment contract, a fee module, a fee structure, or a combination of these elements. After the distribution and completion of the contract, central server 250 may Petition 870250086483, dated 09 / 24 / 2025, pages 118 / 215 113 / 149 initiate the closing of the financial account by the institution's server 150, on 2730.

[0270] The 2700 system can use the 127 ledger (e.g., a blockchain) for storing contracts and also for issuing and storing documents, thus integrating these actions into the payment process.

[0271] FIG. 28 is a ladder diagram illustrating an example of a 2800 system supporting the operation of a settlement system in one or more respects. The 2800 system may include or correspond to the 100 or 200 system. The 2800 system includes the user device 2701, the KYC services 2801, the central server 250, the ledger 127 (e.g., a blockchain), the institution server 150, the settlement server 116, and a second banking device 2862. The KYC services 2801 may include or correspond to the KYC verification of the external services of FIG. 24. The second banking device 2862 may include or correspond to the first banking device 160, the second banking device 162, the recipient device 140, a recipient associated with the recipient device 140, or a combination thereof. In some implementations, user device 2701 includes or corresponds to producer device 102.It is observed that one or more operations described in relation to user device 2701 may be performed through settlement server 116 and / or central server 250, such as through communications between user device 2701 and the respective server, interactions with one or more APIs supported by the respective server, or something similar. The operations shown in the ladder diagram may be associated with a process ranging from KYC onboarding to the final closing of a financial account.

[0272] User device 2701 requests identity verification with KYC services 2801, in block 2802. In some implementations, the verification request may occur via settlement server 116, from the central server. Petition 870250086483, dated 09 / 24 / 2025, pages 119 / 215 114 / 149 250 or a combination of both. Based on successful identity verification, user device 2701, in block 2804, registers information with the client manager 255 of central server 250. In some implementations, central server 250 may receive an indication of successful identity verification from KYC services 2801.

[0273] Central server 250 (and / or settlement server 116) may register a contract and / or a promissory note in ledger 127 (e.g., a blockchain), in block 2806. Central server 250 (and / or settlement server 116) may optionally receive a registration confirmation (of the contract and / or promissory note) from ledger 127 (e.g., a blockchain), in block 2808.

[0274] Central server 250 (and / or settlement server 116) may request that institution server 150 open a user account, in block 2810. The user account may be a personal bank account over which the user has agency. Central server 250 (and / or settlement server 116) may optionally receive confirmation of the opening of the user account, in block 2812.

[0275] User device 2701 may request settlement server 116 to open a financial account (e.g., a transit account or trust account) for the user of device 2701, in block 2814. The financial account (e.g., the trust account) may be associated with the contract (e.g., the registered contract) and settlement server 116 and / or central server 250 may have agency over the account for the user's benefit. Settlement server 116 may instruct central server 250 to open the financial account (e.g., the transit account), in block 2816. Central server 250 may optionally transmit to settlement server 116 a confirmation that the financial account (e.g., the transit account) has been created, in block 2818.

[0276] The second banking device 2862 (for example, a user associated with the second banking device 2862 or a user's device) Petition 870250086483, dated 09 / 24 / 2025, pages 120 / 215 115 / 149 associated with the second banking device 2862) sends a request to register an assignment contract to the central server 250, in block 2820. The central server 250 may optionally transmit to the second banking device 2862 (e.g., a user associated with the second banking device 2862 or a device of the user associated with the second banking device 2862) a confirmation that the contract has been established and / or registered in ledger 127 (e.g., a blockchain), in block 2822.

[0277] Central server 250 may, in block 2824, monitor one or more transactions and / or indicate / identify a fee to be applied by institution server 150. Institution server 150 may optionally provide confirmation that the fee has been applied and / or recorded in relation to a financial account, in block 2826.

[0278] User device 2701 can track, in block 2828, one or more transactions through settlement server 116. To enable this tracking, settlement server 116 can optionally display the status and / or documents associated with the user of device 2701 in block 2830. This status may include the status of the financial account (e.g., transit account) linked to the user of device 2701.

[0279] After a payment is made to the financial account, central server 250 can initiate the payment and settlement (associated with the financial account) through institution server 150, in block 2832. Institution server 150 can optionally confirm the transfer of funds to central server 250, in block 2834.

[0280] Central server 250 may request the closure of the financial account (e.g., transit account) by institution server 150, in block 2836. Institution server 150 may optionally confirm to central server 250 that the account has been closed, that the documentation has been archived, or a combination thereof. Petition 870250086483, dated 09 / 24 / 2025, pages 121 / 215 116 / 149 of both, in block 2838.

[0281] In some implementations, the 2800 system enables KYC identity verification. Additionally, or alternatively, the 2800 system enables interaction between the central server 250 and the ledger 127 (e.g., a blockchain) for the registration of contracts and / or management of promissory notes. The 2800 system also allows the opening of both the user account and the financial account (e.g., transit account or trust account) for management by the central server 250. Furthermore, or alternatively, the 2800 system enables the establishment of a payment assignment agreement with a financial institution, the monitoring of transactions, and the application of fees.

[0282] Referring to FIG. 29, FIG. 29 is a flow diagram illustrating an example of process 2900 of a server supporting the operation of a clearing system, according to one or more aspects. The operations of process 2900 may be performed by a server, such as the clearing server 116 described above with reference to FIGS. 1 or 2 and / or the central server 250 described above with reference to FIG. 2. The clearing system may include or correspond to at least one or more aspects of systems 100 or 200.

[0283] In block 2902, the server retrieves the first agreement data associated with a first agreement between a first user and a second user. For example, the first agreement data might include or match the information from agreement 110. In some implementations, the first agreement includes or matches a contract. The contract might be a sales contract, such as a forward contract or a futures contract, as illustrative and non-limiting examples. The first agreement (e.g., the contract) indicates a payer and a payee. For example, the first agreement might indicate that the second user owes the first user a payment amount based on the delivery of an object by the first user. In some implementations, the first user includes or matches the Petition 870250086483, dated 09 / 24 / 2025, pages 122 / 215 117 / 149 producer associated with producer device 102, and the second user includes or corresponds to the buyer associated with buyer device 130. In other implementations, the first user includes or corresponds to the buyer associated with buyer device 130, and the second user includes or corresponds to the producer associated with producer device 102.

[0284] In some implementations, the first agreement may involve, in addition to the first and second users, an entity associated with the institution's server (for example, institution server 150). For example, the entity associated with the institution's server may agree to provide a financial account linked to the first agreement, and the first and second users may agree to use that financial account for the execution of the agreement.

[0285] In some implementations, to obtain the first agreement data, the server receives the first agreement data from the first device. Alternatively, in other implementations, to obtain the first agreement data, the server generates the first agreement data. For example, the server might generate a draft of the first agreement (e.g., a contract). In some of these examples, the server might obtain digital signatures from the first and second users to establish the first agreement. In these examples, obtaining the digital signatures might include or constitute the verification of the first agreement (e.g., the first agreement data).

[0286] In block 2904, the server verifies that the first agreement data associated with the first agreement is valid based on a first entry received from a first device associated with the first user, a second entry received from a second device associated with the second user, or a combination of both. The first entry may include an indication that the first agreement data or a summary (e.g., a standardized summary of the first agreement data) is correct, a first digital signature of the first Petition 870250086483, dated 09 / 24 / 2025, pages 123 / 215 118 / 149 user, or a combination of both, as illustrative and non-limiting examples. In addition, the second entry may include an indication that the data from the first agreement or a summary (e.g., a standardized summary of the data from the first agreement) is correct, a second digital signature from the second user, or a combination of both, as illustrative and non-limiting examples.

[0287] In block 2906, after verifying the first agreement, the server sends a request to create a financial account associated with the first agreement on an institution server. The institution server may include or correspond to institution server 150. The request to create the financial account may include or correspond to account request 172. The financial account may include or correspond to account information 158 or account ID 174.

[0288] In some implementations, the request to create the financial account associated with the first agreement is sent to the institution's server via a central server. For example, the server might send a request to the central server to create the financial account associated with the first agreement. The central server might include or correspond to central server 250.

[0289] In some implementations, the server receives an identifier associated with the financial account from the institution's server or the central server. For example, the identifier may include or correspond to account ID 174. The identifier may include or indicate a financial account number, a routing number associated with the financial account, the name of an entity providing the financial account, the name of a beneficiary of the financial account, a Quick Response (QR) code or barcode associated with the financial account, or a combination of these elements. The server may send the identifier to the payer (e.g., the second device associated with the second user), store the identifier in a first entry, or a combination of these methods.

[0290] In some implementations, the request to create the account Petition 870250086483, dated 09 / 24 / 2025, pages 124 / 215 Financial 119 / 149 includes or is a request to reserve the financial account, designate the first user as the beneficiary of the financial account, designate an entity (e.g., settlement server 116 or central server 205) as having agency over the financial account, link the financial account to the first agreement, or a combination of these elements. In some examples, the first user requests to reserve the financial account for the purpose of forming the first agreement with the second user. The data in the first agreement may identify or indicate the financial account to make a payment associated with the first agreement. In some implementations, after verification of the first agreement, an additional agreement may be made between the first user, the second user, and an entity (e.g., a bank) associated with the server, an entity associated with the institutional server, or both.In other examples, the request for the financial account is made during the contract formation process. In some implementations, the initial agreement is made between the first user, the second user and the entity associated with the server, the entity associated with the institutional server, or both.

[0291] In block 2908, the server stores, in a database, information from the first entry associated with the first agreement. The database may include or correspond to database 126, ledger 127, or a blockchain, or a combination thereof. The first entry may include or correspond to entry 3880. In some implementations, at least part of the first entry is immutable. In other implementations, the entirety of the first entry is immutable. The information from the first entry indicates the first user, the second user, the data of the first agreement, the financial account, or a combination of these elements.

[0292] In some implementations, the server generates a smart contract based on the first agreement. The smart contract can be a computer program that executes (e.g., automatically executes) the terms of a Petition 870250086483, dated 09 / 24 / 2025, pages 125 / 215 120 / 149 agreement when certain conditions are met. In some examples, the server stores the smart contract on the first entry.

[0293] In some implementations, as part of process 2900, after verification of the first agreement, the server initiates the formation of a second agreement associated with the use of the financial account associated with the first agreement. For example, the second agreement may be between the first user, the second user, and an entity associated with the institution's server. Furthermore, the second agreement may indicate that the payer will make a payment to the beneficiary using the financial account provided (e.g., hosted) by the entity associated with the institution's server. The server may verify that the second agreement is complete, such as based on receiving a digital signature from each (or a representative) of the first user, the second user, and the entity associated with the institution's server.After verifying that the second agreement is complete, the server can store the data from the second agreement (associated with the second completed agreement) in the first entry in the database.

[0294] To form the second agreement, as part of process 2900, the server may generate a first version (e.g., a preliminary version or an unsigned / unexecuted version) of the second agreement based on the first agreement, the financial account, or a combination of both. The server sends (e.g., transmits) to each of the first users, the second user, and the entity, a request to sign the second agreement. The verified second agreement may include or correspond to a second version (e.g., an executed or final version) of the second agreement, which is signed by each (or a representative) of the first user, the second user, and the entity.

[0295] In some implementations, before the verification (or execution) of the second agreement, if the financial account was created by the institution's server, it has a reserved status. For example, the institution's server may maintain the status of Petition 870250086483, dated 09 / 24 / 2025, pages 126 / 215 121 / 149 financial account as reserved and unable to receive funds. After verification of the second agreement, the institution's server can change the status of the financial account to active. To illustrate, the server can send a status change request to the institution's server to change the financial account from reserved status to active status. Alternatively, the institution's server can access the database (e.g., the first entry associated with the first entry), via a database or server API, and determine that the second agreement is verified (e.g., executed). Based on the determination that the second agreement is verified, the institution's server changes the status of the financial account to active and available to receive funds.

[0296] In some implementations, as part of process 2900, the server receives, from the first device associated with the first user, information about the first user associated with the first user. The server may receive the first user's information (or a portion thereof) as part of a registration process performed with the first user, as part of the verification of the first agreement, or a combination of both. The first user's information may indicate the first user's banking information, which indicates a bank account associated with the first user, the name of the bank providing the bank account, the routing number associated with the bank account, the type of bank account, the name of the bank account holder, or a combination of these data.In addition, or alternatively, the first user's information may include the first user's name, a company associated with the first user, the first user's date of birth, the first user's nationality, a government identification number associated with the first user, a CPF number associated with the first user, an email address associated with the first user, a phone number associated with the first user, a fax number associated with the first user, an address associated with the first user, and sustainability information. Petition 870250086483, dated 09 / 24 / 2025, pages 127 / 215 122 / 149 associated with the first user, or a combination of this data. The server can store at least part of the first user's information in the database. For example, part of the first user's information can be stored as part of the first entry or it can be linked to the first entry.

[0297] In some implementations, the server sends a first indicator to a central server (core server), which indicates the first user's information associated with the first user. For example, the server might send the first indicator along with, or included in, a request to authenticate or verify the first user. The server might then receive an indicator from the central server indicating whether the first user is verified or not.

[0298] In some implementations, the server receives information from the second device associated with the second user that is associated with the second user. The server may receive the second user's information (or a portion thereof) as part of a registration process performed with the second user, as part of the verification of the first contract, or a combination of these factors. The second user's information may include the second user's bank account information. For example, the second user's bank account information may include or indicate the second user's bank account number, the name of the bank providing the second user's bank account, the routing number associated with the bank account, the type of bank account, the name of the account holder, or a combination of these elements.In addition, or alternatively, the second user's information may include the second user's name, a company associated with the second user, the second user's date of birth, the second user's nationality, a government identification number associated with the second user, a tax identification number associated with the second user, an email address, phone number, etc. Petition 870250086483, dated 09 / 24 / 2025, pages 128 / 215 123 / 149 fax number, address, or sustainability information associated with the second user, or a combination of these elements. The server may store at least some of this second user information in the database. For example, part of the second user's information may be stored as part of the first entry or may be linked to the first entry.

[0299] In some implementations, as part of process 2900, the server receives, from a third device associated with a third user, a payment request associated with the first contract. For example, the payment request includes document data, a requested amount, or a combination of these elements. The document data may include or correspond to an invoice, a receipt, document information 186, or a combination of these elements. To illustrate, the document data may include or correspond to another contract, such as an assignment or payment assignment agreement for at least a portion of the payment for the first contract.

[0300] The server can verify and register the third contract in the database. The server can send an approval request to a beneficiary's device (e.g., the first user's device) for the first contract, based on the payment request. If the server receives an approval message from the beneficiary's device (e.g., the first user's device) in response to the approval request, it updates the first entry based on the approval message to indicate that the third user should receive a portion of the payment amount paid by the payer (e.g., the second user) according to the first contract. Alternatively, if the server receives a denial / rejection message from the beneficiary's device (e.g., the first user's device) in response to the approval request, the server can inform the third user about the denial / rejection message.In some examples, the server may log the denial / rejection message on the first attempt. Petition 870250086483, dated 09 / 24 / 2025, pp. 129 / 215 124 / 149 entry.

[0301] In some implementations, as part of process 2900, the server receives third-party device information associated with the third-party user. The server may receive the third-party user information (or part thereof) as part of a registration process performed with the third-party user, as part of third-party contract verification, or a combination thereof. The third-party user information may include the third-party user's banking details, such as a bank and account number associated with the third-party user, the name of the bank providing the bank account, the routing number associated with the bank account, the type of bank account, the name of the bank account holder, or a combination thereof.In addition, or alternatively, the third-party user information may include the third-party user's name, a company associated with the third-party user, date of birth, nationality, government identification number associated with the third-party user, CPF or CNPJ number, email address, phone number, fax number, address, sustainability information associated with the third-party user, or a combination thereof. The server may store at least part of the third-party user's information in the database. For example, part of the third-party user's information may be stored as part of the first entry or may be linked to the first entry.

[0302] In some implementations, as part of process 2900, the server obtains, from a device associated with the payer (for example, the second device associated with the second user), data from the third contract associated with a third contract between the second user and another user. The server can verify, based on input received from a fourth device associated with the other user, whether the data from the third contract is valid. In some examples, the activation of the third contract is triggered based on an event associated with the first contract. For example, the third contract may depend on the second user receiving Petition 870250086483, dated 09 / 24 / 2025, pp. 130 / 215 125 / 149 (or change of ownership) a good from the first user under the first contract. The server may store information from the second entry associated with the data from the third contract in the database. The information from the second entry may indicate the second user, the third user, the data from the first contract, the data from the third contract, or a combination thereof. The information from the second entry may be stored in the first entry or may be stored in a second entry associated with the third contract. If the data from the third contract is stored in the second entry, the second entry may be linked to the first entry in the database.

[0303] In some implementations, as part of process 2900, the server identifies the financial account (associated with the first contract between the first user and the second user) on the institution's server. For example, the server may identify the financial account based on identifying a status change (e.g., from pending to delivered) of the object indicated by the first entry, based on receiving (e.g., from the first user or the second user) the invoice data associated with the first contract, or a combination of these. The server may access the database, such as through a database API, and determine, based on the first entry associated with the first contract in the database, one or more disbursements to be made from the financial account. In some implementations, the one or more disbursements are determined based on the first entry and / or the identification of the status change of the object indicated by the first entry.One or more disbursements may include at least the first disbursement to the beneficiary of the first contract (for example, for a first account associated with the first user).

[0304] The server can send a request to the institution's server to carry out one or more disbursements. For example, the request may include or correspond to the 196 disbursement request. In some implementations, the request Petition 870250086483, dated 09 / 24 / 2025, pp. 131 / 215 126 / 149 is sent to the institution's server via the central server. Additionally, or alternatively, the server may receive a notification indicating that the first disbursement from the financial account to the beneficiary (e.g., a first account associated with the first user) has been initiated or completed. The notification may be received from the institution's server or the central server. In some implementations, the server may send a notification indicating that the first disbursement to the beneficiary (e.g., the first account associated with the first user) has been initiated and / or completed. To illustrate, the notification may be sent to the beneficiary.

[0305] In some implementations, as part of process 2900, the server receives a transfer request notification from the institution's server associated with the payer (e.g., the second user). For example, the transfer request might correspond to transfer 192. Additionally, or alternatively, the server might receive a transfer completion notification from the institution's server indicating the completion of a transfer to the financial account based on the transfer request. In some implementations, the transfer completion notification is received before the delivery of an object associated with the first agreement from the first user to the second user. For example, the transfer completion might be associated with an initial payment or a prepayment related to the first agreement.

[0306] In some implementations, the server receives sensor data associated with an object to be provided from the first user to the second user according to the first agreement. For example, sensor data may be received from a sensor associated with the first user, a silo system, a sensor associated with the second user, agricultural equipment, a transport device (e.g., a truck), a tracking device, or a combination thereof. Based on the sensor data, the server may store or Petition 870250086483, dated 09 / 24 / 2025, pp. 132 / 215 127 / 149 update the status of the first entry. Based on the status, sensor data, or a combination thereof, the server can determine whether to determine or indicate (for example, to the institution's server) one or more distributions associated with the financial account.

[0307] In some implementations, the server receives a status request from a user, such as the first user, the second user, a third user, etc., associated with the first agreement. Based on the status request, the server can access the database to obtain input information based on the first entry and obtain status information based on the information from the first entry. Additionally, or alternatively, the server can send a status information request (or forward the status request) to the central server and, in response, receive the status information from the central server. The status information may include or indicate an amount due associated with the first agreement, one or more distribution values, one or more fee values, other information associated with or indicated by the first entry, or a combination thereof.The server can send the status information to the first device, the second device, or the device of the user who initiated the status request.

[0308] In some implementations, the server generates, based on one or more database entries, historical data associated with a user, such as the first user or the second user. The historical data may include an aggregation of data from one or more entries, a result of one or more analyses of the entries, or a combination thereof. For example, based on the historical data, the user information associated with the user, or a combination of these elements, the server determines one or more metrics associated with the user. The metrics may include a risk score (e.g., a liability score) associated with the user, an on-time delivery rate associated with the Petition 870250086483, dated 09 / 24 / 2025, pp. 133 / 215 128 / 149 user, the number of defaults by the user, the total volume of products sold or received by the user, one or more indicators of the quality of the product produced by the user, or a combination of these elements. In some implementations, historical data and / or metrics may have a standard format, or the server may generate a report (e.g., a standardized report) that includes or indicates the historical data, metrics, or a combination of these elements. Additionally, or alternatively, the server may provide the historical data, metrics, user information, a combination thereof, or a report to another entity, such as the user or another user, the central server, the financial institution, another entity (e.g., an insurance provider, a vendor, a lender, etc.), or a combination of these entities.

[0309] In some implementations, the server may use historical data, metrics, risk score, user information, or a combination of these elements, to determine one or more rates associated with the user (e.g., first user or second user). For example, the lower the risk score, the lower the rate may be. As another example, the risk score may be used as a weight value that is applied to a standard rate to determine a rate for the user. Furthermore, or alternatively, the server may, for at least one service in a service set, determine a respective rate based on the metrics associated with the user, and send, to a user's device, an indication of the service and the respective rate. For example, the service may be an insurance product, such as an insurance product associated with the first agreement.

[0310] In some implementations, the server may generate one or more reports associated with the first agreement. For example, based on the execution and completion of the first agreement, the server may generate a summary report of payments and distributions, one or more fees, or a combination thereof. Petition 870250086483, dated 09 / 24 / 2025, pages 134 / 215 129 / 149 elements. In some of these implementations, the report may include a regulatory report, a compliance report, a tax report, or a combination thereof, that is associated with the first agreement, the users associated with the first agreement, or a combination thereof.

[0311] Referring to FIG. 30, FIG. 30 is a flow diagram illustrating an example of process 3000 of a server supporting the operation of a compensation system according to one or more aspects. The operations of process 3000 may be performed by a server, such as compensation server 116 described above with reference to FIGS. 1 or 2 and / or central server 250 described above with reference to FIG. 2. The compensation system may include or correspond to at least one or more aspects of systems 100 or 200.

[0312] In block 3002, the server identifies a financial account on an institution server, the financial account being associated with a first contract between a first user and a second user. The first user is a beneficiary of the financial account, and an entity associated with the central server has authority over the financial account. For example, the institution server may include or correspond to institution server 105. The data of the first contract may include or correspond to the information of contract 110. In some implementations, the first contract includes or corresponds to a contract.

[0313] In some implementations, the first user includes or matches the producer associated with the producer's device 102, and the second user includes or matches the buyer associated with the buyer's device 130. In other implementations, the first user includes or matches the buyer associated with the buyer's device 130, and the second user includes or matches the producer associated with the producer's device 102.

[0314] In block 3004, the server identifies a transfer made to the financial account. For example, the transfer may include or correspond to the transfer Petition 870250086483, dated 09 / 24 / 2025, pages 135 / 215 130 / 149 192. Additionally, or alternatively, the transfer is performed from a second account associated with the second user to the financial account. In some implementations, to identify the transfer, the server may receive a transfer notification (e.g., transfer notification 194) from the institution's server, or the server may monitor the financial account, such as by using an API from the institution's server.

[0315] In some implementations, to identify the transfer, the server receives a transfer request (e.g., transfer 292) from a device associated with the second user. The server can then initiate, based on the transfer request, the transfer to the financial account.

[0316] In block 3006, the server, based on the transfer identification, sends a request to the institution's server to perform one or more disbursements from the financial account, with the disbursements determined based on an initial entry in a database. For example, the request may include or match disbursement information 260. The database may include or match database 126. The initial entry may include or match entry 3880. The initial entry is associated with the first contract and indicates the first user, the second user, the data of the first contract associated with the first user, the financial account, or a combination of these elements. For example, the entry may include or indicate entry information associated with the first contract.The input information may include or indicate that the first entry includes input information associated with the first contract, and the input information indicates one or more payment values, one or more fees, or a combination of these elements. In some examples, at least part of the input information is immutable. In some implementations, the database includes a blockchain ledger that stores the first entry, where the first entry includes a smart contract based on the first. Petition 870250086483, dated 09 / 24 / 2025, pp. 136 / 215 131 / 149 contract.

[0317] In some implementations, the server obtains an indicator that shows the disbursement(s). For example, the indicator may be obtained (e.g., received) from another device or server, such as database 126 or authorization server 116. To illustrate, the server may access the database to obtain at least some of the input information. The server may send the request (to make the disbursement(s)) to the institution's server based on or in response to receiving the indicator.

[0318] In block 3008, the server sends a notification indicating the first disbursement to a first account associated with the first user. For example, the server might send the notification to the first user's device, to the database (to be stored in the first entry), to an authorization server, to the second user's device, or a combination of these.

[0319] In some implementations, the server identifies, based on input information, a third user associated with the first contract. For example, the third user may include or correspond to the recipient associated with the recipient's device. In these examples, the one or more disbursements include a second disbursement to a third account associated with the third user. Additionally, or alternatively, the server may determine, based on input information, a fee associated with the first contract, a fee associated with another contract (related to or linked to the first contract), or a combination thereof. In some examples, the one or more disbursements include a third disbursement to a fourth account associated with an entity associated with the authorization server, the server, or the institution's server. The third disbursement may be fee-based, such as a service fee, a regulatory fee, or a combination thereof.

[0320] In some implementations, the server receives, from the server of Petition 870250086483, dated 09 / 24 / 2025, pp. 137 / 215 132 / 149 authorization, a first indicator that shows information about the first user associated with the first user, a request to create the financial account associated with the first contract, or a combination of these. In some implementations, the server receives a request from an authorization server to verify the first user. In some of these implementations, the request includes or indicates information about the first user associated with the first user. The server may send at least part of the first user's information to the institution's server and receive, from the institution's server, based on that part of the first user's information, a verification response indicating whether the first user has been verified or not. If the first user is verified, the server may send an indicator to the authorization server indicating that the first user has been verified.Additionally, or alternatively, in some implementations, the server may send an account creation request to the institution's server. For example, the account creation request may include or correspond to account request 172. In some examples, the account creation request may be sent via an application programming interface (API) of the institution's server.

[0321] The server may receive an identifier associated with the financial account from the institution's server. For example, the identifier may include or match account ID 174. The identifier may include or indicate a financial account number, a routing number associated with the financial account, the name of an entity providing the financial account, the name of a financial account beneficiary, a Quick Response (QR) code or barcode associated with the financial account, or a combination thereof. The server may send the identifier to the authorization server, to the payer (e.g., the second device associated with the second user), store the identifier in the first entry, or a combination of these actions. Petition 870250086483, dated 09 / 24 / 2025, pp. 138 / 215 133 / 149

[0322] In some implementations, the server obtains confirmation from the institution's server that one or more payments have been executed. Additionally, or alternatively, the server may send a request to the institution's server, based on the confirmation, to close the financial account. The request to close the financial account may include or correspond to closing request 262. To illustrate, the server may receive the confirmation and access the first database entry to determine if the first agreement has been fulfilled (e.g., if the status of the first entry indicates that it has been completed or satisfied). If the first agreement is satisfied, the server may send the request to close the financial account.

[0323] In some implementations, the server receives a status request from the settlement server associated with the first settlement. In response to the status request, the server may access the database to obtain at least some of the entry information based on the first settlement. The server may generate status information based on the entry information and send the status information to the settlement server. The status information may include or indicate an amount due associated with the first settlement, one or more distribution values, one or more fee values, or a combination thereof.

[0324] Note that one or more blocks (or operations) described with reference to Figures 2, 9, 26, 29, or 30 can be combined with one or more blocks (or operations) described with reference to another of the figures. For example, one or more blocks (or operations) in Figure 2 can be combined with one or more blocks (or operations) in Figure 9. As another example, one or more blocks (or operations) in Figure 2 can be combined with one or more blocks (or operations) in Figure 29. As another example, one or more blocks associated with Figure 2 or 9 can be combined with one or more blocks (or operations) associated with Figures 29 or 30. Additionally, or alternatively, one or more Petition 870250086483, dated 09 / 24 / 2025, pp. 139 / 215 134 / 149 operations described above with reference to Figures 3-8, 10-25, 27 or 28 can be combined with one or more operations described with reference to Figures 1A, 1B, 2, 9, 26, 29 or 30. Additionally, or alternatively, one or more operations described above with reference to Figures 1 or 1B can be combined with one or more operations described with reference to Figures 2-38.

[0325] Refers to FIG. 38, a block diagram of an example of database 126 of a release system according to one or more aspects. The release system may include or correspond to system 100 or 200.

[0326] Database 126 includes users 1810, device information 3838, bank account information 1910, agreement information 2110, financial account information 2112, sensor information 3840, and an entry 3880. The entry may include or correspond to the entry (e.g., the first entry) as described herein, at least with reference to FIGS. 1, 2, 29, and 30. Device information 3838 may include or indicate a device ID, a registered device ID, device type (e.g., smartphone, laptop, desktop, etc.), manufacturer, operating system, or a combination thereof. Sensor information 3840 may include or indicate, for a sensor, a sensor ID, sensor location, sensor owner, sensor signature, sensor certification results, laboratory certification and / or test results, sensor data received from the sensor, or a combination thereof.

[0327] In some implementations, the information (e.g., data) stored in users 1810, device information 3838, bank account information 1910, agreement information 2110, financial account information 2112, sensor information 3840, and / or entry 3880 may have a unique reference number (e.g., an index value, a reference value, an address value, or a combination thereof). The Petition 870250086483, dated 09 / 24 / 2025, pages 140 / 215 135 / 149 Clearance server 116 and / or database 126 may link or associate information based on unique reference numbers. For example, a user referred by users 1810 may include a first unique reference number from a device included in device information 3838.

[0328] In some implementations, each user indicated in users 1810 may have respective access rights (for example, read access rights, write access rights, or a combination thereof). User access rights may indicate the same or different access rights for users 1810, device information 3838, bank account information 1910, agreement information 2110, financial account information 2112, sensor information 3840, and / or entry 3880.

[0329] Entry 3880 may include or indicate a buyer 3891, a seller 3892, a contract ID 3893, a financial account ID 3894, and a smart contract 3895. Although entry 3880 is described as including smart contract 3895, in other implementations, entry 3880 may not include smart contract 3895. In some implementations, entry 3880 may optionally include a beneficiary 3896, tracking information 3897, or a combination thereof.

[0330] Buyer 3891 can be filled in based on or referencing users 1810, device information 3838, bank account information 1910, or a combination thereof. Seller 3892 can be filled in based on or referencing users 1810, device information 3838, bank account information 1910, or a combination thereof. Beneficiary 3896 can be filled in based on or referencing users 1810, device information 3838, bank account information 1910, or a combination thereof.

[0331] Contract ID 3893 can be filled in based on or referencing the information from contract 2110. Financial account ID 3894 can be filled in Petition 870250086483, dated 09 / 24 / 2025, pp. 141 / 215 136 / 149 based on or referencing the financial account information 2112. Tracking information 3897 can be filled in based on or referencing the sensor information 3840.

[0332] Smart contract 3895 can be generated based on users 1810, bank account information 1910, contract information 2110, financial account information 2112, or a combination of these elements. In some implementations, one or more operations of smart contract 3895 can be triggered or executed based on financial account information 2112, sensor information 3840, or a combination of these elements.

[0333] In some implementations, database 126 may include ledger 127. Ledger 127 may contain users 1810, device information 3838, bank account information 1910, contract information 2110, financial account information 2112, sensor information 3840, and entry 3880. In one specific implementation, ledger 127 includes one or more entries (including entry 3880) that are immutable. Entry 3880 may be generated or populated based on at least users 1810, device information 3838, bank account information 1910, contract information 2110, financial account information 2112, sensor information 3840, or a combination of these elements.

[0334] In some implementations of FIGS. 1-38, an individual or entity that sends or transfers money may be referred to as a sender. A person or entity that holds a legal right or interest in property may be referred to as a pledgee. A legal document that gives the recipient the right to a future payment, including a promissory note, a forward contract, an invoice, a debenture, may be referred to as a contract. Financial accounts (e.g., trust accounts) are dedicated accounts and have a 1-to-1 relationship with a contract. The primary purpose of a financial account is to distribute the Petition 870250086483, dated 09 / 24 / 2025, pp. 142 / 215 137 / 149 payments received from the sender to the recipient and assignees. After full settlement of the account, it is closed. A financial institution (e.g., Banco do Brasil) that maintains the financial account may be referred to as a bank. An individual or entity that receives money from the sender into a financial account may be referred to as a recipient. An individual or entity designated to receive payment on behalf of another from the financial account may be referred to as an assignee. An individual or entity that is the ultimate recipient of the payment rights, having received those rights after possible multiple transfers or assignments from the original payer or recipient, may be referred to as an ultimate assignee.A legally binding contract signed by the sender, the recipient, and the bank, which includes a summary of the original contract between the recipient and the sender, and serves as an acknowledgment that the contract is valid and enforceable, may be referred to as a credit assignment notice (e.g., a notice). A document (e.g., a legally binding agreement signed by the sender and the recipient) that authorizes the release of funds from a financial account to a specified assignee may be referred to as a payment assignment agreement. A graphical user interface for the platform (e.g., the 116 clearing server) may be referred to as an application.The support team (e.g., employees or agents) of an entity that manages the application and / or the 116 clearing server, and the account executives associated with facilitating the establishment of financial accounts, document verification, and assistance in obtaining signatures, may be referred to as a back-office team. An individual who interacts with the application to access its services, features, or content may be referred to as a user.

[0335] With reference to one or more of the implementations described herein, such as with reference to system 200 of FIG. 1B, the clearing server 116 can be configured to assist one or more users (for example, a sender, Petition 870250086483, dated 09 / 24 / 2025, pages 143 / 215 138 / 149 a recipient, an assignee, a producer, a buyer, or a combination thereof). For example, the clearing server 116 can assist the user through one or more communications (e.g., notifications, requests, or instructions) to identify another participant, confirm a contract or agreement, generate a smart contract, or a combination of these actions. The clearing server 116, and optionally the back-office functionalities of the clearing server 116, can ensure that documents are in order before initiating the settlement process and can expedite the contract settlement process.

[0336] The 116 clearing server can be configured to obtain and / or aggregate transactional data associated with a user. For example, the 116 clearing server can determine historical data (e.g., agreements, parties involved in agreements, terms, payments, settlements, etc.) for a user that would otherwise not be available to the user and / or a third party other than the user. In some examples, historical data can provide an alternative or improvement in obtaining a credit report. In some implementations, the 116 clearing server can be configured to generate (e.g., calculate) a score, such as a credit score, based on the data associated with a user. Based on the data obtained by the 116 clearing server, a user can more easily obtain loans from the bank and / or an assignee.The opportunity to obtain financing and / or a loan based on data obtained by the 116 clearing server can empower the user, eliminating the need to request credit assignments from other parties, which can place the user in a vulnerable position with respect to their creditors. Furthermore, the bank and / or an assignee can benefit from having access to the user's historical data and / or credit score, data that the bank or assignee would not normally have. For example, the bank and / or assignee can reduce or eliminate the risk of default by having access to the server's data. Petition 870250086483, dated 09 / 24 / 2025, pages 144 / 215 139 / 149 compensation 116.

[0337] By using clearing server 116 (and / or, optionally, central server 250), an assignee may be able to reduce the risk of default. For example, using the financial account can provide certainty that the assignee will receive payment as soon as the financial account is funded, ensuring that another user (who owes the assignee) cannot interfere after the financial account is funded. Furthermore, the assignee can gain transparency regarding the payment order (cash flow) and / or receive a warning notification about any problems, such as another or new pledge holder, that might prevent payment to the assignee. Clearing server 116 (and / or central server 250) can also allow the assignee to more easily apply for loans and / or reassign their payment to another user.

[0338] Through the use of clearing server 116 (and / or central server 250), an assignee may be able to participate in new transactions that are occurring outside the bank. For example, clearing server 116 (and / or central server 250) can provide a process flow that is not present in conventional financial systems. The bank's ability to be involved in this process flow can provide the bank with additional information / data about individual users, create new revenue streams, increase competitive differentiation and market relevance due to innovative products, or a combination of these factors.

[0339] In some implementations, clearing server 116 and / or central server 250 (e.g., tariff module 253) may be configured to apply a fee (e.g., a cost). The fee may be applied based on one or more services or operations provided by clearing server 116 and / or central server 250, and / or may be applied / implemented to funds provided to the financial account. In some examples, the user may be charged a Petition 870250086483, dated 09 / 24 / 2025, pages 145 / 215 140 / 149 fee to set up a financial account. However, if the user obtains funding through the 116 clearing server (e.g., the application) and / or adds an assignee, the fee is waived, and the service becomes free for the user. Additionally, or alternatively, an assignee may be charged a fee that is applied to a portion of the settlement funds for the assignee, a loan success fee paid by lenders providing loans to users, or a combination of these factors. Fees for one or more parties may be reduced or eliminated based on the amount of funds provided to the financial account, the frequency of use of the 116 clearing server for settlements, etc.

[0340] In some implementations, the clearing server 116 that supports the application is configured to interact with the institution server 150 (e.g., a financial institution or the bank). For example, the clearing server 116 might interact with an endpoint or API of the institution server 150 to authenticate a user, manage an account at the financial institution, initiate a money transfer or settlement of a financial account, or a combination of these actions. It is worth noting that, in some implementations, an outgoing funds transfer or the closing of a financial account may be controlled by the clearing server 116 and / or the central server 250 – that is, one or more parties that are to receive funds from the financial account may not be able to (directly) initiate an outgoing funds transfer from the financial account or close the financial account.However, one or more parties associated with the financial account may be able to view information (e.g., a report and / or a balance) associated with the financial account through the application.

[0341] In an illustrative example, a user is the recipient associated with a transaction and has an existing unpaid contract with a sender. The user can log in to the application, for example, using bank login credentials. Petition 870250086483, dated 09 / 24 / 2025, pages 146 / 215 141 / 149 of the user. When using the application, the user may have a graphical user interface (GUI) (e.g., a control panel) that includes or indicates one or more contracts and corresponding financial accounts. Additionally, the user may have the ability to create a new financial account through the application. To create the new financial account, the user can submit a contract or a term of agreement. The user can fill out a form (through the application) with information related to the contract and information about the sender associated with the contract. In some implementations, the sender can be contacted through the application to confirm the contract. Furthermore, or alternatively, the application (e.g., clearing server 116 and / or central server 250) can generate a notification document and automatically send a request for digital signatures from the recipient, sender, and bank.It is worth noting that, in other implementations, the sender can log into the application and send the contract so that the financial account can be created.

[0342] Based on the contract, the application can create a new dedicated financial account at the bank (for example, the financial institution associated with institution server 150). The financial account may include or correspond to the contract. The financial account may be opened before or after the notification document is fully executed by the sender, recipient, and bank. In such implementations, the created financial account may be inactive until the notification document is fully executed. After the notification document is fully executed, the financial account becomes active and ready to receive payment from the sender (or other party). It is worth noting that the financial account may have one or more statuses, such as active, inactive, under review, suspended, closed, blocked, unblocked, or other status.

[0343] The user may have the ability to add an assignee. For example, when using the application, the user can select an active financial account. Petition 870250086483, dated 09 / 24 / 2025, pages 147 / 215 142 / 149 specifically and choose an option (via the application) to add an assignee, so that the added assignee will receive a payment from the selected financial account. After selecting the add option, the user can fill out a form with information about the payment destination, amount, and contact details of the assignee. The application can generate a payment assignment agreement using the information collected in the form. This agreement is automatically sent for digital signature collection from the recipient and the assignee. After the complete execution of the agreement via the application, the assignee is added with full effect. In some of these examples, the executed payment assignment agreement is stored in ledger 127, in association with the agreement and / or the financial account.

[0344] After the financial account is created and activated, funds can be deposited into the financial account. The application (e.g., settlement server 116 and / or main server 250) can receive a notification via an endpoint or API from institution server 150 about the payment into the financial account. Additionally, or alternatively, the application (e.g., settlement server 116 and / or main server 250) can provide a notification (e.g., a push notification) to the recipient, sender, one or more assignees, or a combination thereof, confirming the payment.

[0345] Settlement server 116 and / or main server 250 may initiate a distribution process from the financial account according to the order and instructions defined in the setup process and / or additions (e.g., a payment assignment agreement) associated with the agreement. In some implementations, the application (e.g., settlement server 116 and / or main server 250) may send a settlement notification to one or more parties associated with the financial account. Note that the distribution process may also include the application of fees and / or charges on the funds, which will be transferred to the appropriate account(s). After the funds are transferred, the Petition 870250086483, dated 09 / 24 / 2025, pages 148 / 215 143 / 149 settlement server 116 and / or the main server 250 can determine whether the contract has been fulfilled (e.g., whether all payment amounts have been settled) or whether it is still pending. Based on the determination that the contract has been fulfilled, settlement server 116 and / or the main server 250 requests / instructs the institution server 150 to close the financial account.

[0346] Certain features described in this specification in the context of separate implementations may also be implemented in combination in a single implementation. Similarly, several features described in the context of a single implementation may also be implemented in multiple separate implementations or in any suitable subcombination.

[0347] Similarly, although operations are represented in the drawings in a specific order, this should not be understood as a requirement that such operations be performed in the exact order shown or sequentially, or that all illustrated operations be performed to achieve the desired results. Furthermore, the drawings may schematically represent one or more example processes in the form of a flow diagram. However, other operations not represented may be incorporated into the schematically illustrated example processes. For example, one or more additional operations may be performed before, after, simultaneously with, or between any of the illustrated operations. In certain circumstances, multitasking and parallel processing may be advantageous.Furthermore, the separation of various system components in the implementations described above should not be understood as a requirement for separation in all implementations; it should be understood that the components and systems described may be integrated into a single software product or grouped into multiple software products. Additionally, other implementations fall within the scope of the following claims. In some cases, the actions mentioned in... Petition 870250086483, dated 09 / 24 / 2025, pages 149 / 215 Claims 144 / 149 can be made in a different order and still achieve the desired results.

[0348] Professionals in the field would understand that information, messages, and signals can be represented through various different technologies and techniques. For example, data, instructions, commands, information, and signals that may be mentioned throughout the description above can be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0349] The components, functional blocks, and modules described herein with the figures include processors, electronic devices, hardware devices, electronic components, logic circuits, memories, software code, firmware code, among other examples, or any combination thereof. Software should be interpreted broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software packages, routines, subroutines, objects, executables, execution threads, procedures, or functions, among other examples, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. Furthermore, the functionalities discussed herein may be implemented by means of specialized processor circuits, executable instructions, or combinations thereof.

[0350] Experts in the field would also realize that the various illustrative logic blocks, modules, circuits, and algorithmic steps described in connection with the disclosure herein can be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability between hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above in general terms. Petition 870250086483, dated 09 / 24 / 2025, pages 150 / 215 145 / 149 of its functionality. The various illustrative logic, logic blocks, modules, circuits, and algorithmic processes described in connection with the implementations disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. In one or more aspects, the functions described may be implemented in hardware, digital electronic circuits, computer software, firmware, including the structures disclosed in this specification and their structural equivalents, or in any combination of these options. The implementations of the subject matter described in this specification may also be implemented as one or more computer programs, that is, one or more modules of computer program instructions, encoded in a computer storage medium for execution by, or to control the operation of, a data processing device.

[0351] The hardware and data processing apparatus used to implement the various illustrative logic, logic blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented or realized with a single-chip or multi-chip general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, discrete gate logic or transistors, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, or any conventional processor, controller, microcontroller, or state machine.In some implementations, a processor can be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors together with a DSP core, or any other such configuration. In some implementations... Petition 870250086483, dated 09 / 24 / 2025, pages 151 / 215 146 / 149 particular processes and methods can be performed by circuits specific to a given function.

[0352] If implemented in software, functions can be stored or transmitted as one or more instructions or code on a computer-readable medium. The processes of a method or algorithm disclosed herein can be implemented in a processor-executable software module, which may reside on a computer-readable medium. Computer-readable media include both computer storage media and communication media, including any medium that can be enabled to transfer a computer program from one place to another. A storage medium can be any available media that can be accessed by a computer.By way of example, and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired program code in the form of instructions or data structures and that can be accessed by a computer. Furthermore, any connection may be properly termed a computer-readable medium. In addition, the operations of a method or algorithm may reside as one or any combination or set of codes and instructions in a machine-readable medium and a computer-readable medium, which may be incorporated into a computer program product.

[0353] As used in this document, the varied terminology is intended to describe specific implementations and is not intended to limit implementations. For example, as used here, an ordinal term (e.g., first, second, third, etc.) used to modify an element, such as a structure, a component, an operation, etc., does not by itself indicate any priority or order of the element relative to another element, but rather Petition 870250086483, dated 09 / 24 / 2025, pp. 152 / 215 147 / 149 only distinguishes the element from another that has the same name (except for the use of the ordinal term). The term coupled is defined as connected, although not necessarily directly and not necessarily mechanically; two items that are coupled may be unitary to each other. The terms a and an are defined as one or more, unless this document explicitly requires otherwise.

[0354] The term approximately as used in this document may allow a margin of variability in a value or range, for example, within 10%, within 5%, or within 1% of a stated value or range limit, and includes the exact stated value or range. The term substantially is defined as being largely, but not necessarily entirely, what has been specified (and includes what has been specified; for example, substantially 90 degrees includes 90 degrees, and substantially parallel includes parallel), as understood by a person of ordinary skill in the area. In any disclosed implementation, the term substantially may be replaced by within [a percentage] of what has been specified, where the percentage includes 0.1, 1, or 5 percent; and the term approximately may be replaced by within 10% of what has been specified.The expression "substantially X to Y" has the same meaning as "substantially X to substantially Y," unless otherwise indicated. Similarly, the expression "substantially X, Y, or substantially Z" has the same meaning as "substantially X, substantially Y, or substantially Z," unless otherwise indicated. Unless stated otherwise, the word "or," as used in this document, is an inclusive "or" and is interchangeable with "and / or," so that when "or" is used in a list of two or more items, it means that any one of the listed items may be used alone, or any combination of two or more of the listed items may be employed. To illustrate, A, B, or C includes: A alone, B alone, C alone, a combination of A and B, or one. Petition 870250086483, dated 09 / 24 / 2025, pp. 153 / 215 148 / 149 combination of A and C, a combination of B and C, or a combination of A, B and C. Similarly, the phrase A, B, C, or any combination thereof includes: A alone, B alone, C alone, a combination of A and B, a combination of A and C, a combination of B and C, or a combination of A, B and C.

[0355] Throughout this document, values ​​expressed in range format should be interpreted flexibly, including not only the numerical values ​​explicitly mentioned as the limits of the range, but also all individual numerical values ​​or subintervals that are comprised within that range, as if each numerical value and subinterval were explicitly mentioned. For example, a range of approximately 0.1% to approximately 5% or approximately 0.1% to 5% should be interpreted to include not only approximately 0.1% to approximately 5%, but also the individual values ​​(e.g., 1%, 2%, 3%, and 4%) and the subintervals (e.g., 0.1% to 0.5%, 1.1% to 2.2%, 3.3% to 4.4%) within the indicated range.

[0356] The terms “comprises” (and any form of “comprises”, such as “comprises” and “comprising”), “has” (and any form of “has”, such as “has” and “having”), “includes” (and any form of “includes”, such as “includes” and “including”) and “contains” (and any form of “contains”, such as “contains” and “containing”). As a result, a device that “comprises”, “has”, “includes” or “contains” one or more elements possesses those one or more elements, but is not limited to possessing only those one or more elements. Similarly, a method that “comprises”, “has”, “includes” or “contains” one or more steps possesses those one or more steps, but is not limited to possessing only those one or more steps.

[0357] Any implementation of any of the manufacturing systems, methods, and articles may consist of or essentially consist of—rather than comprising / having / including—any of the steps, elements, or features described. Thus, in any of the claims, the term “consisting of” or Petition 870250086483, dated 09 / 24 / 2025, pages 154 / 215 149 / 149 “consisting essentially of” can be replaced by any of the open linking verbs mentioned above in order to alter the scope of a given claim from what it would otherwise be using the open linking verb. Furthermore, the term “where” can be used interchangeably with “where”.

[0358] Furthermore, a device or system that is configured in a particular way is configured at least in that way, but may also be configured in other ways beyond those specifically described. The feature or features of an implementation may be applied to other implementations, even if not described or illustrated, unless expressly prohibited by this disclosure or by the nature of the implementations.

[0359] The claims are not intended to include, and should not be interpreted as including, limitations of the type "means to" or "steps to," unless such limitation is explicitly stated in a specific claim using the expression(s) "means to" or "steps to," respectively.

[0360] The preceding description of the disclosure is provided to enable any person skilled in the field to make or use the disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the field, and the generic principles set forth herein may be applied to other variations without departing from the spirit or scope of the disclosure. Thus, the disclosure and claims that follow should not be limited to the examples and designs described herein, and should be given the widest possible scope consistent with the new principles and features disclosed herein.

Claims

1. A method, executed by a clearing server, to implement a clearing service, the method CHARACTERIZED by the fact that it comprises: obtaining the initial contract data associated with a first contract between a first user and a second user; verifying whether the initial contract data associated with the first contract is valid based on: a first entry received from a first device associated with the first user; a second entry received from a second device associated with the second user; or a combination of both; after verifying the first contract, sending a request to create, on an institutional server, a financial account associated with the first contract; and storing, in a database, input information associated with the first contract, where the input information indicates the first user, the second user, the initial contract data, the financial account, or a combination of both.

2. Method, according to claim 1, CHARACTERIZED in that: at least part of the first entry is immutable; the first agreement is additionally between the first user, the second user and an entity associated with the institution's server; the first entry includes a first digital signature and the second entry includes a second digital signature; obtaining the data from the first agreement includes receiving the data from the first agreement Petition 870250086483, dated 09 / 24 / 2025, page 156 / 215 2 / 28 from the first device or generating the data from the first agreement; or a combination thereof.

3. Method, according to claim 1, CHARACTERIZED in that it comprises: generating a smart contract based on the first contract, wherein: the database includes a blockchain-based ledger that stores the first entry, and the first entry includes the smart contract.

4. Method, according to claim 1, CHARACTERIZED in that it additionally comprises: After verification of the first contract, initiating the formation of a second contract associated with the use of the financial account in association with the first contract, the second contract between the first user, the second user and an entity associated with the institution's server; Verifying if the second contract is complete; and Storing, in the database, the data of the second contract in the first entry, where the data of the second contract are associated with the second contract.

5. Method, according to claim 4, CHARACTERIZED in that it additionally comprises: generating a first version of the second agreement based on the first agreement, the financial account, or a combination of both; and sending, to each of the first user, the second user, and the entity, a request to sign the first version of the second agreement, where the verified second agreement is a second version of the second agreement that is signed by each of the first user, the second user, and the entity.

6. Method, according to claim 4, CHARACTERIZED by the fact Petition 870250086483, dated 09 / 24 / 2025, page 157 / 215 3 / 28 that: Before verification of the second contract, the financial account has a reserved status.

7. Method, according to claim 6, CHARACTERIZED in that it further comprises: After verification of the second contract, sending a status change request to the institution's server to change the status of the financial account from reserved to active.

8. Method, according to claim 1, CHARACTERIZED in that it further comprises: receiving, from the first device associated with the first user, information from the first user associated with the first user, wherein the information from the first user indicates: a first bank account associated with the first user, and a name of the first user, a company associated with the first user, a date of birth of the first user, a nationality of the first user, a government identification number associated with the first user, an email address associated with the first user, a telephone number associated with the first user, a fax number associated with the first user, an address associated with the first user, or a combination of these elements;and storing, in the database, information from the first bank account indicating the first bank account, the bank name, the account type, the account holder's name, or a combination of these elements, and where the first contract indicates that the second user owes the first user a payment amount.

9. Method, according to claim 1, CHARACTERIZED in that it further comprises: Petition 870250086483, dated 09 / 24 / 2025, page 158 / 215 4 / 28 receiving, from the second device associated with the second user, information from the second user associated with the second user, where the information from the second user indicates a second bank account associated with the second user; and storing, in the database, information from the second bank account that indicates the second bank account, and where the first agreement indicates that the second user owes the first user a payment amount.

10. Method according to claim 9, CHARACTERIZED in that it further comprises: receiving, from a third device associated with a third user, a payment request associated with the first agreement, where the payment request includes document data, a requested amount, or a combination of both; sending, to a device of the first user associated with the first user, an approval request based on the payment request; receiving, from the first user's device, an approval message in response to the approval request; and updating the first entry to indicate that the third user should receive a portion of the payment amount paid by the second user according to the first agreement.

11. Method, according to claim 10, CHARACTERIZED in that it further comprises: receiving, from the third-party device associated with the third-party user, information from the third-party user associated with the third-party user, wherein the information from the third-party user indicates a third bank account associated with the third-party user; and storing, in the database, information from the third bank account that indicates the third bank account, and Petition 870250086483, dated 09 / 24 / 2025, p. 159 / 215 5 / 28 in which the document data are associated with an assignment agreement.

12. Method, according to claim 10, CHARACTERIZED in that it further comprises: obtaining, from the second device associated with the second user, data from the third agreement associated with a third agreement between the second user and another user; and verifying, based on an input received from a third device associated with the third user, that the data from the third agreement associated with the third agreement is valid, wherein the activation of the third agreement is triggered based on an event associated with the first agreement.

13. Method, according to claim 12, CHARACTERIZED in that it further comprises: storing, in the first database entry, the data of the third contract.

14. Method according to claim 12, CHARACTERIZED in that it comprises: Storing, in the database, information from the second entry in a second entry associated with the third agreement, where the information from the second entry indicates the second user, the third user, the data from the first agreement, the data from the third agreement, or a combination thereof, and where the second entry is linked to the first entry in the database.

15. Method, according to claim 1, CHARACTERIZED in that it further comprises: identifying the financial account on the institution's server, the financial account associated with the first agreement between the first user and the second user; determining, based on the first entry in the database, one or more distributions of the financial account, wherein the one or more distributions include Petition 870250086483, dated 09 / 24 / 2025, page 160 / 215 6 / 28 a first distribution to a first account associated with the first user, where the first entry is associated with the first agreement; sending a request to the institution's server to perform the one or more distributions; and sending a notification indicating the first distribution to the first account associated with the first user.

16. Method, according to claim 15, CHARACTERIZED in that it further comprises: receiving, from the institution's server, a transfer request notification of a transfer request associated with the second user; and receiving, from the institution's server, a transfer completion notification indicating the completion of a transfer to the financial account based on the transfer request.

17. Method, according to claim 16, CHARACTERIZED in that: the transfer completion notification is received before the delivery, by the first user to the second, of an object associated with the first agreement; and determining one or more disbursements is carried out based on the identification of a change in the status of the object indicated by the first entry.

18. Method according to claim 15, CHARACTERIZED in that it further comprises: receiving, from the first device or the second device, invoice data associated with the first contract.

19. Method, according to claim 1, CHARACTERIZED in that it further comprises: receiving, from the institution's server, an identifier associated with the financial account; and Petition 870250086483, dated 09 / 24 / 2025, page 161 / 215 7 / 28 sending the identifier to the second device associated with the second user; or storing the identifier in the first entry.

20. Method, according to claim 19, CHARACTERIZED in that the indicator includes a financial account number, a routing number, or a combination thereof.

21. Method according to claim 19, CHARACTERIZED in that the identifier includes a Quick Response (QR) code.

22. Method, according to claim 1, CHARACTERIZED in that the request to create the financial account associated with the first agreement is sent to the institution's server via a central server.

23. Method according to claim 22, CHARACTERIZED in that it further comprises: sending a request to the central server to create the financial account associated with the first agreement; and receiving, from the central server or the institution's server, an indicator associated with the financial account.

24. Method, according to claim 22, CHARACTERIZED in that it further comprises: receiving, from the central server, a notification indicating an initial payment from the financial account to an initial account associated with the initial user.

25. Method, according to claim 1, CHARACTERIZED in that it additionally comprises: sending, to a central server, a first indicator that indicates information of the first user associated with the first user; sending, to the central server, a request to create the financial account Petition 870250086483, dated 09 / 24 / 2025, page 162 / 215 8 / 28 associated with the first agreement; receiving, from the central server, an identifier associated with the financial account; and sending the identifier to a device associated with the second user, to the database for storage in the first entry, or a combination thereof.

26. A method according to claim 1, characterized in that it further comprises: sending a request to a central server to verify the first user, wherein the request includes information about the first user associated with the first user; and receiving from the central server an indicator that shows that the first user has been verified.

27. Method, according to claim 1, CHARACTERIZED in that it further comprises: receiving, from the first device or the second device, a status request associated with the first agreement; accessing the database to obtain first-entry information based on the first entry; obtaining status information based on the first-entry information, where the status information indicates an amount due associated with the first agreement, one or more distribution values, one or more fee values, or a combination thereof; and sending the status information to the first device or the second device.

28. Method according to claim 27, CHARACTERIZED in that it further comprises: Petition 870250086483, dated 09 / 24 / 2025, page 163 / 215 9 / 28 In response to receiving the status request, sending a status information request to a central server; and Receiving the status information from the central server in response to the status information request.

29. Method, according to claim 1, CHARACTERIZED in that it further comprises: generating, based on one or more database entries, historical data associated with the first user; determining, based on the historical data, user information associated with the first user, or a combination thereof, one or more metrics associated with the first user; for at least one service in a set of services, determining a respective rate based on the one or more metrics associated with the first user; and sending, to the first device, an indication of at least one service and the respective rate.

30. A method according to claim 1, characterized in that it further comprises: receiving sensor data associated with an object to be provided from the first user to the second user according to the first agreement; storing, based on the sensor data, a status on the first entry; and determining, based on the status, the sensor data, or a combination of both, whether to indicate one or more distributions associated with the financial account.

31. Method, performed by a central server, to implement an authorization service, the method CHARACTERIZED by the fact that it comprises: identifying a bank account on an institution's server, the bank account being associated with a first agreement between a first user and a second user, where the first user is the beneficiary of the bank account and an entity Petition 870250086483, dated 09 / 24 / 2025, p.164 / 215 10 / 28 associated with the central server has authority over the bank account; identify a transfer made to the bank account; based on the identification of the transfer, send a request to the institution's server to make one or more disbursements from the financial account, the disbursement(s) being determined based on a first entry in a database, where the first entry is associated with the first agreement and indicates the first user, the second user, data from the first agreement associated with the first user, the financial account, or a combination of these elements; and send a notification indicating a first disbursement to a first account associated with the first user.

32. Method according to claim 31, CHARACTERIZED in that it further comprises: receiving a transfer request from a device associated with the second user; and initiating, based on the transfer request, the transfer to the financial account.

33. Method, according to claim 31, CHARACTERIZED in that it also comprises: receiving, from a settlement server, an indicator that shows one or more distributions, wherein the sending of the request to the institution's server is carried out in response to the receipt of the indicator.

34. Method according to claim 31, CHARACTERIZED in that: the first record includes record information associated with the first agreement; the record information indicates one or more payment amounts, one or more fees, or a combination thereof; and Petition 870250086483, dated 09 / 24 / 2025, pp. 165 / 215 11 / 28 at least part of the record information is immutable.

35. Method, according to claim 34, CHARACTERIZED in that it additionally comprises: Accessing the database to obtain at least part of the entry information, and where the transfer is carried out from a second account associated with the second user to the financial account.

36. Method according to claim 35, CHARACTERIZED in that it additionally comprises: identifying, based on input information, a third user associated with the first contract, and wherein one or more distributions include a second distribution to a third account associated with the third user.

37. Method according to claim 35, CHARACTERIZED in that it further comprises: determining, based on input information, a rate associated with the first settlement, and where one or more distributions include a third distribution to a fourth account associated with an entity associated with a clearing server, the central server or the institution's server, and where the third distribution is based on the rate.

38. Method according to claim 37, CHARACTERIZED in that the fee includes a service fee, a regulatory fee, or a combination thereof.

39. Method, according to claim 31, CHARACTERIZED in that: The database includes a blockchain ledger that stores the first entry in Petition 870250086483, dated 09 / 24 / 2025, page 166 / 215 12 / 28, and the first entry includes a smart contract based on the first agreement.

40. Method according to claim 31, CHARACTERIZED in that it further comprises: Receiving from the clearing server a first indicator that shows information of the first user associated with the first user; Receiving from the clearing server a request to create the financial account associated with the first contract; Sending to the institution's server a request to create the account; Receiving from the institution's server an identifier associated with the financial account; and Sending to the clearing server a device associated with the second user, the database for storage in the first entry, or a combination thereof, the identifier.

41. Method according to claim 40, CHARACTERIZED in that: The account creation request is sent via an application programming interface (API) of the institution's server; and The identifier associated with the financial account includes an account number, a routing number, the bank name, the beneficiary's name, a quick response (QR) code, a barcode, or a combination thereof.

42. Method, according to claim 31, CHARACTERIZED in that it further comprises: Obtaining confirmation from the institution's server of the execution of the disbursements; and Sending, to the institution's server and based on the confirmation, a request to close the financial account. Petition 870250086483, dated 09 / 24 / 2025, pp. 167 / 215 13 / 28 43. Method according to claim 31, CHARACTERIZED in that it further comprises: Receiving, from a settlement server, a request to verify the first user, the request including information about the first user associated with the first user; Sending, to the institution's server, the information about the first user; Receiving, from the institution's server and based on the information about the first user, a verification response indicating that the first user has been verified; and Sending, to the settlement server, an indicator showing that the first user has been verified.

44. A method according to claim 31, characterized in that it further comprises: Receiving, from a settlement server, a status request associated with the first contract; Accessing the database to obtain input information based on the first entry; Generating status information based on the input information, wherein the status information indicates an amount due associated with the first contract, one or more distribution values, one or more fee values, or a combination thereof; and Sending the status information to the settlement server.

45. System CHARACTERIZED by the fact that it comprises: A settlement server configured to: Obtain first contract data associated with a first contract between a first user and a second user; Verify if the first contract data associated with the first contract are Petition 870250086483, dated 09 / 24 / 2025, page 1.168 / 215 14 / 28 valid based on: A first entry received from a first device associated with the first user; A second entry received from a second device associated with the second user; or a combination thereof; Based on verification of the first contract, send a request to create, on an institutional server, a financial account associated with the first contract; and Store, in a database, entry information from the first entry associated with the first contract, where the entry information from the first entry indicates the first user, the second user, the data from the first contract, the financial account, or a combination thereof.

46. ​​System, according to claim 45, CHARACTERIZED in that it further comprises: A central server, communicatively coupled to the settlement server via a network, wherein the central server is configured to: Identify the financial account on the institution's server, wherein the first user is a beneficiary of the financial account, and wherein an entity associated with the central server has agency over the financial account; Identify a transfer made to the financial account; After identifying the transfer, send a request to the institution's server to perform one or more distributions of the financial account, wherein the distributions are determined based on a first entry in a database, wherein the first entry is associated with the first contract and indicates the first user, the second user, the data of the first contract, the financial account, or a combination thereof; and Petition 870250086483, dated 09 / 24 / 2025, p.169 / 215 15 / 28 Send a notification indicating a first distribution to a first account associated with the first user.

47. System, according to claim 45, CHARACTERIZED in that it also includes the institution's server.

48. System according to claim 47, CHARACTERIZED in that it further includes the database.

49. Server CHARACTERIZED by the fact that it comprises: a memory coupled to at least one processor, with the memory storing processor-readable instructions; and at least one processor coupled to the memory, configured to: obtain first-contract data associated with a first contract between a first user and a second user; verify whether the first-contract data associated with the first contract is valid based on: a first input received from a first device associated with the first user; a second input received from a second device associated with the second user; or a combination thereof; after verifying the first agreement, send a request to create, on an institution's server, a financial account associated with the first agreement;and store, in a database, input information from the first entry associated with the first agreement, where the information from the first entry indicates the first user, the second user, the data from the first agreement, the financial account, or a combination of these elements.

50. Server, according to claim 49, CHARACTERIZED in that: Petition 870250086483, dated 09 / 24 / 2025, p. 170 / 215 16 / 28 At least part of the first entry is immutable; The first agreement is additionally between the first user, the second user, and an entity associated with the institution's server; The first entry includes a first digital signature and the second entry includes a second digital signature; To obtain the data from the first agreement, the processor is additionally configured to receive the data from the first agreement from the first device or generate the data from the first agreement; The memory includes the database; or A combination of these elements.

51. Server, according to claim 49, CHARACTERIZED in that the processor is additionally configured to: generate a smart contract based on the first agreement, wherein: the database includes a blockchain ledger that stores the first entry, and the first entry includes the smart contract.

52. Server, according to claim 49, CHARACTERIZED by the fact that the processor is further configured to: after verifying the first contract, initiate the formation of a second contract associated with the use of the financial account in association with the first contract, the second contract being between the first user, the second user and an entity associated with the institution's server; verify if the second contract is complete; and store, in the database, the data of the second contract in the first entry, where the data of the second contract are associated with the second contract in the first entry. Petition 870250086483, dated 09 / 24 / 2025, pp. 171 / 215 17 / 28 53. Server, according to claim 52, CHARACTERIZED in that the processor is further configured to: generate a first version of the second contract based on the first contract, the financial account, or a combination thereof; and send, to each of the first users, the second user, and the entity, a request to sign the second contract, where the verified second contract is a second version of the second contract that is signed by each of the first users, the second user, and the entity.

54. Server, according to claim 52, CHARACTERIZED by the fact that, prior to verification of the second contract, the financial account has a reserved status.

55. Server, according to claim 54, CHARACTERIZED by the fact that the processor is further configured to, after verification of the second contract, send a status change request to the institution's server to change the financial account from reserved status to active status.

56. Server, according to claim 49, CHARACTERIZED in that the processor is further configured to: receive, from the first device associated with the first user, information from the first user associated with the first user, wherein the information from the first user indicates: a bank account associated with the first user, and a name of the first user, a company associated with the first user, a date of birth of the first user, a nationality of the first user, a government identification number associated with the first user, an email address associated with the first user, a telephone number associated with the first user, a fax number associated with the first user, an address Petition 870250086483, dated 09 / 24 / 2025, p.172 / 215 18 / 28 associated with the first user, or a combination of these elements; and store, in the database, information from the first user's bank account indicating the first user's bank account, the bank name, the account type, the account holder's name, or a combination of these elements, and where the first contract indicates that the second user owes the first user a payment amount.

57. Server, according to claim 49, CHARACTERIZED in that the processor is further configured to: receive, from the second device associated with the second user, information from the second user associated with the second user, wherein the information from the second user indicates a second bank account associated with the second user; and store, in the database, information from the second bank account indicating the second bank account, and wherein the first contract indicates that the second user owes the first user a payment amount.

58. Server, according to claim 57, CHARACTERIZED in that the processor is configured to: receive, from a third device associated with a third user, a payment request associated with the first contract, where the payment request includes document data, a requested amount, or a combination thereof; send, to a device of the first user associated with the first user, an approval request based on the payment request; receive, from the first user's device, an approval message in response to the approval request; and update the first entry to indicate that the third user should receive a portion of the payment amount paid by the second user according to Petition 870250086483, dated 09 / 24 / 2025, pp. 173 / 215 19 / 28 first contract.

59. Server, according to claim 58, CHARACTERIZED in that the processor is further configured to: receive, from the third-party device associated with the third-party user, information from the third-party user associated with the third-party user, wherein the information from the third-party user indicates a third-party bank account associated with the third-party user; and store, in the database, information from the third-party bank account that indicates the third-party bank account, and wherein the document data is associated with an assignment contract.

60. Server, according to claim 58, CHARACTERIZED in that the processor is further configured to: obtain, from the second device associated with the second user, data of the third contract associated with a third contract between the second user and another user; and verify, based on an input received from a third device associated with the third user, that the data of the third contract associated with the third contract is valid, wherein the activation of the third contract is triggered based on an event associated with the first contract.

61. Server, according to claim 60, CHARACTERIZED in that the processor is configured to store, in the first database entry, the data of the third contract.

62. Server, according to claim 60, CHARACTERIZED in that the processor is configured to: store, in the database, information from the second entry in a second entry associated with the third agreement, where the information from the second entry indicates the second user, the third user, the data from the first agreement, the data from the third agreement, or a combination thereof, and where the second entry is linked to the first entry in the database.

63. Server, according to claim 49, CHARACTERIZED in that the processor is further configured to: identify the financial account on the institution's server, the financial account associated with the first contract between the first user and the second user; determine, based on the first entry in the database, one or more disbursements from the financial account, the one or more disbursements including a first disbursement to a first account associated with the first user, where the first entry is associated with the first contract; send a request to the institution's server to carry out the one or more disbursements; and send a notification indicating the first disbursement to the first account associated with the first user.

64. Server, according to claim 63, CHARACTERIZED in that the processor is further configured to: receive, from the institution's server, a transfer request notification associated with the second user; and receive, from the institution's server, a transfer completion notification indicating the completion of a transfer to the financial account based on the transfer request.

65. Server, according to claim 64, CHARACTERIZED by the fact that: The notification of completion of the transfer is received before the delivery, from the first user to the second user, of an object associated with the first agreement; and The first distribution(s) are determined based on Petition 870250086483, dated 09 / 24 / 2025, page 175 / 215 21 / 28 identification of a status change of the object indicated by the first entry.

66. Server, according to claim 63, CHARACTERIZED in that the processor is further configured to receive, from the first device or the second device, invoice data associated with the first agreement.

67. Server, according to claim 49, CHARACTERIZED in that the processor is further configured to: receive, from the institution's server, an identifier associated with the financial account; and send the identifier to the second device associated with the second user; or store the identifier in the first input.

68. Server, according to claim 67, CHARACTERIZED in that the indicator includes a financial account number, a routing number, or a combination thereof.

69. Server, according to claim 67, CHARACTERIZED in that the identifier includes a Quick Response (QR) code.

70. Server, according to claim 49, CHARACTERIZED in that the request to create the financial account associated with the first contract is sent to the institution's server via a central server.

71. Server, according to claim 70, CHARACTERIZED in that the processor is further configured to: send a request to the central server to create the financial account associated with the first agreement; and receive, from the central server or the institution's server, an identifier associated with the financial account.

72. Server, according to claim 70, CHARACTERIZED by the fact that the processor is also configured to: Petition 870250086483, dated 09 / 24 / 2025, page 176 / 215 22 / 28 receive, from the central server, a notification indicating a first payment of the financial account for a first account associated with the first user.

73. Server, according to claim 49, CHARACTERIZED in that the processor is further configured to: send to a central server a first indicator that shows the first user's information associated with the first user; send to the central server a request to create the financial account associated with the first contract; receive from the central server an identifier associated with the financial account; and send the identifier to a device associated with the second user, to the database for storage in the first entry, or a combination of both.

74. Server, according to claim 49, CHARACTERIZED in that the processor is further configured to: send a request to a central server to verify the first user, the request including the first user's information associated with the first user; and receive from the central server an indicator that shows that the first user has been verified.

75. Server, according to claim 49, CHARACTERIZED in that the processor is further configured to: receive, from the first device or the second device, a status request associated with the first agreement; access the database to obtain the first entry information based on the first entry; obtain status information based on the first entry information, Petition 870250086483, dated 09 / 24 / 2025, pp. 177 / 215 23 / 28, wherein the status information indicates an amount due associated with the first contract, one or more distribution amounts, one or more fee amounts, or a combination thereof; and send the status information to the first device or the second device.

76. Server, according to claim 75, CHARACTERIZED in that the processor is further configured to: in response to receiving a status request, send a status information request to a central server; and receive the status information from the central server in response to the status information request.

77. Server, according to claim 49, CHARACTERIZED in that the processor is further configured to: generate, based on one or more database entries, historical data associated with the first user; determine, based on the historical data, user information associated with the first user, or a combination thereof, one or more metrics associated with the first user; for at least one service in a set of services, determine a respective rate based on the metrics associated with the first user; and send, to the first device, an indication of at least one service and the respective rate.

78. Server, according to claim 49, CHARACTERIZED in that the processor is further configured to: receive sensor data associated with an object to be provided from the first user to the second user according to the first contract; store, based on the sensor data, a status on the first entry; and Petition 870250086483, dated 09 / 24 / 2025, p. 178 / 215 24 / 28 determine, based on the status, the sensor data, or a combination thereof, whether to indicate one or more distributions associated with the financial account.

79. Server CHARACTERIZED by the fact that it comprises: a memory coupled to at least one processor, the memory storing instructions readable by the processor; and at least one processor coupled to the memory, the processor configured to: identify a financial account on an institutional server, the financial account associated with a first contract between a first user and a second user, where the first user is the beneficiary of the financial account and an entity associated with the central server has authority over the financial account; identify a transfer made to the financial account;Based on the identification of the transfer, send a request to the institution's server to perform one or more distributions of the financial account, with the one or more distributions being determined based on an initial entry in a database, where the initial entry is associated with the first contract and indicates the first user, the second user, the data of the first contract associated with the first user, the financial account, or a combination thereof; and send a notification indicating an initial distribution to an initial account associated with the first user.

80. Server, according to claim 79, CHARACTERIZED by the fact that the processor is further configured to: receive, from a device associated with the second user, a transfer request; and initiate, based on the transfer request, the transfer to the financial account. Petition 870250086483, dated 09 / 24 / 2025, pp. 179 / 215 25 / 28 81. Server, according to claim 79, CHARACTERIZED in that the processor is further configured to: Receive, from a clearing server, an indicator that shows one or more disbursements, where the sending of the request to the institution's server is carried out in response to the receipt of the indicator.

82. Server, according to claim 79, CHARACTERIZED in that: the first entry includes input information associated with the first agreement; the input information indicates one or more payment amounts, one or more fees, or a combination thereof; and at least part of the input information is immutable.

83. Server, according to claim 82, CHARACTERIZED in that the processor is additionally configured to: access the database to obtain at least the portion of the input information, and where the transfer is performed from a second account associated with the second user to the financial account.

84. Server, according to claim 83, CHARACTERIZED in that the processor is further configured to: identify, based on input information, a third user associated with the first agreement, and where one or more distributions include a second distribution to a third account associated with the third user.

85. Server, according to claim 83, CHARACTERIZED in that the processor is additionally configured to: determine, based on input information, a rate associated with Petition 870250086483, dated 09 / 24 / 2025, page 180 / 215 26 / 28 first agreement, and where one or more distributions include a third distribution to a fourth account associated with an entity associated with a clearing server, the central server or the institution's server, and where the third distribution is based on the rate.

86. Server, according to claim 85, CHARACTERIZED in that the fee includes a service fee, a regulatory fee, or a combination thereof.

87. Server, according to claim 79, CHARACTERIZED in that: the database includes a blockchain-based ledger that stores the first entry, and the first entry includes a smart contract based on the first agreement.

88. Server, according to claim 79, CHARACTERIZED in that the processor is configured to: receive, from a clearing server, a first indicator that shows the first user's information associated with the first user; receive, from the clearing server, a request to create the financial account associated with the first agreement; send, to the institution's server, a request to create the account; receive, from the institution's server, an identifier associated with the financial account; and send, to the clearing server, a device associated with the second user, the database for storage in the first entry, or a combination thereof, the identifier.

89. Server, according to claim 88, CHARACTERIZED by the fact that: Petition 870250086483, dated 09 / 24 / 2025, pp. 181 / 215 27 / 28 the account creation request is sent through an application programming interface (API) of the institution's server; and the identifier associated with the financial account includes an account number, a routing number, the bank name, the beneficiary name, a quick response (QR) code, or a combination thereof.

90. Server, according to claim 79, CHARACTERIZED in that the processor is further configured to: obtain, from the institution's server, confirmation of the completion of one or more disbursements; and send, to the institution's server and based on the confirmation, a request to close the financial account.

91. Server, according to claim 79, CHARACTERIZED in that the processor is further configured to: receive, from the clearing server, a request to verify the first user, wherein the request includes information of the first user associated with the first user; send, to the institution's server, the information of the first user; receive, from the institution's server and based on the information of the first user, a verification response indicating that the first user is verified; and send, to the clearing server, an indicator indicating that the first user is verified.

92. Server, according to claim 79, CHARACTERIZED in that the processor is further configured to: receive, from a verification server, a status request associated with the first agreement; Petition 870250086483, dated 09 / 24 / 2025, pp. 182 / 215 28 / 28 access the database to obtain entry information based on the first entry; generate status information based on the entry information, where the status information indicates an amount due associated with the first agreement, one or more distribution values, one or more fee values, or a combination thereof; and send the status information to the verification server.

Images