Skip to main content

Overview

The Weavr mobile SDK for iOS, Android, and React Native platforms allows you to embed financial services into your own app, providing a seamless experience for your customers. The mobile SDK handles integration with Weavr UI components, and allows your users to verifying themselves via Biometric Authentication when accessing their embedded financial services.

Weavr components​

  • Login Components. Authentication via Weavr UI components such as Password / Passcode.
  • Card components. Access sensitive card information that can be used to make payments.
  • KYC components. Onboard and verifying Consumers via your app.
  • Biometric Authentication. Multi factor authentication via the SDK using the biometrics capabilities of the user's' phone.

Login components​

When onboarding and setting credentials for a user, you must collect their passcode/password. For security reasons, the passcode/password that is submitted is tokenised and your app has no access to the plain text version. This can be achieved by adding either,

  • Password component or,
  • Passcode component

Card components​

  • Card number Component: Securely displays your customer's card details.
  • CVV Components: Securely displays the 3-digit number that is needed to make online purchases using cards.
  • Show card PIN component: Securely displays the 4-digit PIN number needed to make an in-person purchase using a physical card.

KYC component​

Know Your Customer due diligence is one of the steps required to onboard consumers onto your app. Weavr provides a KYC component that you can embed in your app. This lets you provide a seamless experience to your user while capturing the required documentation to verify their identity.

Biometrics authentication​

Weavr mobile SDK provides biometric features that can be embedded into your mobile app for secured authentication through the user's phone.

Support​

It's recommend users to stay up-to-date with Mobile SDK releases to keep up with the latest features, security updates, and underlying dependencies. Continued use of an unsupported SDK version is not recommended and is done at the embedder’s discretion.

For more information, about maintenance and support for SDK latest and major versions and underlying dependencies, please contact support.