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

CustomerDataMapping

FidentityAttributeMapping[]

(tick)

[
	{
		"$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

BaseUrl

string

(tick)

https://your-tenant.stage.fidentity.ch

 

BaseApiUrl

string

(tick)

https://your-tenant.stage.fidentity.ch/api/v1

 

ClientId

string

(tick)

your-tenant-api-key

 

ClientSecret

string

(tick)

laksdjfiwjl84lkjasc92ljasfy

 

ProcessSteps

FidentityProcessStep[]

(tick)

[
  {
    "$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
}

ValidationScoreThreshold

double

(tick)

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 1. If you wanna let some minor adjustments trough, such as Lukasz corrected to Łukasz, set a value for 0.85.

Note: The adjustment from above, will result in a -0.07 score.

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:

  1. verifiedValue This value is set if a human reviewer manually checked the documents and corrected or changed a value manually

  2. vizValue This is the value from the visual identification zone on the document. This zone included special characters such as ä, ö, ü, ç and others.

  3. idValue This 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 false

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 canOverride was false.