> 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="/files/K0MOimZOUojRlsxmFs1c" 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](/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)](/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](/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](/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 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.payments.thalescloud.io/tokenization/implement-tokenization/card-tokenization-request/processing-the-response/decline.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.