---
title: "Wallets at an exchange or custodian (hosted)"
description: "Understand why you declare a hosted crypto wallet before creating a transfer, what can happen without a declaration, and how Nodu checks it."
url: "/guides/transfers/travel-rule/wallets-at-an-exchange-or-custodian/"
index: "/llms.txt"
---

# Wallets at an exchange or custodian (hosted)

A wallet at an exchange or custodian (hosted) is a crypto wallet that a business holds for its owner. The customer owns the funds, but the business controls the crypto wallet. The customer therefore cannot give the proof of control used for [self-custody wallets](/guides/transfers/travel-rule/self-custody-wallets/index.md).

For a hosted crypto wallet, Nodu exchanges the originator's and beneficiary's details with the exchange or custodian through a Travel Rule network. The network connects the businesses so they can check the details against their customer records.

## Why you declare the originator before the transfer

When crypto comes from an exchange or custodian, that business may send Nodu a Travel Rule request before the crypto arrives. Nodu can then check the request for your customer. Not every exchange or custodian sends one, so your integration should not depend on receiving it.

Declaring the originator's crypto wallet before you create the transfer gives Nodu information to make the check itself. You identify who sends the crypto and say that an exchange or custodian holds the sending crypto wallet. Identify that business too when you know it: the crypto wallet's address alone does not always reveal who holds it.

This applies even when the customer sends from their own exchange account. Nodu already knows the customer's identity, but still needs to establish where the sending crypto wallet is held.

## What happens without a declaration

For incoming crypto, Nodu follows this sequence:

1. **Check for an incoming Travel Rule request.** If the sending exchange or custodian has supplied one and Nodu confirms it, the crypto passes the Travel Rule check without information from you.
2. **Establish the originator and custody.** Without a declared originator, Nodu treats the customer as the sender. If the customer's crypto wallet has no custody declaration, Nodu tries to identify the exchange or custodian through a Travel Rule network.
3. **Apply the self-custody checks if custody remains unknown.** Nodu can ask the customer to prove control of the crypto wallet. The transfer then waits in `info_required`.

For crypto sent from an exchange or custodian, this can leave the customer with a proof request they cannot complete. Declare the hosted crypto wallet in advance to avoid relying on this fallback. If a transfer is already waiting for proof, see [While the transfer waits](/guides/transfers/handle-a-transfer-that-needs-action/index.md#while-the-transfer-waits).

Someone else's crypto wallet needs an originator declaration even when it is self-custody: see [Declare who sends incoming crypto](/guides/transfers/external-accounts/declare-the-originator-of-a-crypto-funding/index.md).

## How Nodu checks the declaration

A declaration tells Nodu where you expect the crypto wallet to be held. Nodu still checks it with the exchange or custodian through a common Travel Rule network.

The check can fail if the business cannot be reached, does not confirm the crypto wallet, or gives an answer that does not meet Nodu's compliance requirements. If Nodu refuses the verification, the transfer moves to `error`: see [Track and cancel a transfer](/guides/transfers/track-a-transfer/index.md#errors).

In the sandbox, a crypto wallet declared as hosted is always confirmed. See [Simulate crypto wallet verification](/guides/sandbox/simulate-wallet-verification/index.md) for testing the self-custody proof flow.

## Declare the sending crypto wallet

[Declare who sends incoming crypto](/guides/transfers/external-accounts/declare-the-originator-of-a-crypto-funding/index.md) shows the API requests for the customer's own hosted crypto wallet and for someone else's crypto wallet. It also explains how to reuse an external account registered earlier.

## Receive a payout at a hosted crypto wallet

For a payout, Nodu sends the Travel Rule request and sends the crypto only after the check passes. Declare where the destination crypto wallet is held before creating the transfer, so Nodu can contact the exchange or custodian.

[Find destinations and requirements](/guides/transfers/external-accounts/destinations-and-requirements/index.md#create-the-external-account) shows how to register the destination. Include the [crypto wallet custody fields](/guides/transfers/reference/external-account-requirements/index.md#crypto-wallet-custody) when you create the external account. For an account registered earlier, see [Declare an existing crypto wallet](/guides/transfers/external-accounts/first-party-and-third-party-accounts/index.md#declare-an-existing-crypto-wallet).

## Find an exchange or custodian

The reference calls an exchange or custodian a VASP, which means virtual asset service provider. [List VASPs](/api/tag/vasps/get-v1-vasps.md) returns Nodu's directory of VASPs. Each entry has an `id` and a `name`.

- **Search by name.** Send `search` with a part of the name. The search ignores upper and lower case.
- **Use the entry.** In your interface, you can let the customer choose from the names. Send the `id` of the chosen entry as `vaspId`.
- **Read more entries.** The list is paginated: see [Pagination](/guides/api-basics/pagination/index.md).
- **Look up a stored `vaspId`.** Send `id` to get one entry. Use this to show the name of the `vaspId` that an external account already has. This lookup can also return an exchange or custodian that no longer appears in the list. Do not offer such an entry for selection.

Nodu accepts only a `vaspId` that the list returns when you call it without `id`. For another value, Nodu refuses the request with a [validation error](/guides/api-basics/errors-and-rule-codes/index.md#validation-errors) on `accountRequisites.vaspId`.

When the exchange or custodian is not in the directory, send `walletType=hosted` without `vaspId`.
