The Real Work Begins After the Announcement
Headlines about central banks joining a digital-money initiative tend to focus on the signing ceremony. The harder story sits beneath the communiqué: how do you actually settle a transaction when one counterparty is using a tokenized bank deposit on a permissioned ledger, another is using a regulated stablecoin on a public chain, and a third is operating through a traditional payment network? BLOOM’s answer is architectural rather than monetary. The initiative does not issue a token. It builds the connective tissue that allows existing and emerging forms of digital money to interoperate.
This distinction is easy to miss. BLOOM — Borderless, Liquid, Open, Online, Multi-currency — is often described in shorthand as a stablecoin project or a CBDC experiment. It is neither. It is a standards and settlement-framework initiative convened by MAS, now joined by BNM and BOT as policymaker members, with a participant base that spans banks, card networks, payment firms, blockchain infrastructure providers, and a multilateral development bank.
Three Workstreams, One Settlement Objective
BLOOM’s technical agenda is organized into three interconnected areas. The first is acceptance and settlement across jurisdictions: examining how financial institutions accept different forms of digital money for cross-border transactions, how counterparties contract with one another, and how transactions are ultimately settled across institutions and markets. The second is interoperability across digital money arrangements: the technical and operational approaches needed to connect different networks, infrastructures, and borders. The third is programmable controls: safeguards such as identity verification, sanctions screening, and transaction-level restrictions embedded into digital money flows.
Each workstream corresponds to a layer of the cross-border payment stack that currently fragments along national lines. Acceptance and settlement is the contractual and legal layer. Interoperability is the technical messaging and ledger-connectivity layer. Programmable controls are the compliance and risk layer. BLOOM’s bet is that if these three layers can be standardized across jurisdictions, the cost and latency of cross-border wholesale transactions will fall without requiring a single global ledger or a single settlement asset.
Why “No Token” Is a Feature, Not a Gap
Observers have noted that MAS has not named a preferred token or stablecoin for BLOOM. That absence is deliberate. By remaining asset-agnostic, BLOOM avoids picking winners among tokenized deposits, regulated stablecoins, and central bank money. It also avoids forcing participating jurisdictions to adopt a settlement instrument that might conflict with domestic monetary or regulatory priorities. The framework instead focuses on the rails: how value is accepted, exchanged, and settled across systems, regardless of the digital form it takes.
The multi-currency dimension reinforces this neutrality. BLOOM explicitly covers G10 and Asian currencies, and its wholesale use cases include corporate treasury management, trade finance, and agentic payments — transactions executed by AI agents within pre-set limits and conditions. Agentic payments, in particular, push the framework beyond human-initiated settlement into automated, condition-driven value transfer. That requires programmable controls that can enforce compliance and risk limits at machine speed, which is why the safeguards workstream is not an afterthought but a foundational component.
The Cost Argument
BLOOM’s official rationale is straightforward: by developing implementation frameworks and aligning commercial and operating arrangements, the initiative reduces the need for financial institutions to establish separate arrangements with each counterparty or market, lowering implementation cost and improving time to market. In a correspondent banking landscape where bilateral links are expensive to establish and maintain, that is a meaningful proposition. The involvement of central banks ensures that public policy and regulatory considerations are baked into these frameworks as they develop, rather than retrofitted after commercial arrangements have hardened.
