On This Page

Release Notes

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

Announcements

These are the announcements for
February 6, 2026
.

Webhooks Updates

Webhooks version 1 will be decommissioned in April 2026. See Webhooks version 2 in the Developer Center.

Features Introduced This Week

Payer Authentication
 | 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 Type
Field Name
Expected Value Format
Example
REST
consumerAuthenticationInformation.paSpecificationVersion
2.X.X
2.2.0
Simple Order API
ccAuthService_paSpecificationVersion
2.X.X
2.2.0
SCMP
pa_specification_version
2.X.X
2.2
 or
2.2.0
 depending on processor requirement
Important Dates
Released to production February 4, 2026.

Fixed Issues

No customer-facing fixes were released this week.

Known Issues

Transaction Search Export
 | 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
 | 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
 | 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 Business Center
 | 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 Business Center.
Technical Details
None.
Workaround
None.