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

# Canceled tokenization

The **End User** can cancel **Tokenization** during step-up authentication.

This happens when the End User deletes the inactive digital card.

In this case, the payment network **TSP** deletes the digital card.

D1 reports the **DIGITIZE** operation as `FAILED` to your **issuer backend**.

## Sequence diagram

<figure><img src="/files/URGzWaVIlCLu4jI8IEPb" alt=""><figcaption><p>End User cancels Tokenization during step-up authentication</p></figcaption></figure>

### Integration notes

1. The payment network **TSP** deletes the inactive digital card.
2. D1 receives the deletion event from the payment network.
3. D1 notifies your **issuer backend** using **Notify Card Operation**:
   * `operation=DIGITIZE`
   * `status=FAILED`
4. If **End User notifications** are enabled, D1 can inform the End User.

### What happens next

* Treat this as an End User–initiated cancellation. No digital card is available for **LCM**.
* If your **issuer application** shows a user-facing status, map this to “canceled”.
* If you want reminders instead of immediate cancellation handling, see [Unfinished tokenization](/tokenization/implement-tokenization/card-tokenization-request/processing-the-response/unfinished-tokenization.md).

{% hint style="info" %}
This outcome differs from a D1 decision-based [Decline](/tokenization/implement-tokenization/card-tokenization-request/processing-the-response/decline.md).

Here, D1 returned **APPROVE with STEP-UP**.

The End User then cancels the flow.
{% 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:

```
GET https://docs.payments.thalescloud.io/tokenization/implement-tokenization/card-tokenization-request/processing-the-response/canceled-tokenization.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.