Who it serves
Lerian SPI serves financial institutions that participate in Pix under their own ISPB. Each participant connects straight to BACEN, with no connectivity partner in the money path. The rail carries the participant’s payments, Pix keys, charges, and disputes across every surface below.
Four API surfaces
Lerian SPI has four API surfaces. At runtime, it ships four binaries:
spi, dict, brcode, and core. The surfaces speak the messaging contract of one part of the Pix ecosystem.
Settlement is real-time and asynchronous
The SPI settles each Pix individually, in real time, around the clock. When you submit a payment, the platform dispatches an ISO 20022 credit-transfer message (
pacs.008). The platform records the payment as sent to BACEN, not yet settled. BACEN confirms settlement asynchronously through a status reply (pacs.002). The rail validates the reply and moves the payment to COMPLETED or REJECTED. Each payment carries an end-to-end ID (E2EID).
Money-neutrality
Lerian SPI 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 its settlement state; your ledger consumer records the money movement.
Glossary
For how Lerian SPI sits alongside the other native rails and the partner interfaces, see Native messaging and partner interfaces.

