A
Account
The fundamental unit of value storage in a ledger. An account holds a balance denominated in a specific asset (e.g., BRL, USD). Accounts can represent account holders’ accounts, internal settlement accounts, fee collection accounts, or any other container for tracking value.Account Type
A classification that defines the nature and purpose of an account, such as checking, savings, escrow, or settlement. Account types enable proper transaction routing and consistent business rules across account categories.Asset
A unit of value tracked in the ledger. Assets can be traditional currencies (BRL, USD, EUR), digital currencies (BTC, ETH), or custom units like loyalty points or academic credits. Every account links to exactly one asset.Atomic (Atomicity)
A property of transactions where all operations either succeed together or fail together. There is no partial execution. If a transaction involves three operations (a debit, a credit, and a fee), either all three happen or none do. This prevents incomplete financial events.Audit trail
A chronological record of every action and transaction in the system. Audit trails are immutable. Once recorded, an audit trail cannot change or be deleted. Regulatory compliance and dispute resolution require this.B
Balance
The current amount of an asset held in an account. Midaz tracks the available amount (ready for immediate use) and the on hold amount (reserved for pending transactions).Blast radius
The scope of impact if a failure, misconfiguration, or security incident occurs. In multi-tenancy contexts, blast radius counts the tenants that suffer when something goes wrong in one tenant’s scope. See also: Tenant isolation.BYOC (Bring Your Own Cloud)
A deployment model where you run Lerian software on your own infrastructure, whether public cloud (AWS, GCP, Azure), private cloud, or on-premises. This gives you full control over data residency, security, and scaling. See also: SaaS.C
CEL (Common Expression Language)
A lightweight, type-safe expression language that Tracer uses for writing business rules. CEL lets analysts and compliance teams define validation logic without writing application code or requiring deployments. One example: “if transaction amount exceeds 10,000 and account type is personal, flag for review”.Core banking
A complete banking platform that combines a ledger foundation with the capabilities required to operate financial products. Those capabilities are accounts and balances, value movement, account holder identity, reporting, governance, connectivity, and auditability. A ledger is foundational, but it is not the whole core banking platform.Child account
A sub-account created under a parent account, typically used for budgeting or organizational purposes. For example, an account holder’s savings account might have child accounts for “Vacation Fund” and “Emergency Fund.” Each child account tracks its own balance.D
Double-entry accounting
An accounting principle where the ledger records every financial movement as at least two operations: a debit from one account and a credit to another. This ensures the system always balances. The total of all debits equals the total of all credits. Midaz enforces double-entry automatically on every transaction.DSL (Domain-Specific Language)
A simplified programming language designed for a specific domain. In Flowker, the DSL lets teams define workflow steps, conditions, and integrations using a structured format, without writing general-purpose code.E
ERP (Enterprise Resource Planning)
A business management software system (such as SAP, Oracle, or NetSuite) that integrates core processes like accounting, procurement, and inventory. ERPs are common data sources for reconciliation with Matcher.External account
A special account in Midaz that represents value entering or leaving the system from outside. Its alias is@external/ followed by the asset code, for example @external/BRL. External accounts are boundaries between your ledger and the outside world.
F
Fail closed
A safety posture where a system denies access by default when it cannot verify a required condition, rather than allowing access and risking a breach. In Lerian multi-tenancy, tenant resolution is fail-closed. When the JWT does not identify the tenant, or when the tenant configuration does not load, the system rejects the request. The request never falls back to a default or shared tenant. See also: Tenant isolation, Multi-tenancy.H
Helm Chart
A pre-configured deployment package for Kubernetes. Helm Charts contain all the instructions needed to install, configure, and upgrade software in a Kubernetes cluster. Lerian provides Helm Charts for deploying products in BYOC (self-hosted) environments.I
Idempotency
The property that an operation produces the same result whether executed once or multiple times. In financial systems, this prevents duplicate transactions. If you accidentally send a payment request twice, idempotency ensures the money only moves once.Immutable (Immutability)
A property meaning “cannot change or be deleted after creation.” This guarantees data integrity for compliance and auditing.K
Kubernetes
A platform for running and managing software applications at scale across multiple servers. Kubernetes automates deployment, scaling, and recovery, so applications stay available even when individual servers fail.L
Ledger
The core financial book that records all transactions, balances, and operations for an organization. Think of it as the single source of truth for a business unit’s finances. An organization can have multiple ledgers for different purposes (e.g., retail operations, treasury).M
Metadata
Additional information attached to entities like accounts, transactions, or organizations. Metadata takes the form of key-value pairs. It does not affect ledger logic but enriches records for reporting and integration.Multi-tenancy
An operating model where one deployment serves independent institution contexts (called tenants) with product-specific request scoping and storage isolation. Lerian Cloud operates multi-tenant. See also: Tenant, Tenant isolation.O
Onboarding domain
The part of Midaz responsible for structuring your financial ecosystem: creating organizations, ledgers, assets, accounts, portfolios, and segments. This is the “setup” phase before any transactions occur.Operation
The atomic unit of movement in the ledger: a single debit or credit. Every transaction consists of one or more operations, which gives precise traceability for compliance and reporting.Operation Route
A reusable template that defines the rules for one “leg” of a financial transaction. It specifies which accounts participate, in what direction (source/destination), and under what accounting annotation.Organization
The top-level business entity in Midaz, typically a bank, fintech, or subsidiary. Each organization holds its own ledgers.P
Pix
Brazil’s instant payment system, operated by the Central Bank of Brazil (BACEN). Pix enables real-time transfers 24/7 between individuals, businesses, and government entities.Portfolio
A grouping of accounts belonging to the same account holder, business unit, or purpose. For example, a single account holder may hold checking, savings, and investment accounts across different currencies. A portfolio ties them together for a unified view.Plugin
An optional extension that adds functionality to a specific Lerian product. Examples include Pix (instant payments), TED (bank transfers), and Payments (boletos and bill payment). All available plugins extend Midaz.R
Reconciliation
The process of comparing two sets of records (for example, your internal ledger against bank statements) to verify they match. Matcher automates this process by applying matching rules and flagging discrepancies.S
Lerian Cloud (SaaS)
Lerian’s fully managed deployment model. Lerian operates the licensed platform modules and underlying infrastructure. Institutions use the supported product APIs and configuration surfaces. See also: BYOC.Segment
A classification applied to accounts that share characteristics, like account holder tiers (VIP, Student, Business) or regional divisions. Segments enable differentiated rules, pricing, and benefits across your account holders.Settlement
The process of finalizing a financial transaction, transferring the actual funds between institutions. Settlement accounts in Midaz are clearing points. Money waits there before it moves to its final destination (e.g., via Pix or TED to the central bank).Streaming Hub
Lerian’s event-delivery service. It sits at the edge between the platform’s internal event stream and the systems you run outside it. It delivers each event you care about to a destination you own: a webhook, a cloud queue, or a cursor you pull.T
Tenant
A logically isolated institution context in a multi-tenant deployment. The supported product service defines its data model, authentication claims, routing, and backing resources. Do not assume one product’s tenant model applies to another. See also: Multi-tenancy, Tenant isolation.Tenant isolation
The controls that prevent another tenant from using one tenant’s supported product service, data, configuration, and operations. Authentication and routing controls remain product-specific. See also: Multi-tenancy, Tenant.Terraform
An infrastructure automation tool that provisions and manages cloud resources (servers, databases, networks, security groups) through declarative configuration files. Lerian provides Terraform templates for setting up BYOC infrastructure on AWS, GCP, or Azure.TED (Transferência Eletrônica Disponível)
A Brazilian electronic bank transfer system for high-value or same-day transfers between financial institutions. Unlike Pix, TED operates only during business hours. In the Lerian ecosystem, the TED plugin connects Midaz to the TED network.Transaction
A movement of value between accounts. Transactions can involve multiple operations (debits and credits), and Midaz processes them atomically. Either all operations succeed, or none do. This ensures no partial financial events occur.Transaction domain
The part of Midaz responsible for executing financial movements: processing transactions, updating balances, and maintaining audit trails.Accounting Route (Transaction Route)
A complete transaction blueprint composed of multiple Operation Routes. For example, a “Pix Transfer” route defines all the debits and credits involved, so every transaction of that type complies with double-entry accounting. Called Accounting Route in the Lerian Console and product docs. Exposed astransactionRoute in the API.