> ## 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.

# Crypto deposits

> Get a deposit address for an account, receive funds on-chain, and clear deposit attribution so the funds become available.

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

| Action | Status | Notes |
| :- | :- | :- |
| Get deposit instructions | Live | The address is created on the first request for that account and asset |
| List deposit attributions | Live | |
| Attribute a deposit, or mark it as spam | Live | |

## 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](https://docs.anchorage.com/knowledge-base/platform/users/web-dashboard/trusted-sources) 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](https://docs.anchorage.com/knowledge-base/platform/developers/caas/caas-transactions.md). Webhooks are coming soon.

Attribution applies to crypto only. For USD, see [USD deposits](https://docs.anchorage.com/knowledge-base/platform/developers/caas/caas-deposits-usd.md).

## Attribution status

| Status | Meaning |
| :- | :- |
| `INITIATED` | Recorded, attribution hasn't started |
| `PENDING` | Waiting for attribution. Funds aren't available. |
| `UNDER_REVIEW` | Originator information was submitted and Anchorage Digital is reviewing it |
| `ATTRIBUTED` | Done. Funds are available, unless `attributionType` is `SPAM`. |
| `BLOCKED` | Review didn't clear the deposit. Funds stay unavailable. |
| `NON_ATTRIBUTABLE` | The deposit doesn't need attribution |

> [!WARNING]
>
> 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`.

```bash Request theme={null}
curl --request GET \
     --url https://api.anchorage-staging.com/v4/accounts/cb80459c-a930-444e-8f17-69ba9d0e122f/deposit-instructions/BTC_S \
     --header 'Api-Access-Key: {API Key}' \
     --header 'accept: application/json'
```

```json Response (200) theme={null}
{
  "assetType": "BTC_S",
  "rails": [
    {
      "railType": "BLOCKCHAIN",
      "networkId": "BTC_S",
      "walletAddress": "tb1qxy2kgdygjrsqtzq2n0yrf2493p83kkfjhx0wlh"
    }
  ]
}
```

| Field | Description |
| :- | :- |
| `railType` | `BLOCKCHAIN` for crypto. USD returns `WIRE`. |
| `networkId` | The network and environment the address is valid on |
| `walletAddress` | The address to send to. On chains with more than one address type, this is always the wallet address. |

`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.

> [!NOTE]
>
> 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`.

```bash Request theme={null}
curl --request GET \
     --url 'https://api.anchorage-staging.com/v4/deposit-attributions/attributions?status=PENDING&limit=25' \
     --header 'Api-Access-Key: {API Key}' \
     --header 'accept: application/json'
```

```json Response (200) theme={null}
{
  "data": [
    {
      "depositTransactionId": "0e2b2f9d8d104f1e960b28567255045f",
      "status": "PENDING",
      "sourceAddresses": ["0xb4Bb4E3D7f35ede58d99F5e2b8B04f7AC87f9c88"],
      "createdAt": "2026-11-04T11:01:07.953571Z",
      "attributedAt": null,
      "attributionType": null,
      "sourceWalletType": null,
      "originatorName": null,
      "originatorCountry": null,
      "notes": null,
      "accountId": "cb80459c-a930-444e-8f17-69ba9d0e122f",
      "blockchainTxId": "0x84ddb76708d570101db89fd27b1717484c54417c9f32c63052cdfac9a0bfc0a2",
      "assetType": "ETHHOODI"
    }
  ],
  "page": {
    "endCursor": null
  }
}
```

`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`.

| Field | Required | Description |
| :- | :- | :- |
| `originatorName` | Yes | Name of the sender |
| `originatorCountry` | Yes | Sender's country, ISO 3166-1 alpha-2 |
| `sourceWalletType` | Yes | `CUSTODIAL` (a third party holds the keys) or `SELF_HOSTED` (the sender holds the keys) |
| `notes` | No | Anything the reviewer should know |

```bash Request theme={null}
curl --request PATCH \
     --url https://api.anchorage-staging.com/v4/deposit-attributions/0e2b2f9d8d104f1e960b28567255045f \
     --header 'Api-Access-Key: {API Key}' \
     --header 'accept: application/json' \
     --header 'Api-Signature: {signature}' \
     --header 'Api-Timestamp: {unix epoch seconds}' \
     --header 'Idempotency-Key: 6f1e2a3b-4c5d-4e6f-8a9b-0c1d2e3f4a5b' \
     --header 'content-type: application/json' \
     --data '{
  "originatorName": "Jane Doe",
  "originatorCountry": "US",
  "sourceWalletType": "CUSTODIAL"
}'
```

```json Response (200) theme={null}
{
  "data": {
    "depositTransactionId": "0e2b2f9d8d104f1e960b28567255045f",
    "status": "UNDER_REVIEW"
  }
}
```

### 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.

```bash Request theme={null}
curl --request POST \
     --url https://api.anchorage-staging.com/v4/deposit-attributions/0e2b2f9d8d104f1e960b28567255045f/spam \
     --header 'Api-Access-Key: {API Key}' \
     --header 'accept: application/json' \
     --header 'Api-Signature: {signature}' \
     --header 'Api-Timestamp: {unix epoch seconds}' \
     --header 'Idempotency-Key: 7a2b3c4d-5e6f-4a5b-9c8d-1e2f3a4b5c6d'
```

```json Response (200) theme={null}
{
  "data": {
    "depositTransactionId": "0e2b2f9d8d104f1e960b28567255045f",
    "status": "UNDER_REVIEW"
  }
}
```


## Related topics

- [Crypto deposit](https://docs.anchorage.com/knowledge-base/porto/developers/move-money/deposit/crypto.md)
- [Deposit](https://docs.anchorage.com/knowledge-base/porto/developers/move-money/deposit.md)
- [Trusted sources & deposit attribution](https://docs.anchorage.com/knowledge-base/platform/users/trusted-sources-deposit-attribution.md)
