Android SDK release history

• The bottom sheet no longer allows you to interact with elements underneath it.
• Some edge cases are now fixed.
• We've improved the user journey for some GBP payments.

• The SDK now supports new intersection theme design across all screens in the new UI. The new theme is available for all payments using the new UI (GBP and EUR+Ireland single payments).
• Improved the way that SDK themes are applied to the new UI screens.
• The SDK now correctly applies transparent background behind the bottom sheet.

• Fixed a potential issue with loading screens when updating from version 3.8.x or earlier.

• Updated minimum requirements for end users.
• The SDK now supports payment retries and an improved returning user journey.

• The SDK now supports an AIS + PIS flow. To make the user experience simpler, you can give your user the option of creating an additional Data connection when they consent to a payment. For applicable German banks, your user sees screens allowing them to input their IBAN automatically.

• The SDK is no longer sending a redirect reason alongside a success result. This enables you to retry the redirect to the bank app: for example when the bank app doesn't display the correct result screen. The user can now go back to the merchant app and click the go to bank button again. This reduces the number of payments that are abandoned after authorisation.
• The SDK now refreshes the payment state whenever the user switches back to your app after authorising a payment. This is useful if the redirect back from the bank fails. When the user goes back to your app, the SDK fetches the latest payment status and takes the relevant action.

• If the names of the beneficiary account holder and Console app are the same, the SDK will now display only one name on the payment review screen.

• If there is an issue meaning that the Android SDK isn’t available, it falls back to the HPP in a web view to ensure a payment is always possible.

• 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 users 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.

• Updated the payment result screen for the Android SDK and added a mandate result screen in the Android SDK too. The result screens are enabled by default as of this version.
• The Android SDK no longer supports the Material Theme adaptor.
• The UI now displays Signup+ specific wording when signupplus is specified as a related_product at payment creation.
• Made optimisations to the decoupled authorisation flow for payments in Spain.
• Added localisation for the Italian language.
• Added a default logo in case the merchant doesn't upload a logo in Console.

• Users can now use previously saved accounts for a faster payment flow.
• The SDK now includes a payment result screen that you can use to display the final payment status to the user after they're redirected from their bank.
• Improved and redesigned bank icons.
• Support for Android 14.

• Fix for an issue that occurred when users selected a branch for a small number of banks in France and Germany.

• The SDK now has a refreshed user interface.
• When selecting a provider, users can now search for banks and branches at the same time.
• For providers that support it in Europe, the user can select between the SEPA Credit or SEPA Instant payment schemes. To enable this, ensure that you set scheme_selection to user_selected at payment creation.
• If a preselected provider is currently unavailable, the SDK now displays this.
• A non-branded connect-to-bank icon now displays for regulated customers.
• Improved instructions on the payment confirmation screen.

• 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.

• 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.

• Support for customisation when used with the React Native SDK.
• Improved error handling.
• Enhanced bank and branch search in Germany.
• Improvements to the payment flow, such as IBAN validation and displaying bank details for VRP mandates.

• Adds support for the upcoming React Native SDK.

• Support added for Android 7.0 (API level 24)
• Saves previously used branches
• Usability improvements

• You can now use the SDK to set up recurring payment mandates, in addition to individual payments.
• User experience improvements for the IBAN entry form.
• Bug fixes.
  Version 2.0.0 introduces some small breaking changes. See our migration guide for instructions on how to update.

• Bug fix for text input validation

• SDK is now available via Maven Central
• Support for Cancel Payment, so you can understand when a user cancels the payment
• Wait action support for decoupled authentication flows
• Improved error reporting
• Updated to Compose Material 3

• Support for custom legal text
• Foundational support for embedded authorisation flows (not yet fully supported)

Updated dependencies:

• appcompat 1.4.1 -> 1.4.2
• androidx-core 1.7.0 -> 1.8.0
• material 1.6.0 -> 1.6.1
• coil 1.4.0 -> 2.1.0
  User experience improvements for text input forms

• Improved error handling
• Improved accessibility for additional input forms
• Improved language selection
• Improved analytics and error reporting

• Support for France, Spain, the Netherlands, Portugal and Lithuania.
• IBAN entry form, for providers who require it.
• Branch selection form, for providers who require it.
• UI translations in French, Spanish, Dutch, Portuguese and Lithuanian.
• Support for pre-selected provider IDs
• Pass a set language to override locale.
• UI bug fixes.

• Updated license text

• Support for Ireland
• Allows the user to select their country
• Remembers previously selected country to display first
• Option to set the starting country using an initialisation parameter
• Updated legal text for EU countries
• Improved theme customisation
• Accessibility improvements