Skip to content

Reference stack

Launch a stablecoin

A reference architecture for issuing and operating a stablecoin, covering legal structure, reserves, issuance, custody, networks, liquidity, compliance, assurance and redemption.

Financial institutionsPayment companiesStablecoin issuers

Intended audience and markets

Audience

Financial institutionsPayment companiesStablecoin issuers

Markets

Jurisdiction-specific

Infrastructure layers

01

Legal and regulated structure

Required

Define issuer, instrument, reserve, customer and distribution model.

Selection criteria

  • Applicable issuer regime
  • Rights of holders
  • Redemption and insolvency treatment
02

Reserve banking and custody

Required

Hold reserve assets and operational digital assets with appropriate controls.

Selection criteria

  • Eligible reserve assets
  • Segregation and bankruptcy treatment
  • Custody and access controls
03

Mint, burn and ledger infrastructure

Required

Control issuance, redemption, supply and operational permissions.

Selection criteria

  • Authorisation model
  • Supply reconciliation
  • Emergency and upgrade controls
05

Liquidity and distribution

Required

Support exchange, market-making and redemption liquidity.

Selection criteria

  • Market-maker counterparties
  • Venue and region coverage
  • Redemption liquidity
06

Compliance, assurance and reporting

Required

Screen activity, monitor supply and provide evidence over reserves and operations.

Selection criteria

  • Wallet screening and sanctions
  • Reserve reporting and attestations
  • Audit trail and incident response

Implementation sequence

  • Legal and regulated structure
  • Reserve banking and custody
  • Mint, burn and ledger infrastructure
  • Networks and interoperability
  • Liquidity and distribution
  • Compliance, assurance and reporting

Regulatory considerations

  • Launching a stablecoin requires jurisdiction-specific legal analysis, governance, capital and operating controls.
  • Provider selection does not establish compliance with MiCA, US state or federal law, or any other issuer regime.

Technical considerations

  • Reconcile bank reserves, internal issuance ledger and onchain supply continuously.
  • Use independent permissions, key controls, monitoring and emergency procedures.
  • Plan orderly redemption under stress and network outages.

Questions to ask providers

  • Which legal entity contracts for each service and in which jurisdictions?
  • Which responsibilities remain with the product operator rather than the provider?
  • What are the implementation, approval, testing and migration timelines?
  • How are incidents, exits, data portability and business continuity handled?
  • What legal claim does the holder have and against which entity?
  • Who can mint, freeze, burn, upgrade and redeem?

What this stack does not cover

  • This stack does not constitute a legal, accounting or reserve policy.

Related stacks

Reviewed on 2026-07-07.

Provider options are examples of infrastructure roles, not endorsements or a guarantee of suitability, availability or regulatory compliance. Confirm requirements for your product with each provider and qualified advisers.