...
In order to check the quality of registration of a user, you can configure a various verification methods.
Fidentity
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). The configuration is a JSON object with the following properties:
...
Property
...
Data Type
...
Mandatory
...
Example
...
Description
...
CustomerDataMapping
...
FidentityAttributeMapping[]
...
...
| 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
...
...
https://your-tenant.stage.fidentity.ch
...
BaseApiUrl
...
string
...
...
https://your-tenant.stage.fidentity.ch/api/v1
...
ClientId
...
string
...
...
your-tenant-api-key
...
ClientSecret
...
string
...
...
laksdjfiwjl84lkjasc92ljasfy
...
ProcessSteps
...
FidentityProcessStep[]
...
...
| 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
...
...
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.
Manual
With the manual verification step you can generate a document with detailed instructions for the user and a QR code. These instructions usually include where the user has to present the QR code. With the QR code, a user with access to the manual verification security role can scan the QR code in the Admin User Interface and manually mark the verification process as passed or failed. How the user will verify the identity of the customer is not part of this verification method and has to be defined by the customer.
...
Property
...
Data Type
...
Mandatory
...
Example
...
Description
...
UrlPrefix
...
string
...
...
| Code Block |
|---|
https://localhost:44301/m/CoreLogin/ManualIdentificationRequest/GetById/ |
...
Url where the QR code will point to
AHV / ZAS
You can verify the users data against the swiss Central Compensation Office database. In order to do so, you will need to have an active connectivity to said systems.
...
Property
...
Data Type
...
Mandatory
...
Example
...
Description
...
CustomerDataMapping
...
AhvAttributeMapping[]
...
...
| Code Block |
|---|
[
{
"$type":"iTsense.CoreLogin2.Domain.LoT.QoR.External.AhvAttributeMapping, iTsense.CoreLogin2.Domain",
"AttributeSystemName":"ci_given_name",
"AhvName":"firstname",
"CanOverride":true
},
{
"$type":"iTsense.CoreLogin2.Domain.LoT.QoR.External.AhvAttributeMapping, iTsense.CoreLogin2.Domain",
"AttributeSystemName":"ci_family_name",
"AhvName":"name",
"CanOverride":true
},
{
"$type":"iTsense.CoreLogin2.Domain.LoT.QoR.External.AhvAttributeMapping, iTsense.CoreLogin2.Domain",
"AttributeSystemName":"ci_birthdate",
"AhvName":"dateOfBirth",
"CanOverride":true
}
] |
...
You can define which attributes have to match the record in the AHV / ZAS registry and whether or not the values can be over-riden or not.
...
UseLocalMock
...
boolean
...
true
...
For test purpose set this value to true and each user which meets the following criteria will pass the check:
The AHV number ends on an uneven number
The birthday is today
The user is part of the mock data set
The place of birth is Aarau
...
ValidatePlaceOfBirth
...
boolean
...
false
Whether or not the user must enter his place of birth. If enabled, the place of birth has to match the ZAS registry.
...
AhvNumberAttributeName
...
string
...
ahv_ssn_number
...
| Page Tree | ||||
|---|---|---|---|---|
|