Key | parent | P | fe story points | be story points | story points | Status |
---|---|---|---|---|---|---|
SM-5066 | Slacker Integration in Transactions (MVP) | 1.0 | 2.0 | 3.0 | Resolved |
Role: User
Objective: To be notified about the result of manual approval of the transaction.
Reason: So that I know that the transaction was checked and was approved or rejected.
Functional requirements:
UI requirements:
Process flow:
https://safibank.atlassian.net/l/cp/uo0m9bCH
https://safibank.atlassian.net/l/cp/0fuVFPb4
User creates a transaction
The call to the slacker-manager API is happening for fraud check
Slacker will evaluate the transaction risk as high
manual approval is required
Domain Manager provides API for back office system to enable to manually review the transaction
Ticketing Manager enables Domain Manager to create a ticket for manual approval of the transaction
Backoffice will evaluate the transaction
Result of the evaluation is displayed to the user in form of a push notification
Execution steps:
User creates a transaction
the transaction is in “pending” state while it is checked by the fraud system and back office afterwards
User will receive a push notification of the evaluation
Internal dependencies:
External dependencies:
Alternative scenarios:
Acceptance criteria:
The user is notified via push notification about the result of the manual approval
if the transaction was approved by the Back-office, the push notification will inform about the transaction being approved and the status of the transaction
will remain the same “In process” or
will change from “in process” to “pending” for OTC transactions or
changes to “Successful” (depends on the flow/product)
if the transaction was rejected by the Back-office, the push notification will include just a general message to the user that the transaction was not approved/declined and the status of the transaction
will change to “failed”
if the user taps on the push notification, app will open (login is needed if the user is logged out) and the status screen is displayed to the user with the updated transaction state (in process/pending/failed/successful)
Links to wireframes/UI: n/a