Skip to main content
Lerian SCR is a REST facade over BACEN’s wsscr2n web service, the SCR3 consultation channel. SCR is the Sistema de Informações de Crédito, the BACEN credit information system. A consumer authenticates with a machine-to-machine token and asks Lerian SCR for a client’s consolidated credit position. The service consults wsscr2n for the institution, decodes the result, audits the query, and returns it. Each consultation writes an audit row. The audit write is fail-closed: a failed audit write fails the consultation, and the consumer gets no result. A result cache, a per-institution concurrency limit, single-flight coalescing of identical queries, and a per-institution circuit breaker protect the channel.

​
What Lerian SCR does and does not do

Lerian SCR does:
  • Call the wsscr2n channel. It issues an HTTPS GET to BACEN’s /wsscr2n/cliente/resumo operation with HTTP Basic authentication, over TLS 1.2 or later.
  • Decode the coded fields. BACEN answers with codes. Lerian SCR resolves each code against the SCR annex tables and returns a { code, description } pair.
  • Audit every query. One consultation writes one audit row. Its personal data carries AES-256-GCM encryption at rest and an HMAC-SHA256 blind index for search.
  • Derive the institution from the token. A request body, header, or path parameter never sets it.
  • Protect the tariffed channel. A result cache, a two-connection cap per institution, single-flight coalescing, and a per-institution circuit breaker sit in front of BACEN.
Lerian SCR does not:
  • Use mTLS. The channel authenticates the server only and puts HTTP Basic on top. Lerian SCR sends no client certificate.
  • Log the borrower document. No log line, span, or error message carries it.
  • Hold the consent trail. The request declares the holder’s authorization under LC 105/2001. The consent record itself stays with the institution.
  • Create its database schema. An operator applies the schema out of band before the service starts.

​
Who it serves

Lerian SCR serves the internal consumers of a financial institution, such as a scoring consumer that needs a borrower’s consolidated credit position. One deployment serves a single institution, or many institutions at once when multi-tenancy is on.

​
Glossary

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