The growth of embedded finance means that neobanks, marketplace platforms, BaaS providers, and fintech infrastructure layers are now managing cross-border FX exposure at an institutional scale, often without FX as a core product.
At the center of managing that exposure sits Continuous Linked Settlement (CLS). This is the global mechanism that eliminates FX settlement risk. Understanding CLS settlement eligibility is a strategic priority for embedded finance platforms.
FX loss isn’t volatility. It’s margin erosion. This guide walks through how CLS works, who qualifies, and the practical steps to access CLS FX settlement as part of a robust embedded FX infrastructure strategy.
CLS is a global payment system that eliminates FX settlement risk by synchronizing the simultaneous exchange of currency payments between counterparties, a mechanism known as Payment-versus-Payment (PvP). Established in 2002 by CLS Bank International and regulated by the U.S. Federal Reserve, CLS settles over $6 trillion in FX transactions daily across 18 eligible currencies.
CLS was built to eliminate Herstatt risk, which is the danger that one party delivers currency while the counterparty defaults before reciprocating. Under PvP, neither currency leg is released until both are confirmed. Each member funds only their net position, significantly reducing gross liquidity requirements.
CLS settlement eligibility refers to an institution’s qualification as a direct settlement member or third-party participant to have its FX trades settled through CLS.
Reserved for the world’s largest Tier-1 and Tier-2 banks. Direct settlement membership requirements include regulated financial institution status, minimum capital thresholds, shareholding in CLS Bank, and SWIFT connectivity. Not a realistic pathway for most embedded finance platforms.
Third-party access is the practical route for embedded finance platforms. Non-member institutions, including NBFIs and broker-dealers, submit FX trades for CLS settlement through an existing settlement member, gaining PvP protection without a direct CLS account. The settlement member assumes funding responsibility and applies its own KYC/KYB onboarding criteria.
Every cross-border transaction, payout currency conversion, or multi-currency balance generates FX exposure and with it, settlement risk. Many platforms assume this risk is absorbed by their sponsor bank or FX provider. That assumption is often wrong.
If the sponsor bank or FX provider is not CLS-eligible, the platform’s FX flows may be settling bilaterally outside PvP protection. Bilateral settlement creates the principal risk that the full notional value of a transaction is at risk if a counterparty fails between instruction and settlement. As volumes scale, so does that exposure. Regulators, including the Federal Reserve, BIS, and FSB, are actively closing this gap.
Option one is the most accessible route. The platform submits FX trade instructions to a settlement member, which submits them to CLS on the platform’s behalf. Key considerations are the member’s supported currency pairs, credit limits and collateral requirements. Additionally, take into account SLA commitments for instruction submission within the CLS window, and SWIFT or API connectivity requirements.
Regulated non-bank financial institutions such as licensed payment or e-money institutions can qualify as third-party participants in their own right. Requirements include regulatory oversight in a recognized jurisdiction, minimum FX settlement volumes, SWIFT connectivity, and acceptable credit and risk management standards. Higher autonomy, but a higher operational bar.
Platforms already operating through a CLS member sponsor bank can extend coverage to their FX flows via explicit SLA provisions. This is the lowest-friction option only if the SLA specifically covers PvP settlement for the platform’s trades. Gaps in contractual coverage leave FX volume exposed.
Using a bank for FX does not automatically mean those transactions are CLS-settled. Unless the bank is a CLS settlement member and the arrangement explicitly covers PvP settlement for the platform’s trades, FX flows may be settling bilaterally. Verify the coverage. Don’t assume it.
Direct CLS settlement membership is indeed concentrated among major global banks. But third-party participation is accessible to a wide range of institution types, including NBFIs, broker-dealers, and regulated fintech operators with sufficient volume. The bar is high, but it is not exclusively a Tier-1 domain.
Settlement risk is not a function of volume alone. It is a function of notional exposure and the probability of counterparty failure. Even modest FX volumes carry principal risk in bilateral settlement. And as platforms scale, what appears immaterial today can become a material exposure quickly. Addressing CLS eligibility proactively is far less costly than addressing a settlement failure reactively.
Bilateral netting reduces gross settlement amounts but does not eliminate principal risk; rather, it reduces the size of the principal risk. CLS’s PvP mechanism eliminates principal risk entirely for settled transactions. For platforms managing institutional client funds or operating under regulatory capital frameworks, netting-only strategies may not meet the bar that regulators and clients increasingly expect.
CLSNet is expanding bilateral netting to emerging market currencies and new asset classes, broadening PvP access beyond CLS’s current 18 currencies. The global shift to T+1 settlement is compressing FX settlement timelines and increasing the operational value of PvP infrastructure.
Regulatory pressure on non-bank FX settlement risk is intensifying. Platforms that achieve CLS eligibility or demonstrate a credible pathway gain a measurable trust advantage with institutional partners, clients, and regulators.
CLS settlement eligibility is a strategic infrastructure question with direct implications for margin protection, regulatory standing, and institutional trust. The FX settlement risk embedded in cross-border flows compounds with scale and does not disappear by routing transactions through a bank.
Discover how Okoora can enhance your platform’s global capabilities.