# August 2021 Pre-Release Notes
source: https://developer.mastercard.com/authentication-facilitator/documentation/pre-release-notes/august_2021_pre_release_notes/index.md

### Authentication Facilitator API v1.0.1 corresponds to MDES v2021 Aug (Q3) Release. {#authentication-facilitator-api-v101-corresponds-to-mdes-v2021-aug-q3-release}

The MDES Platform v 2021 Aug Release will add new functionality to the Authentication Facilitator API. The following change will be introduced in Authentication Facilitator API v1.0.1:

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

The MDES Platform v2021 Aug Release will add new functionality to the Authentication Facilitator API. The following change will be introduced in Authentication Facilitator API v1.0.1:

* Introducing a new optional parameters for the Token Requestor domain parameter such as Consumer Facing Entity Name, Token Requestor Id, wallet ID, Payment App Instance Id, and Payment App Name in Deliver Authentication Code.

## Dates for Introduction of Release Aug 2021 (Q3) {#dates-for-introduction-of-release-aug-2021-q3}

* MTF - 22 July 2021

* Production - 26 Aug 2021

### Detailed Change Description for Authentication Facilitator API v1.1 in V2021 Aug (Q3) {#detailed-change-description-for-authentication-facilitator-api-v11-in-v2021-aug-q3}

## Change 1 - Introducing New Parameter {#change-1---introducing-new-parameter}

Introducing a new optional parameters in the Token Requestor domain parameter such as Consumer Facing Entity Name, Token Requestor Id, wallet ID, Payment App Instance Id, Payment App Name in Deliver Authentication Code.

|                                                                            Field and Description                                                                            |    Data Type     | Max Length | Required |
|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------|------------|----------|
| **consumerFacingEntityName** Entity name that an account holder recognizes as the one where they stored their PAN (wallets, merchants, commerce platforms)                  | String           | 100        | No       |
| **tokenRequestorId** The party that requested the digitization.                                                                                                             | string (numeric) | 11 (exact) | Yes      |
| **walletId** The identifier of the Wallet Provider who requested the digitization                                                                                           | string           | 3          | No       |
| **paymentAppInstanceId** The identifier of the Payment App instance within a device that will be provisioned with a token. Only present when supplied by a Wallet Provider. | string           | 64         | No       |
| **paymentAppName** Identifier for the Payment App, unique per app as assigned by Mastercard for this Payment App.                                                           | string           | 64         | Yes      |

Note: This change will only be available to those issuers who have opted in to receive Deliver Authentication Code API

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

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


API Reference: `GET /deliverAuthenticationCode`

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

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

* Change 1 will only be available to those issuers who have opted in to receive this service.

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

Issuers are reminded that the information presented via the Authentication Facilitator 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.