Fidentity
- Silvan Grüter
- Urs Mathis
Introduction
Fidentity is a swiss online verification service that allows you - among other things - to verify users. If you would like to use this service you will need to have an active subscription with fidentity and configure the appropriate verification method (servicecorelogin_quality_of_registration_check).
Configuration
The configuration is a JSON object with the following properties:
Property | Data Type | Mandatory | Example | Description |
|---|---|---|---|---|
|
| [
{
"$type":"iTsense.CoreLogin2.Domain.LoT.QoR.AutoMethod.FidentityAttributeMapping, iTsense.CoreLogin2.Domain",
"AttributeSystemName":"ci_given_name",
"FidentityName":"firstname",
"CanOverride":true
},
{
"$type":"iTsense.CoreLogin2.Domain.LoT.QoR.AutoMethod.FidentityAttributeMapping, iTsense.CoreLogin2.Domain",
"AttributeSystemName":"ci_family_name",
"FidentityName":"name",
"CanOverride":true
},
{
"$type":"iTsense.CoreLogin2.Domain.LoT.QoR.AutoMethod.FidentityAttributeMapping, iTsense.CoreLogin2.Domain",
"AttributeSystemName":"ci_birthdate",
"FidentityName":"dateOfBirth",
"CanOverride":true
},
{
"$type":"iTsense.CoreLogin2.Domain.LoT.QoR.AutoMethod.FidentityAttributeMapping, iTsense.CoreLogin2.Domain",
"AttributeSystemName":"ext_nationality",
"FidentityName":"nationality",
"CanOverride":true
}
] | You can map the result of the verification to local attributes. Available fidentity properties: https://demo.fidentity.ch/docs#tag/fidentity/operation/createProcess
This property defines whether or not, Fidentity can override the appropriate value. Fidentity tends to let similar values pass the check. I.E if the user passes | |
|
|
| ||
|
|
| ||
|
| your-tenant-api-key |
| |
|
| your-tentant-client-secret |
| |
|
| [
{
"$type": "iTsense.CoreLogin2.Domain.LoT.QoR.AutoMethod.FidentityProcessStep, iTsense.CoreLogin2.Domain",
"Key": "00000001",
"Type": 2,
"Subtype": 1
}
] | Depending on your needs, you can initiate various process steps within the fidentity verification process. The following steps are available and can be combined:
public enum TypeEnum
{
Selfie = 1,
DocumentRegistration = 2,
UserReview = 3,
QesSignature = 4,
Signature = 5,
Welcome = 6,
PdfScan = 7,
PersonalData = 8,
HandwrittenSignature = 9
}
public enum SubtypeEnum
{
Main = 1,
Nfc = 2,
Zoom = 3,
Readonly = 4,
IdentOnly = 5
} | |
|
| 0.85 | The fidentity verification will return a validation score. You can define a threshold of how accurate the validation needs to be in order to let the user pass. If for example the data has to match 100%, set a value to Note: The adjustment from above, will result in a |
Prioritizing of verified values
Fidentity will return a verification result containing various values as described in their documentation. The result MAY contain the following data for each verified attribute that we will use in the order shown below:
verifiedValueThis value is set if a human reviewer manually checked the documents and corrected or changed a value manuallyvizValueThis is the value from the visual identification zone on the document. This zone included special characters such as ä, ö, ü, ç and others.idValueThis is the value from the machine readable zone on the document. This zone does not include special characters as ä, ö, ü, ç and others. The special characters are replaced by their appropriate replacements such as ae, oe, ue, c and so on.
Validation Messages
There are three different validation messages that show in different cases:
Message | Reason |
|---|---|
The data check was not successful. | The system decision of the Fidentity check was |
The data stored does not sufficiently match the data recorded on the identity document. Please check the spelling, any double names, your date of birth and nationality. | The threshold was not reached. |
Attribute values cannot be reconciled. Mismatched attributes: {0}. | The attribute value that the user provided and the value that Fidentity returned did not match and the flag |
Editing data before the validation / after a failed validation
This feature is available in version 9.2 an higher
The user has the option to edit the data that is being passed to Fidentity before the validation process is started if the attribute is updatable. If the validation of the data passes the Fidentity check, the updated data will be saved if Fidentity did not further adjust the value. If Fidentity did adjust the value further, i.e. the saved value was Grueter, the user changed it before the validation Grütter and Fidentity corrected it to Grüter, the value will only be saved, if CanOverride of the Fidentity configuration is set to true and thus allowing Fidentity to change data.
Note: The name on the official document ist Grüter
Value saved in COS | User changes | Fidentity changes | Fidentity result | CanOverride setting* | CoreOne result | Value saved in COS after | Explanation |
|---|---|---|---|---|---|---|---|
|
|
| Passed |
| Passed |
| Fidentity matches and the Fidentity result can override the local data. |
|
|
| Passed |
| Passed |
| The user changed the value to the correct value, Fidentity passes without any changes and the CoreOne check passes because the user did the changes. |
|
|
| Passed |
| Passed |
| Fidentity matches and the Fidentity result can override the local data even thought the user changed them beforehand. |
|
|
| Passed |
| Failed |
| The Fidentity check passes, but the data would be changed which is prohibited by the can override setting even thought the user changed the data before. |
|
|
| Passed |
| Failed |
| The Fidentity check passes, but the data would be changed which is prohibited by the can override setting. |
|
|
| Passed |
| Passed |
| The Fidentity check passes, the value does not match the value entered by the user but matches the original name, therefore he passes. |
|
|
| Passed |
| Passed |
| The Fidentity check passes, the value does not match the value entered by the user but matches the original name, therefore he passes. |
Related content
© ITSENSE AG. Alle Rechte vorbehalten. ITSENSE und CoreOne sind eingetragene Marken der ITSENSE AG.