> For the complete documentation index, see [llms.txt](https://stablemesh.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stablemesh.gitbook.io/docs/home/stablemesh-doc/zhong-wen-wen-dang/deposit.md).

# 充值加密货币

在为卡片充值之前，您需要先向 Stable Mesh 加密钱包存入资金。Stable Mesh 支持多条网络上的 USDT 和 USDC。

***

## 充值步骤

1. 进入**首页**仪表盘。
2. 点击 **+ 充值** 按钮。
3. 从下拉菜单中选择网络（例如选择 **SOL** 代表 Solana 网络）。
4. 复制页面显示的充值地址。
5. 从您的外部钱包向该地址发送 **USDT** 或 **USDC**。

> ✅ 链上交易确认后，您的余额将自动更新。确认时间取决于所选网络。

***

## 支持的网络

| 网络            | 代币        |
| ------------- | --------- |
| Solana（SOL）   | USDT、USDC |
| Arbitrum（ARB） | USDT、USDC |

> 可用网络可能有所增加——请在应用内查看网络下拉菜单获取最新选项。

***

## 银行转账充值

Stable Mesh 支持法币银行转账充值，无需加密货币钱包。

**支持的货币：**

| 货币     | 代码  |
| ------ | --- |
| 美元     | USD |
| 新加坡元   | SGD |
| 港元     | HKD |
| 阿联酋迪拉姆 | AED |
| 欧元     | EUR |
| 日元     | JPY |
| 英镑     | GBP |
| 澳元     | AUD |
| 巴西雷亚尔  | BRL |

如需发起银行转账充值，请直接联系我们，我们将提供转账说明及银行账户信息。

{% hint style="info" %}
联系我们安排银行转账充值：

* Telegram：[@stablemesh](https://t.me/stablemesh)
* 邮箱：<contact@stablemesh.io>
  {% endhint %}

***

## 充值后

余额显示在仪表盘**加密资产**模块后，即可为卡片充值。

➡️ 下一步：[为卡片充值](/docs/home/stablemesh-doc/zhong-wen-wen-dang/cards/top-up.md)

***

{% hint style="warning" %}
发送前请务必核对网络。向错误的网络发送代币可能导致资金**永久丢失**。
{% endhint %}


---

# 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://stablemesh.gitbook.io/docs/home/stablemesh-doc/zhong-wen-wen-dang/deposit.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.