I used to think interoperability was mostly a technical coding challenge. After spending more time with Sign’s ISO 20022 claims, I’ve realized it’s not that simple. The way this standard gets discussed in the context of cross-border CBDC transfers often creates confusion, and that matters.
ISO 20022 is essentially a messaging standard. It defines how payment instructions should be structured — where each piece of information sits, how initiation messages are formatted, how status updates are sent, and how regulatory reports are packaged. Sign handles this part well. It provides clean, standardized message formats that should make it easier for central banks to understand one another when coordinating cross-border CBDC movements. At the messaging level, the friction drops significantly.
The problem is that message interoperability and actual settlement interoperability are two very different things. The documentation doesn’t draw this line clearly enough.
Imagine two parties agreeing on the exact wording of a contract, but having completely different ideas about what happens if one side doesn’t deliver. The document looks perfect, yet the actual enforcement and settlement remain messy.
That’s the situation here. Sign’s private CBDC rail runs on Hyperledger Fabric with Arma BFT consensus, delivering immediate finality once a block is committed. If another central bank operates on a completely different infrastructure — perhaps one that uses probabilistic finality with a six-block confirmation period — then both sides may have very different definitions of when a transaction is truly “done.”
If Sign releases funds based on its immediate finality while the other side’s transaction later gets reorganized, the ISO 20022 message was flawless, but the settlement still fails. Someone ends up bearing the loss.
The whitepaper talks about ISO 20022 enabling seamless integration with global financial systems. That’s true for messaging. But real cross-border CBDC settlement needs much more than formatted envelopes. It requires a shared understanding of finality, agreement on who commits first in atomic operations between sovereign rails, clear rules for what happens if one side triggers an emergency pause mid-process, and reliable failure handling when messages get dropped between systems.
ISO 20022 is just the envelope. It doesn’t solve the harder settlement-layer questions where the real risks sit for sovereign nations.
Sign’s stack is properly ISO 20022 compliant and reduces friction at the message layer. However, it doesn’t resolve the deeper settlement challenges that come with connecting different CBDC systems across borders.
I’m left wondering whether ISO 20022 compliance is truly enough for meaningful cross-border interoperability, or if message standardization is only the easy first step in a much tougher problem that the documentation presents as already solved. $SIREN
#SignDigitalSovereignInfra @SignOfficial $SIGN
