What Lerian SLC does and does not do
- It is standalone. Lerian SLC runs the card-settlement messaging on its own and depends on no other Lerian product. Midaz can consume Lerian SLC, but Lerian SLC does not depend on it.
- Signing goes through a custody backend. Lerian SLC builds the unsigned payload and delegates signing to a software key, a PKCS#11 HSM, or AWS KMS. In SaaS, Lerian SLC never receives the signing private key in cleartext.
- One installation serves one client.
Who it serves
Lerian SLC works with the roles of the Brazilian card arrangement. It submits to Núclea as a credenciadora or a subcredenciadora, and it serves the clearing and funding of the IF Liquidante. The IF Domicílio and the bandeira are counterparties in its participant catalog.
Glossary
For how Lerian SLC sits alongside the other native rails and the partner interfaces, see Native messaging and partner interfaces. The card-domain deferred-net settlement family reaches Lerian SLC relayed from Lerian SILOC, the participant-side SILOC connectivity.

