Key | parent | P | fe story points | be story points | story points | Status |
---|---|---|---|---|---|---|
SM-6802 | Automated Scheduling one-time & recurring (MVP) | 0.0 | In Progress |
Role: SaFi bank
Objective:
We do not want to allow the execution of automated future transactions if there are insufficient funds on the bank account balance
Reason:
So that the user will not be able to get an overdraft for scheduled transactions.
Functional requirements: https://safibank.atlassian.net/l/cp/q2AUCGYh
UI requirements: -
Process flow: https://safibank.atlassian.net/l/cp/q2AUCGYh
Execution steps: https://safibank.atlassian.net/l/cp/q2AUCGYh
Internal dependencies:
Restrictions are delivered by the Accounts squad
External dependencies: -
Alternative scenarios:-
Acceptance criteria:
at the moment of execution of a single scheduled transaction, we need to check if there are sufficient funds on the bank account balance (bank account balance > = scheduled transaction amount with fees)
if the account balance IS sufficient, we will execute the transaction
if the account balance IS NOT sufficient, the scheduled transaction will be rejected with the status Failed and no overdraft will be allowed
Links to wireframes/UI: n/a
Attachments:
Paynamics Paygate CC Direct Server ver 2_13_2.pdf (application/pdf)