# Pre-Release Notes - July 2025
source: https://developer.mastercard.com/token-requestor-identifier-api/documentation/release-notes/pre-release-notes-july-2025/index.md

## Summary of Changes {#summary-of-changes}

For OBO (On-Behalf-Of) Token Requestors, the TRID API will support a new parameter to suppress token provisioning updates in the MDES platform July 2025 release.

For customers migrating from M4M to Secure Card on File (SCOF), confirm your preferences to your Mastercard representative to work with the MACS (Mastercard Checkout Services) team. If you wish to suppress these notifications, the MACS team will add your preference in the TRID API.

### Release Dates {#release-dates}

* MTF -- 21 May 2025
* Production -- 28 July 2025

### Release Details {#release-details}

**Change 1** - New parameters added.

To suppress the NTU for the server token on activation, the new parameter is included in the

* The Batch Create Token Requestors API
* The Batch Update Token Requestors API

|                                                                                                                                           Field and Description                                                                                                                                            | Data Type | Min Length | Max Length | Required |
|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------|------------|------------|----------|
| **suppressNTUForServerTokenActivation** Flag to indicate if MDES should suppress the NTU on server token activation. Must be one of the following: **- True** : MDES should suppress the NTU for server token on activation. **- False**: MDES should not suppress the NTU for server token on activation. | Boolean   | 4          | 5          | No       |


API Reference: `GET /token-requestors/batches`

## Impact {#impact}

To ensure backward-compatibility, MDES will continue to send notifications to existing customers until the respective configuration is updated for a given partner.