As an Operator, my biometrics should not be accepted when I am registering an applicant.

Biometrics captured during registration should not match with operator’s biometrics

Components: Match SDK (Local deduplication)

Purpose: develop a reference match sdk comparable in implementation logic with IBioAPIv2 Interface being implemented.

Requirements:

1. The Match SDK should be a build time dependency of the project.

2. A country should be able to replace the reference match sdk with a vendor provided one and be able to use it with no code change.

Purpose: As an Operator, my biometrics should not be accepted when I am registering an applicant.
Pre-requisites:

1. Android Reg Client should be installed.

2. The operator should be onboarded and should be logged in using valid credentials.

Basic flow:

1. As an Operator when I am registering an applicant, my biometrics should not be accepted in the applicant’s biometric capture field.

2. A local deduplication should be performed to identify if the biometrics of the applicant is matching with the Operator’s biometrics. If it does, the user should not be able to proceed further.

Acceptance criteria:

1. This is configurable and can be on and off. If it is on, local deduplication should be performed, if it is not active, local deduplication should not be performed.

When Match SDK is enabled

1. If a biometric match is found, the biometric data should not be saved and operator shouldn’t be able to proceed to screens next to biometric capture screen.

2. If biometric match is found, display the error “Biometrics Matched With Operator Biometrics, Please Try Again".

3. This should work in offline and online mode.

4. If the biometric matches, we will get a message- The biometrics entered matches with Operators’s biometrics.

When Match SDK is disabled:

1. The flow should continue as usual.

Scenario #1: When the Operator logs in using his credential and gives his biometrics instead of the residents biometrics (local dedupe)

Scenario #2: When another Operator logs in using his credential and gives his biometrics instead of the residents biometrics (local dedupe)

Scenario #3: Happy flow, When residents biometrics are captured, the flow should continue.

Since it is mock Match SDK in our case, we will have to manually dictate if we want the match to pass/fail.

Potential Approaches: Two builds of Matcg SDK, one which gives failure responses in all scenarios and the second which gives success in all scenarios. This will help in validating all flows properly.