Release Notes {#rn-general} =========================== These release notes cover all releases to the production server for the week ending October 31, 2025. Announcements {#rn-announce} ============================ These are the announcements for October 31, 2025. Webhooks Updates {#webhooks-validations-decommission} ===================================================== Webhooks version 1 will be decommissioned in April 2026. See [Webhooks version 2 in the Developer Center](https://developer.cybersource.com/api-reference-assets/index.md#webhooks ""). Features Introduced This Week {#rn-features} ============================================ **Reporting** \| RM-39487 ------------------------- Description : This release adds new fields to the reports listed below. These are standard fields and all fields are optional. There will be no changes for existing report subscriptions and users can add these additional fields to their subscriptions if needed. **New Transaction Request Report Fields** * Validation level * Raw validation code * Result code * Validation message * Bin country * Merchant advice code * Code raw * Sub-merchant ID * PFID * Store Name * Auth reversal ID * Order ID {#rn-features_ol_tjy_j5m_dhc} **Payment batch detail report** * Merchant advice code * Code raw * Sub-merchant ID * PFID * Store Name * Auth reversal ID * Order ID {#rn-features_ol_ujy_j5m_dhc} **All standard reports** * Sub-merchant ID * PFID * Store Name * Auth reversal ID * Order ID {#rn-features_ol_vjy_j5m_dhc} Audience : All Reporting module users. Benefit : **Bank account validation** This feature is for merchants boarded on the new Visa Bank Account Validation product. If the new fields are not added to the report, the TRR reports will still show the transactions but only the request information and not the Response information. **Auth reversal ID** This is a requirement from Microsoft Dynamics GP-AP. : **Merchant advice code** This helps avoid excessive reattempts, which could incur penalties. Technical Details : None. Important Dates : Released to production October 21, 2025. **Payer Authentication** \| RM-40448 ------------------------------------ Description : This release adds support for Paypak payments through Payer Authentication version 2. The integration uses the same process as existing payment schemes like Visa and Mastercard. Audience : Domestic merchants in Pakistan who use Payer Authentication version 2. Benefit : Domestic merchants in Pakistan will be able to accept Paypak card payments. Technical Details : None. Important Dates : Released to production October 28, 2025. Fixed Issues {#rn-fixed-issues} =============================== No customer-facing fixes were released this week. Known Issues {#rn-known-issues} =============================== **Cartes Bancaire Payments** \| EPS-34070 ----------------------------------------- Description : This issue affects Cartes Bancaire transactions processed through Payer Authentication, in which the payer has been authenticated. The Business Center's Transaction Details page does not display Payer Authentication information. The page also shows the transaction as unauthenticated (ECI value of `7` or `0`), which might result in issuer downgrades. Audience : Merchants using Payer Authentication. Technical Details : None. Workaround : None. **Merchant Management** \| EPS-34153 ------------------------------------ Description : Resellers who migrate from the legacy merchant management platform to the new platform might not be able to create merchant groups from their portfolio account because the list of merchant accounts does not appear. Audience : Resellers who migrate from the legacy merchant management platform to the new platform. Technical Details : None. Workaround : Create merchant groups from a merchant account that has the required permissions. **Token Management Service** \| EPS-34372 ----------------------------------------- Description : If the value of the merchantId field is fewer than six digits, it is not added to the vault in Token Management. Audience : Merchants who who use the Token Management Service and have a merchantId field with a value fewer than six digits. Technical Details : None. Workaround : None. **Decision Manager** \| EPS-34254 --------------------------------- Description : When Decision Manager is used with Device Fingerprint by a portfolio account, the device attributes are not returned, even though device profiling was successful and the corresponding sessionID field value was sent in the Decision Manager API call. Audience : Users of Decision Manager with Device Profiling through a portfolio account. Technical Details : None. Workaround : None. **Business Center** \| EPS-34419 -------------------------------- Description : When you are at the Service Orchestration page in the Business Center and you try to navigate to any other page, the page is blank until you refresh it. Audience : Users of the Business Center. Technical Details : None. Workaround : Refresh the browser page. **Payment Settlement** \| EPS-34456 ----------------------------------- Description : An intermittent issue affects payment settlement through VDC Vantiv Gateway. When a merchant accidentally attempts to settle a transaction that has already been settled, it is settled again instead of being rejected with an error message. Audience : Merchants who process through the VDC Vantiv Gateway. Technical Details : None. Workaround : None. **Merchant-Initiated Transactions** \| EPS-34461 ------------------------------------------------ Description : In some MIT reauthorization capture scenarios, the settlement process may reference an incorrect network transaction ID, resulting in response code 307 errors and potential funding delays. This occurs when the original authorization has expired. Audience : Users of Merchant-Initiated Transaction. Technical Details : None. Workaround : Perform a manual reauthorization before settlement.