| Key | parent | P | fe story points | be story points | story points | Status |
|---|---|---|---|---|---|---|
| SM-5310 |
EPFS Slacker Integration in Transactions
|
|
3.0 | 5.0 | Done |
Role: User
Objective: I do not want to see transactions that required step-up or were rejected by fraud (slacker component) in my transaction history.
Reason: so that I can see only transactions approved by Slacker in my history.
Functional requirements:
UI requirements:
Process flow:
https://safibank.atlassian.net/l/cp/0fuVFPb4
Execution steps:
Internal dependencies:
Slacker
Domain manager
External dependencies:
Alternative scenarios:
Acceptance criteria:
If transaction is rejected by slacker there is no information about it in history whatsoever.
If step up is requested by slacker, it means, mobile app needs to send new Transaction request with higher authentication level, practically transaction is rejected “with an advice”. Therefore there is no information about the transaction in history as well.
By history I mean history shown by mobile phone.
Links to wireframes/UI: n/a