> For the complete documentation index, see [llms.txt](https://docs.coda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coda.co/https-coda-payments.gitbook.io-zhong-wen-coda-private-technical-documentation/payout/payout-chang-jian-wen-ti/huo-bi-yu-cai-wu-xi-ze.md).
# 货币与财务细则
需要了解货币和财务相关的信息吗？以下是关于如何管理payout请求、获取交易报告以及高效更新联系方式的详细信息。
**货币与财务细则**
1. payout请求和收款人支持哪些货币？
* payout请求主要支持美元（USD) 。收款人将按当地货币接收款项，汇率每日根据市场行情更新。
***
2. 是否提供对帐明细数据的API？
* 暂未开放API。对帐单按T+1（交易次日）提供，月度对账单每月 5 号（M+5）统一发送。
***
3. 是否会提供payout交易报告？
* 支持。需提供您的邮箱地址，我们将发送两类报告
* 每日报告：按交易时间T+1 发送
* 月度报告：每月M+5发送
***
4. 每日/月度报告何时发送？
* 每日报告：将在交易日的次日（T+1）通过邮件发送
* 月度报告：每月第 5 个工作日（M+5）通过邮件发送
***
5. 如何更改我的联系信息以接收支付通知？
* 请发送电子邮件至 ，以更新payout通知的联系方式。
***
6. 我可以将余额从Payin转移到Payout吗？
* 发送电子邮件至[ payouts@coda.co](mailto:payouts@coda.co)，注明金额和详细信息。余额转移只能在同一个国家内进行（例如，埃及 Payin -> 埃及 Payout）。如果我们在工作时间内收到电子邮件指令，转移将在当天处理。如果指令在工作时间后收到，转移将在下一个工作日更新。
***
7. 如何查看现有的Payin余额？
* 查看通过电子邮件发送的月度 Payin PO，邮件主题为：“每月发票 - 月- 年”。
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.coda.co/https-coda-payments.gitbook.io-zhong-wen-coda-private-technical-documentation/payout/payout-chang-jian-wen-ti/huo-bi-yu-cai-wu-xi-ze.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.