GBG Developers

Guides   |   Data-led Journeys or Workflows

Data-led Journeys or Workflows

Journeys or customer workflows describe the process through which a user becomes verified. For example, a particular workflow may involve the customer accessing a web page and entering their address to book a driving lesson. Next, the customer may be able to upload their current driving license details in order to save time, if they have a mobile phone which supports the capability. 

Each stage of this workflow will result in a verification score that is combined into a final result. Workflows where users (customers or staff) type data first can be described as data-first journeys or customer workflows, as opposed to document-first workflows. These names are just for convenience; the GBG solution is compatible with any sequence of verification service usage.

The example sequence below demonstrates a data-first workflow that begins by rapidly capturing address details for the customer first, followed by document capture and verification that the person using the application matches the person on the document photo identification. Click here for more example customer workflows.

Address Capture

The Address Capture feature works in real-time as the user begins to type in their address. As characters are typed, the service rapidly matches the text to possible address completions, and lists them so that the user can tap to complete. This saves time for the user, and also provides them with some reassurance that they didn't mistype.


Verify People

The Verify People service is used to submit text-based data such as name and address to the GBG Identity Solution, and retrieve back a verification result. The text-based information can come from the user typing in details, or from the Address Capture service, or from any other suitable locations (e-mails, databases and so on).

(see the api)

Verify Document

For users with a mobile phone with camera (or for users presenting their documents in a store with a scanner or automated kiosk) the Verify Document service can capture photos of the document and process them to extract information. This also removes a burden from staff who may not be trained to recognise all sorts of identity documents.

(see the api)


The Facematch service is typically used with a mobile phone camera (or a camera in an automated kiosk) in order to compare with the photo identification on a previously scanned document (using the Verify Document service). This reduces the risk that an individual presenting the document does not match the photo in the document.

(see the api)


The Liveness service is used to confirm that a human is present in front of a camera. It detects human movements of facial expressions in order to do this.