# Release Notes source: https://developer.mastercard.com/commercial-event-notifications/documentation/release_notes/index.md ## Release History {#release-history} Mastercard provides release notes as well as updated documentation to help customers understand the content of each major release. These release notes provide details about the application changes in production releases. The list of content is not exhaustive and only includes changes approved for this communication. This page contains the history of what has been implemented into the Commercial Event Notifications service from May 2024. | Enhancement release dates | Enhancement description | |---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | March 2026 | Commercial Event Notifications now supports tokenized Virtual Cards in addition to existing Virtual Card capabilities. * No changes required for existing integrations using standard VCNs. * Clients leveraging tokenization can now receive event notifications seamlessly. * Improves visibility into tokenized commercial payment transactions. | | August 2025 | * Enabled subscription creation on VCN Corp Guid for `TOKEN_PROVISIONING_EVENT` and `TOKEN_LIFECYCLE_EVENT`. * Updated [Reference application](https://developer.mastercard.com/commercial-event-notifications/documentation/reference_application_tutorial/index.md) and [Swagger specification](https://developer.mastercard.com/commercial-event-notifications/documentation/parameters/index.md). * Added explicit format attribute for all integer fields across all supported event types to indicate int32 or int64 value ranges. * This is a documentation update and does not involve functional or code changes to the Event Notifications platform. * Existing customers must ensure their implementations support the value ranges defined in the updated specification to avoid any disruptions. | | May 2025 | * Enabled Event Notifications for Business Payment Controls Clearing Events. * Updated [API Reference](https://developer.mastercard.com/commercial-event-notifications/documentation/parameters/index.md) with DigiCert Sub and Root CAs that must be trusted for [Push Notifications](https://developer.mastercard.com/commercial-event-notifications/documentation/parameters/notifications/notifications/index.md#push-notifications). * Updated [Reference application](https://developer.mastercard.com/commercial-event-notifications/documentation/reference_application_tutorial/index.md), [Swagger file](https://developer.mastercard.com/commercial-event-notifications/documentation/parameters/index.md) and [Postman Collection](https://developer.mastercard.com/commercial-event-notifications/documentation/postman-collection/index.md). * Enhanced [Frequently Asked Questions](https://developer.mastercard.com/commercial-event-notifications/documentation/support/index.md#frequently-asked-questions) section under [Support](https://developer.mastercard.com/commercial-event-notifications/documentation/support/index.md) to provide more comprehensive answers to common customer inquiries, improving overall assistance and user experience. | | October 2024 | * Enabled Event Notifications for In Control for Mobile Payments (ICMP) Token Events. * Updated [Reference application](https://developer.mastercard.com/commercial-event-notifications/documentation/reference_application_tutorial/index.md) and [Swagger specification](https://developer.mastercard.com/commercial-event-notifications/documentation/parameters/index.md). * Added [Postman Collection](https://developer.mastercard.com/commercial-event-notifications/documentation/postman-collection/index.md) for easy API exploration. | | June 2024 | * Enabled Event Notifications for Business Payment Controls Authorization Events. * Updated [Reference application](https://developer.mastercard.com/commercial-event-notifications/documentation/reference_application_tutorial/index.md) and [Swagger specification](https://developer.mastercard.com/commercial-event-notifications/documentation/parameters/index.md). * Increased the default value for the limit field in the GET/notifications API from 100 to 200. | | May 2024 | * Enabled Event Notifications for In Control for Commercial Payments (ICCP) Clearing Events. * Increased the default value for the limit field in the GET/notifications API from 25 to 100. * Updated [Reference application](https://developer.mastercard.com/commercial-event-notifications/documentation/reference_application_tutorial/index.md) and [Swagger specification](https://developer.mastercard.com/commercial-event-notifications/documentation/parameters/index.md). | ## Known Limitations {#known-limitations} The Event Notifications service has certain limitations that you should consider when integrating your application to this service. The Event Notifications service does not guarantee to generate notifications for 100% of authorized events. In certain situations, the Event Notifications service may not generate an authorization message. The situations include but are not limited to the following scenarios: * A timeout in the authorization/clearing network, resulting in a network-generated decline or reversal. * A transient overload in the transmission of authorization/clearing messages to the Event Notifications service or within the service. * An authorization/clearing request for which the funding real card number could not be determined by In Control/Business Payments Control. * Notifications for new subscriptions will generate after 10 minutes due to caching.