Key | parent | P | fe story points | be story points | story points | Status |
---|---|---|---|---|---|---|
SM-3102 | Transaction Categorization | 2.0 | 0.0 | 2.0 | Done |
Role:
User
Objective:
Have all the transactions automatically categorized after the transaction has been executed
Reason:
So that the user can see the pre-defined category based on the type of the transaction
Functional requirements:
Once the transaction has been executed, it is automatically displayed under a category.
UI requirements:
Transaction category has to be present on the Transaction Details screen.
Process flow:
User selects transaction type from Shortcuts panel
Initiates transaction flow
Once the transaction is executed, the transaction is categorised based on the selected transaction type
Execution steps:
Transaction type is selected
Transaction flow initiated
Transaction executed
Transaction is added to the category
Internal dependencies:
Transaction type selection
Transaction flow
Transaction details screen
External dependencies:
-
Alternative scenarios:
-
Acceptance criteria:
the category of a transaction is displayed on a Transaction detail screen
the transaction “type” field will be used to map all the categories
the list of static categories: (subject to change)
Transactions to group under category | Category Name (in app) |
---|---|
Pockets (Main Account > Pocket & Pocket > Main Account) | Alkansaf |
Intrabank Transfer | SaFi Transfer |
Top-up via Cash-in (Paynamics & Digipay) | Cash-in |
Top-up via e-wallet | E-wallet top-up |
Top-up via Bank Transfer | Bank Top-up |
Top-up via Debit Card | Card Top-up |
Withdrawal via Cash-out | Cash-out |
Withdrawal via E-wallet | E-wallet Transfer |
Withdrawal via Bank Transfer | Bank Transfer |
Airtime Load | Mobile Load |
Bill Payment (Paynamics & ECPay) | Bill Payment |
https://docs.google.com/spreadsheets/d/1BlidKZe4ApBnvuRsTTiYoaEvIQMaBIxJDRH1ObDC48s/edit#gid=0
Links to wireframes/UI: not yet prepared