Release Notes {#rn-general} =========================== These release notes cover all releases to the production server for the week ending August 28, 2026. Announcements {#rn-announce} ============================ These announcements are for August 28, 2026. SOAP Tooklit Authentication Update {#soap-p12} ============================================== Cybersource will no longer support username- and password-based authentication for merchants who use the *SOAP toolkit key* . You are required to remove username- and password-based authentication from your SOAP toolkit integration and transition to certificate-based authentication by these dates: * Test Environment: April 15, 2026 * Production validation test (shock test): September 30, 2026. This applies only to selected merchants. * Production Environment: October 7, 2026 {#soap-p12_ul_hbm_lwq_zjc} Your API requests to Cybersource will be rejected if you do not implement P12 authentication by the required dates. See [*P12 Authentication Upgrade for SOAP Toolkit Key Users Migration Guide*.](https://developer.cybersource.com/docs/cybs/en-us/so-p12/migration/all/so/so-p12/so-p12-intro.md "") Batch Upload Service IP Address Updates {#ip-addresses} ======================================================= The legacy IP address for the Cybersource Batch Upload service will be replaced by two new IP addresses. We recommend that you use domain names instead of IP addresses. The new addresses will take effect at these URLs and times: **Testing Environment** `batchtest.cybersource.com` July 28, 2026, at 4:00 am GMT **Production Environment:** `batch.cybersource.com` September 15, 2026, at 4:00 am GMT Enhanced Webhook URL Review and Approval Process {#webhooks-urls} ================================================================= We have introduced an enhancement to webhook subscription processing to improve security, compliance, and visibility for webhook-related URLs. Webhook URLs are now validated and reviewed before they can be used. This includes both subscriptions and existing subscriptions currently on file. **What is Changing** {#webhooks-urls_section_dnx_jdt_1jc} --------------------------------------------------------- When a webhook subscription is created or updated, the URLs associated with that subscription are evaluated through a validation and approval process. Applies to: * **Webhook URL** (required) * **OAuth URL** (if applicable) * **Health Check URL** (if applicable) {#webhooks-urls_ul_enx_jdt_1jc} As part of this enhancement, clients might now see user-facing statuses: * **PENDING_REVIEW** * **BLOCKED** {#webhooks-urls_ul_fnx_jdt_1jc} The existing **INACTIVE** status remains unchanged and continues to indicate that the subscription is approved and ready within the current lifecycle. Status Descriptions ------------------- | **Status** | **Description** | |--------------------|----------------------------------------------------------------------------------------------------------------------------------------| | **PENDING_REVIEW** | One or more submitted URLs are being validated or awaiting required security approval. | | **BLOCKED** | One or more URLs were rejected or identified as unsafe or non-compliant. The subscription cannot proceed until the URL(s) are updated. | | **INACTIVE** | All required approvals are complete, and the subscription is ready under the existing activation flow. | **How the New Process Works** {#webhooks-urls_section_hnx_jdt_1jc} ------------------------------------------------------------------ 1. A webhook subscription is created or updated. 2. Submitted URLs are checked against existing approval records. 3. New or unknown URLs are evaluated through automated validation. 4. If additional review is required, the subscription status changes to **PENDING_REVIEW**. 5. If any URL is rejected or blocked, the subscription status changes to **BLOCKED**. 6. If all required URLs are approved, the subscription status changes to **INACTIVE**. {#webhooks-urls_ol_inx_jdt_1jc} In cases where a subscription status is change to **BLOCKED**, clients are expected to perform these tasks: 7. Review the affected endpoint(s). 8. Update the URL(s) to an acceptable endpoint. 9. Resubmit the subscription for processing. {#webhooks-urls_ul_lnx_jdt_1jc} **For New Subscriptions** {#webhooks-urls_section_mnx_jdt_1jc} -------------------------------------------------------------- New webhook-related URLs may go through validation and, if necessary, security review before the subscription can proceed. **Why We Are Making This Change** {#webhooks-urls_section_pnx_jdt_1jc} ---------------------------------------------------------------------- This enhancement is designed to: * **Reduce security risk** by preventing outbound calls to unapproved endpoints. * **Improve compliance** through stronger review and approval controls. * **Increase transparency** with clearer client-visible statuses. * **Support scale** through a standardized and repeatable validation process. {#webhooks-urls_ul_qnx_jdt_1jc} Message-Level Encryption Upcoming Mandate {#announcement-mle} ============================================================= An updated version of message-level encryption (MLE) will become mandatory in order for merchants to use the APIs. Portfolio owners must enable this updated version of MLE for their merchants by **March 2027**. This required MLE update encrypts all data in your API response messages. The previous version of MLE encrypted only request messages. If your merchants are already using custom JSON Web Token messaging, they must also update how their system constructs JWTs. **Merchants who are using HTTP signature messaging must migrate their system to JWT messaging.** > You risk transaction failures if you do not implement this MLE update. Overview of MLE --------------- MLE is a robust security protocol designed to encrypt individual messages or payloads at the application layer. By protecting sensitive data at the message level, MLE ensures that your information remains secure as it moves through systems and networks, providing a layer of security beyond traditional transport encryption. Enabling MLE requires you to create a REST API key for request messages and a *REST -- API Response MLE* key for response messages. If your organization is using a meta key, the portfolio account or merchant account user who created the meta key must also create the REST -- API Response MLE key. Update Methods : * Create or update your custom MLE integration using JWTs with P12 certificates. For more information, see the [Enable Message-Level Encryption](https://developer.cybersource.com/docs/cybs/en-us/platform/developer/all/rest/rest-getting-started/restgs-jwt-message-intro/restgs-mle-intro.md "") section in the *Getting Started with REST Developer Guide*. For a method using shared secret key pairs, see the HTTP Messaging Migration to JWT Messaging section below. * Update your REST API SDK. For more information, see the *REST API related products* section in the [Cybersource GitHub](https://github.com/CyberSource ""). JSON Web Token Construction Update ---------------------------------- There are new requirements for how to construct JSON Web Tokens (JWTs) in order to send API request messages. If you use a custom integration to construct JWTs, you must update your system to remain compliant. This update is necessary to support the new MLE requirements. Update Methods : * See [Construct JWT Messages Using a P12 Certificate](https://developer.cybersource.com/docs/cybs/en-us/platform/developer/all/rest/rest-getting-started/restgs-jwt-message-intro/restgs-jwt-const-intro.md "") in the *Getting Started with REST Developer Guide* * See [Construct JWT Messages Using a Shared Secret Key Pair](https://developer.cybersource.com/docs/cybs/en-us/platform/developer/all/rest/rest-getting-started/restgs-jwt-shared-secret-intro/restgs-jwt-con-shared-secret-intro.md "") in the *Getting Started with REST Developer Guide* HTTP Messaging Migration to JWT Messaging ----------------------------------------- By **March 2027** , all merchants using HTTP signature messaging must migrate to JWT messaging in order to support MLE. Merchants already using HTTP signature messaging with shared secret key pairs can now continue using their existing keys with JWT messaging. Update Method : * See [Construct JWT Messages Using a Shared Secret Key Pair](https://developer.cybersource.com/docs/cybs/en-us/platform/developer/all/rest/rest-getting-started/restgs-jwt-shared-secret-intro.md "") in the *Getting Started with REST Developer Guide* {#announcement-mle_ul_mkf_nff_1kc} Secure Acceptance Sunset {#secure-acceptance-sunset} ==================================================== Secure Acceptance is being sunset as part of a move toward modern, web-based payment acceptance solutions. The target date for merchants to complete migration from Secure Acceptance is September 30, 2026. If you have already begun migrating off Secure Acceptance and expect to complete the move by this date, disregard this message. Unified Checkout is available as the recommended migration path. It provides a low-code payment acceptance experience with support for expanded payment options and integrated services. For more details about this change and guidance on how to migrate, see this knowledge base article: [Secure Acceptance Sunset (KA-11531)](https://support.visaacceptance.com/knowledgebase/Knowledgearticle/?code=KA-11531 ""). Review your migration plans and take the necessary steps to move off Secure Acceptance before the deadline. If you need assistance, contact your Visa representative. Features Introduced This Week {#rn-features} ============================================ **Login Page Enhancement: Improved Visibility of Forgot Password Link** \| RM-44255 ----------------------------------------------------------------------------------- Description : This release repositions the Forgot Password link on the login page to improve visibility and align password recovery more closely with the login flow. This is a user interface change only. It does not affect authentication behavior or password reset functionality. Mandate : Does not apply. Audience : All clients. Benefit : Clients can locate the password recovery option more easily from the login page. Technical Details : The Forgot Password link now appears in a different position on the login page. The Forgot Password link moved from the page footer to a position next to the Password field. No customer action is required. Before: ![Login page before the change, showing the original position of the Forgot Password link](/content/dam/documentation/cybs/en-us/topics/reference/notes/relnotes/rn-2026-08-28/images/forgot-password-before.png/jcr:content/renditions/original) After: ![Login page after the change, showing the repositioned Forgot Password link](/content/dam/documentation/cybs/en-us/topics/reference/notes/relnotes/rn-2026-08-28/images/forgot-password-after.png/jcr:content/renditions/original) Important Dates : Released on August 24, 2026. {#rn-features_dl_i1g_nxy_hkc} Fixed Issues {#rn-fixed-issues} =============================== Merchant ID Dropdown Fix on Transactions through Merchant Management Service \| RM-48183 ---------------------------------------------------------------------------------------- Description : The Merchant ID dropdown UI element on the Transactions page was producing an error that prevented users from fetching the merchant list. This fix resolves that error and users can now use the UI as intended. Audience : Merchants, Issuers, and Acquirers. Technical Details : The Transaction Search merchant list dropdown UI can now be populated for accounts when account_id is greater than 30 characters. Important Dates : Released on August 25, 2026 Known Issues {#rn-known-issues} =============================== There are no known issues this week.