> 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/campaigns/creator-campaigns/campaign-management/view-your-received-creator-campaign-payments.md).
# 查看您收到的创作者活动付款
您可以查看余额、筛选付款、访问您的银行账户设置，或深入查看付款详情。
1. 在顶部导航菜单中，选择 **发现** → [**活动**](https://app.impact.com/secure/mediapartner/marketplace/influencer-marketplace-flow.ihtml).
2. 选择 **参与中** 选项卡。
3. 将鼠标悬停在您正在处理的活动上，然后选择  **\[更多]** → **查看付款**.
* 或者，您也可以选择该活动，然后在滑出面板中选择 **更多**  **\[下拉菜单]** → **查看付款**.
4. 在 *付款* 页面上，您可以查看余额、筛选付款并查看付款详情。
* 请参阅下面的 *筛选* 和 *付款详情* 部分。
付款筛选条件
| 筛选条件 | 说明 |
| ----- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| 按金额搜索 | 输入您要用于筛选付款的金额。 |
| 日期 | 按交易日期筛选。 |
| 收票实体 | 按接收发票的联系人筛选。 |
| 品牌 | 按品牌筛选交易。 |
| 交易 | 按交易类型筛选：
• 全部
• 付款
• 提现
• 处理费
• 闪电支付
• 其他
|
付款参考表
| 列名 | 说明 |
| ------- | ----------- |
| 日期 | 付款日期。 |
| 交易 / 描述 | 付款描述。 |
| 收票实体 | 接收发票的联系人。 |
| 品牌 | 与该付款相关联的品牌。 |
| 金额 | 付款金额。 |
## 查看付款详情
1. 选择您想查看详情的付款。
* 在付款滑出面板中，您可以查看付款日期和金额。
2. 在 *在此付款* 部分中，选择一个金额以查看该交易的详细信息。
* 选择此金额后，将显示该金额何时赚取以及何时完成付款的时间线。
---
# 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/campaigns/creator-campaigns/campaign-management/view-your-received-creator-campaign-payments.md?ask=&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.
