Android Trust SDK Native Interface

Using the Android Trust SDK

This section is written for developers who want to use the Trust SDK to add local (on-device) authentication and identity verification capabilities to an Android application.

Initializing the Trust SDK:

DaonTrustSDK daonTrustSDK = new DaonTrustSDK(this, new DaonEventListener() {

            @Override 

            public void onFail(DaonEvent event) {

                ...

            }

​

            @Override 

            public void onInfo(DaonEvent event) {

                ...

            }

​

            @Override 

            public void onSuccess(String description) {

                // On successful completion, get the Process Instance status. See Step 7.

            }

        }

    );

    getLifecycle().addObserver(daonTrustSDK);

2. Daon Trust SDK offers setting a DaonOptions object for customization purposes. You can set your own initialization timeout as well as the URL of the environment that you want to use:

DaonOptions options = new DaonOptions();

    options.setServerURL("https://www.example.com");

    options.setInitializationTimeout(15000L); //initialization timeout is expressed in milliseconds

3. Finally, you can start the Onboarding process by calling 'start()' function of the TrustSDK:

daonSDK.start(options);

Obtaining and Parsing Events from the Trust SDK

As stated above, the Trust SDK returns events through the two callback methods ('onInfo()' and 'onFail()') that need to be overridden to initialize the SDK. Events that are returned are represented through the DaonEvent object instances that are carrying feedback information about the Onboarding process status and errors.

• DaonEvent fields:
  • DaonEventCode code - field that contains event code
  • String description - field that contains a description of the event

A list of events, their codes and descriptions that are supported and provided by the Daon Trust SDK can be found below:

• DaonEventCode structure breakdown:
  • First pair of digits represents event status. Event status can be: Success (10), Fail (20), Info (30).
  • Second pair of digits represents section of the event. Event sections can be: QR (01), MRZ (02), NFC (03), Web (04), Other (05).
  • Third pair of digits represents ordinal code number for that section.

Native Interface

This sections describes all classes that represent the public API interface between mobile developer integrators and the Daon Trust SDK.

DaonTrustSDK

DaonOptions

DaonEventListener

DaonEvent