Outbound submission
The institution, or an upstream Lerian product, hands Lerian STA a file for BACEN. Lerian STA then obtains a protocol number from BACEN, uploads the file’s bytes, and has BACEN validate them against the declared SHA-256. The transfer advances through BACEN’s lifecycle:
| State | Meaning |
|---|---|
| Protocol generated | BACEN has assigned the protocol number. |
| Transmitting | Lerian STA is uploading the bytes. |
| Integrity check | BACEN is validating the declared SHA-256. |
| Received | BACEN has received the file. |
| Delivered | BACEN has delivered the file to its destination. |
| In processing | BACEN is processing the file. |
| Accepted | BACEN has accepted the file — a terminal success. |
| Rejected / Inconsistent | BACEN has refused the file — a terminal failure. |
Inbound discovery and download
Lerian STA polls BACEN per active tenant on a configured cadence for available files. For each file, it matches the file’s BACEN system code against the tenant’s inbound source configurations, then downloads the bytes, verifies them against BACEN’s reported SHA-256, and stores the artefact durably in object storage. A hash mismatch or a download failure retries within a bounded budget. Once the budget is exhausted, the transfer is quarantined to a terminal failure — inconsistent or canceled — rather than delivered to its source product.
Operator actions
An operator can act on a transfer that has not reached a terminal state:
- Cancel a non-terminal transfer.
- Retry a failed outbound transfer.
- Mark urgent to prioritize handling.