> For the complete documentation index, see [llms.txt](https://docs.ecommerce.seb.ee/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ecommerce.seb.ee/integration/merchant-api/response-handling/payment-status-reasons.md).

# Payment Status Reasons

Status reasons provide additional details about why a payment reached its current status. They can be used to distinguish between business outcomes, such as issuer declines or insufficient funds, and processing issues, such as communication or system errors.

The following table lists example status reasons and their meanings:

| Status Reason          | Description                                                                                                                                                   |
| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `THREEDS_REJECTED`     | The payment could not be authorized because the issuer rejected the 3-D Secure authentication.                                                                |
| `THREEDS_FAILED`       | The customer failed the 3-D Secure authentication process.                                                                                                    |
| `THREEDS_UNAVAILABLE`  | 3-D Secure authentication could not be completed due to a technical or service availability issue.                                                            |
| `INVALID_ACCOUNT`      | The provided card or account details are invalid.                                                                                                             |
| `INVALID_EXPIRY`       | The card expiry date is invalid or the card has expired.                                                                                                      |
| `INVALID_CSC`          | The card security code (CSC/CVV/CVC) is invalid.                                                                                                              |
| `LOST_OR_STOLEN_CARD`  | The card has been reported as lost or stolen and cannot be used.                                                                                              |
| `DECLINED`             | The transaction was declined by the issuer, acquirer, or payment network.                                                                                     |
| `INSUFFICIENT_FUNDS`   | The account does not have sufficient funds to complete the transaction.                                                                                       |
| `LIMIT_EXCEEDED`       | A transaction amount, velocity, or card usage limit has been exceeded.                                                                                        |
| `SUSPECTED_FRAUD`      | The transaction was declined due to suspected fraudulent activity.                                                                                            |
| `ACQUIRER_UNAVAILABLE` | The acquiring service was temporarily unavailable and could not process the request.                                                                          |
| `ISSUER_UNAVAILABLE`   | The card issuer was temporarily unavailable and could not authorize the transaction.                                                                          |
| `TIMEOUT`              | Processing did not complete within the expected time limit.                                                                                                   |
| `PROCESSING_ERROR`     | The transaction could not be completed due to a technical processing error. The operation may be retried; if the issue persists, contact the service provider |


---

# 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.ecommerce.seb.ee/integration/merchant-api/response-handling/payment-status-reasons.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.