Solutions Credit

Credit, from product to payoff.

One engine for the whole contract journey: product, origination, servicing, accounting, and audit in a single history. The credit decision stays with the institution.

What is included

One journey, one history.

  • Credit products

    A product catalogue with immutable versions of the terms: a fixed rate or a floating table, the term, charges, and the accounting profile that says how the product books into the ledger. Every contract points at the exact version it was originated under; new terms are a new version, never an edit.

  • Origination

    An application received, approved, declined, or withdrawn, with the decision on record. A preview of the schedule and of the mandatory disclosures before any commitment. Disbursement recorded with the schedule and the accounting intent in the same transaction.

  • Loan servicing

    The schedule, installments, charges, and transactions of an active contract. A payment allocated from the oldest installment to the newest, previewed before it is recorded; partial or full early payoff; the balance rescheduled after a renegotiation.

  • Corrections that erase nothing

    No correction edits the past. A reversal is a compensating entry; a replay rebuilds the state from the history. The contract's timeline stays intact and auditable.

  • Accounting in the ledger

    Double-entry rules per event — disbursement, interest accrual, an early payoff settled — written down as durable intent and delivered to Midaz asynchronously and idempotently. Monthly accrual as a routine: once per contract, per accounting period, per amount type.

  • Brazil regulatory pack

    CET, the total effective cost of credit, recorded at origination; a preview of IOF, the federal tax on credit operations; capitalization consent with an integrity check; PDD loan-loss provisioning stages; early-payoff quotes; CDC caps on Brazilian consumer credit enforced by refusal; and the Brazilian business-day calendar.

  • Private-sector payroll lending

    Private-sector payroll-deducted lending, over the Dataprev connection: available deduction capacity, payroll-deduction registration, FGTS collateral, refinancing, portability, and payout. The contracted terms come in as they arrived from the institution's own credit engine; Lender does not reprice.

  • Portfolio, assignment, and audit

    A portfolio and arrears dashboard. Receivables assigned to funds with eligibility, approved pools, file exchange, and every external fact recorded as evidence. An immutable audit trail of every contract event.

Lender

It runs on the platform, not beside it.

Lender is Lerian's engine for the credit journey, built for Brazilian consumer credit (CDC), with private-sector payroll-deducted lending as its deepest journey. It is the source of truth for the contract; the Midaz ledger is the source of truth for balances. It runs on the institution's own infrastructure or on Lerian Cloud, with isolation per tenant.

  • CDC and payroll lending
  • Brazil first, by jurisdiction profile
  • Immutable history

For developers

  • REST API with money as decimals

    Amounts and rates travel as decimal strings, never as floats. Bearer token, permissions per resource and action, the tenant taken from the validated identity and never from a header or a payload.

  • Events in CloudEvents

    Journey facts and commands published over Kafka or RedPanda, with a transactional outbox: the local state and the event are written in the same transaction.

  • Asynchronous booking into Midaz

    The accounting intent is written alongside the state; a dispatcher delivers it to the ledger through the official SDK, with a deterministic idempotency key. With no resolved destination it does not book: it fails closed.

  • Price schedules in decimal arithmetic

    A Price schedule with interest on the outstanding balance, rounding handled, and actual/360, actual/365, and actual/252 bases. Contracted payroll-lending terms come in as data; they are not recalculated.

  • Accounting profiles per product version

    Double-entry rules per event, with the target organization and ledger declared in the profile. With no profile, the product does not disburse.

  • Go, PostgreSQL, a schema per tenant

    A single service in a rootless distroless image, with migrations and health probes. Single- or multi-tenant mode, with a schema per tenant.

Contact

Leave your details and Lerian will get in touch to work out the best way to serve your operation.

Talk to Lerian

Or explore first: Sandbox Documentation GitHub