Skip to main content

Android Secure Components v3.7.0

· 2 min read

Minor release introducing structured error codes, improved error messaging, and a fix for amounts displaying incorrectly in 3DS3DS 3-D Secure - an additional security layer for online credit and debit card transactions. It adds an authentication step where the cardholder verifies their identity with the card issuer during the purchase, reducing fraud and providing liability protection for merchants. 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). and OWTOWT Outgoing Wire Transfer - a transaction that moves funds from a Weavr managed account to a bank account held at a third-party financial institution. OWTs require the managed account to have an assigned IBAN and the user to complete Strong Customer Authentication. screens.

Added​

  • Introduced WeavrErrorCode enum providing typed SDK-level error codes (e.g. cantSetUIKey, cantRecreateKeyPairs, biometricsInvalidChallengeMetadata) to distinguish SDK failures from HTTP errors.
  • Added CurrencyFormattable utility for correct minor-to-major unit conversion and locale-aware currency formatting across all supported currencies (EUR, GBP, USD, and any ISO 4217 code).

Fixed​

  • Fixed 3DS3DS 3-D Secure - an additional security layer for online credit and debit card transactions. It adds an authentication step where the cardholder verifies their identity with the card issuer during the purchase, reducing fraud and providing liability protection for merchants. 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). and OWTOWT Outgoing Wire Transfer - a transaction that moves funds from a Weavr managed account to a bank account held at a third-party financial institution. OWTs require the managed account to have an assigned IBAN and the user to complete Strong Customer Authentication. screens displaying raw minor-unit amounts (e.g. €100 instead of €1.00).
  • All ErrorResponse instances throughout the SDK now include a structured code value instead of defaulting to null.
  • Improved error messages for missing UI key, network failures, biometric precondition failures, and server errors to be more descriptive and consistent.

Changed​

  • ErrorResponse.code is now Int (non-null, defaults to -1 / WeavrErrorCode.unknown).
  • ErrorResponse.message is now String (non-null, defaults to "").
  • ErrorResponse.body is deprecated and will always be null. It previously leaked the raw HTTP response body to the embedderEmbedder A company or developer that integrates Weavr's embedded finance services into their own application to provide financial services to their end customers. unintentionally.

ACTION REQUIRED​

The WeavrErrorCode enum now provides typed SDK-level error codes (e.g. cantSetUIKey, cantRecreateKeyPairs, biometricsInvalidChallengeMetadata) to distinguish SDK failures from HTTP errors. The body field in error responses is now deprecated and will always return null. To continue receiving detailed error information, use the new WeavrErrorCode enum instead.

See the full list of error codes in the Android SDK error codes documentation.