# Pre Release Note v2.0.10
source: https://developer.mastercard.com/mdes-pre-digitization/documentation/pre-release-notes/previousreleasenotes/prereleasenote_2010/index.md

### MDES Pre-Digitization API v2.0.10 corresponds to MDES V2021 January (Q1) Release. {#mdes-pre-digitization-api-v2010-corresponds-to-mdes-v2021-january-q1-release}

This site provides the reference implementation of the MDES Pre-Digitization API version 2.0.10 available from 05 December 2020 in MTF and 23 January 2021 in Production.

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

The MDES Platform v2021 January (Q1) Release will add new functionality to the Pre-Digitization API. The following changes will be introduced in the Pre-Digitization API version 2.0.10:

* A new field, **Token Data**, will be presented to the issuer when a token is re-digitized in the Notify Token Updated (NTU) service.

* A new service, **Notify Suspicious Events**, will be introduced to notify issuers about suspicious activity for a digital wallet that can be detected by MDES during the MCBP device-based cloud token replenishment process.

### Dates for Introduction of Release January 2021 (Q1) {#dates-for-introduction-of-release-january-2021-q1}

* MTF - 5 Dec 2020

* Production - 23 Jan 2021

### Detailed Change Description for Pre-digitization API 2.0.10 in V2021 January (Q1) {#detailed-change-description-for-pre-digitization-api-2010-in-v2021-january-q1}

#### Change 1 - Enhancing the Notify Token Updated Service {#change-1---enhancing-the-notify-token-updated-service}

The Notify Token Updated (NTU) service will support an optional field to provide additional token data to the issuer when a token has been re-digitized. The optional field corresponds to the 'fundingAccountInfo' object that will contain only token data (DPAN and Expiry Date). See [AN3819](https://techdocs.mastercard.com/bundle/m_AN3819/page/ggp1583507148073.html) for further details or to refer the updated API specification below:

API Reference: `GET /notifyTokenUpdated`

Note: This change will be available only to those issuers who have opted in to the Notify Token Updated service, and only impacts messages when the value of reasonCode is REDIGITIZATION_COMPLETE.

If an issuer is still configured to receive cardinfo and opt in to receive NTU for re-digitization, they will get fundingaccountinfo in the NTU.

#### Change 2 - Introducing a new Service: Notify Suspicious Events {#change-2---introducing-a-new-service-notify-suspicious-events}

This service aims to assist issuers with their risk management activities and detection of suspicious activity related to the use of digital wallets using MCBP technology. This API will notify issuers about suspicious activity that can be detected by MDES for a digital wallet during the MCBP device-based Cloud token replenishment process.

Notification of suspicious activity is informative, and several actions are possible based on the strategy used by Issuers for their risk management:

* Issuers can wait for Wallet Providers to provide further details following analysis of the information
* Issuers can suspend tokens anytime using MDES Customer Service APIs/Portal

Security is an important element of our digital strategy. MDES wants to assist issuers to make the right decision as part of their risk management to allow them to take any pro-active action through MDES Customer Service APIs/Portal, such as suspending a token.

* This can be done without any delay while your Wallet Provider is investigating the case as Wallet Providers will also get the same notification message to help them investigating when these events occur.
* We talk about suspicious activity as this can be an implementation issue on the wallet (or wallet server) and not necessarily a fraud case.


API Reference: `GET /notifySuspiciousEvents`

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

By 24 January 2021, when the v2021 Jan (Q1) Release will be available in Production, issuers need to perform the following changes depending on the services that you have already opt for:

* Changes 1 and 2 will only be available in the Pre-Digitization API if the event (re-digitization and/or suspicious activity) occurred
* Change 1 will only be available in the Pre-Digitization API if the re-digitization event occurred and issuer has opted for re-digitization.
* Change 2 will only be available in the Pre-Digitization API if the suspicious event occurred and issuer has opted for the service through MDES Manager.

### 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.