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

# Limits

To meet compliance requirements, **VelaFi** applies different transaction and withdrawal limits based on the user’s region and verification level. This ensures that all users operate within the regulatory framework of their respective jurisdictions.

### 1. Default Merchant Wallet Limit

After successfully creating a **Merchant**, VelaFi automatically provisions a **crypto custody wallet** for that merchant.

* The wallet is activated upon creation.
* The default **monthly withdrawal limit** is **USD 10,000,000,000**.

### 2. Individual Users

VelaFi classifies individual users into two categories — **Consumers** and **Professionals**, each with different verification requirements and transaction limits.

#### Consumers

* Requires minimal documentation for verification.
* Quick review process, with lower transaction limits.
* Suitable for low-frequency or small-value payment use cases.

| Country       | Monthly Trade Limit (USD) |
| ------------- | ------------------------- |
| 🇲🇽Mexico    | 10,000,000,000            |
| 🇧🇷Brazil    | 10,000,000,000            |
| 🇨🇴Colombia  | 10,000,000,000            |
| 🇵🇪Peru      | 10,000,000,000            |
| 🇦🇷Argentina | 10,000,000,000            |

#### Professionals

* Requires more comprehensive identity and business documentation.
* Subject to enhanced compliance review.
* Suitable for high-volume merchants or users requiring higher operational limits.

(Limits vary by jurisdiction and are subject to approval by the VelaFi compliance team.)

### 3. Business Users (After Channel Activation)

For business merchants, limits are applied per country once the corresponding fiat payment channels are activated.

| Country           | Monthly Limit (USD) |
| ----------------- | ------------------- |
| 🇲🇽Mexico        | 10,000,000,000      |
| 🇨🇴Colombia      | 10,000,000,000      |
| 🇦🇷Argentina     | 10,000,000,000      |
| 🇧🇷Brazil        | 10,000,000,000      |
| 🇵🇪Peru          | 10,000,000,000      |
| 🇺🇸United States | 10,000,000,000      |
| 🇭🇰Hong Kong     | 10,000,000,000      |

***

### 4. Increasing Your Limit

If your business or operational needs exceed the default limit, you can request a **limit increase** by submitting additional compliance documentation (e.g., proof of source of funds, business licenses, or audited statements).\
\
[Upgrade Merchant Limit](https://app.gitbook.com/o/eeU0trgBle4zqs7IuQir/s/kcqCFfOVAdQbR1YyMZUY/~/changes/5/api-reference/merchant/upgrade-merchant-limit)\
\
or\
\
Contact Us to learn more about the limit upgrade process.

> **Email:** <contact@velafi.com>


---

# 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/limits.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.