What is Lerian SISBAJUD?

Lerian SISBAJUD is your CNJ/BACEN judicial asset-blocking integration. It receives court orders by file and runs blocks and unblocks on the Midaz ledger.

Lerian SISBAJUD connects a financial institution to SISBAJUD (Sistema de Busca de Ativos do Poder Judiciário), the Brazilian judicial asset-search and blocking system. The CNJ runs it with the Banco Central (BACEN). It lets each institution comply with court orders that block, release, and report on a defendant’s financial assets.

Lerian SISBAJUD receives each judicial order as a fixed-layout file. Courts issue the orders, and BACEN delivers them through its STA file-exchange channel. The service runs the orders against the client’s Midaz ledger and sends response files back to BACEN. No order enters through the API.

One deployment serves many institutions. Lerian SISBAJUD encrypts the personal data it keeps in its own database and bucket.

What Lerian SISBAJUD does and does not do

---

• It is the judicial-order fulfilment boundary between the Judiciary and the institution’s ledger. It receives court orders by file and finds the affected accounts. It runs the block or unblock on the Midaz ledger and reports the outcomes to BACEN.
• It does not accept court orders through its API. Court orders enter only as remittance files through BACEN’s STA channel. POST /remittance-files/notifications is an operational endpoint. It synchronously receives and parses a remittance object already delivered through that channel. It is not an order-entry endpoint. The remaining HTTP surface is administrative and observational.
• It freezes funds without deleting them. A block execution can create one or more per-account block holdings, and an unblock can release held amounts across those holdings. Every ledger transaction accepted by Midaz must be balanced. This does not mean that an entire judicial order is one double-entry transaction, or that an individual block or unblock is one.
• It scopes data by institution. One deployment serves many institutions. Each institution has its own orders, files, credentials, and encryption keys. In multi-tenant mode, each tenant also has its own database.

Who it serves

---

Lerian SISBAJUD serves banks and financial institutions. Each one must honour judicial asset orders under the CNJ/BACEN SISBAJUD regime. Each institution keeps its own credentials, encrypted data, and ledger connection.

Glossary

---

Term	Meaning
Lerian SISBAJUD	Lerian’s participant-institution integration for judicial asset blocking under the CNJ/BACEN SISBAJUD system.
Judicial block (bloqueio)	A court-ordered hold on a defendant’s funds, recorded through ledger block holdings.
Unblock (desbloqueio)	A court-ordered release of previously held funds.
Permanent block (bloqueio permanente)	A standing order that Lerian SISBAJUD re-attempts on each cycle, capturing funds that arrive later. Colloquially, the teimosinha.
Remittance file	The fixed-width file the Judiciary and BACEN send, carrying the judicial orders.
Response / return file	The fixed-width file the institution sends back with order outcomes.
Block account / holding	A ledger holding for blocked funds; an execution can have multiple per-account block holdings.
Envelope encryption (KEK/DEK)	A per-record data key (DEK) sealed under the institution’s key-encryption key (KEK).
Searchable tokenization (blind index)	A one-way index that can support exact-match indexing without plaintext storage. It is not an account-discovery substitute: for a CRM query, SISBAJUD decrypts the CPF/CNPJ.
Audit trail	An append-only log with an authentication code on each entry. An operator verifies a range of entries without decrypting payloads.
Crypto-erasure (LGPD)	Honouring an erasure request by neutralizing the record’s data key (DEK) so its ciphertext becomes irrecoverable.

For how Lerian SISBAJUD sits alongside the other native rails and the partner interfaces, see Native messaging and partner interfaces.