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

> Receive digital assets end to end: create and verify a wallet address, then track the incoming deposit.

Receiving a digital asset is a single end-to-end flow: create a wallet and deposit address, verify and share it, then track the incoming deposit. This page walks the full path. For the shared wallet and address mechanics, see [Deposit](/knowledge-base/porto/developers/move-money/deposit).

Once funds are inbound, `GET /v2/transactions` shows how much arrived, in what asset, from which address, and its on-chain status.

## Deposit flow

<Steps>
  <Step title="Create a wallet">
    Call `POST /v2/vaults/{vaultId}/wallets`, passing the `networkId` and a `walletName`.
  </Step>

  <Step title="Provision a deposit address">
    Call `POST /v2/wallets/{walletId}/addresses`, or list existing addresses with `GET` on the addresses endpoint.
  </Step>

  <Step title="Verify the address">
    Anchorage Digital signs every deposit address so you can confirm it was generated for your organization and hasn't been tampered with. Confirm both that the signature is valid and that the signed address matches the one you intend to share. See [Address verification](/knowledge-base/api-reference/address-verification).
  </Step>

  <Step title="Share the address and receive the asset">
    Share the verified address with the sender, who sends only the correct asset on the correct network.
  </Step>

  <Step title="Track the incoming deposit">
    Subscribe to [webhooks](/knowledge-base/porto/developers/webhooks/webhooks-overview) to be notified on arrival, then read the deposit with `GET /v2/transactions`:

    ```json theme={null}
    {
      "data": [
        {
          "id": "0e2b2f9d8d104f1e960b28567255045f",
          "transactionType": "DEPOSIT",
          "status": "SUCCESS",
          "assetType": "ETH",
          "amount": {
            "quantity": "5.0",
            "assetType": "ETH",
            "currentPrice": "3450.12",
            "currentUSDValue": "17250.60"
          },
          "blockchainTxId": "0x84ddb76708d570101db89fd27b1717484c54417c9f32c63052cdfac9a0bfc0a2",
          "sourceAddresses": ["0xb4Bb4E3D7f35ede58d99F5e2b8B04f7AC87f9c88"],
          "destinationAddresses": ["0x39d9f4640b98189540A9c0Ede2b8B04f7AC8aa21"],
          "dateTime": "2026-06-24T14:08:31.000Z",
          "vaultId": "1c920f4241b78a1d483a29f3c24b6c4c",
          "vaultName": "Treasury Vault",
          "walletId": "d24b424293c0d64c6194f52801b3d293"
        }
      ],
      "page": { "next": null }
    }
    ```
  </Step>
</Steps>

## Address integrity

Always verify a deposit address before use. The addresses API returns a signature and metadata that prove the address belongs to your vault and network. See [Address verification](/knowledge-base/api-reference/address-verification) for the V1 and V2 schemes.

## Failed and unrecognized deposits

Sending the wrong asset type to an Anchorage Digital address results in a failed deposit. An asset sent on a different chain than the address is not recognized. If the address is correct but the asset is unsupported—for example, an unsupported ERC-20 sent to an ETH address—contact [portohelp@anchorage.com](mailto:portohelp@anchorage.com).