Skip to main content
Welcome to the preview portal — This is an early release of the new Doc Hub experience, with more content coming soon.
Release Notes

Release Notes

Weekly production release notes, organized by month: features, fixed issues, and known issues, plus announcements.

Announcements

These announcements apply across weekly releases.

Current Announcements
Message-Level Encryption Upcoming Mandate

An updated version of message-level encryption (MLE) will become required in order for merchants to use the APIs. Portfolio owners must enable this updated version of MLE in order 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.

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.
  • Update your REST API SDK. For more information, see the REST API related products section in the GitHub.

JSON Web Token Construction Update

There are new requirements for how to construct JSON Web Tokens (JWTs) 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 March 2027, all merchants using HTTP signature messaging must migrate to JWT messaging 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:

Enhanced Webhook URL Review and Approval Process

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 new subscriptions and existing subscriptions currently on file.

Introduced Changes

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)

As part of this enhancement, user-facing statuses have been added:

  • 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

StatusDescription
PENDING_REVIEWOne or more submitted URLs are being validated or awaiting required security approval.
BLOCKEDOne or more URLs were rejected or identified as unsafe or non-compliant. The subscription cannot proceed until the URLs are updated.
INACTIVEAll 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.

In cases where a subscription status is changed to BLOCKED, merchants are expected to perform these tasks:

  1. Review the affected endpoints.
  2. Update the URLs to an acceptable endpoint.
  3. Resubmit the subscription for processing.

For New Subscriptions

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

Why We Are Making This Change

This enhancement provides these benefits:

  • Reduce security risk by preventing outbound calls to unapproved endpoints.
  • Improve compliance through stronger review and approval controls.
  • Increase transparency with clearer merchant-visible statuses.
  • Support scale through a standardized and repeatable validation process.
PHP Runtime Security Update Requirement

Organizations should use a supported PHP runtime version and complete any required updates to help keep their payment environments secure.

For more information about this requirement and any necessary actions, follow the link and log in to to review the PHP Runtime Security Update Requirements knowledge base article:

PHP Runtime Security Update Requirements

Network Routing Architecture Update

endpoints will be migrated from the current routing model to a new architecture using updated IP subnet ranges.

This enhancement improves the performance, resiliency, and reliability of transaction delivery over the Internet. It will also enable seamless transaction routing across multiple Visa data centers, supporting more consistent and reliable transaction processing.

Endpoints and IP Addresses Included

Current Application and endpoints:

CAS/Test: apitest.cybersource.com (current IP address: 66.185.182.49)

Production: api.cybersource.com (current IP address: 66.185.182.149)

Potential Impact

Merchants who connect to the REST API endpoints (apitest.cybersource.com and api.cybersource.com) use a Domain Name System (DNS) should not be affected. DNS records will be updated automatically to use the new routing architecture.

Merchants with networks configured to allowlist IP addresses or who have hardcoded IP addresses will likely be impacted. These merchants should update proxy or firewall settings to include the new Visa IP address ranges.

There are no changes to TLS certificates or supported ciphers as part of this migration. However, continues to recommend trusting the root TLS certificates for all secure endpoints.

Migration Timeline

CAS/Test: October 15, 2026

Production: January 31, 2027

Now Available

This technology is now available in both the test and production environments through these domains:

CAS/Test: apitest.visaacceptance.com

Production: api.visaacceptance.com

Deploying in the CAS/Test Environment provides a safe environment to test and validate access. When testing is complete, you can migrate production processing.

How to Adopt This Change

To use the new routing architecture, your firewall or your commerce platform provider's firewall must be configured to permit outbound traffic to the Visa cloud.

This large, dynamic IP address space represents a significant change from current access configurations. Therefore, it is critically important to test firewall configurations and confirm that connections are successful before migrating production traffic.

Merchants who require IP address allowlists can use one of these options:

Option 1: Merchants can add these specific subnet ranges to IP address allowlists:

  • 198.217.128.0/17
  • 198.241.128.0/17
  • 66.185.176.0/20

Option 2: Merchants can add these generic subnet ranges to IP address allowlists:

  • 198.241.206.0/24
  • 198.241.207.0/24
Webhooks Updates

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

TLS Update

TLS Certificate Lifetime Reduction

In alignment with new CA/Browser Forum regulations, the maximum TLS certificate lifetime will be reduced gradually:

• 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:

https://www.digicert.com/blog/tls-certificate-lifetimes-will-officially-reduce-to-47-days

How will this change impact connectivity?

Server-level (leaf) 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:

https://support.visaacceptance.com/knowledgebase/Knowledgearticle/?code=KA-09802

Contact your Customer Support representatives with any questions.

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 end of life occurs October 5, 2026.

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.

Earlier Announcements

These announcements appeared in earlier weekly releases.

Secure Acceptance Sunset

Secure Acceptance is being sunset as part of a move toward web-based payment acceptance solutions. The target date for merchants to complete migration from Secure Acceptance was September 30, 2026.

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).

Review your migration plans and take the necessary steps to move from Secure Acceptance before the deadline. If you need assistance, contact your Visa representative.

Transaction Search Performance Update

is aware of an intermittent issue that impacts transaction search performance. The search functions in the APIs and are served from a shared search platform that is used by all Transaction Management module customers. An issue can occur when there is unusually high search activity, which places a heavy load on the shared search service. applied traffic controls to reduce the impact and is rolling out additional safeguards to prevent recurrence.

