Â
Key | parent | P | fe story points | be story points | story points | Status |
---|---|---|---|---|---|---|
SM-3709 | Display List of Historical Transactions (MVP) | 3.0 | 5.0 | 8.0 | Rework requested |
Role: User
Objective:
When I initiate a single large transaction,
Reason:
I want to see the actioned transaction as a single row in the transaction history both when in pending state and when in success state.
I want to see the underlying split transactions with respective fees only when clicking on the row to see the transaction detail screen.
Example:
I initiate 150K interbank transfer (withdrawal) to another bank with timing âASAPâ but only 100K gets successfully processed and the rest fails.
As Instapay has amount limit per transaction = 50K, the transaction must be split in 3 equal single transaction of 50K each.
At transaction generation, the user is not aware of the split as it happens within the app and s/he is not aware of it.
Therefore, upon generation, the overall transaction will be âPayment in Processâ status and in transaction panel must display a single outbound row of 150K.
Functional requirements:
As Instapay can only process 50k pesos per transaction, larger transactions have to be split up into âsub-transactionsâ.
UI requirements:
In the transaction details screen the user must see 6 rows in total:
3 rows of 50K each - of which 2 rows (1 row = 50K pesos, 1 row = 50K pesos) in success state and 1 row in failed state.
3 rows displaying the respective fee on each 50K transfer under each 50K transaction. For the failed transaction, the fee row should appear but display 0 fee.
Process flow:
Single large transaction is initiated
Separate âsub-transactionsâ are displayed as one on the list of transactions
âSub-transactionsâ can be accessed by tapping on the transaction on the list
Until all the âsub-transactionsâ are processed, the whole transaction is in âPayment in Processâ state
Execution steps (Happy path):
User initiates a large transaction
Transaction is separated into âsub-transactionsâ in the background
User taps on transaction on the âTransaction historyâ screen
âSub-transactionsâ are displayed
Internal dependencies:
Transaction History
Transaction Processor Manager
External dependencies:
Paynamics
Alternative scenarios: -
Acceptance criteria:
In the use case of a partial transaction going through (100K successfully processed over 150K initiated), the user must see this:
The âin processâ 150K outbound transaction row changed to 100K transferred + charged fee on 2 partial transactions (so something like 115K PHP) so both status and quantity on the single initiated transaction row must be updated instantaneously.
When user clicks on that transaction row to see the detail, the user will become aware of a partial transaction failing and he will see detailed info about how much fee s/he is charged.
In the transaction details screen s/he must see 6 rows in total:
3 rows of 50K each - of which 2 rows (1 row = 50K pesos, 1 row = 50K pesos) in success state and 1 row in failed state.
3 rows displaying the respective fee on each 50K transfer under each 50K transaction. For the failed transaction, the fee row should appear but display 0 fee.
Links to wireframes/UI:
https://www.figma.com/file/0LEEFZgkUnPkPTkY9PMREt/SaFi---WF-%26-UI-(Shared)?node-id=10780%3A121143