No, each Organization operates independently and does not communicate with others.

No, each license is tied to a specific Organization. If you need support for multiple Organizations, you must acquire separate licenses for each. The same rule applies to Plugins.

Yes, an Organization can have more than one Plugin associated with it.

Yes, an Organization can manage multiple Ledgers.

While you can create a Parent Organization and a Child Organization, each Organization maintains its own Ledger, operating independently. Since transactions cannot move value directly between ledgers, you need to orchestrate the transfer with the following steps:

1. Initiate a transaction in the source ledger, transferring the amount from the original account (source) to the asset’s external account (distribute). This removes the value from the original ledger.

2. Create a second transaction in the destination ledger, where the source is now the asset’s external account, and the amount is allocated to the receiving account (distribute).

This approach ensures seamless and controlled value transfers between ledgers across different organizations.

No, Ledgers do not communicate directly. Transfers between Ledgers require orchestration.

You must orchestrate the process and transfer the amount to an External Account. Typically, this involves two steps:

1. Ledger A -> External Account
2. External Account -> Ledger B

No, a single Ledger can support multiple Plugins. For example, a Ledger can handle both Exchange and Pix Plugins simultaneously.

No, each Asset is linked to a single Account. However, each Asset will also be linked to an External Account that is automatically created when the Asset is created.

Midaz is built for flexibility, supporting a wide range of Assets:

• currency: Traditional fiat currencies like BRL, USD, and EUR.
• crypto: Digital assets such as BTC, ETH, and other cryptocurrencies.
• commodities: Tangible goods like gold, soybean, and oil.
• others: Custom Assets, including loyalty points and tokenized securities.

A Portfolio groups accounts that belong to the same entity (CPF/CNPJ). For example, if a single CPF has two different segment_id values, it will also have two corresponding account_id values. To simplify retrieval, a Portfolio is created for that CPF, linking both accounts under a single structure.

This ensures easier access and management of related accounts.

No, each Account is associated with a single Asset, and this association cannot be changed.

An External Account is used to receive funds from outside the Ledger, effectively bringing money into the system.

Midaz automatically sets up an External Account when you create an Asset, ensuring seamless backing for all transactions flowing in and out of the Ledger.

No. Each account (account_id) can be linked to only one Segment (segment_id).

A Transaction must have at least two Operations. For example, transferring R$ 100 from Account A to Account B consists of:

• Operation 1: Debit R$ 100 from Account A
• Operation 2: Credit R$ 100 to Account B

Currently, the Chart-of-Account field is fully open, meaning users are responsible for correctly inputting values. In the future, a Plugin will be available to manage this process more efficiently.

Currently, the Entity (entity_id) is open for external IDs, with no validation enforced by Midaz. This means you can use the IDs that already exist in your database, seamlessly integrating them into your system.

Plugins are technologies integrated into the Midaz ledger, designed to simplify process integration and orchestration. They provide abstractions that allow clients to focus on their business model without needing to build or manage essential system logic that falls outside their domain.

No. Plugins are designed to operate exclusively with Midaz. They provide specific abstractions and orchestrate transactions based on the ledger’s structure, ensuring precise and efficient integration.

Once contracted, plugins are provided and installed within the client’s infrastructure (on-premise model), alongside their Midaz instance. Applications connect according to the specific functionality of each plugin.

Lerian provides two types of plugins, categorized by their origin:

• Native Plugins
  Developed and fully integrated into the Midaz ledger by Lerian, these plugins ensure complete support and seamless integration with the platform.

• Marketplace Plugins
  Created by Lerian’s partners to serve specific market niches, these plugins are available in the marketplace. Lerian facilitates their integration into Midaz, but their offering and support are managed directly by the respective partners.