# Release Notes August 2026
source: https://developer.mastercard.com/mdes-customer-service/documentation/release-history/release-notes-august2026/index.md

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

Mastercard has deprecated support for the RSA PKCS#1 v1.5 encryption scheme and transitioned to RSA-OAEP as the supported payload encryption scheme.
This transition enhances security by leveraging the RSA-OAEP encryption scheme which provides stronger security protection and improved resilience against evolving threats.

##### Impacted APIs {#impacted-apis}

* Search
* Token Activate
* Token Update

## Release Timeline {#release-timeline}

|      Date      |                                                                               Change Description                                                                                |   |
|----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---|
| 14 August 2026 | RSA PKCS#1 v1.5 will be deprecated and RSA OAEP became the supported payload encryption scheme. Existing customers may continue to use the RSA PKCS#1 v1.5 until 31 March 2027. |   |
| 31 March 2027  | RSA PKCS#1 v1.5 will no longer be supported. Customers must transition to the RSA OAEP encryption scheme.                                                                       |   |

### Impacted Market {#impacted-market}

* Functionality Available - Global

## Change 1 - Deprecated the RSA PKCS#1 v1.5 encryption {#change-1---deprecated-the-rsa-pkcs1-v15-encryption}

Deprecated support for the RSA PKCS#1 v1.5 encryption scheme as it no longer meets current security standards. As part of this change, the references to the PKCS#1 v1.5 encryption scheme have been removed from the `encryptedKey` parameter.

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


API Reference: `GET /{id}/token/activate`


API Reference: `GET /{id}/token/update`

## Impact {#impact}

### Existing Issuers {#existing-issuers}

Existing issuers must update their integrations to use RSA OAEP as the encryption and decryption mechanism for payloads in both API requests and responses. After implementing and validating RSA-OAEP support, customers must submit a request through the [Support Case Management](https://www.mastercardconnect.com/case-mgmt/) application to update their configuration.

### New Issuers {#new-issuers}

New issuers must follow the updated configuration requirements before using this functionality. Refer to the API specification for details.