On This Page

Release Notes

These release notes cover all releases to the production server for the week ending
May 8, 2026
.

Announcements

These announcements are for
May 8, 2026
.

TLS Updates

We are making changes to our implementation of Transport Layer Security (TLS).

TLS 1.3

To maintain the highest security standards for both browser-based and server-to-server connections, we will enable TLS 1.3 on the endpoints listed below. This enhancement is optional and will supplement the existing TLS 1.2 support, which will remain in place.
We will make changes to these endpoints on these dates:
Testing environment
: May 26, 2026
ics2wstesta.ic3.com
ics2wstest.ic3.com
apitest.cybersource.com
Production environment
: June 2, 2026
ics2wsa.ic3.com
ics2ws.ic3.com
api.cybersource.com
api.in.cybersource.com
ics2ws.in.ic3.com
Contact Customer Support if you have any questions about these changes.

TLS Certificate Lifetime Reduction

In alignment with new CA/Browser Forum regulations, the maximum TLS certificate lifetime will be reduced gradually as follows:
• Currently, the maximum lifetime for a TLS certificate is 200 days.
• Beginning March 15, 2027, the maximum lifetime for a TLS certificate will be 100 days.
• Beginning March 15, 2029, the maximum lifetime for a TLS certificate will be 47 days.
See this blog for more information about the TLS certificate lifetime changes:
How will this change impact connectivity?
Server-level (leaf) SSL/TLS certificates will remain valid until their scheduled expiration. Server-level (leaf) TLS certificates have shorter lifespans and must be reissued more frequently. We therefore recommend that clients trust the root certificate instead.
What is our recommendation?
We continue to recommend trusting the Root TLS certificates for all secure endpoints. This approach removes the need for periodic renewal of server level certificates and helps prevent connection failures caused by expired leaf certificates.
How can I tell which TLS certificate I am using?
Contact your server administrator or your network support team.
Where can I find the TLS Root certificate?
Continue trusting the root certificate to maintain connectivity with supported endpoints. You can download the root certificate from this article:
Contact your Customer Support representatives with any questions.

Webhooks Updates

Webhooks version 1 will be decommissioned by end of the year 2026. See Webhooks version 2 in the Developer Center.

Enhanced Webhook URL Review and Approval Process

We are introducing an enhancement to webhook subscription processing to improve security, compliance, and visibility for webhook-related URLs. Webhook URLs will be validated and reviewed before they can be used. This includes both newly submitted subscriptions and existing subscriptions currently on file. This change is expected to take place at the end of May 2026.

What is Changing

When a webhook subscription is created or updated, the URLs associated with that subscription will be evaluated through a validation and approval process.
This applies to:
  • Webhook URL
     (required)
  • OAuth URL
     (if applicable)
  • Health Check URL
     (if applicable)
As part of this enhancement, clients might now see the following user-facing statuses:
  • PENDING_REVIEW
  • BLOCKED
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

  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
    .

Impact on Existing Subscriptions

After this change goes live, we will run existing webhook subscriptions through the new validation process:
  • Existing subscription URLs will be assessed using the new validation framework.
  • URLs that require additional security review might change the status of the subscription to
    PENDING_REVIEW
    .
  • If any existing URL is identified as blocked, the associated subscription status will be updated to
    BLOCKED
    .
In cases where a subscription status is change to
BLOCKED
, clients will be expected to perform these tasks:
  • Review the affected endpoint(s).
  • Update the URL(s) to an acceptable endpoint.
  • Resubmit the subscription for processing.

For New Subscriptions

New webhook-related URLs may go through validation and, if necessary, security review before the subscription can proceed.

For Existing Subscriptions

Current subscriptions will also be reviewed after they go live. If an existing endpoint does not meet the new validation requirements, the subscription status might be updated to
BLOCKED
 until the URL is corrected.

If Your Subscription Is Marked BLOCKED

This means one or more URLs associated with the subscription cannot be used in their current form. To continue, the client must update the affected URL(s) and resubmit.

Why We Are Making this Change

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.

Message-Level Encryption Upcoming Mandate

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
September 2026
.
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 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.

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

HTTP Messaging Migration to JWT Messaging

By
September 2026
, 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
 in the
Getting Started with REST Developer Guide

Smart Auth Retirement

Smart Auth, also known as SuperAuth, is being discontinued. This product was often included in the Essentials package of products for small merchants.
Support for Smart Auth is being discontinued in phases. The final end of life occurs October 5, 2026.
Merchants currently using Smart Auth will receive a 90-day product sunset notification.
Merchants interested in a similar product can use Fraud Management Essentials (FME). FME is an actively supported service that offers improved fraud protection capabilities and system reliability.

Features Introduced This Week

Merchant-Initiated Transactions
 | RM-45052

Description
In the Transit - Deferred Aggregated Model, riders may tap with either a physical card or a digital wallet. When a physical card is used, the transaction is performed using the card’s Funding Primary Account Number (FPAN). When a digital wallet (for example, Apple Pay or Google Pay) is used, the transit tap generates a Device Primary Account Number (DPAN). If an aggregated or end-of-day transit transaction is declined, an outstanding debt is created and may be recovered through a Merchant-Initiated Transaction (MIT) debt recovery flow, using the appropriate account number, in accordance with applicable card-scheme rules.
Key points:
  • Debt recovery may originate from transactions that initially used a DPAN or FPAN.
  • For the Mastercard transit program the MIT debt recovery requires the use of the FPAN also for the cases that DPAN was initially used.
  • Successful debt recovery enables removal of the card from the transit deny list.
Mandate
Does not apply.
Audience
Users of Merchant-Initiated Transactions.
Benefit
DPAN debt recoveries are now possible for Mastercard. This does not affect Visa DPAN debt recoveries.
Technical Details
None.
Important Dates
Released to production April 24, 2026.

Fixed Issues

Transaction Error Codes
 | RM-44887

Description
This release fixes a mismapped error code that caused an incorrect transaction status.
When FDC Nashville Global or Chase Paymentech Solutions hard-declined an authorization due to an incorrect card verification value (CVV), our response mapped to a soft-decline (reason code 230). This placed the transaction in the status
Authorizations Needing Review
 in the Transaction by Phase page of the Business Center. That enabled merchants to choose to reverse the authorization, leading to incorrect reason code 102 DINVALIDDATA.
These transactions are now correctly mapped to reason code 211 DCARDREFUSED, which is a hard-decline that cannot be reversed.
Audience
Users who process through FDC Nashville Global or Chase Paymentech Solutions.
Technical Details
None.
Important Dates
Released to Production May 6, 2026.

Transactions Through Cielo
 | RM-45175

Description
This release fixes an issues in which authorization timeouts and processing errors from Cielo left transactions in an unknown state, leading merchants to retry them, which caused duplicate transactions. Now the authorization is reversed and the merchant is notified.
Audience
Users that process through Cielo.
Technical Details
None.
Important Dates
Released to production May 6, 2026.

Known Issues

Tax Calculation
 | EPS-37002

Description
A mapping error is causing tax calculation requests that contain a data validation error to return reason code 150 instead of 102.
Audience
Users of tax calculation.
Technical Details
None.
Workaround
None.