SaFi Bank Space : 🟢 Step-up authentication of a single scheduled Transaction

Key	parent	P	fe story points	be story points	story points	Status
SM-6446	Automated Scheduling one-time & recurring (MVP)		0.0	1.0		In Progress

Role: System

Objective: wants to automatically reject the scheduled transaction if step-up authentication is required

Reason: So that we can immediately fail the scheduled transaction and send a push notification to the user.

Functional requirements:

Slacker decides if the transaction evaluation needs additional authentication of the user including the level of the authentication (step-up).

UI requirements: -

Process flow:

1. A single scheduled transaction is initiated by BE automatically

2. The call to the slacker-manager API is happening for fraud check

3. Slacker will evaluate the transaction risk

4. if step-up authentication is required, transaction is rejected automatically

Execution steps:

Internal dependencies:

Slacker

IAM

External dependencies:

Alternative scenarios:

Acceptance criteria:

• We will check the execution of the single scheduled transaction by Slacker in the same way we currently do with regular transactions (no difference) but

  • we will not ask for the step-up

  • this transaction can be approved, rejected or reported to BoFi

• if Slacker requires a step-up authentication of a single scheduled transaction by its execution, the transaction should fail immediately

• user will receive push notification about failed transaction as described here > SM-3119 - Notify user when scheduled Transaction failed To Do

Links to wireframes/UI: n/a