# Pre-Release Notes June 2022
source: https://developer.mastercard.com/mdes-customer-service/documentation/release-history/pre-release-june2022/index.md

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

The MDES Customer Service will support payload encryption for sensitive data supplied in a search request. Additional "Client Encryption Keys" will be used for payload encryption and available to setup when creating a new project or through the My Projects dashboard for existing projects.

1. Search functionality will be enhanced to support Payload Encryption in the request. A new encrypted object `EncryptedAccountInformation` will be added to the search request and is used to contain encrypted parameters used in the search request.

## Dates for Introduction of Functionality {#dates-for-introduction-of-functionality}

* MTF - 1 June 2022
* Production - 27 June 2022

## Change 1 - Introducing Payload Encryption in Search {#change-1---introducing-payload-encryption-in-search}

The Sensitive PCI data used in search requests should be supplied in a new encrypted object called `EncryptedAccountInformation`. Previously accepted non-encrypted search parameters such as PAN and TUR will continue to be supported but will no longer be shown from specification version 2.0.19.

API Reference: `GET /{id}/search`

## Impact {#impact}

### Existing Implementations {#existing-implementations}

Existing issuers can continue to use the Search endpoint without encryption. If they choose to support payload encryption, they will need to update their Mastercard Developer's project to add the Client Encryption key. Issuers can choose to implement this new functionality in their systems, by following the requirements described in the Open API YAML specification. Sufficient testing should be performed in order to prepare issuing systems to process the new request and response data.

### New Implementations {#new-implementations}

New issuers will be required to support payload encryption if search functionality is required. Client Encryption keys are generated during Project creation through Mastercard Developers.

### Sandbox Validation {#sandbox-validation}

For testing in Sandbox:

* Use static keys for payload encryption.
* Download the [public-key-certificate.crt](https://static.developer.mastercard.com/content/mdes-customer-service/uploads/public-key-certificate.crt) file. The public key contained in this certificate is used to wrap the one-time use AES key in requests to MDES.
* Use the fingerprint value: **243e6992ea467f1cbb9973facfcc3bf17b5cd007** for input field `encryptedPayload.publicKeyFingerprint` when testing in the Sandbox environment.

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

Issuers are reminded that the information presented via the MDES Customer Service 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.
