> ## Documentation Index
> Fetch the complete documentation index at: https://cts-docs.cosmos.network/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> How the Cosmos Tokenization Suite's capabilities and applications fit together for a bank.

A tokenized deposit is a representation of a client's deposit balance, held on a
digital ledger that the Cosmos Tokenization Suite (CTS) runs alongside the bank's
existing core. CTS enables banks to issue these deposits on a digital
ledger of their choosing and synchronize them with existing cores. It also
enables interoperability with digital assets on other blockchain networks.

CTS offers tokenization applications built on these capabilities:
24/7 payments, treasury management, and programmable asset movement.

The design assumes that the bank keeps the systems it already runs. The core banking platform remains the record of record, and CTS operates
alongside it.

## Three solutions

CTS comprises three solutions that share a common technology layer. A customer buys the solution that matches the problem.

| Solution                               | What it does                                                         | Who it is for                                                        |
| -------------------------------------- | -------------------------------------------------------------------- | -------------------------------------------------------------------- |
| [Issuance](/cts-issuance/overview)     | Issue, hold, and transfer tokenized deposits                         | Commercial banks                                                     |
| [Settlement](/cts-settlement/overview) | Operate tokenized settlement across a network of member institutions | FMIs, clearing houses, payment and messaging networks, central banks |
| [Interop](/cts-interop/overview)       | Connect an existing ledger to other DLT networks over IBC            | Institutions already running their own ledger                        |

Most of this documentation covers Issuance, which is the solution furthest
along. Settlement and Interop are documented at overview level for now.

## Three capabilities

<CardGroup cols={3}>
  <Card title="Issue" icon="coins">
    Tokenized deposits issued on a digital ledger running alongside the bank's
    existing core, on Cosmos EVM or on the bank's own ledger.
  </Card>

  <Card title="Synchronize" icon="refresh-cw" href="/banking-core-integrations/overview">
    Continuous synchronization with the existing core, so tokenized balances and
    core balances stay in agreement.
  </Card>

  <Card title="Interoperate" icon="arrow-left-right" href="/ibc/overview">
    Movement of value to counterparties and digital assets on other blockchain
    networks.
  </Card>
</CardGroup>

### Issue

The tokenized deposit mirrors the balance on the core, so the deposit remains a
deposit and continues to be held and reported on the core.

The bank chooses what that digital ledger runs on. The Cosmos EVM ledger is the
recommended path and the fastest to deploy. CTS also fully supports a bank
that has its own ledger or must operate one.

See [Digital Ledger Support](/digital-ledger-support/overview).

### Synchronize

CTS connects to the bank's existing core banking platform, including
Fiserv, Jack Henry, ISO 20022 file drops, and others. Tokenization draws from the
core ledger, and balance changes are written back to it. This ensures the two
stay reconciled without manual intervention.

See [Banking Core Integrations](/banking-core-integrations/overview).

### Interoperate

Tokenized deposits are only useful if value can reach counterparties. CTS
uses Inter-Blockchain Communication to exchange transfer messages with other
banks' tokenization infrastructure. It also integrates with digital asset
custody providers to hold and move assets on external settlement networks.

See [Inter-Blockchain Communication](/ibc/overview) and
[Digital Asset Custody](/digital-asset-custody/overview).

## Three applications

These capabilities are the foundation. The applications built on them are what
a bank actually deploys.

<CardGroup cols={1}>
  <Card title="24/7 Payments" icon="clock" href="/digital-asset-custody/settlement-for-payments">
    Client payments clear continuously between banks, with interbank obligations
    settled on demand or on a schedule using a mutually agreed settlement asset.
  </Card>

  <Card title="Treasury Management" icon="wallet" href="/digital-asset-custody/treasury-and-movement">
    The bank's own assets rebalanced across networks and accounts under policy.
  </Card>

  <Card title="Programmable Asset Movement" icon="workflow" href="/digital-asset-custody/treasury-and-movement">
    Transfers executed in response to conditions rather than manual instruction.
  </Card>
</CardGroup>

## Next

* [Architecture](/what-is-cts/architecture) for how the layers fit together
* [Components](/what-is-cts/components) for what each part does
* [Use Cases](/use-cases/overview) for the asset types CTS supports