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

# Verify your tokens

> Register your own token contracts as verified for your DFNS organization, so they count as legitimate assets in wallet search and KYT screening.

DFNS maintains a list of verified tokens. Any other token is unverified: anyone can mint a token under a legitimate name or symbol, so DFNS treats unverified tokens with caution. When you issue or use a token that DFNS has not verified, such as your own stablecoin or a less common asset, register it as verified for your organization.

A token you register is verified for your organization only. It counts as verified wherever DFNS separates verified from unverified assets:

* **Wallet balances**: your wallets' balances of the token are marked verified, including balances that existed before you registered it, so wallet search and asset filters treat it as a legitimate asset.
* **KYT screening**: transfers of the token are screened when your [Chainalysis](/integrations/aml-kyt/chainalysis) or [Elliptic](/integrations/aml-kyt/elliptic) integration is set to screen **Verified tokens only**.

Supported networks: EVM networks (ERC-20), Solana (SPL and Token-2022), and Tron (TRC-20).

## Prerequisites

* Token management enabled for your organization. If **Manage Tokens** shows that custom token management is not enabled, contact DFNS.
* The `Registry: Verified Assets` permissions: `Read` to view the list, `Create` to add a token, `Delete` to remove one (see [Roles and permissions](/core-concepts/roles-and-permissions#registry)).

## Add a token

<Steps>
  <Step title="Open Manage Tokens">
    Navigate to **Settings** and open **Manage Tokens**.

    <Frame>
      <img src="https://mintcdn.com/dfns-6d8c7466/5mhcia3REP59DyiV/images/auto/verifying-tokens-1.png?fit=max&auto=format&n=5mhcia3REP59DyiV&q=85&s=f2a3aeaf5c06363691db17576db9df00" alt="Settings page with the Manage Tokens card highlighted" width="2688" height="2232" data-path="images/auto/verifying-tokens-1.png" />
    </Frame>
  </Step>

  <Step title="Add the token">
    The page lists the tokens your organization registered. Click **Add Token**.

    <Frame>
      <img src="https://mintcdn.com/dfns-6d8c7466/5mhcia3REP59DyiV/images/auto/verifying-tokens-2.png?fit=max&auto=format&n=5mhcia3REP59DyiV&q=85&s=1cd1b3c338a1122a9361fdc5ab8d9a7e" alt="Manage Tokens page listing registered tokens, with the Add Token button highlighted" width="2688" height="1672" data-path="images/auto/verifying-tokens-2.png" />
    </Frame>
  </Step>

  <Step title="Enter the network and contract address">
    In the **Add Token** panel, select the **Network** and paste the token's **Contract Address** (the mint address on Solana). Click **Add Token** and 🔑 sign the request.

    <Frame>
      <img src="https://mintcdn.com/dfns-6d8c7466/5mhcia3REP59DyiV/images/auto/verifying-tokens-3.png?fit=max&auto=format&n=5mhcia3REP59DyiV&q=85&s=59e11c53eed453c1be2d611e3e9cf7b3" alt="Add Token form with a network and contract address filled in" width="2688" height="1672" data-path="images/auto/verifying-tokens-3.png" />
    </Frame>
  </Step>
</Steps>

DFNS reads the token's name and symbol from the contract on chain. The token is rejected when:

* DFNS already verifies it. There is nothing to register.
* your organization already registered it on this network.
* the contract does not declare a name on chain.

<Check>
  The token now appears in the list with its name, symbol, network, contract address, and the date it was added.
</Check>

## Remove a token

Open the token's action menu in the list, click **Delete**, and confirm. The token falls back to the DFNS verification status: it stays verified only if DFNS verifies it.

<Frame>
  <img src="https://mintcdn.com/dfns-6d8c7466/5mhcia3REP59DyiV/images/auto/verifying-tokens-4.png?fit=max&auto=format&n=5mhcia3REP59DyiV&q=85&s=a9b6f3ade505a0f39f09e1c597850fb7" alt="Token action menu with Delete highlighted" width="2688" height="1672" data-path="images/auto/verifying-tokens-4.png" />
</Frame>

## Require approval for token changes

Registering a token decides which assets your organization and your screening treat as legitimate. To require approval, or to block changes, create [user-action policies](/api-reference/policies#useraction-activity) on `CreateVerifiedAsset` and `DeleteVerifiedAsset`. A change held by a policy applies once the approval completes.

## Related guides

<CardGroup cols={2}>
  <Card title="Security best practices" icon="lock" href="/guides/security-best-practices">
    How verified assets protect you from spam tokens
  </Card>

  <Card title="Manage wallets" icon="wallet" href="/guides/manage-wallets">
    Browse wallet assets and history
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.