To improve transaction search performance and provide more consistent response times, the transaction search platform is being updated for requests that use multiple search identifiers. As part of this enhancement, searches that include multiple identifiers will support up to 15 identifiers per request. Merchants whose integrations currently submit larger batches should update their systems to divide searches into smaller requests.

Merchant Impact

  • You might occasionally experience slower response times or timeouts.
  • For API integrators, an HTTP 429 response often indicates that there are too many request responses on Transaction Search, Case Search, or the Find Similar Transactions feature, particularly for large, broad, or long-date-range searches.
  • Keep multi-value lookups to 15 identifiers or fewer per search.
  • Use the narrowest date range that answers your question. A period of no more than 7 days is recommended for interactive transaction searches.
  • Break large bulk lookups into smaller batches instead of using one large combined search.
  • Avoid broad wildcard searches, especially searches that use a short prefix and an asterisk (*).
  • If a search is slow or times out, wait a moment before retrying instead of retrying immediately.
  • For API integrators:
    • Limit each request to 15 or fewer identifiers.
    • Use the narrowest date range your job needs.
    • Implement back off on timeouts or errors instead of tight-loop retries.
    • If you receive a 429 response, honor any Retry-After value and reduce your request rate and batch size rather than immediately retrying.
  • If your workflow repeatedly requires a large multi-identifier or long-date-range search, contact your support or account team so that it can be reviewed for the batch and export path or an appropriate exception.

Review your search and integration patterns and adhere to the guidance provided in the Best Practices for Implementing Searches section.

Best Practices for Implementing Searches

These best practices apply to searches that you implement using the Transaction Search API, Case Search API, and the . Following these practices will help keep your searches and detail lookups fast and reliable.

General Guidance:

  • Keep multi-value lookups to 15 identifiers or fewer per search. Identifiers include reference numbers, request IDs, or account numbers. For larger lookups, use another method instead of one very large interactive request.
  • Use the narrowest date range that answers your question. Use a period of no more than 7 days for interactive transaction searches.
  • Break large bulk lookups into smaller batches. For example, implement several searches of less than or equal to 15 identifiers and less than or equal to 7 days instead of implementing one combined search that spans many identifiers and a long date range.
  • Retry failed or slow searches manually, using a short pause instead of immediately re-running the identical search in an automated loop.

Practices to Avoid:

  • Do not implement broad wildcard searches. These searches scan a large portion of the search index and use the most resources.

  • These wildcard validation rules now apply:

    • Leading wildcard searches are no longer accepted.

    • Wildcard searches must contain a minimum of three characters preceding the wildcard character (*). These examples demonstrate the unsupported and the accepted wildcard formats.

      Unsupported Wildcard Formats:

      • *ABC
      • A*
      • AB*
      • 12*

      Accepted Wildcard Formats:

      • ABC*
      • ABCD*
      • 123*
  • Avoid combining a large number of identifiers with a long date range in the same search. Cost increases roughly with identifiers multiplied by a date range, so a search that is fine alone can be expensive when both are large together.

  • Avoid automated rapid-retry on a timeout. An identical search that timed out will typically time out again if re-run immediately, which adds load on the service without improving results.

API Searches: Request Shape:

  • Cap each request to 15 or fewer identifiers when using multi-value lookups. If your integration currently sends larger batches, split them into multiple smaller requests.
  • Use an end-of-day reconciliation or bulk report instead of paging through many large interactive search requests.
  • Use the narrowest date range your job actually needs. Recurring jobs that request a wide window are a common source of avoidable load.
  • Avoid wildcard or short-prefix values in identifier fields. Search for an exact full value when it is available.

API Searches: Retry and Error Handling:

  • Implement a back-off retry instead of tight-loop retry. If a request times out or errors, wait before retrying, and increase the wait time on repeated failures (exponential back off).
  • If you receive a 429 (rate limited) response, treat it as a signal to slow down, not a bug to route around. Honor any Retry-After value if present, and reduce your request rate/batch size rather than retrying immediately or in parallel.
  • Cap your retry attempts for a given request. For example, make 3 to 5 attempts with increasing back-off retries and alert/log instead of retrying indefinitely.
  • Watch for repeated identical requests from your own systems. A scheduled job that re-issues the exact same search on every run because a previous run did not complete can create a sustained load without your team realizing it. Add job-level locking or de-duplication search so a stopped run does not stack up.

Searches:

  • Transaction Search: search on a specific field (order number, request ID, reference number) instead of a broad free-text and keyword term when possible. Keep the date range to 7 days or fewer.
  • Quick Search: use a reasonably narrow date range rather than the widest default. If you manage multiple sub-accounts under a parent account, search from the specific sub-account instead of from the top-level parent view when you know the account where the transaction belongs.
  • Bulk Export and Reporting: if you need a large number of transactions or cases, use the report feature to pull the full set at once instead of repeatedly re-running and paging through search results. If a search is slow or times out, wait a moment and retry once instead of repeatedly clicking search or refresh in quick succession.
Batch Upload Service IP Address Updates

The legacy IP address for the 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 a.m. UTC

Production Environment:

batch.cybersource.com

September 15, 2026, at 4:00 a.m. UTC

SOAP Toolkit Authentication Update

will no longer support username- and password-based authentication for merchants who use the SOAP Toolkit key. You must 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

See the P12 Authentication Upgrade for SOAP Toolkit Key Users Migration Guide.


Release Archive

Last published: November 18, 2026

Not available for your audience

This page isn't available for your current audience selection.