> 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/merchant-tokenization/network-tokenization/implement-network-tokenization/display-card-art.md).

# Display card art

Use the card art metadata returned during tokenization to retrieve card images.

## Flow

<figure><img src="https://1873847743-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9XBN1F9dv7Dl1ggilGWC%2Fuploads%2F65EWOlpqxuvc52YrqR3A%2FFlow%20-%20Display%20card%20art.svg?alt=media&amp;token=e126711c-7694-4560-ac49-99731083ac23" alt=""><figcaption><p>Card art retrieval flow</p></figcaption></figure>

<table><thead><tr><th width="100">Step</th><th>Description</th></tr></thead><tbody><tr><td>1</td><td>The merchant or PSP calls Thales backend to retrieve card art using the <code>assetId</code> returned during tokenization.</td></tr><tr><td>2</td><td>If Thales backend does not have the image cached, it fetches it from the payment network TSP and caches it.</td></tr><tr><td>3</td><td>Thales backend returns the image to the merchant or PSP. The format is typically PNG or PDF, depending on the payment network TSP.</td></tr><tr><td>4</td><td>The merchant or PSP stores and displays the image in its website or application.</td></tr></tbody></table>

## API

* API reference: [Get asset](https://docs.payments.thalescloud.io/merchant-tokenization/backend-integration/apis/server-api/token-management.md#get-assets-assetid)

{% hint style="info" %}

* This use case is optional.
* The image format may differ depending on the payment network and issuer.
* Follow the payment network rules for rendering the card art.
  {% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.payments.thalescloud.io/merchant-tokenization/network-tokenization/implement-network-tokenization/display-card-art.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
