# October 2025 Pre-Release Notes
source: https://developer.mastercard.com/mdes-pre-digitization/documentation/pre-release-notes/prereleasenote_multi_pan_mapping_oct25/index.md

This site provides the release information of the MDES pre-digitization API for the October 2025 release.

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

The MDES platform October 2025 release will support mapping multiple primary account numbers to a single consumer card account in case of consumer Virtual Card Numbers (VCNs). To support this mapping, issuers must identify the VCNs that belong to the same card account and send the related information during the VCN tokenization.
These mappings enable generation and assignment of a consistent PAR (Payment Account Reference) across all VCNs linked to the same card account. This enables issuers to manage multiple VCNs under a single account umbrella, improving support for rewards, installments, and other value-added services.

This enhancement allows new issuers to associate different VCNs each representing a unique tokenized version of a card with a single underlying card account. For existing VCN token, the FPAN mapping is corrected and PAR is updated which triggers a PAR update notification.

The following APIs have been impacted:

* Authorize Service (AS)
* Notify Token Updated

## Release Dates {#release-dates}

* MTF - 18 September 2025
* Production - 1 October 2025

### Impacted Market {#impacted-market}

* Functionality Available - Global

## Change 1 {#change-1}

Issuers must send the PAN details of the consumer VCN in the following parameters of the cardAccountDataSchema object:

* accountNumber
* expiryMonth
* expiryYear

For issuer-generated VCNs, issuers must also indicate whether a consumer VCN is single-use or multi-use using the following parameter:

* merchantAdviceCode


API Reference: `GET /authorizeService`

## Change 2 {#change-2}

When tokenizing a VCN, Mastercard will assign a payment account reference (PAR) value to the VCN and an optional notification will be sent. A new value will be added to the existing reasonCode field to indicate this change.
Issuers can opt-in to receive notifications when the PAR value is updated to be consistent across all VCNs linked to the same card account. The reasonCode field will have a new value to indicate this change:

* STATUS_UPDATE
* REDIGITIZATION_COMPLETE
* DELETED_FROM_CONSUMER_APP
* AUTHENTICATION_PERFORMED
* PAYMT_CHANNEL_PREFERENCE_UPDATED
* FUNDING_ACCOUNT_UPDATE
* TOKEN_BINDING
* ACCOUNT_BINDING
* **PAYMENT_ACCOUNT_REFERENCE_UPDATED: Payment account reference value was updated.**


API Reference: `GET /notifyTokenUpdated`

For more information about this functionality, refer to [GLB 11165.1](https://trc-techresource.mastercard.com/r/bundle/m_an11165_en-us/page/d/en-US/geq1738707561320.html)

## Impact {#impact}

**Change 1** - Existing issuers using VCNs, must share the PAN details and indicate if the VCN is a single-use or multi-use in the Authorize Service response to Mastercard. Issuers must update their implementation to start sending this information to Mastercard from the effective date.

**Change 2** - Issuers will need to opt-in to receive the NTU when the PAR value is updated to be consistent across all VCNs. Create a CIS project to opt-in.

### Personal data \& Privacy Note {#personal-data--privacy-note}

Issuers are reminded that the information presented via the pre-digitization API includes personal data which is subject to data privacy laws. Issuers must satisfy themselves that the processing of such personal data is compliant with applicable privacy laws.