Skip to main content
Lerian SISBAJUD is the participant-institution integration to SISBAJUD (Sistema de Busca de Ativos do Poder Judiciário), the Brazilian judicial asset-search and blocking system operated by the CNJ with the Banco Central (BACEN). It lets a financial institution comply, per institution, with judicial orders that freeze, release, and account for a defendant’s financial assets. Lerian SISBAJUD receives judicial orders — issued by the Judiciary and delivered through BACEN’s file-exchange channel — fulfils each block or unblock against the client’s Midaz ledger, and transmits result files back. Every order arrives as a file: the integration submits no orders through its API. It is multi-tenant, with per-institution isolation, and every fiscal identifier and payload it holds is encrypted at rest.

​
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, resolves the affected accounts, executes the block or unblock on the Midaz ledger, and reports each outcome back to BACEN.
  • It does not accept orders over its API. Orders enter only as remittance files delivered through BACEN’s file-exchange channel; the HTTP surface is administrative and observational, never an order-entry path.
  • It freezes funds by moving them, not deleting them. A block moves the court-ordered amount from the customer account into a dedicated, per-order block account on the ledger — a balanced double-entry movement — where the funds are held unavailable until an unblock releases them.
  • It is multi-tenant from the ground up: one deployment serves many institutions, each isolated so that institution_id equals the tenant and no order or file crosses an institution boundary.

​
Who it serves

Lerian SISBAJUD serves banks and financial institutions that must honour judicial asset orders under the CNJ/BACEN SISBAJUD regime. Each institution is a tenant with its own credentials, its own encrypted data, and its own ledger connection, so a single deployment can serve many institutions at once without any of them seeing another’s orders.

​
Glossary

TermMeaning
Lerian SISBAJUDLerian’s participant-institution integration for judicial asset blocking under the CNJ/BACEN SISBAJUD system.
Judicial block (bloqueio)A court-ordered freeze of a defendant’s funds into a dedicated block account.
Unblock (desbloqueio)The release of previously blocked funds back to the customer account.
Permanent block (bloqueio permanente / reiteração)A standing order that re-attempts blocking daily until its deadline, capturing funds that arrive later — colloquially the teimosinha.
Remittance fileThe fixed-width file the Judiciary and BACEN send, carrying the judicial orders.
Response / return fileThe fixed-width file the institution sends back with syntactic-validation and fulfilment results.
Block accountA dedicated ledger account holding the funds frozen for one judicial order.
Envelope encryption (KEK/DEK)A per-record data key sealed under a per-institution master key, so personal data at rest is never plaintext.
Searchable tokenization (blind index)A one-way token that enables exact-match search on fiscal identifiers without decryption or plaintext storage.
Tamper-evident audit trailAn append-only, cryptographically protected record of every state change, verifiable without decrypting payloads.
Crypto-erasure (LGPD)Honouring an erasure request by destroying the record’s key so its ciphertext becomes irrecoverable.
For how Lerian SISBAJUD sits alongside the other native rails and the provider interfaces, see Native Messaging.