# July 2024 Release
source: https://developer.mastercard.com/mdes-pre-digitization/documentation/pre-release-notes/previousreleasenotes/prereleasenote_june24/index.md

This site provides the release information of the MDES Pre-Digitization API July 2024 release.

## Release Change Summary {#release-change-summary}

<br />

The Pre-Digitization service will be enhanced to introduce a new response parameter **issuerSpecificPersonalizationData** in Authorize Service endpoint.

## Dates for Introduction of Release July 2024 {#dates-for-introduction-of-release-july-2024}

* MTF - 26 June 2024

* Production - 19 July 2024

### Impacted Market of Release July 2024 {#impacted-market-of-release-july-2024}

* Functionality Available - Global

## Detailed Change 1 - Introduction of a response parameter {#detailed-change-1---introduction-of-a-response-parameter}

As a part reducing the gap between pre-digitization ISO messages and API, we are introducing a new response parameter that allows issuer to share personalizaiton data using the API.

Issuers can provide additional cardholder-specific data (such as a loyalty ID) in their Authorize Service pre-digitization API response. The data is added to the token profile, enabling issuers and merchants to provide customized features and loyalty benefits to the cardholder at the point of service.

Introducing new response parameter - issuerSpecificPersonalizationData

|                                               Field and Description                                                |    Data Type    |               Max Length                | Required |
|--------------------------------------------------------------------------------------------------------------------|-----------------|-----------------------------------------|----------|
| **issuerSpecificPersonalizationData** The operator specific data to be added to the token personalization profile. | Array\[String\] | For each array element - 200 characters | No       |


API Reference: `GET /authorizeService`

This parameter is part of encryption payload in the existing response parameter.

## Impact {#impact}

This change will only be available to issuers who have opted to receive authorize service.

To share this new parameter, ensure that client encryption key is configured and it is valid. If it is expired, then please add a new key using the [key renewal instructions](https://developer.mastercard.com/platform/documentation/getting-started-with-mastercard-apis/renewing-your-keys/).

Please refer to [MIIG](https://techdocs.mastercard.com/bundle/m_MIIG/page/c_MIIG_ProvidingAdditionalPersoData.html) for more detail on creating personalization data.

### Mandate for Implementation {#mandate-for-implementation}

Issuers will need to perform the following changes depending on the services that they have already opt for:

* Change 1 will only be available to those issuers who have opted to receive authorize service and wanted to share personalization data in the response.

### Personal data \& Privacy Note {#personal-data--privacy-note}

Issuers are reminded that the information presented via the Pre-digitization API includes personal data which is subject to data privacy laws. Issuers must satisfy themselves that the processing of such personal data is compliant with applicable privacy laws.