How central banks are building cross-border stablecoin rails: Singapore, Malaysia, and Thailand's BLOOM model

Central banks across Southeast Asia are building infrastructure that lets commercial banks settle cross-border payments using tokenized money—without waiting for a single global digital currency standard. Singapore, Malaysia, and Thailand launched BLOOM (Breakthrough in Linking Onchain Operations and Market infrastructure) in late 2024 to coordinate how tokenized deposits and stablecoins move between their banking systems.

This matters because it sidesteps the coordination problem that has stalled central bank digital currency (CBDC) projects globally, while still giving regulators control over cross-border flows. You'll learn how BLOOM orchestrates settlement across three monetary authorities, why private payment networks are working alongside central bank infrastructure, what tokenized deposits change about correspondent banking, and how regional interoperability projects are moving faster than global standards.

How BLOOM coordinates three central banks on tokenized settlement

BLOOM is a shared protocol layer that sits between each country's domestic payment systems and lets banks settle cross-border transactions using tokens instead of correspondent banking chains. The Monetary Authority of Singapore (MAS), Bank Negara Malaysia, and the Bank of Thailand each maintain their own real-time gross settlement (RTGS) systems domestically—Singapore's MEPS+, Malaysia's RENTAS, Thailand's BAHTNET. BLOOM doesn't replace these systems. Instead, it adds a tokenization bridge that converts local currency settlements into a shared ledger format at the moment money crosses borders.

Here's the architecture: A bank in Singapore converts Singapore dollars into a tokenized deposit on its local ledger. BLOOM's orchestration layer recognizes this token, coordinates with Malaysia's central bank node to verify reserve backing, and instructs a Malaysian bank's system to issue the equivalent Malaysian ringgit tokens on the receiving end. Settlement happens in seconds rather than days because there's no chain of nostro accounts—just cryptographic proof that the sending bank locked funds and the receiving bank can mint the corresponding claim.

Think of it like federated email servers. Each country runs its own email domain (payment system), but they agree on a common protocol (SMTP/BLOOM) so messages (payment instructions) route cleanly between them. No single country controls the whole network, but they all enforce the same addressing and verification rules. The central banks act as authoritative DNS servers—they certify which institutions can participate and which tokens represent valid claims on local currency.

The project runs on distributed ledger technology but deliberately avoids blockchain's typical immutability. Central banks retain the ability to reverse transactions if they detect fraud or sanctions violations. This is a design choice: BLOOM prioritizes regulatory control over censorship resistance. Transactions settle with finality once all three central bank nodes confirm, but the protocol includes escape hatches that let monetary authorities intervene before finality if needed.

Why Ripple, Visa, and Mastercard each play distinct roles in the same infrastructure

Private payment networks aren't competing with BLOOM—they're plugging into different parts of the same stack. Ripple provides the ledger infrastructure that banks use to issue and transfer tokenized deposits. Their XRP Ledger technology handles the atomic swaps and liquidity routing between currency pairs. Ripple doesn't custody funds or settle transactions itself; it supplies the plumbing that lets banks execute delivery-versus-payment (DvP) swaps where Thai baht tokens and Singapore dollar tokens change hands simultaneously with cryptographic finality.

Visa and Mastercard operate one layer higher, at the consumer-facing and merchant-acquiring level. They're building tokenized card networks that settle through BLOOM's rails instead of through traditional card interchange. When a Malaysian cardholder uses a Visa card in Singapore, Visa's network routes the authorization request, but the actual funds movement happens as a BLOOM token transfer between the issuing bank in Malaysia and the acquiring bank in Singapore. This collapses settlement time from T+2 days to minutes and eliminates the foreign exchange spread that card networks typically charge on cross-border transactions.

The card networks benefit because instant settlement reduces their capital requirements and fraud exposure. They still earn fees for authorization, fraud detection, and merchant services—but the payment itself moves on central bank infrastructure. Ripple benefits because banks need its ledger technology to participate in BLOOM, but Ripple's XRP token isn't required for settlement. Banks can issue tokenized deposits backed one-to-one by reserves in their central bank accounts, using Ripple's software as the technical substrate.

