Netcetera 3DS Server 2 - Release Notes - Version 2.4.0.0

Published: 19.08.2021

Version 2.4.0.0 is a major release of the Netcetera 3DS Server 2.

For documentation about this release please refer to the documentation site.

Compatibility

This version is backwards compatible with previous versions of the Netcetera 3DS Server using the Database configuration.

This version is NOT backwards compatible with previous versions of the Netcetera 3DS Server using the XML configuration.

Important notification

Property ds-client.preparation.request.initial-delay.hours is deprecated and it will be removed in the next release. Find more information about the property in the 3DS Server configuration properties. In a clustered environment, we recommend enabling the PReq initiation on one node only or disabling it on all nodes and use the endpoint for manual execution of preparation request.

Schemes have simplified the certificate handling on acquirer level for 3DS 1 and 3DS 2 protocol transactions. As a result, a scheme certificate per acquirer is not needed any longer, but one certificate is used for all acquirers. We advise customers to try processing with one existing certificate in order to elaborate whether a new certificate is needed to use this option .

We have adapted this improvement, so that configuration of Directory Servers is now possible only on the Scheme level, the option to define Directory Servers on Acquirer/Merchant level is removed. In case of XML configuration, adjustments should be made accordingly.

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 (DB, XML), 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.

Changes

New Features

  • Option to export transactions search results in a CSV format file. The data in a CSV exported file is the same as in an Excel exported file.

Improvements

  • Configuration of Directory Servers is now possible only on the Scheme level, the option to define Directory Servers on Acquirer/Merchant level is removed. In case of XML configuration, adjustments should be made accordingly.
  • Configuration of 3DS Requestor ID and 3DS Requestor Name is moved from the Directory Server to the Merchant Acquirer level. In case of XML configuration, manual migration of these fields to the Merchant Acquirer object is required. Please also check the "Important notification" section above.
  • Added AReq and ARes validation rules for checking that the broadInfo value is a valid JSON object.
  • Improved the processing of the 3DS 2 card ranges contained in the preparation responses. Find more information in 3DS Server Card Ranges Processing.
  • Introduced a new endpoint for manual execution of preparation request. Find more information in 3DS Server Card Ranges Processing.
  • Property threedsserver.session.storage.db.card-range-data.cache-update-delay.minutes is removed because reloading of the cache does not require to wait for PRes to be stored.
  • Property fixed.delay.duration.card.ranges is replaced by threedsserver.session.storage.cache.card-range-data.cache-update-check.seconds. Find more information in 3DS Server Card Ranges Caching.
  • Property ds-client.preparation.request.initial-delay.hours will be deprecated in the next release. In a clustered environment, we recommend enabling the PReq initiation on one node only or disabling it on all nodes and use the endpoint for manual execution of preparation request.
  • Introduced property management.health.mail.enabled which indicates whether the actuator health endpoint should include or exclude mail related details.
  • Added Travel Industry Message Extension Data validation rules for checking the version value.
  • The endpoint for providing 3DS Server card ranges is now accessible for any type of configuration, database or XML and is extended with optional schemeId request parameter. Find more information in 3DS Server Web Service API.
  • Removed gender prefix from user accounts in Admin UI.

Bug Fixes

  • Fixed deleting of Acquirer Bins in the Admin UI.
  • Extended validation of the purchaseCurrency field to meet ISO 4217 standard.
  • Adjusted validation of non-required fields in Merchant Acquirer Configuration in Admin UI.
  • Validate field Preparation Request Message Version as mandatory only when preparation request is enabled.
  • Removed columns Purchase Exponent and Purchase Amount (calculated) from Transactions Search in Admin UI and both Excel and CSV exported files.
  • The Time Period filter to be applied when searching the transactions only when it has a value.
  • Fixed NullPointerException when saving logged transactions under high load.