Reduced prefunding
Match funding to payment obligations to reduce idle balances where the funding arrangement permits.
Cross-border and FX
Improve liquidity use in cross-border payments
Develop a payment service for corporate clients using Prividium components. Connect the payment flow to the funding, FX and settlement arrangements that determine how much liquidity each bank needs.
Reduce funding needs and settlement delays
Banks hold balances in multiple currencies to meet cross-border payment obligations. Those balances carry a funding cost. [1]
The service design targets three sources of liquidity efficiency:
Shorter settlement time
Reduce the time funds remain committed before they can be reused.
Netting
Offset eligible obligations and settle the net amount in each currency, reducing the amount that must be funded.
The benefit depends on the participating banks’ funding agreements, settlement arrangements and payment volumes.
A corporate client pays an overseas supplier
The proposed service follows four steps:
From payment instruction to supplier creditIllustrative service design
Corporate client
Payer
Sending bank
Funding and authorization
Commander
Prividium controls
Prividium controls
FX & liquidity
Agreed currency exchange
Receiving bank
Settlement and payout
Commander
Prividium controls
Prividium controls
Overseas supplier
Recipient
Before fundingAgree who supplies each currency and when it must be available.
While pendingCommitted funds remain subject to the settlement and recovery terms.
After completionReuse depends on confirmed settlement and any required payout or redemption.
1. Confirm the quote
The client accepts the exchange rate, fees and the amount the supplier will receive.
2. Fund the payment
The banks and liquidity provider make the required currencies available.
3. Exchange the currencies
The settlement arrangement determines how the two currency payments complete.
4. Credit the supplier
The receiving bank makes the funds available in the supplier’s account.
Prividium’s role
Prividium’s permissioning engine controls who can access the environment and which requests they can make. [2]
The Commander-based service can be designed around three forms of money:
Tokenized deposits
Banks transfer or exchange tokenized claims on deposits through the configured onchain settlement flow.
Stablecoins
Participants transfer or exchange supported stablecoins, with conversion or redemption where the recipient requires bank-account credit.
Bank-account balances
Connected banking systems execute account transfers. Commander provides the control layer for the Prividium part of the workflow.
Each option requires its own asset, settlement and integration configuration.
The bank and its providers deliver FX pricing, liquidity, compliance, client interfaces and connections to bank accounts.
Define the funding and settlement terms
Prefunding
Specify which participant supplies each currency, when funds must be available and how much remains committed while a payment is pending.
Payment-versus-payment
One currency payment is conditional on the other. Confirm support for the selected configuration and establish how funds are recovered if it cannot complete.
Recipient credit
Include redemption and payout steps where required. Onchain settlement alone does not establish when the supplier can spend the funds.
Assess your first payment corridor
Bring a currency pair, participating banks and the current funding process. We’ll identify the Prividium components and integrations to evaluate, then agree how to measure liquidity requirements and payment completion.
Request a walkthrough