Permissioned Ledgers Undercut Ripple xCurrent

The real risk to xCurrent was that banks could buy the faster messaging layer without buying Ripple’s broader liquidity thesis. xCurrent made a cross border payment feel modern, with pre validation, instant confirmation, and tracking, but banks could get similar control and privacy from permissioned systems like Corda and Hyperledger Fabric while keeping their existing account structures and governance inside bank controlled networks.

• xCurrent was sold like enterprise software, with about $10M upfront plus $100,000 to $500,000 in annual fees. That made it easier to compare against other bank software projects than against a new global money network, and it let CIOs evaluate Ripple next to IBM and R3 in a familiar procurement process.
  1 sacra 2 ripple
• Corda and Hyperledger Fabric won attention because they fit how large banks already operate. R3 says Corda connects over 400 institutions and powers projects at market infrastructures like Euroclear, while IBM used Hyperledger Fabric for we.trade with European banks. That showed permissioned ledgers could reach real institutions without requiring a native asset.
  3 r3 4 r3 5 ibm
• The catch is that permissioned ledgers mostly fix coordination, not trapped liquidity. Ripple’s own positioning was stronger in corridors where correspondent banking is expensive and liquidity is scarce, especially in emerging markets. That is why the deeper competitive line was not blockchain versus no blockchain, but messaging software versus balance sheet efficient settlement.
  1 sacra 2 ripple 6 sacra

This pushed Ripple to move beyond selling bank messaging software and toward products where the balance sheet benefit is harder to copy. The long term winners in cross border payments will be the networks that remove prefunding, connect fragmented ledgers, and make regulated digital dollars and tokenized assets move between institutions as easily as data moves between apps.