> 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/home/card-creation-and-management/implement-card-creation-and-management/manage-card/physical-card-and-personalization/create-and-order/chip-personalization.md).

# Chip personalization

<figure><img src="/files/Ej7mKmBxpJS9icscT3wy" alt=""><figcaption></figcaption></figure>

D1 supports EMV chip personalization for physical card personalization.

Choose one of two integration models:

* **Model 1 (recommended):** The **Issuer backend** sends minimal inputs. D1 computes the EMV dataset.
* **Model 2:** The **Issuer backend** sends a prepared EMV dataset. D1 validates and loads it.

### Standard profiles

D1 supports the following standard chip profiles:

* **Visa product (global):** Dual-interface Visa debit/credit cards — VIS 1.6.3 and VCPS 2.2.4.
* **Visa product (US only):** VIS 1.5.4 and VCPS 2.1.3.
* **Mastercard product:** M/Chip Advance 1.2.3 (no data storage).

{% hint style="info" %}
If you need a profile not listed here, contact the Thales delivery team
{% 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/home/card-creation-and-management/implement-card-creation-and-management/manage-card/physical-card-and-personalization/create-and-order/chip-personalization.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.