> For the complete documentation index, see [llms.txt](https://help.listly.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.listly.io/docs/zh-hans/support/faq/1.-fu-kuan-yu-tui-kuan-shuo-ming/fu-kuan-shi-bai-le-zen-me-ban.md).

# 付款失败了怎么办？

订阅或首次付款失败，可能是以下原因导致的，请逐一排查：

* 余额不足
* 银行卡已挂失
* 银行卡已过期
* CVC 安全码输入错误
* 账户无效
* 超出支付限额

如果以上原因都不适用，请将付款失败的截图发送至 <hello@listly.io>，我们会尽快协助处理。


---

# 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.listly.io/docs/zh-hans/support/faq/1.-fu-kuan-yu-tui-kuan-shuo-ming/fu-kuan-shi-bai-le-zen-me-ban.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.
