> For the complete documentation index, see [llms.txt](https://docs.velafi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.velafi.com/guides/stablecoin-payments/get-wallet-list.md).

# Get Wallet List

This API is used to retrieve a list of available stablecoin wallets under a specific merchant account.\
Merchants can use this interface to obtain wallet information before creating payment links or performing fund management operations.

Typical use cases include:

* Selecting a wallet prior to initiating a payment flow
* Wallet configuration and validation
* Managing multiple wallets under a merchant account

#### Endpoint Information

* **Request Header:** `X-BH-TOKEN: ******`
* **Request Header: `Content-Type:`**` ``application/json`
* **Request Method:** `GET`
* **Request Path:** `/v2/payments/wallets`
* **Authorization Required:** Yes

### Request Parameters

The request query should include the following parameters:

* merchantId: The merchant ID.

### Request Example

```
GET /openapi/v2/payments/wallets?merchantId=3
```

### Response Parameters

The response will contain the following parameters:

* wallets: List of wallets under the merchant account.
* walletId: Wallet identifier.
* walletName: Wallet name.

### Response Example

```json
{
  "code": 200,
  "msg": "SUCCESS",
  "data": {
    "wallets": [
      {
        "walletId": 1,
        "walletName": "Primary Wallet"
      }
    ]
  }
}
```

### Notes

* The `merchantId` must correspond to a valid merchant account.
* If multiple wallets are configured for the merchant, all available wallets will be returned in the `wallets` list.
* The returned `walletId` can be used when creating payment links or performing wallet-related operations.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.velafi.com/guides/stablecoin-payments/get-wallet-list.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.