> 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/codapay/chang-jian-cuo-wu-dai-ma/direct-card-api-kou-kuan-cuo-wu-ma.md).

# Direct Card API 扣款错误码

| Codapay 错误码                    | 错误描述                  | 建议处理方式               |
| ------------------------------ | --------------------- | -------------------- |
| UNABLE\_TO\_AUTHORISE          | 交易无法授权                | 提示用户稍后重试             |
| PAYMENT\_DECLINED              | 发卡行拒绝了支付请求            | 核实支付信息后重试，或尝试其他支付方式  |
| INVALID\_REQUEST               | 请求格式或参数无效             | 检查请求参数是否符合格式要求       |
| DO\_NOT\_HONOR                 | 交易被拒但无明确原因            | 建议用户联系银行获取详情，或更换支付方式 |
| CARD\_EXPIRED                  | 卡片已过期                 | 请用户更换卡片或更新卡片信息       |
| CARD\_NOT\_SUPPORTED           | 卡片类型不支持本次交易           | 建议使用其他卡片或支付方式        |
| ADDRESS\_VERIFICATION\_FAILED  | 地址验证失败                | 核实地址信息后重试            |
| DECLINED\_BY\_ISSUER           | 发卡行拒绝交易               | 建议联系银行获取详情，或更换支付方式   |
| DUPLICATE\_TRANSACTION         | 重复交易                  | 检查是否存在重复请求，避免重复提交    |
| INSUFFICIENT\_BALANCE          | 余额不足                  | 建议用户更换支付方式或确认账户资金充足  |
| INVALID\_ACCOUNT               | 提供的账户信息无效             | 核实账户信息后重试            |
| INVALID\_ACCOUNT\_OR\_CARD     | 账户或卡号信息不正确            | 核实并重新输入账户或卡片信息       |
| INVALID\_AMOUNT                | 金额无效或超出限制             | 确认交易金额合法，且在允许范围内     |
| INVALID\_SECURITY\_CODE        | 安全码不正确                | 核实安全码后重试             |
| PROVIDER\_SYSTEM\_ERROR        | 支付通道系统错误              | 稍后重试，若问题持续请联系支持团队    |
| RETRY\_REQUIRED                | 需重试交易                 | 稍后重试，若问题持续请联系支持团队    |
| BLOCKED\_RISK\_CODA\_BLOCKLIST | 被 Codapay 黑名单识别为风险交易  | 建议用户联系银行或更换支付方式      |
| BLOCKED\_RISK\_CODA\_RULE      | 被 Codapay 风控规则识别为风险交易 | 建议用户联系银行或更换支付方式      |
| BLOCKED\_RISK\_PROVIDER        | 被支付通道识别为风险交易          | 建议用户联系银行或更换支付方式      |
| TOO\_MANY\_TRIES               | 尝试次数过多                | 稍后重试，若问题持续请联系支持团队    |
| TRANSACTION\_LIMIT\_EXCEEDED   | 超出支付通道限制              | 降低交易金额后重试            |
| TRANSACTION\_NOT\_ALLOWED      | 发卡行或支付通道禁止该交易         | 核实交易详情，或尝试其他支付方式     |
| UNKNOWN\_ERROR                 | 未知错误                  | 重试交易，若问题仍然存在请联系支持团队  |
| AUTHENTICATION\_FAILED         | 认证过程中发生错误             | 提示用户检查认证信息并重试        |
| INITIATED\_FAILED              | 支付通道交易初始化失败           | 重试交易，若问题仍然存在请联系支持团队  |
| INITIATED\_NOT\_ACCEPTED       | 支付通道未接受初始化请求          | 建议用户更换支付方式重试         |
| FAILED\_TOKEN\_EXPIRED         | Token 已过期，导致交易失败      | 建议用户更换支付方式重试         |
| FAILED\_TOKEN\_CANCELLED       | Token 已取消，导致交易失败      | 建议用户更换支付方式重试         |
| FAILED\_TOKEN\_NOT\_AUTHORIZED | Token 未授权，导致交易失败      | 建议用户更换支付方式重试         |


---

# 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/codapay/chang-jian-cuo-wu-dai-ma/direct-card-api-kou-kuan-cuo-wu-ma.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.