Android Components v3.1.0

The method for exchanging tokens in the biometrics login flow has been updated to make implementation simpler.

Key changes

On biometric login, a token is returned to the SDK; this token is used for two purposes:

1. For your backend to swap for an access token, which can then be used by your backend for all multiMulti Weavr Multi is an embedded finance solution that allows you to integrate financial services into your own application, providing a seamless experience for your customers. It enables you to offer managed accounts, managed cards, and transactions without requiring financial expertise. API endpoints
2. To be set automatically in the SDK, so that UI components (for example card components) can de-tokenise values retrieved by your backend and display the information in plain text to the user. It is no longer required to call "Set user token" (setUserToken) for UI components.

See biometrics overview for a swimlane of a sample implementation, and the Android documentation for specific instructions.

Additional changes

Fixes and clarifications for checking a device's status in relation to biometrics authentication.

Added

UXComponents.psa.isPSAEnrolled() method returns a boolean indicating whether the user is currently enrolled or not Synchronous enrolment check - No longer requires callback/listener for simple enrolment status checks

Deprecated

UXComponents.psa.isPSAEnrolled(context: Context, psaStatusListener: WeavrPSAStatusListener) is now deprecated Note that the enrolment check is local. Therefore if the user enrols on another device, the enrolment of this device can no longer be used.