> For the complete documentation index, see [llms.txt](https://docs.payments.thalescloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payments.thalescloud.io/tokenization/implement-tokenization/card-tokenization-request/processing-the-response/decline.md).

# Decline

A decline (**RED**) means D1 did not approve **Tokenization**. The payment network **TSP** stops the flow, and no digital card is provisioned.

<figure><img src="https://2043231064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FW6dljaTEEzefPQILRFB7%2Fuploads%2FdAG2tu8u8VBnRatuRMgE%2FSequence%20Diagram%20%E2%80%93%20%20Processing%20the%20response.svg?alt=media&amp;token=7841d67e-20f9-4732-9ca5-ce58af8ce5ca" alt=""><figcaption></figcaption></figure>

### Common reasons

Typical reasons for a decline include:

* Card checks failed (for example, an expired card, an invalid **CSC**, or a suspended card). See [Decision engine > Card](https://docs.payments.thalescloud.io/tokenization/implement-tokenization/card-tokenization-request/processing-the-decision/decision-engine.md#card).
* End User data checks failed (for example, a phone number mismatch configured as a decline). See [Decision engine > End User (consumer)](https://docs.payments.thalescloud.io/tokenization/implement-tokenization/card-tokenization-request/processing-the-decision/decision-engine.md#end-user-consumer).
* Wallet/device risk signals resulted in a decline (for example, wallet scoring mapped to **RED**). See [Decision engine > Wallet scoring](https://docs.payments.thalescloud.io/tokenization/implement-tokenization/card-tokenization-request/processing-the-decision/decision-engine.md#wallet-scoring).
* Rate limits were exceeded (for example, too many Tokenization attempts). See [Decision engine > Counters](https://docs.payments.thalescloud.io/tokenization/implement-tokenization/card-tokenization-request/processing-the-decision/decision-engine.md#counters).

{% hint style="info" %}
Because the payment network **TSP** does not provision a digital card for a decline, any `digitalCardId` returned in the flow (if present) is not usable for post-tokenization operations.
{% endhint %}


---

# 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.payments.thalescloud.io/tokenization/implement-tokenization/card-tokenization-request/processing-the-response/decline.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.
