Oraculi Mobile SDK (Beta)

This SDK, and the approach described here, are in beta and subject to change as we take feedback from pilot lenders. If you’d like to use this service, contact [email protected].

Oraculi is Lendsqr’s underwriting scoring engine (the name means “the oracle” in Latin). It provides a RESTful API for accessing user data gathered, with consent, from your customers’ phones through an SDK you embed in your app. The Oraculi Mobile SDK gives you insight into Android customers specifically.

The SDK is only available for Android.

Installing the SDK

The Oraculi SDK is a Java native library that can be embedded into any mobile framework capable of instantiating Java within a mobile app; this documentation assumes a React Native application.

The SDK is distributed via a private GitHub repository. To get access, contact [email protected]; installation instructions are in the repo’s README.

Android permissions

The SDK requires the READ_SMS and RECEIVE_SMS permissions, explicitly declared in your Android manifest. Google classifies both as dangerous permissions, so beyond declaring them, you’ll need to follow Google’s guidelines to get your app approved with these permissions in place.

Definitions

• Entities: when the SDK collects data from an Android phone, it creates unique identifiers for the user and the device. Since you provide a user identifier when you instantiate the SDK, that user can be identified consistently across different devices. Underneath that, the entity is rooted in a unique identifier (UUID) for the device and the session that created the data.
• Institutions: the companies, banks, or other stakeholders that have sent SMS or other information to an entity (a user).
• Transactions: records of a user or entity’s activity with an institution, such as an SMS alert for a financial transaction, a telco balance alert, or a bank credit/debit statement measuring funds moving in or out of an account.

The SDK data journey

When a user installs your app with the Oraculi SDK embedded, they’re prompted to grant the permissions the SDK needs. Google requires detailed on-screen explanations for these prompts; contact [email protected] if you need guidance on wording these.

Once permissions are granted, the SDK collects data from the phone, encrypts it, and sends it to Lendsqr’s backend for parsing and analysis. You then connect to the Lendsqr API endpoints to retrieve the parsed, analyzed data for your loan underwriting workflow.

Every transaction is uniquely identified against the user, so if they uninstall and reinstall your app, their data isn’t duplicated.

Questions about integrating the SDK? Email [email protected].