Who it serves
Lerian SPB serves financial institutions that hold their own reserve and settlement account at BACEN. These institutions send TED-family transfers through the STR. They move liquidity between their reserve account and their liquidity account (Conta PI). They also query their reserve position directly through the STR.
An operation-centric API
You do not hand-pick a wire code. You declare the typed roles of the parties to an operation. You name who debits, who credits, and whether each side is an institution or a client. The platform then derives the correct STR message code for you.
Settlement is asynchronous
The STR is a real-time gross-settlement system. Every operation settles individually against reserve balances. When you submit a transfer, the platform returns the status
ACCEPTED. This status means the platform accepted your command for dispatch. It does not mean BACEN settled the transfer.
BACEN confirms asynchronously through a settlement reply, called the R-leg. The reply moves the operation to CONFIRMED or REJECTED. It carries BACEN’s settlement fields, for example numCtrlSTR and sitLancSTR, projected verbatim.
Money-neutrality
Lerian SPB is money-neutral by design. It forwards the amounts you declare exactly as declared and computes no balance or position of its own. The rail carries the message and settlement state; your ledger consumer records the money movement.
Glossary
For how Lerian SPB sits alongside the other native rails and the partner interfaces, see Native messaging and partner interfaces.

