> 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-decision.md).

# Processing the decision

D1 processes the **Tokenization** request and evaluates available signals (including the data you provide) to make a decision on behalf of the **Issuer**.

### Before you begin

To enable D1 to make a decision on behalf of the Issuer, make sure you:

* Configure your decisioning preferences during **D1 onboarding**. For details, see [Decision engine](/tokenization/implement-tokenization/card-tokenization-request/processing-the-decision/decision-engine.md).
* Provide high-quality, consistent data for:
  * The card
  * The **End User** (called `consumer` in the D1 API)

### Flow

<figure><img src="/files/hV8biWzvogEKUsIpRo4k" alt=""><figcaption><p>Tokenization decision flow (high level)</p></figcaption></figure>

### Sequence diagram

<figure><img src="/files/rZqNaBFqf3YqUaKyOPnX" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/Hscs9DTqZ0ThmzEXw1fG" alt="Tokenization decision sequence diagram"><figcaption><p>Tokenization decision sequence diagram</p></figcaption></figure>

{% hint style="warning" %}
**Card verification behavior**

D1 manages the **Verify card** step only if you provide the **CVK** used to validate the card’s **CVV2**/**dCVV2** during **D1 onboarding**.

If you do not provide the CVK, D1 calls your **issuer backend** using the [Verify card API](/tokenization/integrate-the-d1-api/d1-api-summary.md) and uses your response to determine card eligibility.

Depending on your configuration (this is the default behavior), if the card is not already registered in D1 using the [Register card API](/tokenization/integrate-the-d1-api/d1-api-summary.md), the flow fails before calling your issuer backend (for example, due to an unknown card).
{% endhint %}

{% hint style="warning" %}
**End User (consumer) information behavior**

To retrieve End User information, D1 follows one of the paths below, depending on how you registered the End User:

* If `personalInformation` is provided in the payload of the [Register consumer API](/tokenization/integrate-the-d1-api/d1-api-summary.md), D1 uses the information stored during registration.
* If `personalInformation` is not provided, D1 calls the issuer backend to retrieve End User (consumer) information.
  {% endhint %}

### Decision outcomes

The decision returned by D1 through the [Decision engine](/tokenization/implement-tokenization/card-tokenization-request/processing-the-decision/decision-engine.md) is aligned with payment network TSP protocols.

D1 can return one of the following outcomes:

* **GREEN (approve)**\
  Full approval of the Tokenization request. The End User does not need to complete additional authentication.
* **YELLOW (approve with step-up authentication)**\
  The Issuer must authenticate the End User using an **ID\&V** method to complete Tokenization.
* **RED (decline)**\
  Tokenization is not approved and the payment network TSP stops the flow.

To understand what happens after each outcome, see [Processing the response](/tokenization/implement-tokenization/card-tokenization-request/processing-the-response.md) and the corresponding sections:

* [Decline](/tokenization/implement-tokenization/card-tokenization-request/processing-the-response/decline.md)
* [Approval with no conditions](/tokenization/implement-tokenization/card-tokenization-request/processing-the-response/approval-with-no-conditions.md)
* [Approve with step-up authentication](/tokenization/implement-tokenization/card-tokenization-request/processing-the-response/approve-with-step-up-authentication.md)


---

# 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:

```
GET https://docs.payments.thalescloud.io/tokenization/implement-tokenization/card-tokenization-request/processing-the-decision.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.