> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrating with Lerian SLC

> What Lerian SLC consumes and emits — the CloudEvents lifecycle and clearing event families over the transactional outbox, HMAC-signed webhooks, the NUliquid-keyed domicile webhook — and the optional Midaz and Reporter touchpoints.

Lerian SLC is event-first at its edges. It consumes Nuclea's inbound messages and emits its business facts through a **transactional outbox** onto the platform's streaming backbone and to **HMAC-signed webhooks**, all in a **CloudEvents** envelope. An event is published only when its state change has committed.

## What it consumes

***

From Nuclea inbound, over the **RSFN**:

* **GEN0015**
* **SLC0001** — clearing preview and final
* **SLC0002**
* **PAG0101** — operational status

File returns — **PRO / ERR / RET** — are correlated back to their file **by file name**.

## What it emits

***

Every emission goes through the transactional outbox, so an event is published if and only if its state change committed. Events carry a CloudEvents envelope and are delivered both on the streaming backbone and to HMAC-signed webhooks.

* **Operation lifecycle events** — one per operation state transition.
* **`operation.status_relayed`** — a status has been relayed.
* **`cancellation.confirmed_by_domicile`** — a cancellation confirmed by the IF Domicílio, carrying the NUliquid.
* **`d1.value_mismatch`** — a D0-versus-D+1 value divergence.
* **`certificate.expiring`** — a certificate approaching expiry.
* The **`clearing.*`** family — `cycle_opened`, `cycle_closed`, `cycle_recalculated`, `preview_available`, `final_available`, `credit_settled`, `credit_returned`, `deposit_required`, `deposit_deadline_approaching`, and `divergence_reported`.

A **webhook keyed by the NUliquid** signals the credit to the merchant and carries the return evidence for the domicile flow.

## Midaz touchpoint

***

Lerian SLC is standalone; it does not post to a ledger itself. **Midaz** is an **optional** consumer — it can subscribe to Lerian SLC's events or call its API to mirror settlement into the ledger — but Lerian SLC does not depend on Midaz.

## Reporter touchpoint

***

**Reporter** is an **optional** consumer of Lerian SLC's events, and it can also serve as an **optional pluggable provider of ASLC materialization** through templates. Regulatory ownership of the ASLC layout stays with Lerian SLC; Reporter, when plugged in, only renders it.

## Money-path boundary

***

Lerian SLC owns the card-settlement messaging with Nuclea. It does not perform the monetary settlement itself — the netted position settles at the SLC and Nuclea, and the reserve leg settles at BACEN. The card-domain deferred-net settlement family reaches Lerian SLC relayed from [Lerian SILOC](/en/rails/native/siloc/what-is-lerian-siloc), the participant-side SILOC connectivity.

## API conventions

***

* **Idempotent intake.** Canonical API submissions are idempotent by `external_id`, so a retried submission never double-settles.
* **Online auth.** Individual online operations over REST are secured by mTLS and a per-request JWS signature.
* **Certificates are references, not secrets.** A registered certificate carries its public certificate and a custody reference; the private key is never stored or returned.