> For the complete documentation index, see [llms.txt](https://hub.moonexe.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.moonexe.com/home/zh-cn/yun-zuo-yuan-li/usdt-yi-jia.md).

# USDT 溢价

货币兑换商如何获利，以及为何 USDT 在不同国家价格不同。

## 货币兑换商如何赚钱

货币兑换商不需要汇率发生波动。他们只需以稍低的价格买入某种货币，再以稍高的价格卖出。

|          | 需求        | 与货币兑换商的交易                                 |
| -------- | --------- | ----------------------------------------- |
| **客户 A** | 需要新币（SGD） | 货币兑换商以 **1 USD = 1.340 SGD** 的价格从 A 处买入美元 |
| **客户 B** | 需要美元（USD） | 货币兑换商以 **1 USD = 1.360 SGD** 的价格向 B 卖出美元  |

两个价格之间的差额，即**价差**，就是货币兑换商的利润。

## 同一种币，不同的价格

USDT 与 1 美元挂钩，但这只是理论价格。实际上，USDT 在不同国家的交易价格各不相同。这种价格差异就是 **USDT 溢价**，它为 MoonExe 的流动性带来持续、反复的需求。

| 国家         | 溢价成因                   | 一般溢价范围       |
| ---------- | ---------------------- | ------------ |
| 🇦🇷 阿根廷   | 恶性通货膨胀，比索不稳定           | 高峰期可达 10–20% |
| 🇳🇬 尼日利亚  | 本币贬值，美元短缺              | 高峰期 +5–15%   |
| 🇪🇬 埃及    | 外汇管制，黑市美元刚需            | +5–12%       |
| 🇹🇷 土耳其   | 里拉波动剧烈，对冲通胀            | +3–8%        |
| 🇵🇰 巴基斯坦  | 美元短缺，海外汇款需求            | +2–6%        |
| 🇻🇳 越南    | 加密货币需求旺盛，银行渠道有限        | +1–3%        |
| 🇮🇩 印度尼西亚 | 进出口贸易结算需求              | +0.5–2%      |
| 🇹🇭 泰国    | 跨境贸易与汇款需求              | +0.5–1.5%    |
| 🇪🇺 欧元区   | 几乎没有溢价：外汇流动性充足，可自由兑换外币 | 0–1%         |

{% hint style="info" %}
**哪里存在货币流通摩擦，哪里就会产生稳定币需求。** 全球约有 1,400 亿美元的 USDT 在流通，但在各国之间分布并不均衡。MoonExe 正是弥合这一失衡的桥梁。
{% 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://hub.moonexe.com/home/zh-cn/yun-zuo-yuan-li/usdt-yi-jia.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.