# Receiving assets

To receive funds you share an account's deposit address. Because an address shown on screen could in principle be tampered with, Webapp 2.0 is built around **verifying the address on your Physical Security Device (PSD)** before you trust it.

## Get a deposit address

From the **Accounts list** or an **account's detail page**, click **Receive**. A window opens showing the account's identity (name, coin, ticker, network) and its full deposit address, with a warning recommending you verify the address on your PSD before using it.

You can copy the address at any time by selecting the text manually, but for anything that matters, verify it first.

## Verify on your device

{% stepper %}
{% step %}

### Click **Verify**

Webapp 2.0 starts talking to your device and shows an in-progress state with the steps to follow on the device.
{% endstep %}

{% step %}

### Compare the address

**The address stays on screen** throughout, deliberately, so you can compare it character-for-character against the address shown on your device. (Unlike other reviews, nothing covers the address while you verify.)
{% endstep %}

{% step %}

### Connect and unlock your device if needed

If no device is connected, you're simply invited to connect and unlock it. That's not an error.
{% endstep %}

{% step %}

### Use quick-copy after verification starts

Once verification starts, a **quick-copy** button becomes available for after you've confirmed the match.
{% endstep %}

{% step %}

### Approve on the device

When you approve on the device, the window confirms the review is complete. The address and copy button remain, and you can close the window.

> **Important:** If you try to close the window while a verification is still in progress, you'll be asked to confirm, so you don't cancel a security check by accident.
> {% endstep %}
> {% endstepper %}

## If verification doesn't complete

| Situation                   | What you'll see                                                                                            |
| --------------------------- | ---------------------------------------------------------------------------------------------------------- |
| The address can't be loaded | A message that the address couldn't be retrieved; close and try again, and contact support if it persists. |
| You cancel on the device    | A note that verification was cancelled; if the addresses didn't match, contact support.                    |
| Timeout or disconnection    | A note that the connection was lost; check the connection and try again.                                   |

After any of these you can simply retry the verification.

> **Note:** Reopening the window starts the flow fresh. If you closed it mid-verification, its state isn't carried over, to avoid any conflict.

Some networks need a one-time setup before an address can receive a given token. See [Network-specific guidance](/helpcenter2/when-network-behaviour-differs.md), for example token association on [Hedera](/helpcenter2/network-specific-guidance/hedera-hbar-and-hts-tokens.md) and token accounts on [Solana](/helpcenter2/network-specific-guidance/solana-spl-token-accounts.md).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.enterprise.ledger.com/helpcenter2/for-operators/receiving-assets.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.