What it does — and does not — do
- It is the integration boundary between the platform’s credit engine and Dataprev’s Crédito do Trabalhador. It fetches margin, registers signed contracts, discovers loan-auction requests, and reconciles settlement. It reports each outcome back as a business fact.
- It holds no credit logic. The credit engine decides whether to lend, at what rate, and to whom. This rail runs the Dataprev-facing steps and relays the rail’s own result codes. It does not decide them.
- It owns no money movement. It makes no direct ledger postings. The facts it emits let downstream systems originate loans and reconcile settlement in their own records.
- It is sink-agnostic. It emits its results to a transactional outbox and owns no per-destination routing. A downstream streaming hub decides which system receives each fact.
- It is multi-tenant from the ground up. Each financial institution is a tenant with its own credentials and isolated data.
Who it serves
Lerian Consignado — Dataprev serves banks and financial institutions that originate payroll loans under the Crédito do Trabalhador (CLT) program. Each institution is a tenant with its own ICP-Brasil certificate, OAuth2 credentials, and Dataprev código solicitante. Its data is isolated from every other institution on the deployment.
Glossary
For how Lerian Consignado — Dataprev sits alongside the other native rails and the partner interfaces, see Native messaging and partner interfaces.

