StableNexus
Docs

What It Is and How It Works

Tokenized deposits are bank-liability instruments with explicit create, move, return, recredit, and redemption semantics.

What the instrument is

A tokenized deposit is a recorded representation of a bank liability under an issuing-institution programme. It is neither a reserve-backed stablecoin nor a tokenized security, even when those neighbouring products interact with the same treasury or settlement workflow.

The public description covers how the instrument is created, how it moves inside or across institutions, what controls must pass before release, and how return, recredit, or redemption closes the obligation.

Operating modes

  • Same-bank treasury movement where the issuing institution controls both the originating and destination balance context.
  • Cross-bank coordination where a receiving institution must accept and credit the movement under the agreed rules.
  • Tokenized-asset cash-leg support where the deposit programme provides the governed payment leg for a separate asset workflow.

Create, move, and close sequence

  1. Admit the institution, client, or treasury participant into the programme.
  2. Recognize funding and confirm the control-account or reservation state before creation.
  3. Create the deposit representation only when programme and liability checks pass.
  4. Evaluate release conditions before any same-bank, cross-bank, or cash-leg movement.
  5. Confirm destination acceptance or return-state evidence where the route requires it.
  6. Close through recredit, return, or redemption with reconciled evidence.