GBG Developers

Guides   |   Document-led Journeys or Workflows

Document-led Journeys or Workflows

Journeys or customer workflows describe the process through which a user becomes verified. For example, a particular workflow may require two physical documents to be scanned and passed, followed by a face matching comparison with a video camera. Each stage of this workflow will be scored and combined into a final result. Workflows where documents are presented first (rather than say a workflow where the customer telephones and states their name and address, or types in details in a web page) can be described as document-first journeys or customer workflows.

A document-first workflow can be a mobile journey that starts by extracting personal data from an identity document, like a passport or driving licence, using a mobile-handset camera. Alternatively it could be a journey or workflow where the user presents their documents to staff in a store, or at an automated kiosk with scanner.
Document-first journeys reduce error-prone typing effort for customers, enabling a better experience and improving data quality.

The sequence below describes an example customer workflow, where documents are verified first, followed by verification that the person present matches the photo identification in the document, and then finally allows the user to enter in an address rapidly (perhaps for a delivery) and then have it verified. Click here for more example customer workflows.

Verify Document

Verify Document

Use this service in order to rapidly capture documents such as driving licenses, identity cards and passports. Images can be captured from a camera, or can be uploaded or selected from a gallery application.

 (see the api)
Facematch

Facematch

This service can be used after a document verification, in order to compare the user's image with that on the documents. Use the Facematch service to reduce the risk that an individual does not match the person indicated on documents. Typically Facematch will be used with a mobile phone camera.

(see the api)
Liveness

Liveness

The Liveness service is intended to ensure that a real person is present when the application is being used. Liveness captured images can also be used with the Facematch service. The Liveness service checks for human movements on a camera.

 
Address Capture

Address Capture

In a document-first journey, there may still be a requirement to capture an address - for instance some documents do not contain an address. The Address Capture feature allows the user to enter in an address with minimal typing. As the user begins typing their address, the service will automatically find matches and list them so that the user can select from them at any time.

 
Verify People

Verify People

The Verify People service can be used to submit text data (for instance taken from documents or manually entered by the user) and perform a verification. 

(see the api)