DVP vs FOP Settlement: Why the Wrong Choice Can Cost You Everything

DVP vs FOP Settlement: Why the Wrong Choice Can Cost You Everything
Benjamin Avraham

Benjamin Avraham

  • 20 Apr 2026
  • 17:13
  • 14 min

It’s 9:47 a.m. on a Tuesday in Frankfurt. A mid-sized European bank has just completed a $47 million cross-border FX transaction with a correspondent counterparty in New York. The currency leg — the euros — went out the door at settlement open. The dollar leg was supposed to arrive within hours.

By 3 p.m., the dollars haven’t arrived. By the end of the day, it becomes clear why: the counterparty has filed for insolvency.

The euros are gone. The dollars aren’t coming. And $47 million in principal has just evaporated because one settlement decision wasn’t made correctly.

This isn’t a theoretical scenario. It’s the logical end-state of a free of payment workflow applied to the wrong transaction. And as FX volumes surge across embedded finance platforms, fintech operators, and institutional desks, processing trillions in cross-border transactions annually, the settlement method you choose is no longer a back-office detail. It is your first and most consequential risk management decision.

The Two Models Every Finance Professional Needs to Understand

Every currency transaction settles in one of two structural frameworks:

  • Delivery Versus Payment (DVP): Both legs of the transaction — the currency delivered and the payment received — are linked and conditional. Neither transfers without the other.
  • Free of Payment (FOP): The asset or currency moves independently, without a simultaneous, guaranteed payment leg. Settlement of the payment side happens separately.

The difference sounds technical. The consequences are anything but.

Settlement 101: What’s Actually at Stake

Before dissecting the models, it’s worth clarifying what “settlement” actually means in currency markets, because most practitioners conflate execution with settlement, and that confusion is expensive.

Settlement is the moment of finality. It’s when currency legally changes hands, when obligation becomes delivery, and when risk either transfers cleanly or gets stranded in limbo.

Every settlement carries two core risks:

  1. Principal risk — the risk that you deliver your leg of the transaction and your counterparty fails to deliver theirs. The full notional value of the trade is at stake.
  2. Liquidity risk — the risk that even a solvent counterparty fails to deliver on time, forcing you to fund positions or source currency at unfavorable rates.

Currency markets carry settlement risks that equity and bond markets don’t. The sheer geographic and time-zone fragmentation of global FX — where a yen-dollar trade involves settlement systems in Tokyo, New York, and potentially London — creates timing windows where principal can be exposed for 12 to 18 hours or more in correspondent-based settlement chains.

That exposure window is where fortunes are lost.

The most notorious example: the Herstatt Bank failure of 1974. German regulators closed Bankhaus Herstatt mid-business day. Counterparties had already paid deutschmarks to Herstatt earlier that morning. But because U.S. dollar payments from Herstatt’s New York correspondent hadn’t yet been processed, those counterparties received nothing. The resulting cascade nearly froze interbank FX markets globally and gave birth to what we now call Herstatt risk — the textbook case for why DVP settlement exists.

What Delivery Versus Payment Actually Does

DVP settlement is not a product. It’s a structural guarantee.

The core principle is deceptively simple: neither leg of a transaction transfers unless both legs transfer. The delivery of currency is conditional on the simultaneous receipt of payment. If one fails, both fail. There is no partial settlement. There is no exposure window.

The Bank for International Settlements (BIS) defines three DVP models, each reflecting a different approach to gross vs. net settlement:

  • Model 1 settles both legs on a gross, trade-by-trade basis in real time. Maximum protection, highest operational cost.
  • Model 2 settles the delivery leg gross but nets the funds leg across multiple trades. Common in securities markets.
  • Model 3 nets both legs — securities and funds — across a batch of trades. Highest efficiency, used in large multilateral netting systems.

For FX specifically, the most relevant DVP mechanism is payment-versus-payment (PvP), where both currency legs are settled simultaneously. CLS Bank — the Continuous Linked Settlement system backed by major central banks and over 70 financial institution members — is the preeminent infrastructure provider for PvP settlement in FX. CLS processes over $6.5 trillion in daily FX settlement value, eliminating principal risk for member institutions by acting as the simultaneous settlement agent for both currency legs.

