Understanding Entity Profile KYC Results

The results of a verification check (or a call to GET /entity/{id}/checks) when an entity has a profile configured will still return all of the structures of the existing check results. There is however an additional section named entityProfileResult. An example response would look something like the following:


Raw Result	Commentary
"entityProfileResult": { "actionRecommended": "PASS_MANUAL", "addressResults": { "a63d471b-9417-4474-0ee0-aa7310055e38": { "checked": true, "matchCount": 1, "matchSources" : [ "au-ntd" ], "matchType": "curr_addr", "verified": true } }, "checkResults": [ { "checkType": "two_plus", "result": "PASS" }, { "checkType": "id", "result": "PASS" }, { "checkType": "pep_media", "result": "PASS" }, { "checkType": "idvalidate", "code": "MISSING_PREREQUISITE", "message": "Attestation check succeeded. The attestation documents are not present, but are not required", "result": "NA" } ], "checkType": "two_plus,id,pep_media,idvalidate", "documentResults": { "4a38bc35-f2de-77e0-cbbe-b3b27f644ce8": { "checked": true, "matchCount": 1, "matchSources" : [ "au-govid-dl" ], "matchType": "gov_id", "verified": true }, "9e658277-9bbc-11cc-1f83-593abf54ed6c": { "checked": true } }, "entityId": "b90d22ab-9571-48c9-6c66-1e7924501b9b", "kycResults": [ { "matchCount": 3, "matchSources" : [ "au-ntd", "au-elec-roll", "au-phone-pub" ], "matchCountRequired": 2, "matchTypes": { "name": { "checked": true, "matchCount": 3, "verified": true } }, "verified": true }, { "matchCount": 4, "matchSources" : [ "au-ntd", "au-elec-roll", "au-phone-pub", "au-asic" ], "matchCountRequired": 2, "matchTypes": { "address": { "checked": true, "matchCount": 1, "verified": true }, "dob": { "checked": true, "matchCount": 3, "verified": true } }, "verified": true }, { "matchCount": 1, "matchSources" : [ "au-govid1-dl" ], "matchCountRequired": 1, "matchTypes": { "gov_id": { "checked": true, "matchCount": 1, "verified": true } }, "verified": true } ], "latestCheckDate": "2020-08-09T14:04:35.624Z", "manualIntervention": true, "profileName": "default", "riskLevel": "MEDIUM", "riskPolicy": "CDD" },	- This is the same actionRecommend as found in the original checkSummary. Use this as your guide for the final outcome. Each address gets its own results Was the address checked? How many matches found? What were the individual data sources matched. See this article for the list of sources that can appear in the list. Is it the current or previous address? Were there enough matches to consider this address verified? For each checkType that was applied in this profile - did it PASS, FAIL or was NA (not applicable) When a simple PASS/FAIL is not enough, we supply additional notes and feedback. The list of checkTypes applied as part of this profile. Like the addresses, we supply the results of each document that was checked. What were the individual data sources matched. See this article for the list of sources that can appear in the list. This document was checked, but was not matched nor verified. The entityID We break down each ID element that is used to verify an entity. In this case the name has been matched 3 times out of a required 2. What were the individual data sources matched. See this article for the list of sources that can appear in the list. We confirm that the element has been both checked as is considered verified as per the profile rules. In this case we’re combining the matches of addresses (all addresses) and date of birth. These can also be split individually, depending on profile rules. What were the individual data sources matched. See this article for the list of sources that can appear in the list. This example shows a standard two_plus result where the name is matched twice and address matches + dob matches must be >= 2 as well. The total ID document verifications are also counted and detailed summed up. What were the individual data sources matched. See this article for the list of sources that can appear in the list. When we last ran this check Was manual intervention required? What profile was applied? Final risk level Risk policy applied, based on the risk rules engine.

This new format, we think you’ll agree, gives a more detailed and clearer picture than having to dig through the original check results and checkSummary key/value pairs. But all of that raw data is still available if you request a “full” check result.

A “summary” result will return the checkRisk, checkSummary and entityProfileResult sections.

A “simple” result will just return the entityProfileResult section - although this only works for entity’s with a profile.