This article details all the identified risks that you may encounter when reviewing TreeFort Reports, as well as common causes for each identified risk. This can be used as a helpful reference when reviewing client reports to provide insight into why a client failed the TreeFort ID verification or why a certain identified risk is present on a client’s TreeFort Report.
Note: risks shown on a TreeFort Report do not necessarily mean that a fraud is being perpetrated by the client, but depending on the severity of the risks identified, you may want to ask for a satisfactory explanation from the client before continuing to interact with the client. This also applies to identified risks that are marked as Automatic Failure and result in a failed TreeFort ID verification report. In certain cases, it is possible that the client simply did not complete the process correctly, or that the data used in the ID verification process was inputted incorrectly by a team member at your organization. A full list of common reasons for each identified risk is outlined below, organized according to severity (low risk to automatic failure).
Risk Level
Risk Description
Common Causes
Low Risk
The address on the individual’s government-issued photo ID did not match the address provided by the Initiator.
1 – The address inputted into TreeFort by a team member at your organization may have been different than the address on the client’s government-issued photo ID. It is possible that the client has recently moved and has not updated the address on their ID document, or has provided you with a previous address.
2 – The address may have been entered incorrectly into TreeFort by a team member at your organization. Compare the address on the photo of the client’s ID from the TreeFort Report to the address entered into TreeFort and used in the ID verification process.
3 – It is possible that the client has used a passport for their ID document that does not have an associated address.
4 – It is possible that the client provided you with an incorrect address.
Low Risk
The individual’s phone plan may be under a family member’s name, or the individual may be using a family member’s phone.
1 – The client is likely using a cell phone that is belongs to a family member, or has a phone plan that is under a family member’s name.
Low Risk
The account associated to the individual’s cell phone number could not be found. They may not have a phone plan with Telus, Bell, or Rogers.
1 – The client likely does not have a cell phone account with Telus, Bell, or Rogers.
Low Risk
The account associated to the individual’s cell phone number did not match the date of birth provided by the Initiator.
1 – It is likely that the client’s date of birth is not linked to their account with their cell phone provider.
2 – It is possible the client’s date of birth may be entered incorrectly with their cell phone provider.
3 – It is possible the client is using a cell phone of another individual with the same name and address.
Low Risk
The account associated to the individual’s cell phone number did not match the information provided by the Initiator.
1 – It is possible the client was recently married and has not updated their last name with their cell phone provider.
2 – It is possible the client used a different variation of their first name with their cell phone provider (e.g. Bob vs Robert).
3 – It is possible that the client is using the cell phone of an individual with the same name.
4 – It is possible that some information (e.g. address and date of birth) are not associated to the client’s account with their cell phone provider.
5 – It is possible that the client is using a cell phone that does not belong to them, or is not in their name.
Low Risk
The account associated to the individual’s cell phone number is a business or corporate account.
1 – It is likely that the cell phone that the client is using is associated to a business or corporate account.
Low Risk
The address on the credit file found for the individual at a Canadian credit bureau did not match the address provided by the Initiator.
1 – The address inputted into TreeFort by a team member at your organization may have been different than the address associated to the credit file found for the client. It is possible that the client has recently moved and the new address has not yet been reflected in the client’s credit history, or the client has provided you with a previous address not associated with the client’s credit history.
2 – The address may have been entered incorrectly into TreeFort by a team member at your organization. Compare the address on the photo of the client’s ID from the TreeFort Report to the address entered into TreeFort and used in the ID verification process.
3 – It is possible the client provided you with an incorrect address.
Low Risk
The credit file for the individual that matched the information provided by the Initiator does not have a history of at least 3 years.
1 – It is likely that the client is a recent immigrant or is too young to have a credit history of at least 3 years.
2 – If it seems unlikely that a certain client would not have a credit history of at least 3 years, it is possible that the client is trying to pass for someone who does not exist (i.e. they have provided you false information about who they are), and they may have recently been creating a trail of false credit history.
Medium Risk
There was no credit file found at a Canadian credit bureau that matched the information provided by the Initiator.
1 – It is possible that this client does not have any credit history if they are a recent immigrant or are too young to have a credit history.
2 – It is possible that this client’s credit file could not be found due to missing information (e.g. incorrect address).
3 – It is possible the client was recently married and the change in last name has not yet been reflected in the client’s credit history.
4 – It is possible that the client is trying to pass for someone who does not exist (i.e. they have provided you false information about who they are).
High Risk
The date of birth on the credit file found for the individual at a Canadian credit bureau did not match the date of birth provided by the Initiator.
1 – It is possible that this client’s credit file could not be found due to missing information (e.g. incorrect address).
2 – It is possible that a credit file does not exist for this client with the same name and date of birth. The client may be trying to impersonate someone with the same name who is a different age.
Automatic Failure
The individual’s government-issued photo ID did not match the information provided by the Initiator.
1 – It is likely that some of the information on the client’s government-issued photo ID does not match the information entered into the TreeFort platform by a team member at your organization. Compare the name and address on the photo of the client’s ID from the TreeFort Report to the name and address entered into TreeFort and used in the ID verification process. This may occur if the client was recently married and has not yet updated their government-issued ID, or if the client has a different variation of their first name on their government-issued ID (e.g. Bob vs Robert).
2 – It is possible that the client’s name may have been entered incorrectly into TreeFort by a team member at your organization.
3 – It is possible that the client was trying to pass as a different person and provided you false information to use in the ID verification process. Compare the name and address on the photo of the client’s ID from the TreeFort Report to the name and address entered into TreeFort and used in the ID verification process.
Automatic Failure
The individual used a photocopy of their government-issued photo ID, not the original.
1 – It is likely that the client was attempting to use a photocopy of their government-issued photo ID and not the actual ID. An original copy of a government-issued photo ID must be used.
Automatic Failure
It appears there is not a valid hologram on the individual’s government-issued photo ID.
1 – It is likely that TreeFort could not detect a valid hologram on the client’s government-issued photo ID. It is possible that the hologram could not be detected in the image of the ID document that the client uploaded, possibly due to poor camera quality, however it may be an indication that the ID document uploaded is not authentic.
Automatic Failure
The photo on the individual’s government-issued photo ID appears to be tampered with.
1 – It is likely that TreeFort found indications that the photo of the client on their government-issued photo ID has been tampered with.
Automatic Failure
It appears there is no hologram on the individual’s government-issued photo ID.
1 – It is likely that TreeFort could not detect a hologram on the client’s government-issued photo ID while analyzing for security features.
Automatic Failure
The individual’s government-issued photo ID appears to be tampered with.
1 – It is likely that TreeFort detected inconsistencies while analyzing for security features. This will vary document to document, an example of features checked: Expected data present and in the correct position, microprint, watermarks, optically variable ink, presence of fingerprint / other notable (non-text) features and any visible embossing / engraving.
Automatic Failure
The individual’s government-issued photo ID is expired.
1 – It is likely that the client’s government-issued photo ID is expired and cannot be used in the ID verification process.
Automatic Failure
The individual’s government-issued photo ID is present on a list of known frauds.
1 – It is likely that the client’s government-issued photo ID was flagged as being present on a list of known frauds. This feature is currently only available for ID documents from the United Kingdom.
Automatic Failure
The individual failed multiple attempts to prove that they were a real person during the face scan process. They may have been holding a photograph, wearing a mask or other disguise, or using an automated program.
1 – It is likely that the client could not complete the face scan (liveness detection) process properly within the 3 allowed attempts. Instructions and prompts are provided to assist the client in completing the face scan process, however some clients may still have difficulties.
2 – It is possible that the client may have been trying to manipulate the system by holding a photograph, wearing a mask or other disguise, or using an automated program.
Automatic Failure
The individual appears to be a significantly different age from what appears on their government-issued ID.
1 – It is likely that TreeFort detected that the client was a significantly different age than what is listed on the client’s government-issued photo ID. The client may be trying to pass for someone of a different age. Compare the date of birth on the photo of the client’s ID from the TreeFort Report to the photo taken of the client during the face scan process.
Automatic Failure
The photo on the individual’s government-issued photo ID did not match a face scan of the individual presenting the ID.
1 – It is likely that the client is trying to pass for someone else and has used their government-issued photo ID. Compare the photo of the client’s ID from the TreeFort Report to the photo taken of the client during the face scan process.
Automatic Failure
The information on the individual’s government-issued photo ID could not be extracted.
1 – It is likely that TreeFort could not validate that the data returned from a passport was correct. This will only occur when the client uses a machine-readable passport as their source of government-issued photo ID.
Automatic Failure
The individual failed three attempts to upload their ID Document (e.g. driver’s license or passport) and complete a face scan correctly.
1 – It is likely that the client was having difficulties uploading their ID document and was not successful after 3 allowed attempts. They may have been unable to take a clear picture, or may not have uploaded both the front and back of their ID document. Review the photo of the client’s ID and the photo taken of the client during the face scan process from the TreeFort Report.
2 – It is possible that the client was trying to bypass the system and avoid having to upload an ID document and complete a face scan. Review the photo of the client’s ID and the photo taken of the client during the face scan process from the TreeFort Report.
Automatic Failure
The individual’s government-issued photo ID was rejected. It may have been expired, a photocopy, appeared to be tampered with, or present on a list of known frauds.
1 – TreeFort rejected the client’s ID document for an unknown reason. It is likely that the ID document was either expired, a photocopy, or appeared to be tampered with in some way.
Automatic Failure
The photo on the individual’s government-issued photo ID did not match a face scan of the individual presenting the ID, or they may have been trying to manipulate the program (e.g. they may have been holding a photograph, wearing a mask or other disguise, or using an automated program).
1 – TreeFort could not validate that the photo on the client’s government-issued ID matched the photo taken during the face scan process, and therefore rejected the client’s ID document.
Automatic Failure
The account that the individual was able to access at a Canadian financial institution did not match the information provided by the Initiator.
1 – It is likely that the address inputted into TreeFort by a team member at your organization was different than the address associated with the client’s financial institution. It is possible that the client has recently moved and has not updated the address at their bank, or has provided you with a previous address.
2 – It is possible the client was recently married and has not updated their last name with their financial institution.
3 – It is possible the client used a different variation of their first name with their financial institution (e.g. Bob vs Robert).
4 – The client information may have been entered incorrectly into TreeFort by a team member at your organization. Compare the information on the photo of the client’s ID from the TreeFort Report to the information entered into TreeFort and used in the ID verification process.
5 – It is possible the client is impersonating another individual and does not have access to their banking information.
