# 2021 January (Q1)
source: https://developer.mastercard.com/mdes-token-connect/documentation/pre-release-notes/prereleasenote_jan2021/index.md

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

The MDES Platform will add a new functionality to the Token Connect API in 2021 January (Q1) Release.

* A new field, supportsCardholderAuthentication, is added in the Get Eligible Token Requestors API that will present token requestors with the capability to indicate that they support post-tokenization cardholder authentication, where required by the issuer.

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

* MTF - ~~5 Dec 2020~~ 08 Jan 2021

* Production - ~~23 Jan 2021~~ 03 Feb 2021

### Change Description for Token Connect API in V2021 January (Q1) Release {#change-description-for-token-connect-api-in-v2021-january-q1-release}

**Change 1 - Enhancing Get Eligible Token Requestors (Response)**

The Get Eligible Token Requestors API will present token requestors with the capability to support post-tokenization cardholder authentication in the token requestor environment.

If a token requestor \& issuer both support post-tokenization cardholder authentication, the issuer should expect authentication-related requests from MDES when a token requestor initiates cardholder authentication. On successful authentication of cardholder MDES updates, the token assurance will be upgraded, which will help increase transaction approval rates.

The below flow illustrates the end-to-end post-tokenization authentication flow.

![alt text](https://static.developer.mastercard.com/content/mdes-token-connect/documentation/pre-release-notes/img/authenticationFlow.png)

The response to `getEligibleTokenRequestors` is enhanced with a new field as follows:

* `tokenRequestors[].supportsCardholderAuthentication` -- An optional boolean parameter to indicate if the token requestor supports post-tokenization cardholder authentication in the token requestor environment


API Reference: `GET /getEligibleTokenRequestors`

Note: This enhancement will be automatically available to all issuers implementing MDES Token Connect.

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

By ~~23 January 2021~~ **++03 February 2021++**, when the v2021 January (Q1) release will be available in Production, this change will be automatically available to all issuers implementing the MDES Token Connect API.

* This change is backward compatible. It will be automatically available to all issuers implementing the MDES Token Connect API. Issuer must adapt to this if th issuer integrations is not resilient to the addition of new elements being added to requests and responses.

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

Issuers are reminded that the information presented via the Token Connect includes personal data which is subject to data privacy laws. Issuer must satisfy themselves that the processing of such personal data is compliant with applicable privacy laws.