Process Overview

A typical vanilla verification session follows this basic flow:

• Your application decides that it is time for the consumer to verify their identity, and initialises the greenID Mobile SDK.
• The SDK greets the consumer and gives them an overview of the verification process they will be going through.
• Depending on your greenID configuration, the consumer may be prompted to choose the type of document they will use to help verify their identity.
• The consumer is guided through the process of capturing an image of the front, and possibly the back, of their identity document.
• The image is checked for quality and sent to greenID for authentication and automatic data extraction.
• The consumer is guided through the process of taking a selfie for comparison to their identity document.
• The selfie is sent to greenID for comparison against the image on the identity document.
• The consumer is presented with the information that was extracted from their identity document (if any), and asked to check it, and correct it if necessary.
• The SDK sends the data to GreenID, which registers a new verification attempt, runs any background checks that are configured, and returns the status to the SDK.
• If the configured verification rule has not been satisfied, then an interactive session is launched, and the consumer can select from various options to complete the verification process.
• Once the verification process is complete, the SDK does a "handoff" to your application with the ID of the verification attempt, and the overall status.  Your application can then make a decision about the next step in the workflow.  Your application can make a secure query to greenID to get the full outcome of the verification process; this is highly recommended.

There are only two contact points your application has with the SDK: initialisation and handoff.  The SDK handles the rest of the on-boarding and identity verification process.

The diagram illustrates the process.

Modes

The process described above applies to the "on-boarding" mode of greenID Mobile.  In on-boarding mode, a new verification attempt is registered with greenID every time a person begins the process. However, verification attempts may be registered with greenID via another channel, such as a web service call, and the person can pick up the process on a mobile device for the purpose of photographing an ID document.  This is referred to as "returning user" mode.

Returning user mode

Starting a verification session in returning user mode requires slightly different configuration parameters.  These are documented in the section Configuration Variables.

Using "returning user" mode requires the use of a verification token.  It is recommended that your native mobile application makes a call to your back end, which in turn makes a call to greenID to fetch a verification token.  This is the most secure option.  For details on how to fetch a verification token, please refer to the getVerificationToken web service.