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 ofhttps://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 (
AccessCheckoutEditText
) 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
EditText
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()
inAccessCheckoutClientBuilder
to pass your Checkout ID is deprecated and replaced bycheckoutId()
. Support formerchantId()
will be removed in the next major version.
Minimum version requirements
- The minimum version supported is
API Level 26