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

# Processing the response

After D1’s decision engine evaluates a **Tokenization** request, D1 returns a decision to the payment network **TSP** (for example, **MDES** or **VTS**). The TSP then completes the Tokenization flow with the **token requestor** and, when applicable, provisions and activates the digital card.

{% hint style="warning" %}
**Avoid TSP decision overrides**

Some payment networks can be configured to override the **Issuer** Tokenization decision at the TSP level. Thales does not recommend this because it can cause D1 and the payment network TSP to get out of sync.
{% endhint %}

### Decision outcomes

D1 can return one of the following outcomes:

* [**GREEN (approve)**](/tokenization/implement-tokenization/card-tokenization-request/processing-the-response/approval-with-no-conditions.md)\
  The Tokenization request is approved and no additional End User authentication is required.
* [**YELLOW (approve with step-up authentication)**](/tokenization/implement-tokenization/card-tokenization-request/processing-the-response/approve-with-step-up-authentication.md)\
  The Tokenization request is conditionally approved. The End User must complete an additional authentication step (an **ID\&V** method) before the digital card can be activated.
* [**RED (decline)**](/tokenization/implement-tokenization/card-tokenization-request/processing-the-response/decline.md)\
  The Tokenization request is declined and the payment network TSP stops the flow.

Each outcome has specific implications for the digital card state and the End User experience.

### Notifications

During and after Tokenization, D1 can generate notifications that you manage in your **issuer backend**. Optionally, D1 can also send informational notifications to the **End User**.

{% hint style="warning" %}
**TSP notification delays**

The TSP might delay sending notifications. These delays are outside D1’s control.
{% endhint %}

#### Notifications to the issuer backend

D1 notifies your issuer backend of Tokenization outcomes and life cycle events (depending on what you enable during **D1 onboarding**).

For the APIs involved, see:

* [API summary](/tokenization/integrate-the-d1-api/d1-api-summary.md)

#### End User notifications

End User notifications are informational messages sent by SMS or email (when enabled). D1 can send these notifications on behalf of the Issuer in the following cases:

* [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)
* [Tokenization cancelled](/tokenization/implement-tokenization/card-tokenization-request/processing-the-response/canceled-tokenization.md)
* [Card replacement](/tokenization/implement-tokenization/post-tokenization-requests/life-cycle-management/card-life-cycle.md#card-replacement) and [card renewal](/tokenization/implement-tokenization/post-tokenization-requests/life-cycle-management/card-life-cycle.md#card-renew)
* [Digital card deletion](/tokenization/implement-tokenization/post-tokenization-requests/life-cycle-management/digital-card-life-cycle.md)

For configuration options and message templates, see [End User notifications](/tokenization/implement-tokenization/end-user-notifications.md).

{% hint style="warning" %}

* If the Issuer sends **OTP** by SMS/email (instead of D1), D1 does **not** send End User notifications.
* If End User notifications are enabled, D1 may call your issuer backend to retrieve the latest End User contact information using [Get consumer information API](/tokenization/integrate-the-d1-api/d1-api-summary.md).
  {% 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.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.