DBS Basic
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", "objective": "BASIC" }}Response
DBS Basic assertion 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.
IDV response
This identity profile contains:
The identity assertion required by the DBS scheme
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
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
- Fields extracted from each document (to satisfy the DBS scheme requirement for Passport and Driving Licence details)
- Links to the IDV resource entity for that evidence (containing media such as document images and extracted fields)
- Links to relevant checks listed separately, outside the verification report, in the IDV session report for completeness
- A high-level description of the checks passed for this evidence
Biometric evidence, including
- Links to the IDV resource entity for that evidence (containing media such as face images)
- Links to relevant checks listed separately, outside the verification report, in the IDV session report for completeness
- A description of the liveness method used
{ "identity_assertion": {}, "verification_report": {}, "proof": "<signature provided here>"}Note that, outside the “identity profile” object given above, the IDV session report will also include details of all evidence that was captured, checks performed etc. for completeness.
Elements of the identity profile verification report link to relevant checks and resources, for ease of reference.
Failure to reach scheme compliance
DBS Basic assertion where scheme compliance has NOT 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.
IDV response
This identity profile contains:
- The identity assertion required by the RTW/R scheme, or as much of it as we have been able to gather
- A verification report accompanying that assertion, including
- A boolean to indicate whether RTW/R scheme compliance has been reached overall
- A reason to indicate why scheme compliance was not achieved
{ "identity_assertion": { "current_name": { "given_names": "JOHN JIM FRED", "first_name": "JOHN", "middle_name": "JIM FRED", "family_name": "FOO", "full_name": "JOHN JIM FRED FOO" }, "date_of_birth": "1979-01-01" }, "verification_report": { "report_id": "61b99534-116d-4a25-9750-2d708c0fb168", "timestamp": "2022-01-02T15:04:05Z", "subject_id": "f0726cb6-97c1-4802-9feb-eb7c6cd07949", "trust_framework": "UK_TFIDA", "schemes_compliance": [ { "scheme": { "type": "DBS", "objective": "BASIC" }, "requirements_met": false, "requirements_not_met_info": "INSUFFICIENT_ACTIVITY_HISTORY" } ] }, "proof": "<signature provided here>"}Note that, outside the “identity profile” object given below, the IDV session report will include details of all evidence that was captured, checks performed etc. for completeness.