Epic:
SM-31
-
ONB: Verify customer's unique identity
Done
User story:
SM-1053
-
Deduplicate customer
Done
User story: As a system I want to make sure each customer is unique so that I can prevent fraud or creation of multiple customer instances for the same person.
Role: System
Objective: to prevent fraud or the creation of multiple customer instances for the same person.
Reason: fraud prevention and anti-duplicity check
Functional requirements:
General info: 
1st Duplicty Check will be executed always. 2nd Duplicty Check will be executed always. 3rd Duplicity Check will be executed always.
Deduplicity checks are meant to be a micro-service, fetching data for OSP.
Deduplication will be managed by OSP, as a part of its risk assessment tree.
- 1st Duplicity Check / Timing
: During the Phone number verification / https://www.figma.com/file/dkDQHRa1zq7tU58MiL6hBR/SaFi---UI---MVP-(Shared)?node-id=484%3A7667
1.1. Phone number
The entered phone number is compared to the phone numbers stored in DB.
2. 2nd Duplicity Check / Timing : After Liveness check / https://www.figma.com/file/dkDQHRa1zq7tU58MiL6hBR/SaFi---UI---MVP-(Shared)?node-id=484%3A7889
2.1. ID number and ID type
The entered ID number and ID type are compared to the ID numbers and ID types stored in DB.
2.2. Cross-values
Entered values are compared to the values stored in DB. The check result is determined based on the
cross-values table. 
Cross-values table:
First name | Last name | Whole name | DoB | ID# + type | Device fingerprint | Wifi / IP address | Email address | |
|---|---|---|---|---|---|---|---|---|
First name | OK | vKYC | OK | vKYC | OK | OK | vKYC | |
Last name | vKYC | vKYC | vKYC | vKYC | vKYC | vKYC | ||
Whole name | vKYC | vKYC | vKYC | vKYC | vKYC | |||
DoB | vKYC | vKYC | vKYC | vKYC | ||||
ID# + type | vKYC | vKYC | vKYC | |||||
Device fingerprint | OK | vKYC | ||||||
Wifi / IP address | vKYC |
Source: https://advancegroup.larksuite.com/docs/docusybbVC8Eg2hG6vFpoKzlzZg#lMOY8d
3. 3rd Duplicity Check takes place / Timing : After Liveness check / https://www.figma.com/file/dkDQHRa1zq7tU58MiL6hBR/SaFi---UI---MVP-(Shared)?node-id=484%3A7889
3.1. Face search
Photo captured from Liveness check (selfie) is compared to all already captured Face photos in DB.
AAI service: “Photo search” should be used in this case.
Checks result:
The result will be pushed into OSP. OSP will return Onboarding result (Success or vKYC) based on Risk Decision Tree.
UI requirements: vKYC screen
Process flow: n/a
Execution steps: How each step is executed (what is happening in FE, BE, 3rd party calls)
Internal dependencies: n/a
External dependencies: AAI for Face recognition check
Alternative scenarios: n/a
Acceptance criteria:
IF all Duplicity checks are FALSE, i.e. no duplicity has been found, THEN Customer is displayed the Success screen at the end of the onboarding flow (https://www.figma.com/file/dkDQHRa1zq7tU58MiL6hBR/SaFi---UI---MVP-(Shared)?node-id=484%3A8189 ) and onboarding is finished.
IF at least 1 Duplicity check is TRUE, i.e. some duplicity has been found, THEN Customer is displayed the vKYC screen at the end of the onboarding flow, i.e. the onboarding can’t be finished without a call with the human Agent.
Links to wireframes/UI: Successful result: https://www.figma.com/file/dkDQHRa1zq7tU58MiL6hBR/SaFi---UI---MVP-(Shared)?node-id=484%3A8189 and vKYC result: TBD