Payment Network Interoperability: Standards Bridging Crypto and Traditional Rails

The payments industry has never had more ways to move money. FedNow processes instant bank transfers across 1,800 US financial institutions. Circle's CCTP moves USDC across 17 blockchains in under 20 seconds. Visa settles stablecoin transactions at a $4.6 billion annualized rate. Yet these systems cannot natively talk to each other. Payment network interoperability: the ability for different payment rails to exchange value and data seamlessly: remains the central unsolved problem in modern finance.

A merchant accepting Visa, ACH, and USDC today integrates three separate systems with three different message formats, three settlement timelines, and three compliance workflows. The standards emerging to bridge these rails will determine whether crypto payments reach mainstream adoption or remain siloed alongside legacy infrastructure. This article examines the protocols, standards, and orchestration layers connecting these worlds.

Why Interoperability Matters for Merchant Adoption

According to a PayPal survey from January 2026, 39% of US merchants now accept cryptocurrency at checkout, with 50% of large enterprises ($500M+ revenue) offering crypto payment options. Among merchants already accepting crypto, 84% believe these payments will become commonplace within five years.

Yet 90% of these same merchants say they would expand crypto acceptance if the experience matched traditional card payments. The gap is not demand: it is infrastructure. Merchants want unified dashboards, consistent reporting, and a single integration point. Instead they get fragmented APIs that change quarterly, siloed blockchain networks, and separate compliance workflows for each payment method.

The core challenge is connecting systems that were never designed to work together. A Visa authorization uses ISO 8583 message formats designed in the 1980s. A SWIFT cross-border transfer uses ISO 20022 XML messages. A stablecoin transfer is a blockchain transaction with on-chain data. For merchants to treat crypto as just another payment method, these systems need a common language.

ISO 20022: The Common Messaging Standard

ISO 20022 has emerged as the most significant messaging standard in global payments. On November 22, 2025, SWIFT completed its migration from legacy MT messages to ISO 20022, with 97% of payment instructions now using the new format. Major clearing systems including TARGET2 (Eurozone), CHAPS (UK), and Fedwire (US) have all migrated or are in active transition.

What ISO 20022 Actually Does

ISO 20022 defines a universal financial messaging standard using structured XML (and increasingly JSON). Unlike ISO 8583's fixed-field format, ISO 20022 messages carry rich, structured data: purpose of payment, regulatory identifiers, remittance information, and detailed party identification. This structured data is precisely what crypto payments have been missing.

When a stablecoin transfer carries only an address and amount, it cannot satisfy travel rule requirements or provide the remittance data merchants need for reconciliation. ISO 20022 alignment means wrapping crypto transactions in standardized metadata that traditional banking systems already understand.

Crypto Projects Aligning with ISO 20022

Several blockchain projects have formally joined the ISO 20022 Registration Management Group (RMG). Ripple became a member in late 2024, mapping XRP Ledger messaging to ISO 20022 data schemas. Stellar, which focuses on cross-border stablecoin transfers, is also a member. Other aligned projects include Algorand, Hedera, IOTA, and XDC Network.

A related standard, ISO 24165 (Digital Token Identifier), published by ISO TC 68 in 2021, provides standardized identification for digital assets. This DTI standard gives each token a globally unique identifier, similar to how ISIN codes identify traditional securities. Together, ISO 20022 messaging and ISO 24165 token identification form the foundation for integrating digital assets into existing financial messaging infrastructure.

Why this matters for stablecoins: When a USDC payment carries ISO 20022-compliant metadata with a valid DTI, receiving banks can process it through existing compliance systems without special handling. The payment looks like any other structured financial message, reducing the integration burden from months to days.

Interledger Protocol: Connecting Heterogeneous Networks

The Interledger Protocol (ILPv4) takes a fundamentally different approach. Rather than standardizing message formats, ILP creates a routing layer that connects any payment network to any other. Originally developed at Ripple in 2015 and now maintained by the independent Interledger Foundation, ILP is a W3C standard designed for routing large volumes of small-value payment packets across network boundaries.

