3.1.0

• Improved the UI for users to learn more about how VRP mandates work.
• There is a new ResultShown callback you can use to see the payment or mandate result that the user received.
• Fixed an issue where you would be forced to update all fields if one was incorrect. For example, users would have to update both username and password if validation found that one was incorrect.

3.0.1

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.

2.6.0

Release Notes:

• Saved Accounts: Users can now use their previously saved accounts for faster payments
• Payment Result Screen: The SDK now offers a screen for displaying the final status of a payment to the user after they have been redirected from their bank.
• New prettier icons for all banks
• Android 14 support

2.5.1

Release Notes:

• Bug fixes

2.5.0

Release Notes:

• When selecting a provider users can now search for banks and branches at the same time
• The SDK now has a refreshed UI
• If a preselected provider is currently unavailable it is now displayed
• Regulated customers will now display a non-branded connect-to-bank icon
• Improved instructions on the confirmation screen

2.4.0

Release Notes:

• A new screen in the payment flow for selected banks in France and Finland, which displays for international payments. This screen primes new users on how to enable international payments from their bank.
• If a provider is currently unavailable, this now displays on the provider selection screen before a user selects them.
• PISP license holders who process payments under their own certificate can now choose to remove TrueLayer branding from the user interface. Contact us to request this feature.

2.3.0

Release Notes:

• Updated user information for Signup+ payments
• Shows cross-app recently used providers, rather than simply those used with the current app
• Extended support from Android 7.0+ (API level 24+) to Android 5.0+ (API level 21+)
  Version 2.3.0 introduces the need to enable desugaring in your app. See our migration guide for guidance on how to do this, and for details of the latest dependency updates.