# February 2024 Release source: https://developer.mastercard.com/mdes-pre-digitization/documentation/pre-release-notes/previousreleasenotes/prereleasenote_jan24/index.md This site provides the release information of the MDES Pre-Digitization API Feb 2024 release. ## Release Change Summary {#release-change-summary}
The Pre-Digitization service will be enhanced to introduce a new reason code **FUNDING_ACCOUNT_UPDATE** in the Notify Token Updated endpoint. ## Dates for Introduction of Release Feb 2024 {#dates-for-introduction-of-release-feb-2024} * MTF - ~~07 Dec 2023~~ | Date | Details | |--------------|-------------------------------------------------------------------------------------------------------------------------------------| | 28 May 2024 | Available if funding account update initiated through ABU (Automatic Billing Update), and PAM API (Payment Account Management API) | | 3 July 2024 | Available if funding account update initiated through Customer Service API and Portal | | 24 July 2024 | Available if funding account update initiated through 0302 - Issuer File Update Network message and R311 Batch File update message. | * Production - ~~28 Feb 2024~~ | Date | Details | |------------------------------|-------------------------------------------------------------------------------------------------------------------------------------| | 28 May 2024 | Available if funding account update initiated through PAM (Payment Account Management API) | | ~~28 June 2024~~ 1 July 2024 | Available if funding account update initiated through ABU (Automatic Billing Update) | | 31 July 2024 | Available if funding account update initiated through Customer Service API and Portal | | 15 August 2024 | Available if funding account update initiated through 0302 - Issuer File Update Network message and R311 Batch File update message. | ### Impacted Market of Release Feb 2024 {#impacted-market-of-release-feb-2024} * Functionality Available - Global ## Detailed Change 1 - Introduction of a New Reason Code {#detailed-change-1---introduction-of-a-new-reason-code} Many issuers require a notification when FPAN and token mapping has been updated. When an issuer sends an FPAN update request to MDES to map a new FPAN with an existing token, the issuer will receive a notification with the reasonCode **FUNDING_ACCOUNT_UPDATE** in the `notifyTokenUpdated` API issuer. This happens when an FPAN associated to a token is updated to a new FPAN in the same account range. Introducing new reason code - FUNDING_ACCOUNT_UPDATE | Field and Description | Data Type | Max Length | Required | |----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|------------|----------| | **reasonCode** The reason code for why the notification is being sent. This applies to all tokens in the Tokens array. Must be one of: * STATUS_UPDATE: The status of the tokens has been changed when the token is activated, suspended, deleted, or inactivated. * REDIGITIZATION_COMPLETE: The token has been re-digitized to the device in the token expiry and FPAN update to a new range use cases * DELETED_FROM_CONSUMER_APP: The token has been deleted from the consumer application. The token may still be active in MDES. * AUTHENTICATION_PERFORMED: Account holder authentication was performed on the token. The status did not change as a result. * **FUNDING_ACCOUNT_UPDATE: Token and FPAN mapping has been updated due to an FPAN, expiry, or a Financial account change but the token did not change. The status did not change as a result.** | String | 32 | Yes | API Reference: `GET /notifyTokenUpdated` ## Impact {#impact} This change will only be available to issuers who have opted to receive token lifecycle notifications and subscribe to the Notify Token Updated endpoint. As we are adding a new value to the enumeration while supporting backward compatibility, by default, this value is not available to any issuer. To receive notification for the reason code FUNDING_ACCOUNT_UPDATE, please contact your regional Mastercard representative to opt-in. Issuer must increase the TPS value by 50 while opting-in to this notification. For example, if an issuer has setup existing TPS value as 50 then the new TPS value will be 100 or more. If you opt-in to receive a notification for FUNDING_ACCOUNT_UPDATE, you will also receive the FPAN information in the `fundingAccountInfo` object for REDIGITIZATION_COMPLETE. Note: No changes are required for those issuers who do not wish to receive this information and their integration is resilient to addition of new optional elements in the request and response. ### Mandate for Implementation {#mandate-for-implementation} 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 who have opted to receive these services and this value. ### 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.