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

# Custody Integrations

> Connect custody providers for secure token settlement

## Overview

Custody integrations enable automated token settlement through institutional-grade custody providers. When vestings are ready for distribution, settlements are routed through your connected provider.

***

## Supported Providers

<CardGroup cols={2}>
  <Card title="Anchorage Digital" icon="shield-halved">
    Institutional-grade custody for digital assets with Anchorage Digital.
  </Card>

  <Card title="Fireblocks" icon="fire">
    Secure digital asset infrastructure for custody, transfer, and settlement.
  </Card>

  <Card title="Safe (Gnosis)" icon="vault">
    Multi-signature smart contract wallet for secure on-chain custody.
  </Card>

  <Card title="Off Platform" icon="building">
    Manage custody independently outside of the Toku platform. No API credentials required.
  </Card>
</CardGroup>

***

## Connecting a Provider

### During Onboarding

During the initial setup checklist, click **Connect** next to "Connect custody integration" on the dashboard. A modal presents the four provider options — select one to begin the setup flow.

### From Settings

<Steps>
  <Step title="Navigate to Integrations">
    Go to **Integrations** from the sidebar.
  </Step>

  <Step title="Select your provider">
    Click on the custody provider you want to connect.
  </Step>

  <Step title="Enter credentials">
    Provide the required API keys and configuration:

    * **Fireblocks**: API key, secret key, vault account ID
    * **Anchorage**: API key, organization ID
    * **Safe (Gnosis)**: Safe wallet address
    * **Off Platform**: No credentials required — select to acknowledge custody is managed externally
  </Step>

  <Step title="Test connection">
    For Fireblocks, Anchorage, and Safe, the system verifies connectivity before saving.
  </Step>

  <Step title="Configure settlement settings">
    Set default vault accounts, signing policies, and notification preferences.
  </Step>
</Steps>

***

## Settlement Flow by Provider

### Fireblocks

1. Settlement submitted to Fireblocks vault
2. Policy engine evaluates the transaction
3. Required signers approve in Fireblocks console
4. Transaction broadcasts on-chain

### Anchorage

1. Settlement submitted to Anchorage
2. Anchorage processes the transfer
3. Transaction confirms on-chain

### Safe (Multisig)

1. Transaction proposal created in Safe
2. Required signers approve the transaction
3. Final signer executes the transaction on-chain

***

## Related

<CardGroup cols={2}>
  <Card title="Settlements" icon="file-invoice-dollar" href="/tga/client/settlements">
    Learn about the full settlement process
  </Card>

  <Card title="Wallet Setup" icon="wallet" href="/tga/client/wallet-setup">
    Configure recipient wallets
  </Card>
</CardGroup>