Skip to main content
Lerian SILOC is event-driven at its edges. With a configured SILOC MQ connection, it consumes supported SFN messages from Nuclea and emits facts onto the platform. It has no client-facing webhook consumers. Downstream systems subscribe to the streaming topics rather than receive callbacks.

​
What it consumes

  • SFN messages from Nuclea. With the complete SILOC MQ connection descriptor configured, Lerian SILOC decrypts and decodes each inbound message from the regulated envelope, then routes it by a closed (CodProdt, CodMsg) policy. LDL0020, LDL0006, and every other unsupported pair fail closed to an operator exception. See How Lerian SILOC works for the routes.
  • SPB LDL settlement facts, when LDL_FACT_CONSUMER_ENABLED=true. Each fact records the outcome of the instruction it names.
  • Card commands from Lerian SLC, when CARD_COMMAND_CONSUMER_ENABLED=true. The service sends each command to Nuclea and publishes its outcome.

​
Ingestion and delivery semantics

  • SLC relay is at-least-once. For a successfully decoded SLC funding frame with a nonblank BCMSG.NUOp, the durable deduplication key is BCMSG.NUOp, not a message ID alone.
  • The service writes that processed-message record only after a successful relay. It creates no processed-message record for an undecoded or unsupported message. A failure before the record is written can result in another delivery, so this behavior is not an unconditional end-to-end exactly-once guarantee.

​
What it emits

  • Participant facts. Lerian SILOC publishes siloc.participant.registered, siloc.participant.updated, and siloc.participant.status-changed as CloudEvents on the platform’s streaming backbone. Downstream systems track the participant directory without polling.
  • Operational facts. Alert transitions (siloc.alert.raised, siloc.alert.cleared, and siloc.alert.acknowledged), schedule changes, câmara advices and notices, answers to the institution’s requests, and OT cycle settlement facts.

​
No Midaz touchpoint

Lerian SILOC has no direct ledger integration. It holds no accounting position and performs no monetary arithmetic. It routes bytes and emits facts. This rail does not book money. The settlement of the net position happens at SILOC and the STR. Any ledger posting lives with the service that owns the money movement.

​
Money-path boundary

The separate STR rail, Lerian SPB, executes the STR deposit leg, the monetary settlement at BACEN. SILOC does not. Lerian SILOC carries the SILOC messages and administers the connection. It never moves money. It sends the institution’s transfer and withdrawal requests to Nuclea, which executes them.

​
API conventions

  • Base path is /api/v1/siloc, and errors follow the RFC 9457 problem-detail format.
  • Auth follows the platform’s standard bearer-token scheme.
  • Idempotency. A state-changing request needs an X-Idempotency header of up to 255 characters. Within 24 hours, a retry of the same request with the same key returns the stored response instead of running the command again. A request refused with a 4xx does not spend its key.
  • Certificates are references, not secrets. A registered certificate carries a public certificate and an external custody reference. It stores or returns no private key.