How ILP Works

ILP uses a concept called "penny switching": breaking payments into small packets routed independently across interconnected ledgers. Connectors between networks provide liquidity and earn fees, similar to how internet routers forward data packets. The protocol is ledger-agnostic: it does not care whether the underlying system is a blockchain, a bank ledger, or a mobile money platform.

The Foundation's open-source implementation, Rafiki, reached v2.4.0-beta by May 2026 with support for the Open Payments API. Rafiki provides a deployable node that speaks ILP and handles authentication, rate quoting, and compliance hooks. Its 2025-2026 architecture updates introduced event-driven processing that significantly improved throughput.

Production Deployments

ILP has moved beyond theory. The People's Clearinghouse deployed a production Rafiki-based cross-border payment system between the US and Mexico by March 2026, with real-time AML inspection, FX rate integration, and compliance reporting. The project routes ILP payments from US wallets to Mexican community bank accounts, demonstrating the protocol's ability to bridge crypto-native and traditional banking infrastructure.

Mojaloop, the open-source financial inclusion platform, uses ILP as its internal routing protocol to connect mobile money operators in emerging markets. The Interledger Foundation has also extended ILP support to organizations launching stablecoins, enabling them to settle across heterogeneous networks without building custom integration for each counterparty.

Circle CCTP: Native Cross-Chain Stablecoin Transfers

While ILP bridges different types of payment networks, Circle's Cross-Chain Transfer Protocol (CCTP) solves a narrower but critical problem: moving USDC between blockchains without wrapping or synthetic representations. CCTP V2, launched in March 2025, supports 17 chains including Ethereum, Solana, Arbitrum, Base, Optimism, Avalanche, and Polygon.

How CCTP Eliminates Wrapping Risk

Traditional cross-chain bridges lock tokens on the source chain and mint wrapped representations on the destination. This creates counterparty risk: if the bridge is exploited, wrapped tokens lose their backing. CCTP eliminates this by burning USDC on the source chain and minting native USDC on the destination, using Circle's attestation service to verify the burn before authorizing the mint.

CCTP V2 introduced "Fast Transfers" that settle in 8 to 20 seconds across 11 chains, compared to the 15+ minutes required when waiting for full source-chain finality on Ethereum. A new Hooks feature enables atomic execution of arbitrary smart contract actions alongside USDC transfers, opening the door for cross-chain payment flows that include compliance checks, fee splits, or automated treasury routing.

CCTP by the Numbers

Since its initial launch in April 2023, CCTP has processed over $110 billion in volume across 5.3 million cross-chain transfers. In March 2026 alone, $2.4 billion moved through the protocol. These figures reflect growing demand for native stablecoin portability as merchants and payment processors operate across multiple blockchain networks simultaneously.

Comparing the Interoperability Standards

Each standard addresses a different layer of the interoperability problem. They are complementary, not competing.

The full stack: A fully interoperable payment might use the W3C Payment Request API at the browser layer, ISO 20022-formatted metadata for compliance, ILP for routing between the payer's network and the merchant's network, and CCTP for the underlying stablecoin settlement. No single standard solves the entire problem.

Payment Orchestration: The Missing Middle Layer

Standards define how systems should communicate. Payment orchestration platforms implement the actual routing logic that decides which rail to use for a given transaction. Traditional orchestrators like Spreedly, Primer, and Gr4vy connect merchants to hundreds of payment processors and acquirers through a single API.

The Crypto Orchestration Gap

As of mid-2026, established payment orchestration platforms do not natively support stablecoin or crypto settlement. This creates an emerging category of crypto-native orchestrators: abstraction layers that route stablecoin payments from a customer's wallet to the merchant's preferred chain and token. These orchestrators handle pricing, cross-chain rail selection, transfer execution, and finality confirmation.

