SaFi Bank Space : 🟢 Slacker checks on scheduled Transaction

Key	parent	P	fe story points	be story points	story points	Status
SM-6801	Automated Scheduling one-time & recurring (MVP)					To Do

Role: System

Objective: We want to send the Schedule when created or a single scheduled transaction when executed to the Slacker system.

Reason: So that we will know, if the transaction should be accepted, rejected or step-up is required.

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 executed by BE automatically or a Schedule is created

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

3. Slacker will evaluate the transaction risk

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

Execution steps:

1. a single scheduled transaction is executed

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

3. User will receive a push notification of the evaluation

4. The transaction was approved and its status screen is displayed with “in process” message

or

1. User creates a schedule

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

3. The schedule was approved and is displayed in the list of active schedules

Internal dependencies:

Slacker

IAM

External dependencies:

Alternative scenarios:

1. a single scheduled transaction is executed

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

3. User will receive a push notification of the evaluation

4. The transaction was rejected or step-up was needed so the transaction was also rejected automatically

5. status screen is displayed with “failed” message

or

1. User creates a schedule

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

3. The schedule was rejected and will not be created or step-up is required

Acceptance criteria:

• We will check the creation of a Schedule in synchronous way so Slacker can act immediately (and ask for step-up or reject)

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

• We will flag transactions that were executed from the BE (including scheduled transactions), so Slacker is aware

Links to wireframes/UI: n/a