> ## 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.

# Event streaming integration contracts

> Event-streaming documentation now clarifies Lender, Midaz, Reporter, and rail integration contracts.

<Badge stroke icon="calendar-days" iconType="regular">August 20, 2026</Badge> <Badge stroke icon="file-code" iconType="regular">Documentation correction</Badge> <Badge color="red" size="lg" stroke icon="triangle-exclamation" iconType="regular">Action required</Badge>

## Affects

***

Teams that consume Lender, Midaz, or Reporter events, or operate streaming for Lender, Pix Switch, Boleto, or SLC.

## What changed

***

Lender's `loan_account.debt_balance_changed` event uses schema major `2` and the topic `lender.loan_account.debt_balance_changed.v2`. `OUTBOX_RETRY_WINDOW_SEC` is the minimum delay between attempts for a row, not a total retry window. A catalog definition key is not always the dispatch key; derive dispatch from `ce-resourcetype` and `ce-eventtype`.

Reporter writes critical events to its durable Mongo streaming outbox after the business-state commit. The two writes are not one atomic application transaction. Only terminal report facts and critical deadline transitions have deterministic identifiers; consumers must treat other `ce-id` values as opaque and deduplicate on `(ce-source, ce-id)`.

Midaz lifecycle-event payloads include `routeId`. CRM facts now share the `lerian.streaming.ledger` application topic; `ce-resourcetype` remains `holder` or `instrument`, with no `crm_` segment.

The guides also document an optional Lender `STREAMING_TLS_CA_CERT`, optional Pix Switch streaming with required broker and source settings when enabled, Boleto's internal Midaz outbox, and SLC's circuit-breaker requirement for an MQ RSFN consumer.

This is a documentation correction that records implemented contracts. It does not announce a runtime release.

## Impact

***

**Classification: Action required.** Consumers that derive the former Lender or CRM topics, assume all Reporter identifiers are deterministic, or use the prior retry and deployment guidance can misroute events or operate an unsupported configuration.

## What you need to do

***

<Steps>
  <Step>Update Lender subscriptions for `lender.loan_account.debt_balance_changed.v2` and derive dispatch keys from the CloudEvents resource and event type.</Step>
  <Step>Accept `routeId` in Midaz lifecycle payloads, use the documented CRM topic form, and retain `(ce-source, ce-id)` as the consumer deduplication key.</Step>
  <Step>Review Reporter delivery assumptions, Lender retry controls, and streaming configuration before the next deployment.</Step>
</Steps>

### Deadline

Complete the review before the next consumer or streaming-integration deployment.

## Resources

***

* [Event streaming overview](/en/reference/events/overview)
* [Lender events](/en/reference/events/lender)
* [Midaz events](/en/reference/events/midaz)