Netcetera iOS 3DS SDK - Release Notes - Version 2.5.2.0
Published: 11.02.2025
Version 2.5.2.0 is a minor release of the Netcetera iOS 3DS SDK.
Compatibility
This version is fully backwards compatible with the previous 2.5.1.1 version of the Netcetera iOS 3DS SDK
New features
- Introduced dynamic fetching of scheme logos and additional static values via the SDK Support Server
Improvements
- Extended UiCustomization API to accept UIFonts
- Improved compatibility mode validation to potentially increase transaction success rates
- Improved Bridging Message Extension handling
- Improved logging
Important Notes:
- After a thorough analysis of a publicly available data as well as our Support Server data (for 3DS SDK users on version 2.4.0.0 and above), we have come to a conclusion that the number of iOS devices running iOS 11, 12, 13, and 14 is nearly negligible (below 0.1%). To optimize our product by leveraging the latest OS technologies, reducing potential errors, and minimizing SDK size by removing legacy code, we plan to increase the minimum supported iOS version to 15. Additionally, we plan to discontinue Objective-C support for the same reasons. If you are currently using the iOS 3DS SDK in an Objective-C project, please let us know. Both changes are planned for an upcoming major release in 2025.
- The device data encryption certificate for AMEX is set to expire on May 24, 2025, while the encryption certificate for UnionPay will expire on July 8, 2025. These certificates will be updated dynamically for integrators using 3DS SDK version 2.4.0.0 and above. We strongly encourage any integrators who have not yet updated to 2.4.x.x or 2.5.x.x to do so before the certificate expiry dates, as transactions for these schemes will fail after the due date.
- Encryption certificate key IDs (required for EMVCo protocol version 2.3.1) are updated regularly on our Support Server. If you plan to perform 2.3.1 transactions, please update to SDK version 2.5.x.x, as dynamic fetching of key IDs was introduced in 2.5.0.0. Transactions using protocol version 2.3.1 may fail if the key ID is not properly configured.