The orchestration challenge for crypto payments is fundamentally different from traditional payments. A card payment orchestrator optimizes for authorization rates and interchange costs. A crypto payment orchestration layer must optimize for gas fees, chain selection, bridge routing, and settlement finality: all while abstracting this complexity from the merchant. The merchant should not need to know whether a USDC payment arrived on Ethereum, Solana, or Base.

Multi-Rail Routing in Practice

True multi-rail payment routing means a single checkout can dynamically select the optimal rail based on transaction characteristics. A $5,000 cross-border payment might route through stablecoin rails for speed and cost. A $12 in-store purchase might use a card network for familiarity. A $200 peer-to-peer transfer might use FedNow or a Layer 2 network depending on the recipient's capabilities.

The orchestration layer must normalize the experience: same reporting, same reconciliation, same dispute handling regardless of which rail carried the transaction. This normalization is where ISO 20022 alignment pays dividends: if both the card payment and the stablecoin payment produce ISO 20022-formatted settlement records, the merchant's treasury system processes them identically.

Multi-Rail Settlement in Practice

Several major payment companies have begun operating across both traditional and crypto rails, providing early evidence of how interoperability works at scale.

Stripe and Bridge

After acquiring Bridge in 2025, Stripe launched stablecoin payments accepting transactions from 70+ countries. Merchants can settle in USDC on Solana, Ethereum, or Polygon, or convert to USD: all at a flat 1.5% fee. This is significant because it treats stablecoin settlement as a first-class option alongside traditional bank settlement within the same API.

Visa Stablecoin Settlement

Visa expanded its stablecoin settlement capabilities to support USDC, PYUSD, USDG, and EURC across Ethereum, Solana, Stellar, and Avalanche. By March 2026, Visa reported a $4.6 billion annualized stablecoin settlement run rate across 130+ stablecoin-linked card programs in 50+ countries. USDC settlement went live in the US in December 2025.

PayPal PYUSD

PayPal's stablecoin expanded to 70 markets by March 2026, processing approximately $8.2 billion in cross-border stablecoin transactions in Q1 2026 alone. Fiserv launched FIUSD with announced interoperability with PYUSD, demonstrating that even stablecoin-to-stablecoin interoperability is becoming a competitive feature.

Real-Time Payment System Interoperability

The interoperability question extends beyond crypto. FedNow, launched in July 2023, has grown to approximately 1,800 participating banks and credit unions, including seven of the top ten US banks. In Q2 2025, FedNow processed $245 billion in transactions: a 49,000% year-over-year increase from $492 million in Q2 2024.

Yet FedNow does not interoperate with the Clearing House's RTP network (142 million transactions worth $576 billion in Q2 2026), and neither connects to instant payment systems in other countries. India's UPI, Brazil's Pix, and Europe's SEPA Instant all operate as isolated national systems.

BIS Project Nexus

The Bank for International Settlements is attempting to solve this with Project Nexus, a multilateral platform connecting domestic instant payment systems. The initial phase links India (UPI), Malaysia, the Philippines, Singapore, and Thailand, with a target go-live of 2026-2027. If successful, Project Nexus could enable cross-border payments in 60 seconds or less, potentially reaching 1.7 billion individuals.

The significance for crypto interoperability: FedNow uses ISO 20022 messaging, aligning it with the same standard crypto projects are adopting. A stablecoin payment system that speaks ISO 20022 could theoretically connect to FedNow or a Project Nexus-linked system through the same messaging infrastructure, rather than requiring a separate integration path.

Regulatory Catalysts: The GENIUS Act

Regulation is accelerating interoperability by providing the legal clarity needed for traditional institutions to integrate stablecoin rails. The GENIUS Act, signed into law on July 18, 2025, established the first federal regulatory framework for payment stablecoins in the United States.

