Netcetera 3DS Server - Release Notes - Version 2.5.1.0

Overview

Published: 07.02.2022

Version 2.5.1.0 is a minor release of the Netcetera 3DS Server.

Compatibility

This version is backwards compatible with previous 2.5.x.x versions of the Netcetera 3DS Server.

Important notification

Reminder: Configuration of 3DS Requestor ID and 3DS Requestor Name is moved from the Directory Server to the Merchant Acquirer level. According to the EMVCo specification, Requestor ID and Name are unique identifiers, provided by the Schemes to each 3DS Requestor on an individual basis. Therefore, these two values should be either configured for each Merchant Acquirer, or should be passed in the transaction payload as part of the Merchant data. For more recommendations please check 3DS Requestor ID and Name Guidelines.

The Netcetera 3DS Server 2.5.1.0 frontends will not support Microsoft's Internet Explorer 11 (IE11) or older anymore. Please use a different browser to access the Netcetera 3DS Server frontends.

Changes

New Features

  • Added possibility to provide the Results Response notification URL via the 3DS Server API Authentication request. See more information under resultsResponseNotificationUrl field in ThreeDSServerAuthenticationRequest#MerchantData This offers a simplified alternative to the multi organization functionality. With this feature, customers don't need to establish separate organizations to use multiple endpoints.

The URLs are sent in the 3DS Server Authentication request payload from the Requestor, so that the Result Response can be sent to multiple endpoints. This means no routing is needed on Requestor side. In the Admin UI one organization will be existent and visible.

Every URL must be whitelisted from our side, otherwise it can not be used.

Please be aware that this functionality is available on demand.

Improvements

  • Admin UI / Search Transactions: Ordering of messages inside the transaction flow is now done based on the timestamp and messageType.
  • The field threeDSServerTransID is now part of the ResultsResponse payload even in case of an error.
  • Added logging even in case of an invalid protocol message.
  • Netcetera 3DS Server is now using a new Reference Number issued by EMVCo (3DS_LOA_SER_NEAG_020200_00524), supporting 2.1.0 and 2.2.0 transactions. The updating of reference number was not based on functional changes, but rather was a requirement due to the approaching expiration date.

Bug Fixes

Added a missing validation rule for null check of messageCategory field in 2.2 AReq.