Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Property

Data Type

Mandatory

Example

Description

CustomerDataMapping

FidentityAttributeMapping[]

(tick)

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

your-tentant-client-secret

 

ProcessSteps

FidentityProcessStep[]

(tick)

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

Code Block
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.

...