Netcetera iOS 3DS SDK - Release Notes - Version 2.4.0.0

Published: 06.11.2023

Version 2.4.0.0 is a major release of the Netcetera iOS 3DS SDK.

Important Note: Each customer will receive a unique API Key via e-mail with the release of the Netcetera iOS 3DS SDK version 2.4.0.0, which will replace the current license file.

Compatibility

This version is not backwards compatible with previous versions of the Netcetera iOS 3DS SDK (see Breaking Changes).

New features

• EMVCo 3-D Secure Protocol and Core Functions Specification version 2.3.1 compliant
• Remote update of Integrator License and Pre-configured DS Certificates, which eliminates the need for releases due to their expiry
• Included configuration option to toggle support for EMVCo 3-D Secure Bridging Message Extension
• Pre-configured EFTPOS DS configuration into the Netcetera 3DS SDK

Breaking changes

• The Netcetera iOS 3DS SDK configuration now requires an API Key instead of a License Key

Improvements

• New LOA Reference Number
• Improved Challenge Response processing from legacy ACS providers which should improve conversion rates
• Updated device info version to SDK—Device Information Data Version 1.5
• Updated the SDK API with a new Initialization method that provides success and failure callbacks to the integrator
• Support for XCode 15 and iOS 17

IMPORTANT: We advise all of the SDK integrators to replace the old initialize method with the new one. The old initialize method will still be available for all integrators. The initialization of the SDK can have a longer than usual duration based on the established connection (latency) with the remote configuration server and should be handled in a way that will ensure proper UX (avoid UI unresponsiveness).

Bug fixes

• Fixed a bug where the SDK sends Challenge Request multiple times during OOB challenge redirect.

Known issues

• We are aware of the fact that there is a false positive warning when calling the doChallenge method in XCode 14 and above, informing integrators that the method may lead to UI unresponsiveness and should not be called on the main thread. We confirm that the warning is a false positive. The SDK handles the long lasting operations gracefully (without UI unresponsiveness). The integrators should continue to call the method on main thread, while we are working on a solution that will not show the false positive.