---
title: "Self-custody wallets (unhosted)"
description: "Learn when Nodu asks a customer to prove that they control their own self-custody wallet, how you handle the transfer state info_required, and what Nodu remembers."
url: "/guides/transfers/travel-rule/self-custody-wallets/"
index: "/llms.txt"
---

# Self-custody wallets (unhosted)

A self-custody wallet (unhosted) is a crypto wallet that its owner controls. Knowing the customer's identity does not establish that they control a particular crypto wallet. When the customer uses their own self-custody wallet in a transfer, Nodu can ask for proof of that control.

```mermaid
sequenceDiagram
    participant Customer
    participant You as Your system
    participant Nodu
    Note over Customer,Nodu: The transfer uses the customer's own self-custody wallet,<br/>with no earlier proof of ownership
    Note over Nodu: The funds arrive or are reserved,<br/>and Nodu checks the crypto wallet
    Nodu-->>You: v1.transfer.info_required
    You->>Nodu: Read the requirement<br/>GET /v1/transfers/{transferId}
    Nodu-->>You: requirements[]: action verify_wallet_ownership,<br/>side, url
    You->>Customer: Show which crypto wallet needs proof<br/>and open the url
    Customer->>Nodu: Prove ownership on Nodu's page:<br/>a test transaction or a signed message
    Note over Customer,Nodu: A failed attempt can be repeated at the same url.
    Nodu-->>You: v1.transfer.in_review
    You->>Nodu: Read the transfer again<br/>GET /v1/transfers/{transferId}
    Note over You,Nodu: If the other side also needs proof, its requirement<br/>can appear without a new event: repeat for it.
    Nodu-->>You: v1.transfer.funds_received
    Note over Customer,Nodu: The transfer continues. Nodu remembers the proof<br/>for later transfers with the same crypto wallet.
```

## Which crypto wallets Nodu checks

Nodu checks every crypto wallet of the customer that takes part in a transfer and is not held at an exchange or custodian. The crypto wallet can be on either side of the transfer:

- **The source**: the crypto wallet that the customer sends crypto from, for example in an off-ramp.
- **The destination**: the crypto wallet that receives the payout, for example in an on-ramp.

For incoming crypto from the customer's own self-custody wallet, leave out `source.externalAccountId`. For a payout, [register the destination account](/guides/transfers/external-accounts/destinations-and-requirements/index.md#create-the-external-account). If an exchange or custodian holds the crypto wallet, see [Wallets at an exchange or custodian (hosted)](/guides/transfers/travel-rule/wallets-at-an-exchange-or-custodian/index.md).

If someone else sends the crypto, [declare the originator](/guides/transfers/external-accounts/declare-the-originator-of-a-crypto-funding/index.md), including when their crypto wallet is self-custody.

## When Nodu asks for proof of ownership

Nodu makes the check during its review of the transfer, after the funds arrive. Nodu asks for proof when all of these are true:

- The crypto wallet is the customer's own.
- You did not declare the crypto wallet with `walletType=hosted`.
- For crypto that the customer sends: Nodu has received no Travel Rule request for it from the exchange or custodian that sent it.
- Nodu cannot establish through a Travel Rule network that an exchange or custodian holds the crypto wallet.
- Nodu holds no earlier proof from this customer for this crypto wallet.

Whether Nodu asks also depends on the Nodu entity you integrate with and on the amount of the transfer. Build this flow even if your first test transfers need no proof.

## Two ways to prove ownership

The customer proves ownership on a page that Nodu provides. The customer uses one of two methods:

| Method | What the customer does |
|---|---|
| A test transaction | The customer sends a small amount of crypto from the crypto wallet. After a successful verification, Nodu sends the amount back, minus the network fee of that transaction. |
| A signed message | The customer signs a message with the crypto wallet. |

The customer submits the proof directly on Nodu's page.

## Handle the `info_required` state

Follow [Handle a transfer that needs action](/guides/transfers/handle-a-transfer-that-needs-action/index.md) to read every pending requirement, open the customer's verification page and check progress after they return.

### While the transfer waits

[Action handling](/guides/transfers/handle-a-transfer-that-needs-action/index.md#while-the-transfer-waits) explains what to do if the customer cannot complete the proof. A failed attempt can be repeated; a final refusal moves the transfer to `error`.

## What Nodu remembers

Nodu stores an accepted proof for the customer and the address of the crypto wallet. The customer normally does not need to provide new proof for later transfers using the same crypto wallet.

- A proof does not cover another customer who uses the same crypto wallet.
- A proof does not cover another crypto wallet of the same customer.

## Next steps

- [Wallets at an exchange or custodian (hosted)](/guides/transfers/travel-rule/wallets-at-an-exchange-or-custodian/index.md): declare a crypto wallet that the customer does not hold themselves.
- [Track and cancel a transfer](/guides/transfers/track-a-transfer/index.md): every other state of a transfer.
- [Simulate crypto wallet verification in the sandbox](/guides/sandbox/simulate-wallet-verification/index.md): produce and resolve the requirement without a real proof.
