Skip to content

3.0.1
Compare
Choose a tag to compare
@tl-keenen-charles tl-keenen-charles released this 23 Feb 12:17
· 5 commits to main since this release
3.0.1
cf6167c
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Release Notes:

  • The material theme adapter library has been removed. For clients using customisation via XML theming you can follow the migration guide in the docs.
  • The paymentUseCase has parameter has been removed. To use Signup+ you'll now need to specify it on payment creation with the related products field.
  • VRP mandates are now supported on the result screen
  • Improved accessibility
  • Bank branch search now supports a mix of names and search aliases
  • You can search for countries by 2- and 3-character international country codes
  • A new default theme
  • Italian translations are now available
  • Fixed bug to allow a missing account_holder_name field for mandates

Migration Guide

1. UI customisations

To use version 3.x.x of the SDK, you must integrate with Compose to customise your app UI. You can no longer use XML files to do this.

You can integrate without migrating your app to Compose. Here's how:

Enable Compose in your project by adding the code snippet below to the android block in your app-level build.gradle file.

buildFeatures {
    compose = true
}

composeOptions {
    kotlinCompilerExtensionVersion = "1.5.4"
}

Add the following dependencies to your build.gradle file:

implementation("androidx.activity:activity-compose:$latest-version")
implementation("androidx.compose.material3:material3")

Follow the steps for the Compose integration.
For a full list of customisation options, read the Compose customisation guide.

2. Result screen

The direct access to Result Screen has been removed. The result screen is now launched when you re-invoke SDK as described in handling redirects.

The result screen is now enabled by default. If you'd like to opt out and continue with the behaviour of 2.X.X versions of the SDK you can use the setting shouldPresentResultScreen = false on the PaymentContext or MandateContext

PaymentPreferences(
    // if you want SDK to not present the result screen
    shouldPresentResultScreen = false
)

3. Mandatory re-invoking SDK on redirect

IMPORTANT

In order to support some new payment flows, you have to re-invoke the SDK as a part of handling redirect from bank. Without this step payments from some banks will not be able to complete. Use the same PaymentContext/MandateContext as the one you've used to start the payment.

More information on how to do it, as well as some diagrams, in chapter Handle redirects from bank.

4. Kotlin and Android SDK version

The SDK now uses Kotlin version 1.9.22 and a minimum SDK version 24

5. Payment Use Case deprecated

The paymentUseCase property has been deprecated and now SignUp+ payments must be configured when creating the payment with the payments API with the related_products.signup_plus property.

Assets 2
Loading