# Feb 2022 Release
source: https://developer.mastercard.com/mdes-pre-digitization/documentation/pre-release-notes/previousreleasenotes/prereleasenote_feb2022/index.md

### MDES Pre-Digitization API Feb Release 2022. {#mdes-pre-digitization-api-feb-release-2022}

This site provides the release information of the MDES Pre-Digitization API Feb 2022 release available from 20 Jan 2022 in MTF and 22 Feb 2022 in Production.

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

##### **Please note that the following changes apply to the India market only, in order to comply with local regulations.** {#span-stylecolorredstrongplease-note-that-the-following-changes-apply-to-the-india-market-only-in-order-to-comply-with-local-regulationsstrongspan}

<br />

The MDES Platform v2022 Feb Release will add a new functionality to the Pre-Digitization API. The following change will be introduced in Pre-Digitization API Feb 2022:

* A new event **(reason code) - PAYMT_CHANNEL_PREFERENCE_UPDATED)** will be added in the `Notify Token Updated` API.

## Dates for Introduction of Release Feb 2022 {#dates-for-introduction-of-release-feb-2022}

* MTF - 20 Jan 2022

* Production - 22 Feb 2022

## Impacted Market of Release Feb 2022 {#impacted-market-of-release-feb-2022}

* Functionality Available - Global

* Applicable -- Indian issuer

### Detailed Change Description for Pre-digitization API in Feb 2022 {#detailed-change-description-for-pre-digitization-api-in-feb-2022}

## Change 1 - Introduction of a New Event (Reason Code) {#change-1---introduction-of-a-new-event-reason-code}

As part of the Payment Channels functionality, cardholders can opt out of specific payment types, such as contactless, QR-code-based, or Digital Secure Remote Payments (DSRPs) on Mastercard Digital Enablement Service (MDES) tokenized devices. This will send a notification to issuers each time the payment channel preferences are modified. To facilitate this notification:

* A new Reason Code - **PAYMT_CHANNEL_PREFERENCE_UPDATED**- will be introduced. This will acknowledge that the cardholder has updated the payment channels for which the token can be used.
* A new parameter - **disabledPaymentChannels** -- is added in the `Token` object. This will provide a list of payment channels that are disabled.

This enhancement offers issuers in India a convenient way to comply with the Reserve Bank of India (RBI) guidelines.

**Background**
This change is in relation to the Reserve Bank of India Department of Payment and Settlement Systems Central Office Department of Payments directive reference RBI/2018-19 /103, DPSS.CO.PD No.1463/02.14.003/2018-1.

|                                                                                                                                                                                          Field and Description                                                                                                                                                                                           |    Data Type    | Max Length |                                                         Required                                                         |
|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|------------|--------------------------------------------------------------------------------------------------------------------------|
| **disabledPaymentChannels** The list of disabled payment channels. Elements in the array must be one of: * CONTACTLESS: Contactless * MP_QR_CODE: Merchant Presented QR (MPQR) * CP_QR_CODE: Consumer Presented QR (CPQR) * ECOMMERCE: Digital Secure Remote Payment (DSRP) / In-App * P2P: Person to Person (P2P) * POS_SWIPE: Magnetic Secure Transmission (MST) / Dynamic Magnetic Stripe Data (DMSD) | Array\[String\] | NA         | Conditional -- required for notifyTokenUpdated if reasonCode = "PAYMT_CHANNEL_PREFERENCE_UPDATED". Not present otherwise |

Note: Issuer will receive an empty list if all payment channels are enabled (no channels are disabled).

### API Specification for Reference {#api-specification-for-reference}


API Reference: `GET /notifyTokenUpdated`

### Impact {#impact}

* This change will be available to all issuers but only issuers in India who have opted to receive the Notify Token Updated API are eligible to use this functionality.
* This change will be available to issuers in India who have opted to receive this value.
* This change will be available to all new issuers in India (opt-in is not required).

Note: No changes are required for those issuers who do not want to receive this information and their integration is resilient to addition of new optional elements being added to request and response.

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

By 22 Feb 2022, when the v 2022 Feb Release will be available in Production, 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 in India who have opted to receive these services.

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