# Release Notes January 2025
source: https://developer.mastercard.com/mdes-customer-service/documentation/release-history/release-notes-jan2025/index.md

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

MDES Customer Service API has been enhanced as part of the January 2025 platform release.

**Change 1** : MDES Customer Service API will now support token activation using [Mastercard Identity Check](https://techdocs.mastercard.com/bundle/MICAG/page/zol1725028815858.html) for MCBP wallets. To support this change:

* The Token Activation Methods API response will be enhanced to include a new value called **EVM_3DS** in the existing parameter `ActivationMethodType`. This new value will be used to authenticate the cardholder and activate the token. This enhancement will provide an additional method for card activation and enhance security measures.

**Change 2**: MDES Customer Service will now support post-tokenization authentication of the cardholder through the issuer's mobile application or banking portal. To support this change:

* A new API endpoint called **NotifyAuthenticationDecision** will be introduced. This optional enhancement enables issuers to notify MDES with the post-tokenization authentication result for a cardholder.

### Release Dates {#release-dates}

**Change 1**

* MTF - 25 November 2024
* Production - 02 January 2025

**Change 2**

* MTF - 08 January 2025
* Production - 15 January 2025

### Release Details {#release-details}

## Change 1: Enhanced the Token Activation Methods API {#change-1-enhanced-the-token-activation-methods-api}

Issuers can now support the Mastercard Identity Check program to authenticate a cardholder and activate the token to enhance security and ensure a smooth and secure authentication process. To support this method, a new value **EVM_3DS** has been introduced. MDES will return this value in the list of activation methods.

API Reference: `GET /{id}/token/activationmethods`

## Change 2: Introduced a new endpoint {#change-2-introduced-a-new-endpoint}

Issuers can now perform post-tokenization authentication of the cardholder through issuer mobile application or issuer banking portal. A new customer service endpoint will be introduced to receive cardholder authentication result when an issuer authenticates the cardholder through the issuer mobile application or the issuer banking portal post tokenization. MDES will use this authentication result to update the system with the token verification status when the cardholder has been successfully authenticated. For details, refer to the announcement [GLB 9396.3](https://techdocs.mastercard.com/bundle/m_an9396_en-us/page/zew1712058422502.html).

API Reference: `GET /{id}/token/notifyauthenticationdecision`

## Issuer Impact {#issuer-impact}

### Existing Issuers - Change 1 {#existing-issuers---change-1}

#### Change 1 {#change-1}

* Issuers who wish to support the Mastercard Identity Check program will need to follow the Identity Check onboarding protocols before using this functionality. They should be prepared to receive the new value in the Token Activation Methods API.
* Issuers who already support the Mastercard Identity Check program and plan to use this method to authenticate the cardholder and activate the token should be prepared to receive the new value in the Token Activation Methods API.
* In addition, the following profiles in MDES Manager need to be updated 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.

### Existing \& New Issuers - Change 2 {#existing--new-issuers---change-2}

* Issuers can use the new MDES Customer Service API endpoint to notify MDES of cardholder authentication results for post-tokenization authentication when the cardholder is authenticated through the issuer mobile application or the issuer banking portal.

### New Issuers - Change 1 {#new-issuers---change-1}

New issuers can follow the configuration details outlined in the [MDES Issuer Implementation Guide](https://techdocs.mastercard.com/bundle/m_MIIG) to support:

* Mastercard Identity Check program to authenticate the cardholder and activate the tokens.
* Post-tokenization authentication of the cardholder.