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.

February 2026


Production releases for the weeks ending February 6 to February 27, 2026: features, fixed issues, and known issues.

February 27, 2026

These release notes cover releases for the week ending February 27, 2026.

Transaction Details

Ticket: RM-37859

Description: This release updates the 's Transaction Details page. In Request Information tab, the Status field will no longer be visible. In Processor Information tab, the Status field is renamed Processor Status.

Mandate: Does not apply.

Audience: Global.

Benefit: Users will now see a standarized view of the transaction status.

Technical Details: None.

Important Dates: Released production February 26, 2026.

No customer-facing fixes were released this week.

Flex Microform

Ticket: EPS-36000

Description: Some of the custom styling elements of Flex Microform do not take affect when applied.

Audience: Users of Flex Microform.

Technical Details: None.

Workaround: None.


.Net SDK

Ticket: EPS-36468

Description: There is a minor bug in version 1.51 of the .NET SDK that affects the responses from GET requests made to the tms/v1/paymentinstruments/{paymentInstrumentId} endpoint. The values of expirationPrinted and securityCodePrinted use the string data type instead of boolean.

Audience: Users of the .Net SDK.

Technical Details: None.

Workaround: None.

February 20, 2026

These release notes cover releases for the week ending February 20, 2026.

Partner Risk Controls

Ticket: RM-42234

Description: This release enhances the custom rules capability in Partner Risk Controls (PaRC) to include the below mentioned fields. This improvement will help us to better perform risk and fraud management using PaRC.

  • ICS_Credit Service (Credit Type): contains Standalone_refund and Followon_credit.
  • Country Checks: Acquirer, Merchant and Issuer country codes.
  • AFT: 24 Fields related to Account funding transactions, to set rules that restrict AFT transactions using PaRC

Mandate: Does not apply.

Audience: Users of PaRC.

Benefit: Customers and acquirers can now be better prepared against merchant and transaction frauds performed using standalone credit and AFTs.

Technical Details: None.

Important Dates: Released to production February 17, 2026.

Partner Risk Controls

Ticket: RM-37119

Description: This release fixes minor, intermittent errors in velocity aggregation that were the result of a discrepancy in foreign exchange currency conversion.

Audience: Users of Partner Risk Controls.

Technical Details: None.

Important Dates: Released to production February 17, 2026.

Ticket: EPS-36072

Description: For Pay By Link, if a payment link is set to Inactive status, customers who already paid using that payment link can no longer view their receipts. The receipt URL returns red banner error with HTTP 500.

Audience: Customers paying merchants that use Pay by Link.

Technical Details:

Workaround: Merchant can set the payment link back to Active status to allow the receipt page to load successfully, however that also activates the payment link again.


VAP Portfolio Management

Ticket: EPS-36190

Description: In Visa Platform Connect, card processing setting, portfolio users are not able to manage the aggregator ID information because the placeholders are disabled.

Audience: Portfolio users who manage merchants processing transactions from third-party vendors.

Technical Details: None.

Workaround: Merchants can use the following API field to send the aggregator ID in the transaction requests.

REST API Field: aggregatorInformation.aggregatorId

Simple Order API Fields:

ccAuthService_aggregatorID

ccCaptureService_aggregatorID

ccCreditService_aggregatorID

octService_aggregatorID

February 13, 2026

These release notes cover releases for the week ending February 13, 2026.

No customer-facing features were released this week.

No customer-facing fixes were released this week.

Tax Calculation

Ticket: EPS-35675

Description: Tax calcuations for invoices in the are not rounding up for values that end with 5.

Audience: Users of Invoicing.

Technical Details: None.

Workaround: None.


Decision Manager

Ticket: EPS-35998

Description: The Decision Manager Performance Statistics reports are loading slowly for some long time ranges.

Audience: Users of Decision Manager.

Technical Details: None.

Workaround: Try using shorter time ranges until the problem is solved.


Authorization Transactions

Ticket: EPS-36017

