# Release Notes - March 2025 - Additional Updates
source: https://developer.mastercard.com/mdes-digital-enablement/documentation/release-notes/updates-pre-release-notes-march-2025/index.md

## Release Details {#release-details}

As part of the updates in the [March 2025 release](https://developer.mastercard.com/mdes-digital-enablement/documentation/release-notes/pre-release-notes-march-2025/index.md), the iv parameter also supported the field size change to support the GCM encryption. The following APIs were impacted:

* Tokenize
* Transact
* Notify Token Updated (NTU)
* Search Tokens
* Get Tokens

### Change 1 - Enhanced the iv field {#change-1---enhanced-the-iv-field}

The existing parameter iv was updated to support the field size changes required to support GCM encryption.

|                                                   Field and Description                                                    | Data Type |                                         Min Length                                         |                                         Max Length                                         | Required |
|----------------------------------------------------------------------------------------------------------------------------|-----------|--------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------|----------|
| **iv** Initialization vector used when encrypting data using the onetime use AES key. Hex-encoded data (case-insensitive). | String    | Must be exactly 12 bytes (24 character hex string) when using GCM to match the block size. | Must be exactly 16 bytes (32 character hex string) when using CBC to match the block size. | No       |


API Reference: `GET /digitization/static/1/0/notifyTokenUpdated`


API Reference: `GET /digitization/static/1/0/tokenize`


API Reference: `GET /digitization/static/1/0/searchTokens`


API Reference: `GET /remotetransaction/static/1/0/transact`


API Reference: `GET /digitization/static/1/0/getToken`

<br />

## Impact {#impact}

Existing issuers need to ensure they support the updated field size if they decide to use the GCM encryption.