What is Lerian SISBAJUD?

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). Courts use it to order an institution to block, release, transfer, and report a defendant’s funds. Lerian SISBAJUD has two components:

Lerian SISBAJUD Mensageria (the Mensageria) receives the judicial orders as files through Lerian STA. It keeps the order record. It writes the response files and submits them to BACEN through Lerian STA. The Mensageria calls no ledger and holds no ledger credential.
Lerian SISBAJUD executor (the executor) runs the orders on the client’s Midaz ledger: blocks, unblocks, and information requests.

How Lerian SISBAJUD works shows the path of an order through both components.

What Lerian SISBAJUD does and does not do

It receives orders as files. A remittance file reaches the Mensageria as a Lerian STA event. The Mensageria has no HTTP operation that accepts an order, and it does not poll for files.
It separates the regulatory side from the ledger side. The Mensageria keeps the files and the order record. The executor makes the ledger writes.
It does not start work when a deadline time arrives. Response files are generated at configured intervals. Set those intervals so that each cycle ends inside the BACEN response window.
It runs one tenant per executor process. The executor does not start when its tenant list holds more than one tenant.

Who it serves

Lerian SISBAJUD serves banks and financial institutions that must honour judicial asset orders under the CNJ/BACEN SISBAJUD regime. One Mensageria serves many institutions. It reads the CNPJ root from the header of each file and matches it to an institution registered on the Mensageria. Each institution has its own orders, files, and encryption keys.

Glossary

Term	Meaning
Lerian SISBAJUD	Lerian’s participant-institution integration for judicial asset blocking under the CNJ/BACEN SISBAJUD system.
Mensageria	The Lerian SISBAJUD component that receives the order files, keeps the order record, and sends the response files.
Executor	The Lerian SISBAJUD component that runs the orders on the Midaz ledger.
Execution notice	The event `judicial_order.execution_requested`. The Mensageria publishes it when it releases an order to the executor.
Human decision	An order that the executor hands to an operator instead of finishing it alone.
Judicial block (bloqueio)	A court-ordered hold on a defendant’s funds.
Unblock (desbloqueio)	A court-ordered release of held funds.
Permanent block (bloqueio permanente)	A block order that the court marks as permanent. In the 2026 layout, the indicator `P` or `D` marks it. Colloquially, the teimosinha.
Remittance file	The fixed-width file that the Judiciary and BACEN send with the judicial orders.
Response / return file	The fixed-width file that the institution sends back with the order outcomes.
Block account	The Midaz account that holds the funds of one block order. Its alias is `@block_sisbajud_` followed by the 32 hexadecimal digits of the order ID.
Envelope encryption (KEK/DEK)	A data key (DEK) for each operation, wrapped by the institution’s key-encryption key (KEK).
Searchable tokenization (blind index)	A per-institution token that supports equality lookup.
Audit trail	An audit log in which each record carries a message authentication code (MAC) under an institution key. The audit verification operation checks these codes.

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

​What Lerian SISBAJUD does and does not do

​Who it serves

​Glossary

What Lerian SISBAJUD does and does not do

Who it serves

Glossary