4.0.0

PCI SSF Compliance

• Version 4.0.0 of the Checkout iOS SDK is compliant with the PCI SSF standard. This has been done to help merchants reduce the scope of their own PCI assessments.

Breaking change - Functionality deprecated in version 3.0.0 has been removed in version 4.0.0

• Support for using UITextField has been removed. AccessCheckoutUITextField must be used instead. This component is dedicated to capturing and encapsulating your customers card details to minimize your exposure to PCI Data. More information in the Worldpay Developer Documentation
• Support for passing directly card details to create an instance of CardDetails has been removed
• Support for using merchantId() in AccessCheckoutClientBuilder to pass your Checkout ID has been removed. It is replaced by checkoutId().

Breaking change - Minimum version requirements

• The minimum iOS version supported by the SDK for the purpose of providing a PCI SSF compliant solution is iOS 15
• Note that although the SDK supports iOS 12 to iOS 14 it is not PCI SSF compliant for these versions. This is due to the fact that Apple has stopped supporting/delivering security fixes for these versions

Licensing

• The Access Checkout iOS SDK licence is now a proprietary licence (was open source before). This is for the purpose of protecting merchants against a risk of breaking changes in case where the Worldpay APIs consumed by the SDK are to change in the future.

3.0.0

Support for enhanced card sessions

• Support for enhanced card sessions has been released. These card sessions will support integration with our Verified Payments API (to be released soon) and remain compatible with the Verified Tokens API.
• The way you integrate the SDK does not change.
• However, the card session URL returned by the SDK is now in the form https://access.worldpay.com/sessions/... , instead of https://access.worldpay.com/verifiedTokens/sessions/... before.

Support for minimizing exposure to card details

• Up to version 2 of our SDK, you had to capture and pass card details in your code to our SDK, which meant you were exposed to card details and made your PCI compliance assessment more difficult.
• We have added a new UI Component (AccessCheckoutUITextField) dedicated to capturing and encapsulating your customers card details to minimize your exposure to PCI Data. At a high level, you now pass references of instances of this UI component to our SDK and in return the SDK will do all the heavy lifting for you, making sure that you do not have to manipulate card details directly. This allows your app to be assessed against the PCI SAQ-A standard.

Functionality added in version 2.. and deprecated in version 3.0.0

• Support for using UITextField is deprecated and will be removed in the next major version.
• Support for passing directly card details to create an instance of CardDetails has been deprecated and will be removed in the next major.
• Support for using merchantId() in AccessCheckoutClientBuilder to pass your Checkout ID is deprecated and replaced by checkoutId(). Support for merchantId() will be removed in the next major version.

Minimum version requirements

• The minimum version supported is iOS 12

2.4.1

• Add support for Access Checkout React Native versions

2.4.0

Add support for Swift Package Manager

2.3.1

• Fix compatibility issues with ReactNative for Pan and ExpiryDate fields validation

The issue has been fixed by raising .editingChanged events when the Pan or ExpiryDate text is automatically reformated by the SDK. This is done so that ReactNative is notified of the changes

2.3.0

• Add support to enable card number spacing (will display spaces between groups of digits in the card number field)

2.2.0

• Add support to restrict card brands in validation feature
• Add a builder to CardValidationConfig and CvcOnlyValidationConfig and made constructors deprecated

2.1.0

• Added support for UITextFields in Validation feature
• The use of the SDK’s PanView, ExpiryDateView and CvcView components is now deprecated (these components will be removed in the major version). UITextFields should be used instead.

2.0.0

• Simplified integration of the session and validation features. This is a breaking change if you are currently using version 1.x.x
• Session feature now supports requesting a Cvc session (this is a requirement for gambling merchants supporting Mastercard payments)
• Session feature now supports requesting a Card session and a Cvc session at the same time
• Additional card types are now supported: Diners, Discover, JCB, Maestro
• Support for custom validation rules has been dropped
• Validation behaviour has been changed so that validation events are only fired when the Pan, Expiry Date or Cvc become invalid or valid

1.2.1

• Default card type images are now fetched from an external location. This allows apps using this feature to always display the most up-to-date version of a given card type image.