HBAR and ISO 20022
No coin is "ISO 20022 compliant", HBAR included: the standard covers messages between banks, not coins. What the coin lists get wrong, and where Hedera does fit.
Content reviewed on

What ISO 20022 is
Why it keeps coming up
Can a cryptocurrency be ISO 20022 compliant?
A payment provider can translate between ISO 20022 messages and ledger transactions, so a bank sends a standard message and the settlement happens on chain. A ledger transaction can carry a reference to the ISO 20022 message it settles, so both sides can reconcile it. An organization can take part in the bodies that maintain ISO 20022 or register message definitions. That is membership, not certification of a token.
Where Hedera fits
- Finality in seconds
A payment is final once it reaches consensus, which suits instant payment schemes that promise settlement in seconds. - Fees fixed in US dollars
An operator can price a service without guessing tomorrow's network fee. See why HBAR fees stay predictable. - Room for references
Each transaction can carry a memo, and a Hedera Consensus Service message can carry a reference or a hash of the full ISO 20022 message, with a consensus timestamp. - Controls regulated issuers need
Hedera Token Service supports KYC, freeze and wipe keys, so a regulated issuer of a stablecoin or tokenized deposit can meet its own compliance duties. - Institutional governance
The network is governed by the Hedera Council, whose members include financial institutions as well as technology and industrial companies.
The ISO standard written for tokens
How to read an ISO 20022 claim
Does it name a message type, such as pacs.008for a customer credit transfer? Real integrations do.Does it name an institution that uses the integration in production, with a source from that institution? Does it separate the network from the applications built on it? The standard applies to the second. Does it confuse ISO 20022 with a certificate, or with a price prediction? Either is a warning sign.