For institutions with CLS access, DVP settlement for FX is as close to risk-free settlement as global markets currently provide.

For everyone else, fintechs, non-bank payment processors, and embedded finance platforms, the DVP principle must be replicated through contractual and operational architecture, often through prime brokers, settlement agents, or increasingly, API-driven settlement platforms.

Free of Payment: Legitimate Tool, Dangerous Default

Here’s what most practitioners get wrong about free of payment settlement: FOP isn’t inherently dangerous. It’s just dangerous in the wrong context.

Free of payment means exactly what it says — an asset or currency transfer that occurs without a simultaneous, linked payment on the other side. The two legs are decoupled. Principal risk exists from the moment of delivery until payment is confirmed through a separate process.

FOP settlement is legitimate and appropriate in specific scenarios:

  • Internal book transfers between accounts held at the same institution or custodian
  • Collateral movements under a Credit Support Annex (CSA), where both parties are already operating under a legal netting framework
  • Securities lending and repo operations, where principal risk is contractually addressed through margin and haircut agreements
  • Transfers between affiliated entities under a consolidated risk and compliance framework
  • Reorganization and restructuring workflows where no third-party counterparty risk exists

In all of these cases, the reason FOP is acceptable is the same: the principal risk has been structurally mitigated through legal agreement, institutional consolidation, or operational design. The FOP settlement mechanism isn’t introducing new risk because the risk management has already happened upstream.

The problem occurs when institutions use FOP as a default settlement method for market-facing transactions — particularly in correspondent banking chains, cross-border FX, and fintech payment flows — because it’s simpler and cheaper to operate than DVP. That’s where Herstatt risk lives in 2025.

DVP vs FOP: The Dimensions That Matter

The cost and complexity trade-offs are real, but they’re often misread. DVP settlement costs more to operate in isolation. But the cost of a single principal risk event in an FOP workflow will dwarf years of DVP infrastructure spend. The math isn’t close.

The Hidden Cost of Getting This Wrong

Let’s make the exposure concrete.

Imagine a fintech platform processing $2 billion in monthly cross-border FX volume for corporate clients. Their settlement workflow relies on a correspondent banking chain with two intermediary hops, and payments are settled free of payment with a 24-hour reconciliation window.

In that window, the platform carries unsecured principal exposure on every single trade that hasn’t cleared.

Assume a 0.5% daily volume of trades in-flight at any given moment — that’s $10 million in exposed principal. If one counterparty in the chain experiences even a temporary liquidity event — not a full insolvency, just a delayed wire — the platform is funding the shortfall out of its own capital or unwinding positions at market rates that may have already moved against them.

Industry estimates suggest that FX settlement fails cost the global banking system between $2 billion and $4 billion annually in direct costs — funding penalties, opportunity costs, and operational remediation. The indirect costs — reputational damage, client churn, and regulatory scrutiny — are harder to quantify but historically larger.

And regulators are paying attention. According to analysis from the Financial Stability Board, a significant portion of global FX transactions — estimated at over 30% — still settle without PvP protection, despite the availability of infrastructure like CLS. That’s a systemic exposure the FSB has flagged as an ongoing priority for market reform.

When to Use DVP (and When You’re Probably Required To)

DVP settlement is the appropriate — and often legally mandated — choice for:

  • Spot, forward, and swap FX transactions executed between distinct counterparties with independent balance sheets
  • Interbank and prime brokerage transactions where notional values make principal risk material by definition
  • Cross-border payments routed through correspondent networks, where settlement timing mismatch creates principal exposure across time zones
  • Embedded finance platforms processing FX at scale on behalf of end clients — here, the fiduciary dimension makes DVP not just operationally sound but ethically necessary
  • Any transaction where your legal agreements, ISDA master agreements, or regulatory frameworks explicitly require simultaneous settlement

The BIS FX Global Code — the voluntary code of conduct for wholesale FX markets — is explicit: participants are expected to use PvP settlement mechanisms wherever available and practical. That language has teeth. Regulators in the UK (FCA), EU (under EMIR), and US (OCC, Federal Reserve) have increasingly aligned their FX settlement risk guidance with BIS CPMI standards, which position DVP as the preferred framework for reducing systemic exposure.

