Created by User d1ebf, last modified on Nov 25, 2022

Key parent P fe story points be story points story points Status
SM-4990 Epic Slacker Integration in Transactions (MVP) Medium 0.0 2.0 2.0 To Do

Role: SaFi Bank

Objective: wants to additionally authenticate the user with a face match or vKYC

Reason: So that we can confirm user’s identity and let him initiate the transaction.

Functional requirements:

Slacker decides if the transaction evaluation needs additional authentication of the user including the level of the authentication (step-up) and send this information to the FE.

UI requirements:

Process flow:

https://safibank.atlassian.net/l/cp/uo0m9bCH

https://safibank.atlassian.net/l/cp/0fuVFPb4

Execution steps:

  1. User creates a transaction

  2. The loader is displayed while the transaction is checked by the fraud system

  3. User will receive an additional authentication request for the face match or vKYC

  4. User will provide the requested data/action

  5. The transaction is approved and its status screen is displayed with “in process/pending” message

Internal dependencies:

Slacker

IAM

External dependencies:

Alternative scenarios:

  1. User creates a transaction

  2. The loader is displayed while the transaction is checked by the fraud system

  3. User will receive an additional authentication request for the face match or vKYC

  4. User will provide incorrect data/action or will not provide them at all

  5. The transaction is rejected and user is redirected back to the first screen after selecting the type of the transaction

Acceptance criteria:

  • User creates (confirms) a transaction

  • the slacker-manager API is called for a fraud check

  • Slacker decides whether the transaction is approved, rejected or additional authentication of the user is needed (step-up)

  • Slacker evaluates the transaction with a certain level of fraud probability risk

  • Slacker sends this information to the FE

  • the user is challenged with ‘Face match’ authentication or ‘vKYC’ right after he confirmed the transaction (the flow is continuous)

  • the step-up result is evaluated

  • Result of the authentication is displayed to the user in form of a push notification (which includes status of the transaction)

  • There are 3 possible answers from Slacker (step-up):

    • if the face match/vKYC was successful - status screen with the transaction state is displayed to the user (“pending” for OTC or “in process” or ‘successful’)

    • If the face match/vKYC failed - the transaction is rejected, an error message is displayed (described here SM-5093 - Error message if the Transaction is rejected by the Step-up In Progress ) and the user will be redirected to the initial screen where he selected the merchant/or transaction type (whichever is furthest) (CTA button ‘Try it again’)

    • manual approval may be requested

Links to wireframes/UI:

face match flow (incl. in onboarding) https://www.figma.com/file/dkDQHRa1zq7tU58MiL6hBR/SaFi---UI---MVP-(Shared)?node-id=484%3A7873

video call flow (incl. in onboarding) https://www.figma.com/file/dkDQHRa1zq7tU58MiL6hBR/SaFi---UI---MVP-(Shared)?node-id=13576%3A76752

error screen https://www.figma.com/file/dkDQHRa1zq7tU58MiL6hBR/SaFi---UI---MVP-(Shared)?node-id=20196%3A183969