> 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/unfinished-tokenization.md).

# Unfinished tokenization

An **APPROVE with STEP-UP** decision means **Tokenization** is pending.

The **End User** must complete an **ID\&V** method. This activates the digital card.

Use this page when the **End User** does not complete the step.

{% stepper %}
{% step %}

### End User does not take any action

The **End User** might not complete the step-up flow.

Common reasons include:

* They do not recognize the request.
* They abandon the flow.
* They do not have access to the chosen channel (email/SMS).

To reduce drop-off, D1 supports [End User notifications](/tokenization/implement-tokenization/end-user-notifications.md).

After a configured delay, D1 can send email or SMS reminders.

These reminders prompt the End User to complete **ID\&V**.

This completes **Tokenization**.

Configure the reminder delay and maximum number of messages during **D1 onboarding**. Contact the Thales delivery team to enable it.

Sequence diagram:

<figure><img src="/files/ICU2ILz06hgRsipCw1i4" alt=""><figcaption><p>End User reminder notification flow</p></figcaption></figure>

{% hint style="info" %}
If the End User takes no action, D1 sends the first notification 24 hours after it returns the Tokenization response to the payment network **TSP**.

You can configure this delay during **D1 onboarding**.
{% endhint %}
{% endstep %}

{% step %}

### Session expires

The system cannot wait indefinitely for the **End User** to complete **ID\&V**.

In D1, you configure a session length for step-up **Tokenization**.

When the session expires, D1 deletes the inactive digital card.

It does this through the payment network **TSP**.

For example, set the session length to 30 days.

This aligns with **xPay Wallets** requirements.

Sequence diagram:

<figure><img src="/files/Dd5r1HOmGbvlG8wxQrXa" alt=""><figcaption><p>Tokenization session expiry flow</p></figcaption></figure>
{% endstep %}
{% endstepper %}


---

# 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/unfinished-tokenization.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.