This creates a separation of concerns. Central banks control monetary policy and reserve requirements. Ripple provides technical infrastructure. Card networks handle consumer interfaces and merchant relationships. Each layer has distinct commercial incentives but relies on the others to function.

Central banks are keeping control of the money layer while outsourcing the technology layer to private firms—a reversal of how payment systems evolved historically, where private networks owned both the rails and the settlements.

What tokenized deposits mean for cross-border liquidity

Tokenized deposits are blockchain-native representations of commercial bank money, where each token is a direct claim on a deposit account at a licensed bank. Unlike stablecoins issued by non-bank entities (Tether, Circle), tokenized deposits are regulated as bank deposits—they're covered by deposit insurance, subject to reserve requirements, and redeemable on demand at par value. When a Thai bank issues tokenized baht, those tokens represent actual baht deposits on the bank's balance sheet, not algorithmic pegs or collateralized IOUs.

The liquidity advantage comes from eliminating nostro-vostro accounts—the pre-funded foreign currency accounts banks maintain with each other to facilitate cross-border payments. In correspondent banking, a Thai bank sending money to Singapore needs either a nostro account at a Singapore bank or a relationship with an intermediary that does. This ties up capital: the Thai bank must keep Singapore dollars sitting idle in that account to ensure it can settle payments.

With tokenized deposits on BLOOM, the Thai bank only needs to hold tokenized Thai baht. At the moment of settlement, the protocol executes an atomic swap—Thai baht tokens are destroyed on the Thai side, and equivalent Singapore dollar tokens are minted on the Singapore side, using real-time exchange rates from liquidity providers.

Traditional correspondent banking follows this path: Customer initiates payment → Thai bank debits account → Thai bank sends SWIFT message → Correspondent bank receives message → Correspondent bank credits Singapore bank's nostro → Singapore bank credits end customer. Each step takes hours or days, and each intermediary charges fees.

BLOOM collapses this into: Customer initiates → Thai bank locks tokenized baht → BLOOM protocol verifies → Singapore bank mints tokenized SGD → Customer receives. One logical transaction, settled in seconds.

The cost savings are structural, not just operational. Banks can reduce the total capital they keep in foreign nostro accounts because they're not pre-funding settlement—they're executing just-in-time swaps. Liquidity providers (often the same banks, plus specialized market makers) quote real-time foreign exchange (FX) rates on the BLOOM network, competing for transaction flow. This creates a continuous auction for cross-border liquidity instead of opaque bilateral pricing between correspondent banks.

ASEAN stablecoin interoperability as a regional alternative to global CBDC fragmentation

BLOOM is explicitly designed as a regional solution to a global coordination failure. The Bank for International Settlements (BIS) has spent years trying to harmonize CBDC designs across major economies, but progress has been slow because central banks have conflicting priorities on privacy, programmability, and interoperability. China's digital yuan emphasizes state surveillance and capital controls. The European Central Bank's digital euro prioritizes privacy and retail access. The U.S. Federal Reserve hasn't committed to a CBDC at all. Waiting for these systems to converge could take decades.

ASEAN (Association of Southeast Asian Nations) economies decided to solve their own problem first. Singapore, Malaysia, and Thailand collectively process over $500 billion in annual intra-regional trade, most of it still settled through U.S. dollar correspondent accounts in New York. That's inefficient—it adds latency, FX conversion costs, and dependency on Western financial infrastructure. BLOOM lets these countries settle directly in local currencies using tokenized deposits, bypassing dollar intermediation entirely.

The project is designed for expansion. Indonesia and the Philippines are already testing integration, and Vietnam has observer status. The architecture is modular: new countries join by connecting their RTGS system to BLOOM's orchestration layer and agreeing to the shared API standards. There's no central authority that controls admission—the existing members vote on new entrants, but technically any central bank that meets the technical and regulatory requirements can participate.

