Solutions Financial Messaging
Messaging you own.
Pix, TED, settlement, files, and court orders exchanged with the Central Bank of Brazil (Bacen), Nuclea, and Dataprev in the institution's own software, with no messaging middleman. The operation watches every connection from the Cabine.
What is included
The connections and the Cabine console.
Pix — SPI
The institution's connection to SPI, Brazil's instant-payment settlement system, on its own ISPB and in ISO 20022: sending and receiving Pix, keys and claims in DICT, QR Code (Cob and CobV), Pix Automático, returns, and MED. Pix also runs over partner interfaces: as a direct participant via JD, or indirectly via BTG.
TED and STR — SPB
TED-family transfers and reserve-account operations in STR, Brazil's real-time gross settlement system, with the message derived from the parties' roles rather than from a code picked by hand. Acceptance and Bacen's confirmation are distinct states: accepted is not settled. TED also runs via JD.
SILOC
A participant connection to Nuclea's SILOC, the deferred net settlement system for boletos (Brazilian payment slips) and cards: a single gateway, a participant directory, certificates, and a view of settlement coverage. SILOC computes the position; the connection carries the messages.
SLC
Nuclea's centralized card settlement service, over the ASLC protocol, for an acquirer, a sub-acquirer, a domicile institution, a settlement institution, or a card scheme. The files are assembled and transmitted by the institution; the private key never leaves its custody.
STA
Two-way exchange of regulatory and operational files with Bacen over its file transfer system, with integrity verified by SHA-256 and each file handed to the product that understands its contents.
SISBAJUD
Judicial freeze, release, and transfer orders from SISBAJUD, Brazil's judicial asset search and freezing system, received as files over STA and executed against the Midaz ledger, with the result returned to Bacen. Sensitive data encrypted at rest.
Payroll lending — Dataprev
A connection to Dataprev's Crédito do Trabalhador: available deduction capacity, auctions, contract registration and payroll-deduction registration, amendments, portability, FGTS collateral, and payout reconciliation. The credit decision stays with the institution's own credit engine.
Cabine
The institution's operating console in front of the financial system, for treasury and reserve desks: the readiness of every connection, an alert queue by connection, owner, and severity, and a shift handover with evidence and approval. It shows facts; it holds no position of its own.
Native messaging
The institution's software, homologation per connection.
Every native connection is the institution's own software, running in its environment, with its certificate and its ISPB, and it passes through the corresponding authority's homologation before operating. Pix and TED also run in production over partner interfaces, and the integration with the platform is the same either way.
- Your own software
- Private key with the client
- Settlement facts to the ledger
For developers
One protocol per connection
ISO 20022 in SPI, STR messages in SPB, ASLC over XML in SLC, fixed-layout files in SISBAJUD and STA. Nothing is homogenized by force.
Signing at the regulated edge
Messages signed with the institution's ICP-Brasil certificate; in SLC, signing is delegated to a custody the client controls. STA authenticates with a Bacen operator credential.
Accepted is not settled
Every send is persisted before dispatch and comes back as accepted; Bacen's confirmation arrives later and moves the operation to confirmed or rejected, with an idempotency key per operation.
Queues, retries, and recovery
A dispatch sweep, event redelivery, a dead-letter queue, and retransmission, per connection. Settlement events can be redelivered; deduplication is the consumer's job.
Settlement facts to the ledger
The connections carry the message and the settlement state and publish facts in CloudEvents; the institution's ledger records the money. SISBAJUD executes orders straight into Midaz; the Dataprev payroll connection talks to Lender through commands and events.
Authenticated APIs, tenant from the JWT
Every connection exposes an API authenticated by bearer token, with the tenant taken from the validated identity. STA and SLC isolate institutions by database.
Contact
Leave your details and Lerian will get in touch to work out the best way to serve your operation.
Or explore first: Sandbox Documentation GitHub