| Key | parent | P | fe story points | be story points | story points | Status |
|---|---|---|---|---|---|---|
| SM-6003 |
Instapay Inbound Interbank & E-wallet Transactions | Outside App (PL)
|
|
2.0 | To Do |
Role: User
Objective:
The user should be able to see the inbound interbank and E-wallet transactions in the transaction history list
Reason:
so that the user has evidence of such transactions and can access the transaction details.
Functional requirements:
After Slacker checks the incoming transaction, it is saved in THM and displayed in the transaction history in the app.
UI requirements:
All the details on the screen are in a read-only mode.
Process flow:
Execution steps (Happy path):
User is on “Transaction history” screen
User taps on a transaction
Transaction details are displayed
Internal dependencies:
Transaction History Manager
Slacker
External dependencies:
Alternative scenarios:
Acceptance criteria:
after the transaction was checked by Slacker (Fraud management system) it is saved in the transaction history manager
the transaction is also displayed in-app in the transaction history list on the Payments page
user can select the transaction from the history list and display its details
the inbound transaction can only have status “successful” or “failed”
Links to wireframes/UI:
n/a