Release Notes {#rn-general} =========================== These release notes cover all releases to the production server for the week ending January 9, 2026. Announcements {#rn-announce} ============================ These are the announcements for January 9, 2026. 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 ""). Email Notifications {#email-notifications} ========================================== A new risk-mitigation feature will be introduced for Visa Acceptance Platform customers in the near future. When a merchant's business information or contact information is updated, the system will automatically send an email notification to the designated business contact for that account. This applies to updates performed using either the Business Center or an API. Legacy customers already receive a similar email notification alert for boarding registration and account information changes, as well as status updates. This upcoming release will include a modification to that email format to ensure a more consistent display with branding support for all customers. The email format will match the email sent to Visa Acceptance Platform customers to support a seamless transition when legacy customers migrate to Visa Acceptance Platform. For Visa Acceptance Platform customers, the email notification will not be sent for status or boarding registration-related events. Features Introduced This Week {#rn-features} ============================================ **Unified Checkout** \| RM-41346 and RM-41387 --------------------------------------------- Description : This release in the Business Center allows portfolio accounts and transacting merchant accounts to be enabled for Unified Checkout and its features. Portfolio users can see additional features. This functionality was already available for the API. Mandate : Does not apply. Audience : Portfolio account users. Benefit : Unified Checkout is a hosted payment solution that provides a single integrated interface for accepting a wide range of digital payments directly on a merchant's ecommerce page. It is designed to reduce checkout friction, enhance security, and increase sales conversions. Technical Details : None. Important Dates : Released to production January 6, 2026. **Merchant Boarding** \| RM-40886 --------------------------------- Description : This release enables Payouts as a card type on the merchant boarding template for merchants that process through VPC. Mandate : Not applicable. Audience : Portfolio users who board merchants with VPC as their processor. Benefit : Enabling Payouts provides an additional payment option for merchants. Technical Details : Enable Payouts at the portfolio level and check the Payouts box in the Processor section. Important Dates : Released to production January 7, 2026. **Invoicing** \| RM-40845 ------------------------- Description : This release enables merchants to use these optional capabilities: * Set an expiration date when you create or edit invoices. * Extend expiration dates on existing invoices. {#rn-features_ul_xpc_11c_xhc}When an invoice payment link expires, the status of the link does not automatically change from *Active* to *Inactive*. The link remains in its current state, but the expiration message appears when the expired link is accessed. : When a customer attempts to access an expired invoice payment link, they receive a message stating that the link is expired. The message also directs the customer to contact the business that issued the link. : When this feature is released, expiration dates will not be applied automatically to existing invoices. Merchants can manually update expiration dates on existing invoice payment links. Mandate : Does not apply. Audience : Merchants who use invoicing. Benefit : Setting an expiration date for an invoice payment link can prevent unauthorized payments. Unauthorized payments can occur when a link remains accessible or relies on manual deactivation. Technical Details : To configure an invoice payment link expiration date, go to the **Pay by Link** module in the Business Center, create a new link or edit an existing link, and configure the expiration date field. If a customer needs more time to complete a payment, the merchant can update expiration dates on the existing invoice payment link. Important Dates : Released to production January 8, 2026. **Pay By Link** \| RM-40845 --------------------------- Description : This release enables merchants to use these optional capabilities: * Set an expiration date when you create or edit payment links. * Extend expiration dates on existing payment links. {#rn-features_ul_ukf_2bc_xhc}When a payment link expires, the status of the link does not automatically change from *Active* to *Inactive*. The link remains in its current state, but the expiration message appears when the expired link is accessed. : When a customer attempts to access an expired payment link, they receive a message stating that the link is expired. The message also directs the customer to contact the business that issued the link. : When this feature is released, expiration dates will not be applied automatically to existing payment links. Merchants can manually update expiration dates on existing payment links. Mandate : Does not apply. Audience : Merchants who use Pay By Link. Benefit : Setting an expiration date for a payment link can prevent unauthorized payments. Unauthorized payments can occur when a link remains accessible or relies on manual deactivation. Technical Details : To configure a payment link expiration date, go to the **Pay by Link** module in the Business Center, create a new link or edit an existing link, and configure the expiration date field. If a customer needs more time to complete a payment, the merchant can update expiration dates on the existing payment link. Important Dates : Released to production January 5, 2026. **Webhooks** \| RM-40845 ------------------------ Description : A webhook notification can be sent to merchants and independent software vendors when invoices or payment links are created in the Business Center. : Merchants must subscribe to an Invoicing or Pay by Link creation event to receive the Webhook notifications. Mandate : Does not apply. Audience : Benefit : Merchants and independent software vendors can integrate the Invoicing or Pay by Link webhooks as a trigger that begins their business processes. Technical Details : None. Important Dates : Released to production January 5, 2026. **Salesforce Commerce Cloud** ----------------------------- Description : This release adds Unified Checkout to Salesforce Commerce Cloud. Mandate : Does not apply. Audience : Users of Salesforce Commerce Cloud. Benefit : Unified Checkout is a hosted payment solution that provides a single integrated interface for accepting a wide range of digital payments directly on a merchant's ecommerce page. It is designed to reduce checkout friction, enhance security, and increase sales conversions. Technical Details : None. Important Dates : Released to production January 6, 2026. **Merchant Boarding** \| RM-39965 --------------------------------- Description : Portfolio merchants who use Prisma and the Visa Acceptance Platform can now board merchants using the Business Center's Merchant Management feature. Mandate : Does not apply. Audience : Portfolio merchants who use Prisma and the Visa Acceptance Platform. Benefit : Merchant management enables partners and resellers to board and manage their merchant accounts in a streamlined online interface instead of using the API. Technical Details : No action is required by merchants. Important Dates : Released to production Janaury 5, 2026. **Merchant Boarding in Japan** \| RM-40408 ------------------------------------------ Description : This release enables portfolio merchants to enter a shop name during merchant boarding in three new languages: Japanese, Romaji, and Katakana, for portfolios that are enabled for CSKK. Mandate : Does not apply. Audience : Portfolios that are CSKK-enabled. Benefit : Additional language enable additional flexibility in naming shops. Technical Details : No action is required. Important Dates : Released to production January 5, 2026. **Transaction Search** \| RM-39799 ---------------------------------- Description : Searching by token ID will now show more API events related to that token, including creation, updates, retrievals, and deletions, in addition to the existing view of payments and other service calls made using the token. Mandate : Does not apply. Audience : Merchants who use the Token Management System. Benefit : Additional details about token events. Technical Details : None. Important Dates : Released to production January 5, 2026. Fixed Issues {#rn-fixed-issues} =============================== No customer-facing fixes were released this week. Known Issues {#rn-known-issues} =============================== **Transaction Search** \| EPS-34742 ----------------------------------- Description : When merchants load a saved search that contains more than one filter, only one filter is shown. The other filters are blank or missing. Audience : Merchants who use Transaction Search. Technical Details : None. Workaround : None. **Virtual Terminal** \| EPS-35660 --------------------------------- Description : If a merchant is generating reports by filtering *Client Application* with *UBC Virtual Terminal* or *Legacy Virtual Terminal* options, they will not see Virtual Terminal transactions in the reports. Audience : Merchants who use the legacy Virtual Terminal for payment transactions. Technical Details : The transactions use the value *UBC Virtual Terminal* , but the filter option in the report setting is *Legacy Virtual Terminal*. As a result, it falsely appears that transactions are missing in the reports. Workaround : Until the issue is fixed, do not use the *Legacy Virtual Terminal* filter option in the report setting. Follow these steps: : 1. In report settings, set **Client Application** to **All**. 2. Add the **Source** field to your report. 3. After export, filter the **Source** column in Excel for **UBC Virtual Terminal**.