> 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/fund-collection.md).

# Fund Collection

This API is used to consolidate multiple stablecoin payment records generated within the system into the merchant’s **Primary Wallet** for settlement and fund management purposes.

The collection process is an **internal fund operation** and does not involve on-chain transactions or additional blockchain transfers.

* Consolidated funds are reflected in the **Primary Wallet balance**
* Sub wallets are used solely for accounting categorization and do not hold on-chain assets
* Suitable for centralized fund management and settlement scenarios

***

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

***

### Request Parameters

The request body should include the following parameters:

* merchantId: Merchant ID.
* currency: Stablecoin type (supported values: `USDT`, `USDC`).
* walletId: Wallet ID.

***

### Request Example

```json
{
  "merchantId": 1,
  "currency": "USDT",
  "walletId": 1
}
```

***

### Response Parameters

The response will contain the following parameters:

* code: Response status code.
* msg: Response message.
* data: No data returned for this operation.

***

### Response Example

```json
{
  "code": 200,
  "msg": "SUCCESS",
  "data": null
}
```

***

### Notes

* This operation performs **internal balance consolidation** within the platform and does **not trigger any blockchain transaction**.
* Funds recorded under sub wallets are consolidated into the merchant’s **Primary Wallet** for settlement.
* The specified `walletId` must belong to the merchant account.


---

# 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.velafi.com/guides/stablecoin-payments/fund-collection.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.