> 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/xpay-enablement/data-preparation/hce-issuer-wallets-personalization.md).
# HCE issuer wallets personalization
The TSH is fully capable of personalizing an EMV application for HCE Issuer Wallets solution. Here is the set of data required from the TSP in the 'submitTokenData' operation.
### PURE
| Name | Format | Length | Description | Example |
| ------------ | ------------ | ------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- |
| KEK\_label | ASCII string | max 64 | Label of the key used for CMKs encryption. The value is defined during the key ceremony. | "G062C.TEST.SGKEK.KEK.01" |
| KEK\_kcv | Hexa string | 6 | KCV of the key used for CMK encryption. | "E95500" |
| DEK\_label | ASCII string | max 64 | Label of the key used for Track2 Data ("track2\_data") encryption. The value is defined during the key ceremony. | "G062C.TEST.SGDEK.MKDATA.01" |
| DEK\_kcv | Hexa string | 6 | KCV of the DEK key. | "50FE57" |
| track2\_data | Hexa string | max 64 | Track 2 Equivalent Data (max length is 19 bytes)
Format in clear is:
- Token PAN up to 19 digits: 'ppppppppppppppppppp'
- 'D'
- Expiry date: 'yymm'
- Service code: 'sss'
- (optional) Discretionary data (depending on PAN length)
- 'F' (if needed to ensure whole byte)
track2\_data is padded with 80h + 00h..00h in order to reach encryption algorithm block size (ISO7816-4 padding)
track2\_data is ciphered under the DEK key using CBC mode.
Encryption algorithm is defined during project setup.
| "FAB7FF4EFE1989AC25EBBEC2ED72378BDA79D244B89F7F25" |
| MK\_AC | Hexa String | max 64 | Value of the Application Cryptogram Card Master Key for proximity payment ciphered under the KEK key. Encryption algorithm is defined during project setup. | "F1452589A51C5E88FA451236A5C49687" |
| MK\_LC | Hexa String | max 64 | Value of the Local CDCVM Card Master Key for proximity payment ciphered under the KEK key. Encryption algorithm is defined during project setup. | "F1452589A51C5E88FA451236A5C49688" |
| MK\_AC\_kcv | Hexa string | 6 | KCV of the Application Cryptogram key. | "ABDEFF" |
| MK\_LC\_kcv | Hexa string | 6 | KCV of the Local CDCVM Stamp key for proximity payment. | "123344" |
| DKI | Hexa string | 2 | DKI of the Application Cryptogram key. | "01" |
| PSN | Hexa string | 2 | PAN Sequence Number to personalize in the application. | "01" |
| PAR | ASCII bytes | 58 | Payment account reference. | "323352305041594D454E544143434F554E545245464552454E43455858"
which represents "23R0PAYMENTACCOUNTREFERENCEXX"
|
{% hint style="info" %}
**Note1**:
The data element name is case sensitive.\
For example, DEK\_kcv and dek\_kcv are not equivalent
{% endhint %}
{% hint style="info" %}
**Note2**:
Some data elements may be added or removed upon project configuration
{% endhint %}
{% hint style="info" %}
**Note3**:
All KCVs described above are calculated by encrypting 8 bytes of 00h for 3DES keys or 16 bytes of 01h for AES keys with the related key using ECB mode.\
In both cases, the 3 high-order bytes shall be used as KCV.
{% 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/xpay-enablement/data-preparation/hce-issuer-wallets-personalization.md?ask=
```
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.