How It Works
Each clearing system connection (BIC) maintains separate settlement accounts for SCT (SEPA Credit Transfer) and INST (SEPA Instant). The liquidity engine periodically checks these balances against your configured minimums and takes action when needed.Automatic liquidity is available for CENTROlink and EKS. To move liquidity manually, see Transfers between settlement accounts; to move excess liquidity out, see Withdraw to safeguarding.
Balance Thresholds
You configure four values that control the engine’s behavior:Configuration
Configure liquidity settings through the Dashboard under Settings > Liquidity. These settings are not available through the API; the transfers the engine creates can be followed with Get liquidity transfers.Enable Auto-Liquidity
- Navigate to Settings > Liquidity
- Enable Auto-Liquidity
- Set SCT Minimum, INST Minimum, and Transfer Amount
- Optionally set a Warning Balance above the critical minimum
- Save the configuration
What-If Calculator
The settings page includes a what-if calculator. Enter hypothetical SCT and INST balances to see what the engine would do - which alerts fire, whether a transfer is triggered, and in which direction. Use the sliders to explore thresholds.Automatic Transfers
When auto-liquidity is enabled and a scheme balance drops below its minimum, the engine:- Checks if the opposite scheme account has enough surplus (its own minimum + transfer amount)
- If yes, initiates a transfer of the configured amount from the surplus account to the deficit account
- Sends the transfer to the clearing system:
- CENTROlink: as a dedicated liquidity transfer instruction, not a regular customer payment. It is recorded as an Adjustment transaction and cannot be cancelled or returned
- EKS: as a SEPA payment from your operational account to Latvijas Banka. The scheme the payment is sent on decides which account is debited, see Transfers between settlement accounts. Automatic EKS transfers do not go through 4-eyes signing
Notifications
Configure webhook URLs to receive alerts when balance thresholds are breached or when automatic transfers occur.Signing and delivery
Liquidity notifications carry the samefinventi-signature-N, finventi-signature-timestamp and finventi-receiver-tenant-id headers as payment webhooks, and the signature is built the same way. See Signature verification.
Delivery differs from payment webhooks:
- Liquidity notifications are sent to the URLs set under Settings > Liquidity, not to the webhooks you manage under Settings > Webhooks, and they do not appear in the webhook delivery history.
- They are delivered independently of payment webhooks. A slow or failing liquidity endpoint does not delay payment status notifications.
- A failed delivery is retried a few times in quick succession. After that the notification is not sent again, so use Get liquidity transfers and Account balances as the source of truth.
Low Balance Notification
Payload
Which limit was breached. One of:
RECOMMENDED_TOTAL_MINIMUM_BREACHED, ABSOLUTE_TOTAL_MINIMUM_BREACHED, SCT_MINIMUM_BREACHED_NO_TRANSFER, INST_MINIMUM_BREACHED_NO_TRANSFERLiquidity Transfer Notification
Payload
API Reference
Account balances
View current settlement account balances
Initiate transfer
Move funds between settlement accounts or withdraw to safeguarding
Liquidity transfers
View past liquidity transfers and withdrawals
Account statements
View settlement account statements