TLS 1.3

TLS Certificate Lifetime Reduction

What is Changing

Webhook URL
(required)
OAuth URL
(if applicable)
Health Check URL
(if applicable)

PENDING_REVIEW
BLOCKED

Status Descriptions

How the New Process Works

A webhook subscription is created or updated.
Submitted URLs are checked against existing approval records.
New or unknown URLs are evaluated through automated validation.
If additional review is required, the subscription status changes to
PENDING_REVIEW
.
If any URL is rejected or blocked, the subscription status changes to
BLOCKED
.
If all required URLs are approved, the subscription status changes to
INACTIVE
.

Impact on Existing Subscriptions

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
.

Review the affected endpoint(s).
Update the URL(s) to an acceptable endpoint.
Resubmit the subscription for processing.

For New Subscriptions

For Existing Subscriptions

If Your Subscription Is Marked BLOCKED

Why We Are Making this Change

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.

Overview of MLE

JSON Web Token Construction Update

HTTP Messaging Migration to JWT Messaging

3-D Secure

| RM-44940

Description

This release adds support for 3-D Secure data-only transactions for Rede for Visa and Mastercard e-commerce transactions in Brazil. It enables merchants to submit enriched 3-D Secure data in the Cybersource REST API without triggering cardholder authentication or challenge flows. This is an API-only enhancement; there are no changes in the Business Center.

Mandate

Does not apply.

Audience

This release affects Cybersource merchants using Rede in Brazil, for Visa and Mastercard e-commerce transactions.

Benefit

This feature enables merchants to submit authorization requests with additional security-related data and checks in the background, without adding friction to the checkout experience. Because no cardholder challenge is triggered, merchants can provide more issuer-relevant transaction context while keeping the purchase flow unchanged for the customer.

By giving issuers more information during authorization, this enhancement can improve approval rates, reduce false declines, and decrease unnecessary authentication challenges. Liability remains with the merchant.

Technical Details

To implement this feature, merchants submit a standard authorization request with the following 3DS Data Only fields:

Required fields

consumerAuthenticationInformation.cavv

consumerAuthenticationInformation.paSpecificationVersion

consumerAuthenticationInformation.directoryServerTransactionId

processingInformation.commerceIndicator

Optional field

consumerAuthenticationInformation.xid

Additional implementation requirements:

Submit the transaction as an e-commerce payment.
Submit the transaction in BRL.
Process the transaction as Visa or Mastercard through REDE.
No challenge is performed, no step-up authentication is expected, and the response follows the standard authorization response structure.

Request Example

{
  "processingInformation": {
    "commerceIndicator": "internet"
  },
  "paymentInformation": {
    "card": {
      "number": "4111111111111111",
      "expirationMonth": "12",
      "expirationYear": "2030",
      "sourceAccountType": "C"
    }
  },
  "consumerAuthenticationInformation": {
    "cavv": "AAABBIIFmAAAAAAAAAAAAAAAAAA=",
    "xid": "MDAwMDAwMDAwMDAwMDAwMzIyNzY=",
    "paSpecificationVersion": "2.2.0",
    "directoryServerTransactionId": "f3eecb72-31b3-4a62-b9af-8e6a8b7a0abc"
  },
  "orderInformation": {
    "amountDetails": {
      "totalAmount": "100.00",
      "currency": "BRL"
    },
    "billTo": {
      "firstName": "First",
      "lastName": "Last",
      "address1": "Av Paulista 123456",
      "locality": "Sao Paulo",
      "administrativeArea": "SP",
      "postalCode": "01310-100",
      "country": "BR",
      "email": "[email protected]"
    },
    "shipTo": {
      "firstName": "First",
      "lastName": "Last",
      "address1": "Av Paulista 123456",
      "locality": "Sao Paulo",
      "administrativeArea": "SP",
      "postalCode": "01310-100",
      "country": "BR"
    }
  }
}   				

Response Example

{
  "id": "6654706105956431203955",
  "status": "AUTHORIZED",
  "submitTimeUtc": "2026-04-21T14:22:10Z",
  "processorInformation": {
    "approvalCode": "831000",
    "responseCode": "00",
    "transactionId": "123456789012345"
  },
  "networkTransactionId": "987654321234567",
  "reconciliationId": "6654706105956431203955"
}				

Important Dates

Released to production April 24, 2026.

Updates for FDC Nashville Global

| RM-44320

Description

These features are released for FDC Nashville Global:

Account Name Inquiry

: Ensures compliance with network mandates and enhances fraud prevention by validating account holder names during account verification and 0 amount authorization transactions.

Extended Authorizations

: Enables Extended Authorization capabilities, allowing merchants to hold approved authorizations for up to 30 calendar days for eligible Card Not Present transactions and customer-initiated transactions.

AFT Refund

: AFT bitmap 43 Authorization/Credit Authorization changes and AFT Credit Authorization changes, disabling Credit Auth for FDC Nashville Global Visa AFT transactions, and updating bitmap 43 merchant name for all AFT transactions.

Mandate

Does not apply.

Audience

FDC Nashville Global merchants.

Benefit

This release enhances fraud prevention and allows merchants to hold approved authorizations for up to 30 calendar days.

Technical Details

None.

Important Dates

Released to production May 28, 2026.

Follow-On Credit Transactions

| RM-45829

Description

This release fixes an error in which some follow-on credit transactions for some payment gateways were failing with an ESYSTEM error, returning the message

The follow-on credit cannot be processed because the capture transaction has not been processed yet

.

Audience

All gateways that have enabled Auto Capture.

Technical Details

None.

Important Dates

Released to production May 22, 2026.

Transaction Search

| EPS-37429

Description

After new transacting organizations are created, merchant-level organizations cannot see the transacting organization's transactions in the Business Center immediately. In some cases, it can take weeks for tansactions to appear.

Audience

Portfolio merchants.

Technical Details

None.

Workaround

Search for the transactions using a transacting MID user or a portfolio MID user.

Payer Authentication

| EPS-37750

Description

When portfolio accounts onboard merchants to 3-D Secure processing for Cartes Bancaires cards on the Business Center's Payer Authentication Configuration screen for transacting accounts, the Acquirer ID is validated for 1-35 alphanumeric characters only. Accounts with space or hyphen characters in their names are not being accepted.

Audience

Portfolio merchants.

Technical Details

None.

Workaround

Contact support.