Skip to main content

Android Secure Components v3.6.0

· One min read

Patch release focused on SCASCA Strong Customer Authentication - a two-factor authentication solution required by PSD2 regulations for when end-users are accessing their payment account sensitive information or initiating transactions. SCA requires at least two of the following: something you know (password), something you have (device), or something you are (biometrics)./biometrics reliability and UI/branding stability improvements.

Fixed​

  • Improved reliability of SCASCA Strong Customer Authentication - a two-factor authentication solution required by PSD2 regulations for when end-users are accessing their payment account sensitive information or initiating transactions. SCA requires at least two of the following: something you know (password), something you have (device), or something you are (biometrics). decline and fallback flows.
  • Improved PSAPSA Push Step-up Authentication - the mechanism in our mobile SDKs that delivers a step-up challenge to an enrolled device as a push notification and verifies it with the user's device biometrics. PSA covers device enrollment, biometric login, and biometric verification of SCA challenges for sensitive operations such as outgoing wire transfers or accessing card details. Exposed as `UXComponents.psa` on iOS and Android and via `initializePSA` on React Native. networking stability
  • Improved error messaging when the SDK is not initialized.
  • Fixed UI issues in authorization/consent bottom sheets (layout gaps, button visibility).
  • Improved branding robustness with a safe fallback when invalid colors are returned by the API.