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

# Unsupported assets and wrong networks

> Understand why a deposit isn't showing and how recovery works for unsupported assets.

If an asset isn't supported, or was sent on the wrong network, it won't show a balance because Anchorage Digital doesn't scan for it. This guide explains why, and how recovery works.

## Why a deposit isn't showing

If an asset isn't supported or enabled for your organization, Anchorage Digital doesn't scan the blockchain for it, so no balance appears. This is different from a pending-attribution hold, where the deposit does show but the funds are held until you attribute the sender. See [Deposit attribution](/knowledge-base/platform/users/receiving-assets#deposit-attribution).

## Recovering an unsupported or wrong-network deposit

Share the receiving address and the on-chain transaction link with your client experience team so the asset team can investigate.

If the asset isn't supported, the asset team may be able to temporarily enable it and rescan to surface the balance, then return the funds to the sender. Outcomes depend on the asset and network.

<Warning>
  Some deposits—especially assets sent on the wrong network or unsupported variants—may be unrecoverable. Confirm both the asset and the network before sending.
</Warning>

To have an asset or network supported going forward, see [Requesting asset support](/knowledge-base/platform/users/asset-support-requests).
