GBG Developers

Frequently Asked Questions

.red { fill: #b0013a; }
  • I want to use multiple verification checks in my users on-boarding journey, how do I group them together?

    Combining multiple verification checks for a single cistomer is achieved using the person-id. This id tells IDAAS to group requests submitted under the same person-id, and generate a combined score across them. A new person-id will be created if it is not supplied with a request, so you should retrieve it from your initial verification check, and supply it to all further requests in the journey to tie them together. For more information on how to submit a person-id for a specific request type, see our API Reference.

  • How do I know which scopes I need for a particular verification request?

    Without the correct scopes on your auth token you will get 401 unauthorised or 403 Forbidden responses when you make requests. You need to ensure that your SSO provider is granting the correct scopes for the verification you are trying to perform. You can find more information on scopes in our guides.

  • Which verification checks should I use?

    You can choose data checks, document checks or both. The choice depends on your business requirements and attitude to risk. GBG can help you decide which checks are appropriate. (contact)
    Using both documents and data achieves the best results. Documents and faces should always be captured using a mobile handset to optimise the captured images.

  • Which approach to verification should I use?

    Businesses using both data and documents can decide which of the two to start the onboarding journey with.
    Starting with a document allows personal data (name, address, date of birth) to be extracted from the identity document (where present). See the guide for more information.
    Starting with manual customer input allows the entered details to be compared against the data extracted from a document at a later stage. See the guide.