> For the complete documentation index, see [llms.txt](https://docs.exoclick.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.exoclick.com/publishers/zh/fu-kuan/publisher-payments.md).

# 付款选项卡

在 **付款** 选项卡中，你可以查看你的付款是如何设置的，以及你已经收到的付款历史记录。

![添加仪表板](https://docs.exoclick.com/assets/images/publisher-payments-bd44f49d66d2c45da29c315d29de58ae.png)

## 付款信息部分 <a href="#the-payment-information-section" id="the-payment-information-section"></a>

在 **付款信息** 在屏幕顶部的部分中，你可以看到：

* **账户状态**：你的账户是否已获批准。
* **最低支付额**：这是一个门槛金额，超过该金额后发布者将获得付款。
* **付款频率**：自动付款\*是否生成发票 **每周** 或 **每月**
* **下次付款日期**：你预计收到付款的下一个日期。
* **下一个付款周期**：你的下一笔付款将涵盖的期间。
* **下个周期应付**：你下一笔付款应支付的金额。
* **应付总额**：你应收到的总金额。

\*自动付款将按 **每周** 或 **每月** 周期并根据发布者的选择自动生成发票。

## 付款历史记录 <a href="#payment-history" id="payment-history"></a>

在 **付款历史记录** 在屏幕底部的部分中，你可以查看你已收到的付款历史记录：

* **期间**：付款所涵盖的期间。
* **金额**：付款金额。
* **推荐**：你从中获得的收入金额 **推荐**.
* **增值税**：你在付款中支付的任何增值税。
* **总计**：包含增值税在内的付款总金额。
* **日期**：生成发票的日期。
* **到期日**：发票预计应在该日期前支付。
* **付款日期**：发票的付款日期。
* **状态**：付款是否 **已支付** 或 **待处理**.


---

# 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.exoclick.com/publishers/zh/fu-kuan/publisher-payments.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.