> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/partner/zh/ni-xiang-liao-jie-shen-me/platform-features/finance/finance-documents/mt103-explained.md).

# MT103 说明

MT103 是一种标准化的 SWIFT（环球同业银行金融电讯协会）付款报文，专门用于跨境或国际电汇转账。它是全球通用的付款凭证，包含所有必要的付款详情，例如付款日期、金额、货币、发送方和接收方。

{% hint style="success" %}
**注：** 请注意在以下情况下的限制 [通过中介银行提取时](/partner/zh/ni-xiang-liao-jie-shen-me/platform-features/finance/payments-withdrawals-and-balance/payout-setup/limitations-of-withdrawals-via-intermediary-banks.md).
{% endhint %}

<div data-with-frame="true"><figure><img src="https://1152657667-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fb2rE79d9UhOKZQLgzSqx%2Fuploads%2Fgit-blob-a346ab099b2ac2a8456c2e4b240b4c3893e2820d%2Faeeb5fe4892bd8112b808a95aa83cc7d6948f8199dfd6fa347be6dca93c6197b.png?alt=media" alt=""><figcaption></figcaption></figure></div>

## 我应该如何处理 MT103？

MT103 证明付款已发送。 **这是 impact.com 能提供的唯一付款凭证**。作为该笔付款的收款方，您可以将 MT103 信息提供给您的银行，银行需要利用这些信息来协助查找您的资金。

* 请参见下方的 *MT103 格式* 部分，了解 MT103 中各项信息的详细说明。

<details>

<summary>MT103 格式</summary>

| 行           | 说明                | 示例                                              |
| ----------- | ----------------- | ----------------------------------------------- |
| 20          | 交易参考编号            | `:20:GB123456ABCD21C1`                          |
| 23B         | 银行操作代码            | `:23B:CRED`                                     |
| 32A         | 价值日期、币种和金额        | `:32A:220113ZAR15000,05`                        |
| 33B         | 币种和原始订单金额         | `:33B:ZAR15000,05`                              |
| 50A、F 或 K   | 付款客户 - 姓名和地址      | `:50K:P SHERMAN 42 WALLABY WAY SYDNEY 2000,AUS` |
| 52A 或 D     | 汇款行               | `:52A:AAYBAU2S`                                 |
| 53A、B 或 D   | 发送方代理行            | `:53B:12345678901`                              |
| 54A、B 或 D   | 接收方代理行            | `:54A:BL20070000`                               |
| 56A、C 或 D   | 中介行（银行）           | `:56A:CP0103`                                   |
| 57A、B、C 或 D | 开户机构（您的银行）        | `:57A://SC400515`                               |
| 59 或 59A    | 收款客户 - 4x35       | `:59:/12345678 ACME HOLLYWOOD, CA`              |
| 70          | 汇款信息              |                                                 |
| 71A         | 费用详情（OUR/SHA/BEN） | `:71A:SHA`                                      |
| 72          | 发送方至接收方信息         | `:72:/INS/PMT LEGAL FEES //SYDNEY BRANCH`       |
| 77B         | 监管申报              | `:77B:PURPOSE:SUPP`                             |

</details>

{% hint style="success" %}
**注：** impact.com 不是金融机构，也无法访问全球银行数据。如需帮助查找您的付款资金，请携带您的 MT103 信息直接联系您的银行。
{% 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://help.impact.com/partner/zh/ni-xiang-liao-jie-shen-me/platform-features/finance/finance-documents/mt103-explained.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.