> ## Documentation Index
> Fetch the complete documentation index at: https://docs.finventi.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Transfers between settlement accounts
> Move liquidity between your SCT and SCT Inst settlement accounts in CENTROlink or EKS.
## Overview
A transfer between settlement accounts moves liquidity between the SCT and SCT Inst settlement accounts of the same BIC, using `POST /v1/nostro-accounts/transfers` with `transferType: INTERNAL`, the default. Both accounts must be in the same clearing system; transfers across clearing systems are not supported.
How the transfer is executed depends on the clearing system:
| | CENTROlink | EKS |
| - | - | - |
| Vehicle | Dedicated liquidity transfer instruction | SEPA payment to Latvijas Banka, sent on the scheme opposite to the destination account |
| `debtorAccount` | Source settlement account | Your registered operational account |
| `creditorAccount` | Destination settlement account | Destination settlement account (cover account) |
| Linked transactions | Two adjustments, one per account | The outgoing payment, then the adjustment when the credit is booked |
| Setup needed | None, go to [Step 4](#step-4-initiate-the-transfer) | Steps 1 to 3 below |
## Step 1: Register an operational account (EKS)
Register an operational account under **Settings > Liquidity** or with [Add bank account](/payments/api/nostro/liquidity-bank-accounts/create-liquidity-bank-account). It is an IBAN under one of your BICs, used as the debtor of the transfer payment; it can be an IBAN from your own range that holds no funds.
## Step 2: Register the same IBAN with Latvijas Banka (EKS)
Register the operational account's IBAN as a pre-fund increase source in your EKS registration forms:
* field **1.3.1** for transfers into the clearing cover account
* field **1.5.1** for transfers into the IP cover account
Existing participants can add it with a signed modification form. The forms accept several IBANs, so your existing funding account stays registered.
## Step 3: Ask us to enable EKS transfers
EKS transfers are enabled per participant on request. Both your SCT and SCT Inst payments must be cleared through EKS.
## Step 4: Initiate the transfer
### CENTROlink
```bash theme={null}
curl -X POST https://{host}/v1/nostro-accounts/transfers \
-H "Authorization: Bearer {token}" \
-H "Idempotency-Key: 6f1c2a7e-0b1d-4c55-9f0e-3c2b1a9d8e77" \
-H "Content-Type: application/json" \
-d '{
"transferType": "INTERNAL",
"debtorAccount": "LT121020100000000001",
"creditorAccount": "LT891020100100000001",
"amount": 1000000,
"currency": "EUR"
}'
```
`debtorAccount` and `creditorAccount` are your source and destination settlement accounts of the same BIC.
CENTROlink transfers execute only during the operating window, typically 08:00-18:40 EET on business days.
### EKS
EKS has no dedicated liquidity transfer instruction, so the transfer is executed as a SEPA payment to Latvijas Banka. The scheme the payment is sent on decides which cover account is debited:
| Transfer | Sent as | Debited | Credited | Same-day cut-off |
| - | - | - | - | - |
| Clearing cover to IP cover | SCT | Clearing cover account | IP cover account | 17:19 Latvian time |
| IP cover to clearing cover | SCT Inst | IP cover account | Clearing cover account | 17:59 Latvian time |
The platform picks the scheme and fills in the creditor agent and the payment details that Latvijas Banka requires. You provide the destination account and the amount:
```bash theme={null}
curl -X POST https://{host}/v1/nostro-accounts/transfers \
-H "Authorization: Bearer {token}" \
-H "Idempotency-Key: 2d4e8b1c-7a3f-4e2d-8c9b-1f0a6e5d4c33" \
-H "Content-Type: application/json" \
-d '{
"transferType": "INTERNAL",
"debtorAccount": "MT31ABCD40154000000001000000001",
"creditorAccount": "LV12LACB0000000100001",
"amount": 500000,
"currency": "EUR"
}'
```
`debtorAccount` is your registered operational account, not a cover account: it identifies you as the sender of the payment, while the funds come from the cover account of the scheme the payment is sent on.
### Request fields
| Field | Description |
| - | - |
| `transferType` | Optional. `INTERNAL`, the default, so it can be omitted |
| `debtorAccount` | CENTROlink: source settlement account. EKS: registered operational account |
| `creditorAccount` | Destination settlement account |
| `amount` | Amount in minor units (`1000000` = 10,000.00 EUR) |
| `currency` | `EUR` |
| `Idempotency-Key` header | Required. Repeating a request with the same key returns the original transfer |
Do not send `paymentScheme` for this transfer type.
## Step 5: Track the transfer
The transfer appears in [Get liquidity transfers](/payments/api/nostro/get-nostro-account-liquidity-transfer-list) with `transferType: INTERNAL`.
| | CENTROlink | EKS |
| - | - | - |
| Status | Follows the clearing system's response to the instruction | Follows the outgoing payment: stays `CREATED` while the payment awaits signing, then `SENT_TO_CLEAR`, `ACCEPTED`, `COMPLETED` |
| Linked transactions | Two adjustments in `adjustmentTransactionIds` once completed. CENTROlink liquidity transfers cannot be cancelled or returned | The payment in `paymentTransactionId`; the credit appears as an adjustment once Latvijas Banka confirms it |
On EKS credit confirmations the debtor is shown as the funding account configured for your participation, because Latvijas Banka does not transmit the actual sending account. Reconcile transfers by reference and amount, not by the debtor shown on the credit.
### Errors
| Error | Cause |
| - | - |
| Accounts under different BICs | Debtor and creditor do not belong to the same BIC |
| Same account twice | `debtorAccount` equals `creditorAccount` |
| Account not found | The debtor is neither one of your settlement accounts nor a registered operational account, or EKS transfers are not enabled for your BIC |
| Feature disabled | EKS does not clear both your SCT and SCT Inst payments |
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.