Introduction

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

Property	Data Type	Example	Description
`CustomerDataMapping`	`AhvAttributeMapping[]`	[ { "$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 even 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. Available in version 9.1
`AhvNumberAttributeName`	`string`	`ahv_ssn_number`	If the AHV number should be persisted at the end of the verification process, you can define the attribute it will be stored in here. Available in version 9.1.2

AHV / ZAS

Introduction

AHV / ZAS