> For the complete documentation index, see [llms.txt](https://docs.iproyal.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.iproyal.com/cn/dai-li/huang-jia-zhu-zhai-dai-li/yi-biao-ban/ding-dan.md).

# 订单

在订单部分，如图中橙色虚线边框所示，您可以跟踪和管理您的订单。仪表板的这一部分呈现了一个表格，列出了您所有的交易，包括订单ID、任何关联的备注、订单日期、支付的金额、订单前的可用流量以及每个订单的当前状态。您可以使用备注或ID搜索特定的订单，筛选每页显示的条目，并按订单状态进行筛选。对于每个列出的订单，都有查看详细信息的选项。您还可以选择下载所有确认订单的发票。这个功能的目的是让您对您过去的活动有一个清晰明了的视图，并帮助您有效地管理您购买的服务。

<figure><img src="https://1496375911-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FocBfddKBo5nf8WdKl9vN%2Fuploads%2FOxmvuqKD6BQ0B1kvcNjr%2FG1.png?alt=media&amp;token=c439a456-b5f0-42bb-8341-558dcf39ffce" alt=""><figcaption></figcaption></figure>


---

# 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.iproyal.com/cn/dai-li/huang-jia-zhu-zhai-dai-li/yi-biao-ban/ding-dan.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.
