# Pre Release Note v2.0.11 source: https://developer.mastercard.com/mdes-pre-digitization/documentation/pre-release-notes/previousreleasenotes/prereleasenote_2011/index.md ### MDES Pre-Digitization API v2.0.11 corresponds to MDES V2021 April (Q2) Release. {#mdes-pre-digitization-api-v2011-corresponds-to-mdes-v2021-april-q2-release} This site provides the reference implementation of the MDES Pre-Digitization API version 2.0.11 available from 15 March 2021 in MTF and 15 April 2021 in Production. ### Release Change Summary {#release-change-summary} The MDES Platform v2021 April (Q2) release will add new functionality to the Pre-Digitization API. The following changes will be introduced in the Pre-Digitization API version 2.0.11: * **Authentication Service Click to Pay and Secure Card on File Tokens** will be introduced. This enables MDES Token Requestors to authenticate cardholders post tokenization through leveraging cardholder information maintained by card Issuers. * **Reason Codes** field will be presented to the issuer in Deliver Activation Code (DAC) Service Request and Activation Methods (RAM) service. This is the new field to support the Authentication service. All tokens associated with issuer's MDES-enabled cards can be authenticated when the card issuer participates in the Authentication Service. Only MDES-integrated card issuers can integrate with the Authentication Service. However, issuers are not automatically opted in. They can opt-in per account range and Wallet App (MWA) using the MDES Manager application. 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, the token assurance will be upgraded, which will help increase transaction approval rates. ### Dates for Introduction of Release April 2021 (Q2) {#dates-for-introduction-of-release-april-2021-q2} * MTF - 15 March 2021 * Production - 15 April 2021 ### Detailed Change Description {#detailed-change-description} The following diagram illustrates the end-to-end **Authentication Service for Click to Pay and Secure Card on File Token** flow. ![alt text](https://static.developer.mastercard.com/content/mdes-pre-digitization/documentation/pre-release-notes/previousreleasenotes/img/Authentication_ADD_Card_YellowPath.png) ![alt text](https://static.developer.mastercard.com/content/mdes-pre-digitization/documentation/pre-release-notes/previousreleasenotes/img/Authentication_Verify_Account.png) ![alt text](https://static.developer.mastercard.com/content/mdes-pre-digitization/documentation/pre-release-notes/previousreleasenotes/img/Authentication_ADD_Card_GreenPath.png) #### Change 1 - Enhancing the Deliver Activation Code {#change-1---enhancing-the-deliver-activation-code} A new field, **Reason Codes** , will be presented to the issuer in the Deliver Activation Code (DAC) Service as a part of **Authentication Service for Click to Pay and Secure Card on File Token**. This enables MDES Token Requestors to authenticate cardholders post tokenization through leveraging cardholder information maintained by card Issuers. **Following parameter is added in the request** * reasonCodes: The reason the account holder is being authenticated. New reason codes can be added at any time and should not result in a failure. * Must be one of: * ADD_CARD The account holder is being authenticated after adding the card to the token requestor. * VERIFY_ACCOUNT The account holder is being authenticated in order to verify account ownership. * OTHER The account holder is being authenticated for a reason not enumerated in this list. API Reference: `GET /deliverActivationCode` #### Change 2 - Enhancing the Request Activation Methods {#change-2---enhancing-the-request-activation-methods} A new field, **Reason Codes** , will be presented to the issuer in the Request Activation Methods (RAM) Service as a part of **Authentication Service for Click to Pay and Secure Card on File Token**. This enables MDES Token Requestors to authenticate cardholders post tokenization through leveraging cardholder information maintained by card Issuers. **Following parameter is added in the request** * reasonCodes : The reason the account holder is being authenticated. The reason could impact the generation and validation of the code in a number of ways including but not limited to the time period of validity of the code and the number of attempts allowed to validate the code. New reason codes can be added at any time and should not result in a failure. * Must be one of: * ADD_CARD: The account holder is being authenticated after adding the card to the token requestor. * VERIFY_ACCOUNT: The account holder is being authenticated in order to verify account ownership. * OTHER: The account holder is being authenticated for a reason not enumerated in this list. API Reference: `GET /requestActivationMethods` Note: These changes will be available only to those issuers who have opted for "Authentication Service for Click to Pay and Secure Card on File Token". ### Mandate for Implementation {#mandate-for-implementation} By 15 April 2021, when the v2021 April (Q2) Release will be available in Production, issuers need to perform the following changes depending on the services that they have already opt for: * Change 1 will only be available in the Pre-Digitization API if the issuer has opted for Authentication Requests of "Authentication Service for Click to Pay and Secure Card on File Token". * Change 2 will only be available in the Pre-Digitization API if the issuer has opted for Authentication Methods of "Authentication Service for Click to Pay and Secure Card on File Token". ### 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.