This creates an interesting dynamic with global CBDC projects. If ASEAN builds working cross-border settlement infrastructure before the BIS finalizes global standards, other regional blocs might follow the same pattern. The African Union could build its own tokenized payment network for intra-Africa trade. Latin American central banks could link their systems using a similar protocol. The result would be a fragmented but functional global payment system—clusters of regional interoperability, with bridges between clusters, rather than one unified global CBDC.

Compare this to the internet's evolution: Email started as fragmented systems (university networks, corporate intranets, commercial services like AOL) that gradually adopted common protocols (SMTP, IMAP, POP3) to interoperate. No one designed a single global email system; it emerged from regional networks agreeing on standards. BLOOM is betting that cross-border payments will follow the same path—regional solutions first, global interoperability later, driven by pragmatic adoption rather than top-down design.

The table shows why regional approaches are moving faster: they avoid the hardest coordination problems (global standards, harmonized regulations) while still delivering most of the efficiency gains.

What this means for builders

If you're building payment infrastructure, BLOOM demonstrates that central banks are willing to adopt blockchain technology for settlement if it preserves regulatory control. The key design pattern is permissioned interoperability—the ledger is distributed across central bank nodes, but participation is gated by licensing requirements. This means you can build on top of these rails, but you'll need partnerships with licensed banks or payment service providers to access them.

For fintech companies, the opportunity is in the interface layer. BLOOM handles settlement, but it doesn't provide consumer wallets, merchant payment acceptance, or value-added services like FX hedging or payment scheduling. Those are open territory. You could build a cross-border payment app that routes through BLOOM-connected banks and competes on user experience, speed, or pricing—similar to how Wise and Revolut sit on top of traditional banking rails but deliver a better customer experience.

For protocol developers, watch how BLOOM handles privacy and compliance. Transactions are visible to central bank nodes but not fully public. Each bank sees its own transactions, and central banks can see everything, but there's no global transparency like on Ethereum. This is a deliberate trade-off: regulators get visibility, but commercial banks retain customer privacy. If you're designing cross-border payment protocols, expect similar requirements—some transparency for compliance, full privacy for end users.

Liquidity providers (market makers, specialized FX desks) have a new role here. BLOOM's atomic swaps need someone to quote exchange rates and provide immediacy. Banks will play this role initially, but there's room for specialized liquidity providers who can offer tighter spreads or deeper markets for less-liquid currency pairs. The infrastructure is open to any licensed institution, so competitive pricing should improve over time.

If you're working on stablecoin projects, understand that tokenized deposits are direct competitors in the cross-border payment space. Tokenized deposits have regulatory clarity (they're bank deposits), existing compliance infrastructure (banks already do KYC/AML), and central bank support. Stablecoins have better programmability, global reach, and permissionless access. The winning approach might be hybrid: stablecoins for crypto-native use cases, tokenized deposits for regulated cross-border payments, with bridges between the two.

Conclusion

BLOOM shows that cross-border payment infrastructure is fragmenting into regional networks rather than converging on a single global standard. Central banks in ASEAN are building interoperable tokenized settlement systems because waiting for global CBDC coordination is too slow, and the benefits of eliminating correspondent banking are too large to ignore.

The project demonstrates that blockchain technology can work within existing regulatory frameworks if it preserves central bank control over monetary policy and transaction visibility. Private payment networks like Ripple, Visa, and Mastercard are cooperating because they benefit from faster settlement and lower capital requirements, even if central banks own the settlement layer.

Tokenized deposits are emerging as a regulated alternative to stablecoins for institutional cross-border payments, backed by deposit insurance and reserve requirements rather than algorithmic pegs. This regional approach to payment infrastructure might become the template for how global interoperability actually happens—not through grand unified standards, but through pragmatic federations of compatible systems that solve local problems first and connect globally later.