Description: Some failed authorization transactions that were processed through FDC Nashville are listed in the as reversible, which is not true of failed transactions. When the user attempts to reverse one, they receive the error message auth code is missing or invalid.

Audience: Merchants who process transactions through FDC Nashville.

Technical Details: None.

Workaround: None.


Reporting

Ticket: EPS-34739

Description: In the Transaction Search Results report, some token transactions do not display the Customer ID.

Audience: Users of Reporting.

Technical Details: None.

Workaround: Search for the transaction in the and click Transaction Details. The Customer ID is shown on the Transaction Details page.

February 6, 2026

These release notes cover releases for the week ending February 6, 2026.

Payer Authentication

Ticket: RM-41999

Description: This release introduces support for sending 3-D Secure major and minor version values in Payer Authentication requests through Omnipay Direct during authorization and settlement processing of Visa and Mastercard payments. An example of a major and minor version is 2.2, where the first 2 is major and the second 2 is minor.

If you already include this information, you are not required to change anything. This enhancement ensures that when you submit Payer Authentication results in a payment authorization, Omnipay Direct now passes the full 3-D Secure specification version, when supported.

Mandate: This release complies with these mandates:

  • Mastercard Data Integrity Monitoring Program, requiring monitoring and validation of 3-D Secure major and minor version values during authentication.
  • EMVCo 3-D Secure Specifications, which require payment systems to correctly interpret and transmit 3-D Secure version details.

Audience: This release updates these Omnipay Direct gateways:

  • Omnipay Direct (Europe region)
  • OPDFDE (First Data Europe)
  • OPDCARDNET (Lloyds Cardnet)
  • OPDBAMS (Bank of America Merchant Services)

This release applies to merchant integrations using 3-D Secure, versions 2.x, including:

  • Combined Payer Authentication plus authorization flows
  • Separate Payer Authentication and authorization flows

Benefit:

  • Compliance assurance: Ensures transactions continue to pass Mastercard and Visa validation programs as they increase 3-D Secure monitoring.
  • Reduced decline and failure rates: Correct version transmission prevents invalid/missing 3DS version errors.
  • Future readiness: Supports scheme migrations (for example, 3-D Secure 2.1 deprecation) and evolving EMVCo standards.
  • No integration overhead for merchants already submitting full Payer Authentication specification version values.

Technical Details: If you use sparate Payer Authentication and authorization flows, you must ensure that the Payer Authentication specification version from the Payer Authentication response is copied into the payment authorization request.

API Fields and Supported Values

Integration TypeField NameExpected Value FormatExample
RESTconsumerAuthenticationInformation.paSpecificationVersion2.X.X2.2.0
Simple Order APIccAuthService_paSpecificationVersion2.X.X2.2.0

Important Dates: Released to production February 4, 2026.

No customer-facing fixes were released this week.

Transaction Search Export

Ticket: EPS-34739

Description: When a user exports transaction search results in CSV format, and the results include transactions that were captured or credited more than 60 days after the initial authorization, the Customer ID field is blank.

Audience: All users.

Technical Details: None.

Workaround: None.


Address Verification Service

Ticket: EPS-35856

Description: For merchants who process transactions through Moneris and use relaxed requirements for the Address Verification Service, if the customer's last name is not submitted, the transaction will fail.

Audience: Merchants who process transactions through Moneris and use relaxed requirements for the Address Verification Service.

Technical Details: None.

Workaround: None.


Merchant Management

Ticket: EPS-36008

Description: In Merchant Management, if you try to add Unified Checkout to a merchant account, and the mechant account ID is exactly 30 characters, Unified Checkout cannot be enabled.

Audience: Users who create merchant management profiles.

Technical Details: None.

Workaround: None.


Token Management in the

Ticket: EPS-36060

Description: In the Token Management screen, when you filter by token and open the token details, the transaction history section at the bottom displays correctly, but the Application section does not show the details properly.

Audience: Users of Token Management in the .

Technical Details: None.

Workaround: None.

Last published: November 18, 2026

Not available for your audience

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