> 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/coda-hou-tai/zhu-yao-gong-neng/shu-ju-dong-cha/3.-jiao-yi-shi-bai-shu-ju-yi-biao-ban-gai-lan.md).

# 3. 交易失败数据仪表板概览

此仪表板展示了整体支付成功率以及错误码的分析视图，便于您掌握交易中常见的问题类型。

您可快速识别在某一时段内最常出现的错误代码，并进一步分析失败原因，以优化支付流程。

同时，我们也提供 Coda 平均支付成功率趋势线，帮助您对比并评估自身表现。

<figure><img src="https://files.readme.io/4e75272-image3.png" alt=""><figcaption></figcaption></figure>

您可利用下方图表查看每日错误代码数据，识别出失败交易数量较高的日期，以便进行更深入的诊断与优化。

例如，在图表中可以看到，9 月 24 日 Go-Pay 的交易失败数量达到了最高峰。

<figure><img src="https://files.readme.io/676998c-image1.png" 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 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/coda-hou-tai/zhu-yao-gong-neng/shu-ju-dong-cha/3.-jiao-yi-shi-bai-shu-ju-yi-biao-ban-gai-lan.md?ask=<question>&goal=<endgoal>
```

`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.