The Act's key provisions directly affect interoperability. Payment stablecoins are not classified as securities, removing one of the largest barriers to institutional adoption. Issuers must maintain 100% reserve backing with high-quality liquid assets. All issuers must comply with Bank Secrecy Act requirements for AML and KYC, aligning stablecoin compliance with existing banking compliance frameworks.

The regulatory clarity has triggered a wave of institutional activity. Payoneer acquired Skuad and Boundless to build stablecoin-enabled workforce payment infrastructure. Standard Chartered and Amazon are reportedly exploring stablecoin issuance. The OCC published a Notice of Proposed Rulemaking in March 2026 for permitted stablecoin issuers, establishing supervision standards.

Industry Initiatives Bridging the Gap

Beyond protocol-level standards, several industry groups are specifically working on crypto-traditional payment convergence.

Regulated Liability Network

The Regulated Liability Network (RLN) represents a particularly significant effort. In the US, the Federal Reserve Bank of New York Innovation Center partnered with ten financial institutions to test commercial bank deposit tokens and wholesale CBDC on a shared distributed ledger. The proof of concept concluded that the RLN is a "viable and executable construct."

In the UK, UK Finance and 11 member institutions including Barclays, HSBC, Lloyds, and NatWest launched a live pilot for tokenized sterling deposits running through mid-2026. Use cases include person-to-person payments, remortgaging, and digital asset settlement. The RLN model is notable because it preserves existing banking relationships while introducing tokenized settlement on shared infrastructure.

ISO TC 68 Advisory Group 5

ISO's Technical Committee 68 (Financial Services) launched Advisory Group 5 specifically for digital currencies. AG 5 provides direction on standard definitions and identification for CBDCs and non-fiat digital currencies, ensuring that future ISO standards account for digital assets. The group's work on ISO 24165 (Digital Token Identifier) is already in production, and future work will likely address standardized digital asset settlement messaging.

Where Bitcoin Layer 2s Fit

The interoperability standards discussed above were primarily designed for bank-to-bank or chain-to-chain communication. Bitcoin Layer 2 networks occupy a unique position in this landscape: they offer instant settlement with self-custody guarantees, but their integration with traditional payment infrastructure depends on the same standards.

Spark, for example, enables instant Bitcoin and stablecoin transfers without on-chain transactions. Stablecoins like USDB on Spark provide dollar-denominated payments with Bitcoin settlement finality. For merchants, the question is not whether Spark is fast enough: it is whether Spark payments can plug into the same reconciliation, compliance, and treasury workflows that process their card and bank payments.

This is where interoperability standards become critical. A Spark-based stablecoin payment wrapped in ISO 20022-compliant metadata, routed through an ILP connector, and settled with cryptographic finality proof could appear to the merchant's systems as just another instant payment. The underlying innovation is invisible: exactly as it should be. Developers building on Spark can explore the Spark SDK documentation to see how these integration points work in practice.

The Road Ahead

Payment network interoperability is converging from multiple directions. ISO 20022 provides the messaging lingua franca. ILP offers ledger-agnostic routing. CCTP handles native stablecoin portability. The GENIUS Act provides regulatory clarity. BIS Project Nexus links national instant payment systems. The Regulated Liability Network experiments with tokenized deposit settlement.

The total stablecoin transaction volume reached $33 trillion in 2025, a 72% year-over-year increase. EY estimates stablecoins could handle 5% to 10% of cross-border payments by 2030. Whether that projection materializes depends less on any single protocol and more on how well these standards compose into a unified stack that merchants, banks, and fintechs can adopt without rebuilding their existing infrastructure.

For a deeper look at how traditional and crypto payment rails compare, or to explore how money movement infrastructure actually works under the hood, the research library covers each layer of the stack in detail.

This article is for educational purposes only. It does not constitute financial or investment advice. Bitcoin and Layer 2 protocols involve technical and financial risk. Always do your own research and understand the tradeoffs before using any protocol.