# January 2025 Pre-Release Notes
source: https://developer.mastercard.com/mdes-pre-digitization/documentation/pre-release-notes/prereleasenote_3ds_jan25/index.md

This site provides the release information of the MDES Pre-Digitization API for supporting Identity checks as an authentication method to activate a device token.

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

Mastercard is allowing issuers to support Mastercard Identity Check as a cardholder authentication method for participating device wallets during the MDES Pre-Digitization process.

## Dates for Introduction of Release January 2025 {#dates-for-introduction-of-release-january-2025}

* MTF - 25 Nov 2024
* Production - 2 Jan 2025

### Impacted Market of Release January 2025 {#impacted-market-of-release-january-2025}

* Functionality Available - Global

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

Mastercard is allowing issuers to support Mastercard Identity Check using EMV 3-D Secure during the MDES Pre-Digitization process by:

* Choosing EMV 3-D Secure as the default or override authentication method within MDES Manager.
* Sending EMV 3-D Secure as the authentication method within the:
  * Authorize Service (AS) API response messages
  * Request Activation Method (RAM) API response messages

|                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             Field and Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | Data Type | Max Length | Required |
|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|------------|----------|
| **activationMethod.type** Specifies the activation method type. Must be one of the following: TEXT_TO_CARDHOLDER_NUMBER = Text message to Account holder's mobile phone number. The value will be the Account holder's masked mobile phone number. EMAIL_TO_CARDHOLDER_ADDRESS = Email to Account holder's email address. The value will be the Account holder's masked email address. CARDHOLDER_TO_CALL_AUTOMATED_NUMBER = Account holder-initiated call to automated call center phone number. The value will be the phone number for the Account holder to call. CARDHOLDER_TO_CALL_MANNED_NUMBER = Account holder-initiated call to manned call center phone number. The value will be the phone number for the Account holder to call. CARDHOLDER_TO_VISIT_WEBSITE = Account holder to visit a website. The value will be the website URL. CARDHOLDER_TO_USE_MOBILE_APP = Account holder to use a specific mobile app to activate token. The value will be replaced by a formatted string. ISSUER_TO_CALL_CARDHOLDER_NUMBER = Issuer-initiated voice call to Account holder's phone. The value will be the Account holder's masked voice call phone number. **EMV_3DS = Identity check using EMV 3DS will be used to authenticate the cardholder. The value will be replaced by the issuer's 3DS URL.** | String    | 64         | Yes      |


API Reference: `GET /authorizeService`


API Reference: `GET /requestActivationMethods`

For more detail, refer the announcement [MDES Offers Mastercard Identity Check as a Cardholder Authentication Method During Predigitization](https://techdocs.mastercard.com/bundle/m_an10205_en-us/page/dfo1721054919349.html)

## Impact {#impact}

### Existing Issuers {#existing-issuers}

This change will be available to issuers who wish to support Identity check authentication method. The following profiles need to be updated in MDES Manager to support this functionality:

* Message Profile, to configure the message choices for Pre-digitization API or ISO messages
* Wallet Profile for any overrides
* Activation profile to select the Identity Check activation method.

### New Issuers {#new-issuers}

New issuers can choose to support the Identity check authentication method. These issuers will need to follow the Identity Check onboarding protocols before using this functionality.

### Personal data and Privacy Note {#personal-data-and-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.