Read more about trusted sources in the user guide.
Types of deposits
Deposits landing in your wallets fall into two categories:- Known deposit — from a recognized source wallet.
- Unknown deposit (dust, spam, etc.) — from unrecognized addresses; may include address poisoning, dusting attacks, and similar activity.
How to attribute a deposit
Three options are available:Attribute a known deposit
Field guidance:
originatorCountry&originatorName— provide the actual person or entity that sent the funds, not the financial institution.sourceWalletType:CUSTODIAL— the wallet owner does not hold the private key; a third party does (e.g., Binance, Coinbase, Kraken, BitGo).SELF_HOSTED— the wallet owner holds the private key (e.g., MetaMask, Trust Wallet, Ledger, Trezor, Electrum, Exodus, Phantom).
Trusted sources
Trusted sources are addresses for which attribution is applied automatically on future deposits. Create trusted sources in the Anchorage Digital dashboard — this is not currently available via API. Trusted sources are recommended for addresses you expect to receive recurring or multiple deposits from. If Anchorage Digital cannot make an attribution with available data, the client is responsible for providing the required information via API before assets are accessible in the wallet.Automatic attribution by Anchorage Digital Bank
Crypto deposits from VASPs over $2,100 (the travel rule reporting threshold) are automatically attributed if Anchorage Digital receives a travel rule message from an active TRUST network participating VASP. This process is not instant — use the deposit attribution API if faster access to funds is needed. If automatic attribution fails, one or more of your authorized users will be notified by email. Follow the step-by-step instructions in the web dashboard to attribute pending deposits.Deposit webhooks
Use webhooks to get notified when funds arrive in your wallet. Alternatively, poll for pending attributions via the list deposit attributions endpoint.Spam and unknown deposits
Deposits identified as spam or dusting can be attributed asSPAM, preventing unwanted balances from appearing in account statements or trading balances. If these balances need to be removed, Anchorage Digital will coordinate sweeping the assets into a sanctioned Anchorage-owned wallet.
API reference
Deposit status values
status | Description |
|---|---|
PENDING | Deposit landed after Anchorage Digital auto-attribution attempt. Deposits marked spam by Anchorage will not appear here. |
INITIATED | Deposit detected; Anchorage Digital attempting automatic spam attribution. Moves to PENDING if auto-attribution fails. |
ATTRIBUTED | Terminal state — happy path. |
UNDER_REVIEW | Attribution completed but triggered a sanctions hit pending compliance clearance. |
BLOCKED | Deposit confirmed as a true sanctions hit. |
NON_ATTRIBUTABLE | Semi-terminal state applied in specific edge cases. |
Attribution type values
attributionType | Description |
|---|---|
MANUAL_STAFF | Attributed by Anchorage Digital staff using previously known source wallet information. |
MANUAL_CLIENT | Attributed by the wealth manager via web dashboard. |
CLIENT_API | Attributed by the wealth manager via API key. |
AUTOMATIC | Attributed automatically via travel rule information from the originating VASP. |
SPAM | Attributed as spam by Anchorage Digital or the wealth manager. |
TRUSTED_SOURCES | Attributed automatically using previously collected information for a designated trusted source. |

