DBS Basic and RTW

For clarity the JSON below provides an example of the 'identity-profile-requirements' object which is the relevant part of the full request.

Request

{

  "trust_framework": "UK_TFIDA",

  "scheme": {

    "type": "DBS_RTW",

    "objective": "BASIC"

  }

}

Response

An assertion which meets both the DBS Basic and RTW scheme requirements, where scheme compliance has been reached. For clarity the JSON below provides an example of the 'identity profile' object which is the relevant part of the full response. This JSON is not full response itself.

This example is very similar to the DBS Basic example above, because a GBR Passport is used in both cases. The main difference here is that the attribute IDs for document images and the ‘selfie’ of the user are also included, as required by the RTW scheme. In addition, there are now two scheme compliance reports: one for DBS Basic, and one for RTW.

Digital ID response

This identity profile contains:

• The identity assertion required by the DBS and RTW/R schemes (the union of the two sets)

• A verification report accompanying that assertion, including

  • A boolean to indicate whether DBS scheme compliance has been reached overall, for the level of DBS check (objective) requested

  • A boolean to indicate whether RTW/R scheme compliance has been reached overall

  • The GPG45 LoC reached, and the route used to achieve this

  • Detail of the ‘scores’ obtained in each category under GPG45, with links to evidence

  • Evidence details

    • Document evidence, including

      • Links to images of each document (as required by the RTW/R scheme)
      • Fields extracted from each document (to satisfy the DBS scheme requirement for Passport and Driving Licence details)
      • A high-level description of the checks passed for this evidence

    • Biometric evidence, including

      • A link to the image of the user’s ‘selfie’ (as required by the RTW/R scheme)
      • A description of the liveness method used

• An authentication report, including details of which level of authentication was used to authenticate this transaction from the user’s reusable digital ID

{

  "identity_assertion": {...},

  "verification_report": {...},

  "authentication_report": {...},

  "proof": "<signature provided here>"

}