perspective
The $1B Settlement Graveyard
Over the past decade, more than $1 billion has been spent on cross-border payment projects that failed to scale. Ripple xRapid. Libra. Bank consortiums. CBDC pilots. The common failure pattern is not technical - it's institutional.
Published
The graveyard pattern is clear: projects that tried to replace existing rails failed, while the survivors upgraded something within an existing rail.
Reader Brief
Over the past decade, more than $1 billion has been spent on cross-border payment projects that failed to scale. Ripple xRapid. Libra. Bank consortiums. CBDC pilots. The common failure pattern is not technical - it's institutional.
Reading Guide
Four ideas to anchor the settlement graveyard.
The read moves from four failure patterns to the replace-versus-upgrade distinction, then tests the thesis against the survivors and the strongest counter-arguments.
Four failure patterns: Ripple's volatility ask, Libra's sovereignty threat, bank consortia's governance drag, and CBDC's wrong-problem mismatch.
xRapid asked banks to hold a volatile token, XRP, as a liquidity bridge. Libra/Diem proposed a basket-backed currency that triggered monetary-sovereignty alarm in every G7 capital. Bank consortia such as IBM World Wire, Fnality, and Contour ran out of runway before network effects kicked in. CBDC cross-border pilots addressed domestic modernization, not the actual cross-border problem: correspondent retreat, FX scarcity, and compliance fragmentation. The projects looked different on the surface but shared a common architectural failure: misalignment between what the project asked of counterparties and what counterparties needed.
The deeper pattern: every graveyard project tried to replace something, while every survivor upgraded something within an existing rail.
Wise did not replace banks; it built local-account networks on top of them. SWIFT gpi did not replace correspondent banking; it added speed within existing relationships. USDC and USDT did not create new currencies; they tokenized USD claims. Licensed stablecoin operators did not replace licensing regimes; they worked within them. The graveyard projects asked counterparties to abandon something proven for something novel. The survivors asked counterparties to keep doing what they were doing, just faster or cheaper.
Aggregate $1B+ deployed: $1.1B Ripple, $2.7B Libra Association, and $500M+ across bank consortia. The capital was not the problem.
The graveyard demonstrates that capital alone does not buy adoption in cross-border payments. Ripple's $1.1B raised against the xRapid thesis did not produce treasury-integrated bank usage. The Libra Association assembled $2.7B in commitments and the most powerful technology and finance brands in the world before regulatory pushback dissolved it. IBM World Wire, Fnality, Partior, and Contour collectively absorbed hundreds of millions in bank IT spending. Architectural fit with counterparty incentives was more decisive than capital deployment [2][3][4].
The survivors: Wise, USDC/USDT, SWIFT gpi, and licensed stablecoin operators scale because they minimize the new risk they ask counterparties to accept.
Wise asked banks to provide local accounts, which is a transaction that already happens. SWIFT gpi asked banks to add tracking and service levels to existing correspondent flows. USDC and USDT asked users to hold a USD-denominated claim on an issuer, economically close to a money market fund unit. Licensed stablecoin operators asked counterparties to use existing local fiat for settlement and limit stablecoin exposure to transit only. None required counterparties to take meaningful new risk in exchange for the upgrade.
The Graveyard
Capital was deployed. Adoption did not follow.
Cross-border payment transformation has been promised for a decade. The promises have come with significant capital: $1.1B raised by Ripple against the xRapid thesis, $2.7B committed to the Libra Association before dissolution, and hundreds of millions in bank consortium spending on early tokenized deposit networks. The aggregate is well north of $1 billion spent on projects that did not scale to their original vision. The failure pattern is worth studying because the same mistakes are being made again [2][3][4].
- $1B+ Capital deployed Aggregate capital deployed into failed or scaled-back cross-border payment initiatives from 2015 to 2024.
- 4 Failure patterns Volatility ask, sovereignty threat, consortium governance drag, and CBDC wrong-problem mismatch.
Failure 1: Ripple xRapid
A technically sound thesis still asked banks to accept the wrong risks.
Ripple raised over $1B against a thesis that banks would replace their nostro prefunding with XRP liquidity, enabling real-time cross-border settlement. The thesis was technically sound. The adoption was limited [2].
What went wrong: asking banks to hold XRP was asking them to accept token volatility, counterparty risk, and regulatory ambiguity.
xRapid's value proposition required banks to hold XRP as a liquidity bridge. This required banks to accept price volatility between payment initiation and settlement, take on XRP custody and operational risk, navigate unclear regulatory treatment of XRP in each jurisdiction, and replace a proven operational model with a novel one. The SEC's 2020 enforcement action alleging XRP was an unregistered security, partially rejected in 2023, added multi-year regulatory friction. Even without that action, the model asked banks to take risk they had other ways to avoid. Most banks that engaged with Ripple used RippleNet, the messaging layer with no XRP required, rather than xRapid, the liquidity layer with XRP required. The messaging product found some adoption. The liquidity product, which was the economic core of the thesis, did not scale [2].
The lesson: payment infrastructure must minimize the new risks it asks counterparties to accept.
Stablecoin-based settlement architectures avoid this trap by using USD-pegged instruments with stable value, eliminating the volatility risk that xRapid imposed. Counterparties face no price risk between initiation and settlement. That is one structural advantage current stablecoin-based clearing networks have over Ripple-era designs. It is not a coincidence; it is a direct lesson from the xRapid experience.
Failure 2: Libra / Diem
A new monetary unit triggered a sovereignty response no technology could solve.
Facebook's Libra, later Diem, promised a global stablecoin for cross-border payments, backed by a basket of fiat currencies and managed by a consortium of major technology and financial companies. After regulatory pushback from G7 finance ministers and US Congressional hearings, the Libra Association dissolved in 2022. Its technology assets were sold to Silvergate Bank, which later failed [3].
The timeline is part of the argument: Libra launched in June 2019, drew G7 regulatory pushback, lost consortium members including Visa, Mastercard, and PayPal, renamed itself Diem in 2020, kept facing regulatory resistance, sold assets to Silvergate, and then saw Silvergate collapse in March 2023.
What went wrong: proposing to create a new monetary unit triggered monetary sovereignty concerns.
Libra's original design proposed a basket-backed currency that would function as a new unit of account. That is precisely what central banks cannot permit: an instrument that could challenge domestic currency as a unit of account directly attacks monetary sovereignty. The eventual pivot to single-currency Diem coins addressed this but came too late. The regulatory damage was done, and the political coalition that had formed to block Libra did not disband. Payment infrastructure that positions itself as complementary to sovereign currencies gets regulatory tolerance. Infrastructure that positions itself as replacing sovereign currencies gets regulatory opposition [3].
The contrast: USDC, USDT, and regulated payment stablecoins explicitly position as complementary.
Current payment stablecoins, including USDC under the GENIUS Act framing, EURC under MiCA, and regulated local stablecoins under UAE and Singapore frameworks, are structured explicitly as claims on underlying fiat. They are USD tokens or fiat tokens, not new currencies. They complement monetary sovereignty; they do not challenge it. This distinction is often dismissed as semantic. It is not. It is the architectural choice that determines whether regulators will tolerate the instrument. Libra failed this test; regulated stablecoins aim to pass it. The Dollarization Myth explores the transit versus store-of-value distinction.
Failure 3: Bank Consortium Projects
Shared governance and expensive bank integration slowed the network before scale arrived.
Multiple bank consortium projects to build tokenized cross-border settlement have scaled back or failed to launch at their original scope. IBM World Wire dissolved in 2021, Fnality International is years behind its original timeline, early Partior iterations reduced scope, and Contour closed in 2023. Aggregate capital deployed into bank consortium projects likely exceeds $500M [4].
What went wrong: consortium governance is slow, and bank IT integration is expensive.
Bank consortium projects face a specific cold-start problem. Every participating bank must integrate to the shared network, often as a multi-quarter project. Participants must agree on governance, compliance standards, and fee structures. The network must reach critical mass before it delivers meaningful value to any individual bank. During the build phase, each bank continues to operate its existing correspondent network, which competes with the new network for volume. The result: many projects launch with three to five participating banks and limited corridors. They deliver some value at that scale but not enough to justify the investment. Additional banks join slowly because the value is limited. The network does not reach the inflection point where growth becomes self-sustaining.
The lesson: network effects require early commitment beyond immediate ROI.
Successful payment networks, including Visa, Mastercard, CLS, and SWIFT, had patient capital or member commitment to ride out the build phase. Bank consortium projects typically have quarterly earnings pressure, rotating management attention, and competing internal priorities. The current generation of stablecoin clearing networks faces the same cold-start challenge. The difference is that licensed non-bank operators, including fintechs and VASPs, face less internal friction and often have more patient capital than bank consortiums.
Failure 4: CBDC Cross-Border Pilots
Domestic modernization did not solve correspondent retreat, FX scarcity, or compliance fragmentation.
Multiple central bank CBDC projects focused on cross-border use cases have scaled back or stalled. The eNaira in Nigeria saw its app removed from Google Play, USSD discontinued, and 98.5% of wallets inactive within a year of launch. The Sand Dollar in the Bahamas saw limited adoption outside pilot corridors. DCash in the Eastern Caribbean came in below adoption projections. Project mBridge reached minimum viable product status in 2024, but remains a central-bank pilot and governance experiment rather than a commercial corridor rail [1][4].
What went wrong: CBDCs solved the wrong problem for cross-border payments.
CBDC projects were designed to modernize domestic payment systems. The cross-border benefit was theoretical: if multiple countries had CBDCs, inter-CBDC bridges could enable fast cross-border settlement. But the core cross-border problem is not domestic modernization. It is correspondent banking retreat, FX scarcity, and compliance fragmentation. CBDCs address none of these directly. They provide a domestic digital cash instrument, which is useful domestically but does not solve the international settlement problem. The eNaira is the clearest case: launched partly to reduce foreign currency dependence, it did not reduce USDT demand because USDT solved the cross-border problem while eNaira solved a different, domestic problem [1].
The lesson: solve the actual problem, not the problem your architecture can address.
Cross-border payments need fast settlement, low cost, multilateral clearing, deep corridor liquidity, and regulatory visibility. CBDCs deliver none of these in their current form. Inter-CBDC bridges might deliver some in theory, but the governance complexity of multi-sovereign tokenized settlement is proving as difficult as the bank consortium problem. Meanwhile, regulated stablecoins deliver settlement speed, multilateral clearing potential, and corridor liquidity today. The lesson for future cross-border infrastructure is to solve settlement first, then add sovereignty controls, not the other way around.
The Survivors
The projects that scaled minimized new risk and upgraded specific layers.
Not everything in cross-border payment innovation has failed. The projects and architectures that scaled share specific properties the graveyard projects lacked.
| Survivor | What scaled | Why it worked |
|---|---|---|
| Wise | Local account network for consumer FX | Worked within existing banking regime |
| USDC + USDT | Global stablecoin circulation above $260B in May 2026 | Framed as fiat tokens, not new currencies |
| SWIFT gpi | Minutes-level settlement for G7 | Upgrade within existing rails, not replacement |
| Licensed stablecoin operators | EM corridor settlement at 1-3% | Worked within licensing regimes, no new token |
The pattern: survivors minimize new risk. They work within existing frameworks and upgrade specific layers, not replace the whole stack.
Every successful cross-border payment innovation has this property. Wise did not ask banks to hold a new asset; it built on top of local banking. SWIFT gpi did not replace correspondent banking; it added speed to existing relationships. Stablecoins did not create new currencies; they tokenized existing ones. The graveyard projects all tried to replace something. The survivors all tried to upgrade something. This is the pattern future cross-border infrastructure designers should internalize.
Counter-Arguments & Limitations
Where the replace-versus-upgrade thesis can be challenged.
The replace-versus-upgrade thesis is a useful predictor, not a law of nature. The strongest objections are about successful replacement, failed upgrades, and the possibility that some graveyard architectures return in more sovereign-aligned form.
Counter 1: The replace-versus-upgrade dichotomy is too clean.
The simplification case: USDC and USDT effectively replaced the function of money market funds and bank deposits for payment liquidity, and they scaled. Fnality and Partior tried to upgrade existing bank-to-bank settlement and have struggled to reach scale. So replace-versus-upgrade is not a clean predictor. The counter-counter: USDC and USDT replaced an instrument category but kept the underlying claim structure intact. They are USD-denominated claims on issuers, structurally similar to money fund units in user experience. They did not ask users to accept a new monetary unit, which was Libra's mistake. Fnality's challenge is closer to bank consortium governance drag than to architectural mismatch. The dichotomy is a useful heuristic, not a deterministic rule.
Counter 2: Some graveyard projects may revive.
The revival case: Libra's failure was political, not technological. A sovereign-aligned successor, such as a USD-only stablecoin issued by a US-chartered consortium under the GENIUS Act framework, could capture the global payment vision Libra targeted. Bank consortia with patient capital could outlast the runway problem. Inter-CBDC bridges, including BIS Project Agora and successors to mBridge, could solve cross-border settlement if multi-sovereign governance is structured correctly. The counter-counter: USDC and PayPal USD already capture much of what a sovereign-aligned Libra successor would target. Patient capital does not solve consortium governance drag; it delays the runway problem. Inter-CBDC bridges face the same multi-sovereign governance challenge that has slowed every prior central bank settlement project. Revival of any specific graveyard project is possible; revival as the dominant cross-border architecture is unlikely. Why Ripple Spent $1B and Built Zero Lock-In drills into Failure 1.
Evidence And Sources
This raw HTML export preserves source visibility for crawler and contractor review. Indexing decision: index, follow.
- Nigeria's eNaira, One Year After; Is Nigeria's eNaira Dead? - IMF; Yahoo Finance
- SEC v. Ripple Labs complaint and litigation records (2020-2023) - SEC; court records
- Libra/Diem Association public disclosures and G7 working group reports (2019-2022) - Libra/Diem Association; G7
- Project mBridge disclosures; IBM World Wire announcements; Fnality International quarterly updates - BIS; IBM; Fnality