# Announcements
source: https://developer.mastercard.com/commercial-event-notifications/documentation/announcement/index.md

Here you can find information about upcoming changes that are planned for the Alerts for Commercial Event Notifications API.

## March 2026 updates {#march-2026-updates}

Commercial Event Notifications now supports tokenized Virtual Card Numbers (VCNs) for authorization and clearing event notifications. Previously, event notifications were generated only for transactions involving standard VCNs. With this release, notifications will also be generated when transactions are processed using tokenized VCNs.  

**What is changing** : Event notifications for authorization and clearing events will now include transactions where the underlying VCN is tokenized.  

**Impact to customers** : Customers subscribing to authorization and clearing notifications may begin receiving notifications related to tokenized VCN transactions in addition to existing VCN transactions.  

**Action required**: No action is required. Existing integrations will continue to function as expected. The API specification has been updated to explicitly identify mandatory and optional fields for ICMP token events (Token Lifecycle event and Token Provisioning event).  

**What is changing** : The OpenAPI (Swagger) specification now clearly defines which fields are mandatory and which are optional for ICMP token events.  

**Impact to customers** : This is a documentation-only update intended to improve clarity for developers integrating with ICMP token events.  

**Action required**: No action is required. There are no functional or platform changes associated with this update. The documentation has been updated to clarify how masked PAN and account numbers are represented in event notification payloads.  

**Background** : The actual Primary Account Number (PAN) typically ranges from 12 to 19 digits. For security and PCI compliance reasons, PAN and account numbers are always returned in a masked format, where all digits except the last four are replaced with asterisks. The masked value maintains the same total length as the original PAN.  

**What is changing**: Documentation has been updated to clarify the following:

* Masked PAN and account numbers may range from 16 to 23 characters in length.
* This length reflects the masked representation of PAN values that may be up to 19 digits.

<br />

**Impact to customers** : This update resolves confusion caused by earlier payload examples that showed a 20-character masked value without explaining how the length is derived.  

**Action required**: No action is required. This is a documentation clarification only, and there are no changes to existing payload formats.