I used to think interoperability was mainly a technical coding challenge, but deeper analysis has shifted that view. After reviewing the ISO 20022 compliance claims within the SIGN stack, it’s clear that this concept is often misunderstood—especially in the context of cross-border CBDC transactions between sovereign entities.
ISO 20022 is fundamentally a messaging standard. It defines how payment instructions are structured, where data fields sit, how transaction status updates are communicated, and how regulatory reporting is formatted. The SIGN implementation handles these aspects effectively: standardized message structures, consistent payment initiation and status flows, and automated regulatory reporting. This level of standardization is valuable because it reduces friction in data interpretation between central banks, enabling smoother coordination at the communication layer.
However, message interoperability is not the same as settlement interoperability—and this distinction is critical.
The current documentation does not emphasize this gap strongly enough. Think of it like two parties agreeing on a contract format but not agreeing on enforcement rules. The agreement looks clean on paper, but execution risk still exists.
A similar issue arises here. The SIGN private CBDC rail operates on Hyperledger Fabric X with Arma BFT consensus, offering deterministic and immediate finality once a block is committed. But if a counterparty central bank operates on infrastructure with probabilistic finality (e.g., requiring multiple confirmations), then both systems have fundamentally different definitions of “final.”
This creates a key question: who commits first?
If the SIGN rail finalizes a transaction instantly while the counterparty system is still within a reversible confirmation window, there is a real risk. A reorganization on the counterparty side could invalidate the transaction after SIGN has already released funds. In that case, the ISO 20022 message worked perfectly—but settlement integrity failed.
The documentation highlights ISO 20022 as enabling seamless integration with global financial systems. While that is true at the messaging level, true cross-border CBDC interoperability requires alignment beyond messaging. It demands:
A shared definition of transaction finality
Clear atomic settlement mechanisms across sovereign rails
Defined protocols for emergency intervention during settlement
Robust handling of bridge or communication failures
ISO 20022 provides the envelope—but not the execution guarantees inside it.
To be clear, SIGN’s ISO 20022 compliance is a strong foundation and an important step toward interoperability. But it addresses only the communication layer. The real challenge—and the real risk—lies in settlement coordination between sovereign systems.
The question is not whether ISO 20022 enables interoperability—it does. The question is whether it is sufficient on its own to deliver secure, reliable cross-border CBDC settlement. That part of the problem remains open.