Bank-issued stablecoins: Creating a cross-network digital asset

Banks evaluating U.S. dollar-denominated stablecoins face a practical question: how can they integrate onchain assets without disrupting existing compliance, custody, and ledger workflows?

While bank-issued stablecoins are now a possibility, they’re just one part of a much broader array of digital services, including issuing tokenized deposits, partnering with third-party stablecoin issuers, or providing reserve and custody services. Each of these services comes with unique features and limitations. How institutions and clients use them depends heavily on their underlying architecture and capabilities. Before getting serious about experimenting with these digital assets, learn more about the basics of what they offer and where they fit into the broader ecosystem.

Bank-issued stablecoins vs. tokenized deposits

A fiat-backed stablecoin is designed to maintain a stable value relative to a fiat currency, commonly one token per unit of currency. Its reserve model, redemption rights, and market price depend on the issuer and product terms; a stable value is not guaranteed. The defining feature of bank-issued stablecoins is that financial institutions are the ones who issue these tokens, and the redemption rules depend on the financial institution’s legal structure and the reserve system they use to back their offering.

Banks are also involved with digital ledger models, though tokenized deposits represent a direct liability at a commercial bank just like a traditional deposit. While the digital format expands a tokenized deposit’s potential use cases, the underlying claim is still in the client’s hands.

Central bank money is a separate category: it is a liability of the central bank, including currency and reserve balances. Commercial banks do not issue central bank money.

Why do banks issue stablecoins?

Corporate treasurers face mounting internal demand for onchain settlement to handle cross-border payments, programmatic payouts, and 24/7 liquidity management. Financial institutions issue stablecoins for these operational advantages:

• Direct onchain access: Instead of treating onchain transactions as a separate system or leaving the activity to third-party issuers, banks can directly help clients who want to move their money onchain.

• Extended network reach: The more networks and counterparties a stablecoin connects with, the more opportunities a bank may have to use it across different geographic markets and currency corridors.

• Programmable payment logic: Since stablecoins interact with smart contract commands, they support automated payment workflows for predefined conditions without requiring constant manual oversight.

What does interoperability mean for bank-issued stablecoins?

At its core, stablecoin interoperability measures how easily value and payment data move across disparate networks, public ledgers, and legacy systems. In the context of bank-issued stablecoins, this can include moving value between different blockchains or exchanging between other stablecoins or tokenized deposits. Greater interoperability could also mean expanding outside of a bank’s internal network to a wider range of third-party clients and counterparties.

Interoperability can expand counterparty reach and operating options

For an institution to successfully deploy stablecoins, counterparties must accept them under existing compliance policies, and the underlying infrastructure must prevent fragmented liquidity. Interoperability can connect stablecoin settlement with traditional payment infrastructure through banks and payment providers. ACH and wire systems handle fiat transfers, while SWIFT carries financial messages. Preserving compliance context and payment references requires integrations between these systems.

How can bank-issued stablecoins lead to fragmentation?

Despite the promise of seamless connectivity, there’s a risk that poor implementation could create a fractured financial experience. Instead of money moving through a shared set of rails, clients using bank-issued stablecoins must navigate unique liquidity arrangements and counterparty accessibility in different issuer-specific systems. When two stablecoins lack integration, moving value requires separate conversion and settlement arrangements, adding unnecessary friction and prefunding costs.

There are also operational complexities banks must consider as transactions move between systems. Financial institutions need to preserve key information, such as sender/receiver context and transaction purpose, to satisfy compliance checks and confidentiality requirements. If this context doesn’t move reliably with the value, banks face time-consuming verification and reconciliation processes.

When are bank-issued stablecoins not the right fit?

Stablecoins don’t automatically boost a bank’s operational efficiency in every context. Before committing engineering and compliance resources, treasury teams should recognize where onchain mechanics offer little to no strategic advantage over existing infrastructure:

• Domestic payments are already handled efficiently: If an existing payment rail like ACH or wire already meets speed, cost, and operational requirements, adding a stablecoin layer is probably redundant at best.

• Transfers within the same bank or closed network: Adding an extra settlement asset may offer little benefit when both sending and receiving accounts already operate within an internal ledger system.

• Limited acceptance among key counterparties: A stablecoin becomes operationally cumbersome when businesses or institutions in a bank’s network refuse to support the asset, wallet environment, or redemption process.

• Unclear custody or regulatory requirements: Institutions can’t adopt stablecoins at scale if basic obligations like asset safeguarding, accounting treatment, and cross-jurisdictional compliance remain ambiguous.

What bank-issued stablecoins need to interoperate across networks

The key to making bank-issued stablecoins useful beyond one network is to focus on ways to seamlessly connect these digital assets with the systems clients and counterparties already use to move money.

Shared standards connect issuers and networks

Shared standards provide a common language for payments context across different networks, helping banks avoid custom rules for every integration. Banks and payment providers can then connect stablecoin settlement with traditional bank accounts or tokenized deposits through the relevant funding, redemption, and payout arrangements.

Coastal Financial Corporation is building a cross-border payment corridor on Tempo. In the described design, a sending bank performs KYC/AML screening, sends Coastal the payment instructions, and funds a wallet through a stablecoin issuer. Stablecoins move to Coastal’s wallet on Tempo; Coastal then redeems them, confirms the payment, and credits the recipient’s account in USD. The story describes infrastructure being built, rather than measured live results. It illustrates how banks can change the settlement layer while retaining existing messaging, compliance, and confirmation processes.

Compliance, custody, and confidentiality determine institutional fit

Stablecoin interoperability encompasses a wide range of controls and operational requirements that institutions already rely on, including:

• Transaction monitoring: Providing sufficient transaction data and context to support ongoing monitoring for unusual activity and potential financial crimes

• Sanctions screening: Ensuring transfers fit screening standards against applicable sanctions and flagging transactions for holds, rejections, or escalations when appropriate

• Institutional custody support: Verifying that the selected custody provider supports existing access controls, recovery processes, and multiparty authorization workflows

• Auditability: Making it easier to reconcile transactions across networks and maintain clean internal records that support a bank’s regulatory reporting and audit processes

How Tempo supports stablecoin settlement alongside bank systems

Tempo provides a stablecoin settlement layer that banks can integrate with their existing infrastructure. Transfer memos can carry short payment references that applications map to their internal records, supporting ISO 20022-compatible reconciliation workflows. The memo is a fixed 32-byte field, rather than a complete ISO 20022 message. Memos are public transaction data, so sensitive customer and compliance details should stay in controlled systems. Banks and their providers remain responsible for custody, screening, reconciliation, and fiat funding or delivery.

Learn more about how Tempo’s payments-first settlement layer can help you integrate with stablecoins without compromising your compliance or reconciliation systems.

FAQ

Are bank-issued stablecoins regulated or insured like bank deposits?

Not necessarily. The regulation surrounding bank-issued stablecoins depends on three factors: their legal structure, the issuing entity, and the jurisdiction they’re issued and used. Just because a bank issues a stablecoin doesn’t mean it automatically carries federal deposit insurance or the same legal standing as a traditional commercial bank deposit.

Who can redeem a bank-issued stablecoin?

Redemption rights differ between bank-issued stablecoins based on the issuer’s model and the terms of the digital asset. Some models may restrict direct redemption to eligible institutional or wholesale counterparties, while others may provide broader access.