> For the complete documentation index, see [llms.txt](https://docs.b2core.b2broker.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.b2core.b2broker.com/back-office-guide/finance/deposit-wallets.md).

# Deposit wallets

On this page, you can view a list of client cryptocurrency wallets.

To view the wallets of a particular client, go to the [Finance tab](/back-office-guide/clients/general/finance-tab.md) on the client details page, and then select **Deposit wallets**.

The following information is provided about each deposit wallet:

**ID**

The identifier of a wallet in the system.

***

**Client ID**

The identifier of a wallet owner.

***

**Client**

The name of a wallet owner.

***

**Tags**

The tags assigned to a wallet owner that are used to sort the list of wallets displayed to [Back Office administrators](/back-office-guide/system/users.md).

***

**Address**

The public wallet address.

***

**Destination tag**

Applicable only for certain currencies (XRP, XLM, BNB, and XEM).

***

**Method**

The link to the details of a [method](/back-office-guide/system/deposit-system.md#deposit-methods) used to deposit funds.

***

**Currencies**

The currencies enabled for a wallet.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.b2core.b2broker.com/back-office-guide/finance/deposit-wallets.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.