For US banks specifically, the OCC and Federal Reserve’s joint guidance on FX settlement risk management creates a supervisory expectation — not merely a recommendation — that institutions actively minimize principal risk exposure in their FX settlement workflows.

When FOP Is the Right Call — and the Controls You Need

Free of payment has a legitimate role in a well-structured settlement framework. But “legitimate” carries strict conditions.

FOP is appropriate when:

  • You’re moving collateral between accounts at the same custodian under a CSA — both legs of the agreement are governed by the same legal netting framework
  • You’re executing internal book transfers between entities within the same consolidated group, where counterparty risk is effectively zero
  • You’re processing margin and repo operations with full documentation of haircut, margin, and recall rights
  • The payment is so operationally certain — pre-funded, escrowed, or contractually secured — that the principal risk is effectively zero in practice

When you use FOP, you must have:

  • A current, signed legal netting agreement covering the transaction
  • Reconciliation controls that flag any FOP leg outstanding beyond a defined window (typically same-day)
  • Clear escalation protocols when payment confirmation is delayed
  • Counterparty credit limits that account for the unsecured exposure your FOP workflow creates
  • Audit trails proving that each FOP use case falls within your internal policy for approved FOP usage

Operational simplicity is not a justification for using FOP in market-facing transactions. If your team’s reason for using FOP is “it’s faster to set up” or “our systems don’t support DVP,” those are infrastructure problems — not settlement strategy decisions.

The Technology Stack Behind DVP Settlement

The good news for fintechs and non-bank operators is that DVP settlement is increasingly accessible without direct CLS membership — through a combination of settlement agents, API-native platforms, and emerging distributed ledger infrastructure.

The current landscape includes:

  • CLS Bank (PvP): The gold standard for FX DVP settlement. Direct access requires membership, but many institutions access PvP protection through CLS-settling correspondent banks and prime brokers.
  • RTGS systems (Real-Time Gross Settlement): Central bank RTGS infrastructure — Fedwire in the US, TARGET2 in Europe, CHAPS in the UK — underpins DVP for large-value transactions by providing intraday finality.
  • SWIFT and STP: Straight-through processing via SWIFT messaging dramatically reduces the settlement fail rates that plague manual DVP workflows. Automation is not optional at scale.
  • Atomic settlement via DLT: Blockchain-based FX platforms — and particularly stablecoin settlement rails — implement atomic swaps as a native DVP mechanism. If both legs don’t confirm on-chain simultaneously, neither executes. This is DVP in its purest structural form, and it’s already in production for digital currency and tokenized asset settlement.
  • CBDCs: Central bank digital currencies, as they move from pilot to implementation, are being designed with DVP and PvP settlement capabilities built into the protocol layer. The BIS Innovation Hub’s Project Jura (EUR/CHF cross-border CBDC settlement) and Project Dunbar (multi-CBDC platform) both demonstrate the priority regulators are placing on DVP as the settlement standard for the next generation of currency infrastructure.

The Decision Framework Your Treasury Team Needs

If you’re auditing your current settlement workflows — and you should be — use this framework:

Step 1: Categorize each transaction flow Is this a market-facing transaction between distinct counterparties? → DVP required. Is this an internal transfer within a consolidated entity? → FOP may be appropriate.

Step 2: Assess counterparty risk profile What is the credit quality of your counterparty? Do you have a current ISDA master agreement and CSA in place? What is your unsecured credit limit to this counterparty, and does your FOP exposure stay within that limit at all times?

Step 3: Review your legal agreements What does your ISDA master, your prime brokerage agreement, or your correspondent banking agreement say about settlement method? Are you in compliance with its terms?

Step 4: Map your infrastructure Do you have access to DVP settlement through a CLS-settling correspondent, an RTGS-linked settlement agent, or an API-native settlement platform? If not, that infrastructure gap is your most urgent operational risk.

Step 5: Identify red flags in your current FOP workflows Red flags include: FOP settlement used for third-party market transactions, reconciliation windows exceeding same-day, no documented credit limit framework for FOP counterparties, and manual confirmation processes for FOP payment receipt.

What DVP Settlement Actually Earns You

