Skip to main content
Every account can receive crypto. You ask for deposit instructions for an asset, share the address with the sender, and the deposit lands in the account. Unlike a USD wire, an on-chain deposit isn’t usable the moment it arrives: it first clears deposit attribution, the step that identifies who sent it.

What’s available

How it works

1

Get instructions for an asset

GET /v4/accounts/{accountId}/deposit-instructions/{assetType} with the asset you want to receive. If the account has no address for that asset yet, one is created on this call. Share it with the sender.
2

The deposit lands and attribution opens

When funds arrive on-chain, a deposit attribution record is created in PENDING. The funds aren’t available while it’s pending.
3

Anchorage Digital tries to attribute it automatically

If the source address is already known, a trusted source you registered or an address attributed before, the deposit attributes on its own with attributionType set to AUTOMATIC or TRUSTED_SOURCES.
4

Otherwise, you supply the originator

PATCH /v4/deposit-attributions/{depositTransactionId} with the originator’s name, country, and wallet type. The record moves to UNDER_REVIEW.
5

Review resolves it

Review ends in ATTRIBUTED, which releases the funds, or BLOCKED. Poll GET /v4/deposit-attributions/attributions to follow it, or watch for the DEPOSIT transaction to move from PENDING to POSTED in transactions. Webhooks are coming soon.
Attribution applies to crypto only. For USD, see USD deposits.

Attribution status

A deposit marked as spam also reads ATTRIBUTED, but its funds never become available. Check attributionType alongside status before you treat a deposit as usable.
attributionType says how the deposit resolved: AUTOMATIC, TRUSTED_SOURCES, CLIENT_API (you attributed it through this API), MANUAL_CLIENT (through the web dashboard), MANUAL_STAFF, or SPAM. It’s null until the deposit is attributed.

Integration steps

Step 1: Get deposit instructions

GET /v4/accounts/{accountId}/deposit-instructions/{assetType} assetType is a code from GET /v4/asset-types. In the sandbox the codes are testnet assets, so check the list rather than guessing: BTC_S for Bitcoin Signet and ETHHOODI for Ethereum Hoodi, for example. An asset your organization doesn’t support returns 404.
assetType and networkId aren’t always the same value. A token settles over its chain’s network, so a USDC deposit on Ethereum returns the Ethereum network ID.
The same address is returned on every later call for that account and asset. A returned address doesn’t mean a deposit to it is usable right away. It still clears attribution.

Step 2: List deposit attributions

GET /v4/deposit-attributions/attributions Lists every deposit attribution in your organization, oldest first. Filter with status, accountIds, a startDateTime and endDateTime range on when attribution started, or an attributedAtStartDateTime and attributedAtEndDateTime range on when it resolved. Page with limit and after.
depositTransactionId is the 32-character hex ID of the DEPOSIT transaction. accountId can be null when the deposit isn’t tied to an account.

Step 3: Attribute a deposit

PATCH /v4/deposit-attributions/{depositTransactionId} Only a PENDING attribution can be attributed. Anything else returns 409 Conflict. On success the status moves to UNDER_REVIEW and attributionType becomes CLIENT_API.

Step 4: Mark a deposit as spam

POST /v4/deposit-attributions/{depositTransactionId}/spam Only a PENDING attribution can be marked as spam. The record moves to UNDER_REVIEW, then ATTRIBUTED with attributionType: SPAM, and the funds are never made available. No body is needed, but the write headers are.