> 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/post-tokenization-requests/retrieve-tokenization-data.md).

# Retrieve tokenization data

## Retrieve tokenization data

Use these APIs after D1 notifies your **issuer backend** of a **Tokenization** event.

Start from the `operationId` included in the notification.

Then retrieve the `digitalCardId` and, if needed, digital card details and credentials.

### Retrieve operation details

Call [Get operation](/tokenization/integrate-the-d1-api/d1-api-summary.md) with the `operationId`.

This returns the processed operation and, when available, the `digitalCardId`.

<figure><img src="/files/nf9xg0RhIZOORotDSXls" alt=""><figcaption><p>Retrieve operation details and, when available, the <code>digitalCardId</code></p></figcaption></figure>

#### Use the `digitalCardId`

The operation response includes the `digitalCardId` when the payment network **TSP** created (or is creating) the digital card.

If the operation `status` is `SUCCESSFUL` or `PENDING`:

* Retrieve non-sensitive data with [Get digital card information](/tokenization/integrate-the-d1-api/d1-api-summary.md).
* Retrieve sensitive credentials with [Get digital card credentials](/tokenization/integrate-the-d1-api/d1-api-summary.md).

{% hint style="info" %}
Digital card credentials are encrypted with your issuer encryption certificate provided during **D1 onboarding**.

Decrypt them in your **issuer backend**.
{% endhint %}

Store only what you need.

### Search a digital card

Use this flow when you do not have `digitalCardId`.

You can start from the digital card PAN (DPAN) observed in authorization traffic.

Common use cases:

* Link a digital card to an **End User**, funding card (FPAN), or device.
* Investigate fraud signals raised by your authorization host.

1. Call [Search digital card](/tokenization/integrate-the-d1-api/d1-api-summary.md) to resolve the DPAN to a `digitalCardId`.
2. Optionally, call [Get digital card information](/tokenization/integrate-the-d1-api/d1-api-summary.md) to retrieve details for that `digitalCardId`.

{% hint style="info" %}
Pass the digital card PAN (DPAN).

You typically receive it in authorization requests from the **Acquirer** via the payment network.
{% endhint %}

<figure><img src="/files/WrbMZ4sXiUuOcxk0hxhh" alt=""><figcaption><p>Search a digital card by DPAN and optionally fetch digital card details</p></figcaption></figure>


---

# 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/post-tokenization-requests/retrieve-tokenization-data.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.