Beyond risk mitigation — which is reason enough — DVP settlement has measurable business returns:

  • Reduced capital requirements. Banks operating under Basel III/IV must hold capital against unsecured counterparty exposures. DVP settlement eliminates those exposures, reducing the capital floor you’re required to hold against FX settlement risk.
  • Lower counterparty credit costs. When you eliminate principal risk, you also eliminate the credit cost embedded in your FX pricing. Some institutional desks price a 1-3 basis point credit adjustment into FX quotes for counterparties without DVP settlement capability. Eliminating that spread improves your effective execution rate across every trade.
  • Regulatory credibility. Demonstrating a DVP-first settlement policy is increasingly a requirement for institutional counterparty relationships, prime brokerage access, and regulatory examination outcomes. It’s not just risk management — it’s a commercial differentiator.
  • Client confidence. For embedded finance platforms and fintech operators processing FX on behalf of clients, DVP settlement is the foundation of fiduciary credibility. Clients don’t understand settlement mechanics — but they understand when their money doesn’t arrive. DVP removes that risk before it becomes a conversation.

The Stakes Are Getting Higher

Global FX turnover reached $7.5 trillion per day in the BIS 2022 triennial survey — and the trend line continues upward. As cross-border commerce expands through embedded finance APIs, digital wallets, and multinationals paying distributed workforces across 40 currencies, the volume of transactions touching FX settlement infrastructure is growing faster than the awareness of the risks that infrastructure carries.

The Herstatt failure happened with far smaller volumes and far simpler market structures. The operational lesson — that free of payment settlement for market-facing FX transactions is categorically the wrong architecture — has been known for 50 years.

And yet, a meaningful share of global FX still settles without PvP protection.

Your Next Three Moves

  1. Audit your settlement workflow by transaction type. Map every currency transaction your institution executes in a typical month. Categorize each as market-facing (DVP required) or internal/operational (FOP potentially appropriate). Identify any market-facing transaction currently settling free of payment. That gap is your immediate risk.
  2. Assess your DVP infrastructure access. If you don’t have access to a CLS-settling correspondent, a prime broker with PvP capability, or an API-native settlement platform that implements DVP mechanics, build that partnership today. The infrastructure exists. Accessing it is a business decision, not a technical impossibility.
  3. Build settlement policy into your legal and operational framework. Document your DVP-first policy in writing. Define the approved use cases for FOP settlement. Set counterparty credit limits that govern FOP exposure. Make settlement method selection an auditable, policy-governed decision — not an ad hoc operational call.

The Bottom Line

In currency markets, settlement is not a back-office footnote. It is where risk is either contained or realized.

DVP settlement — delivery versus payment — eliminates principal risk by making both legs of a transaction conditional on each other. It is the gold standard, it is the regulatory expectation, and it is the architecture that modern FX settlement infrastructure was built to deliver.

Free of payment settlement is a legitimate tool for a narrow set of operational use cases — internal transfers, collateral movements, and affiliated-entity flows — where principal risk has been structurally addressed through legal agreement or institutional consolidation.

Using the wrong model in the wrong context doesn’t just expose you to theoretical risk. It exposes you to the kind of $47 million loss that starts with a delayed wire at 9:47 a.m. and ends with a write-down at close.

Understand your settlement architecture. Know which model governs every transaction type in your book. And where DVP is required — by regulation, by counterparty agreement, or by the basic economics of principal risk — build the infrastructure to deliver it.

The cost of getting this right is manageable. The cost of getting it wrong is not.

Key Topics Covered: 

About the author

Newsletter

Stay in the loop.
Get Okoora’s latest news, insights, and product updates straight to your inbox.
Benjamin Avraham

About the author Benjamin Avraham

Benjamin Avraham is the Founder & CEO of Okoora, the company defining the category of Embedded FX Infrastructure. With decades of experience in building trading operations and advising enterprises on complex currency exposures, he created the FX360 stack to eliminate FX risk and monetize global flows. Benjamin is known for his blitzscaling mindset, execution discipline, and mission to establish FX360 as the global standard in cross-border finance.

Ready to take your business global?

Discover how Okoora can enhance your platform’s global capabilities.

Might be interesting for you