Liquidity and Settlement Risk in Payments
When you tap a card or send a mobile payment, the confirmation feels instant. Behind that confirmation, though, the actual movement of funds between the institutions involved often happens later — sometimes seconds later, sometimes at the end of the day. The gap between promising value and delivering it is where two of the most important risks in payments live: liquidity risk and settlement risk. Understanding them is essential for anyone operating a payment system.
Two risks, clearly separated
Settlement risk is the risk that a payment obligation is not settled as expected — that a party which owes value fails to deliver it. Its sharpest form is principal risk: you hand over your side of a deal and the counterparty never delivers theirs, so you lose the full amount. It also includes replacement-cost risk, the cost of having to redo a failed transaction at worse terms.
Liquidity risk is subtler: the counterparty will eventually pay, but not when expected. You are good for the money in the end, but a delay leaves you short of funds you were relying on to meet your own obligations. A liquidity problem for one participant can cascade into others who were counting on that inflow.
Why the gap exists at all
Settlement lags because moving real funds between institutions is a batch, trust-mediated process governed by banking hours, correspondent relationships, and scheme rules. Authorization is a fast message; settlement is the slower reality of funds actually changing hands. The wider the gap, the more accumulated obligations sit unsettled, and the larger the potential loss if a participant fails mid-window.
Net versus gross settlement
A foundational design choice is whether participants settle each transaction individually or settle only their netted position. The trade-off is between liquidity efficiency and risk exposure.
| Gross settlement | Net settlement | |
|---|---|---|
| How it works | Each payment settled one-by-one, in full | Payments accumulated; only the net difference settles |
| Liquidity needed | High — full value of every payment | Low — only the net owed |
| Risk profile | Lower — each settles immediately, little builds up | Higher — exposures accumulate until the settlement cycle |
| Typical use | High-value, time-critical transfers (RTGS) | High-volume, lower-value retail payments |
Consider three banks exchanging many payments through a day. Under gross settlement, each of, say, 300 payments moves in full — safe, but every party must keep large balances on hand. Under net settlement, all the day's flows are collapsed into one net figure per participant; a bank that sent 1,000 and received 950 settles just 50. Netting dramatically reduces the funds that must move, but it means obligations pile up during the cycle, so a failure before settlement is potentially larger and can spill onto others.
Prefunding: capping the exposure
A powerful control, common in mobile money and interoperability schemes such as Mojaloop, is prefunding. Each participant places funds into a settlement account in advance, and the scheme lets it send payments only up to that available balance — its net debit cap or position limit. The switch checks the position on every transfer and refuses any that would breach it.
Prefunding largely converts settlement risk into a managed, bounded quantity. A participant cannot run up an obligation larger than what it has already funded, so if it fails, its counterparties are covered by the funds already set aside. The cost is capital efficiency: money sits in settlement accounts rather than being deployed elsewhere, and participants must actively monitor and top up their positions to keep transacting.
Other tools in the kit
- Delivery-versus-payment (DvP) and payment-versus-payment (PvP). Structuring an exchange so that one leg only completes if the other does removes principal risk — nobody delivers unless they receive. Mojaloop-style reserve-then-commit transfers apply the same idea within a single payment.
- Shortening the cycle. Settling more frequently, or moving toward real-time settlement, shrinks the window in which obligations accumulate and thus the exposure.
- Collateral and default funds. Schemes may require collateral or maintain a shared fund so that if one participant fails, the network can still complete settlement.
- Position monitoring and alerts. Operators watch each participant's net position in real time and warn or throttle before a limit is breached.
The engineering view
For builders, these concepts land squarely on the ledger. A well-designed system tracks each participant's position continuously against its prefunded balance, enforces the cap before authorizing a transfer rather than discovering a breach afterward, and models money-in-transit in dedicated settlement and suspense accounts so nothing is double-counted. Cross-rail platforms have to manage liquidity in several pools at once — mobile money float, bank settlement balances, FX positions — and rebalance between them as flows shift. Getting this right is what lets a system move value quickly while never promising more than it can actually deliver.
Takeaway
Liquidity and settlement risk both arise from the gap between authorizing a payment and settling it. Net settlement saves liquidity but lets exposure build; gross settlement is safer but capital-hungry; prefunding bounds the risk by requiring participants to fund their positions up front. The art of running a payment system is choosing and combining these mechanisms so that speed for users never outruns the certainty that the money is really there.