SaFi Bank Space : PL Epic: Scheduling | SEMI-AUTOMATED recurring

Objective:

Money must be scheduled in advance to be transferred in the future from the master account of user A to another account in the same SaFI bank (sub-account of user A or master account of user B ).

The scheduling can be for a one-off money transfer or instalments on a regular basis (given period).

Reason:

The client wants to transfer money from his/her own master account to another active master account in the same bank in the pre-defined period, re-occurring payment. Set-up information for re-occurring transfers should be provided via manual input from the user.

Functional requirements:

• https://safibank.atlassian.net/wiki/spaces/ITArch/pages/31260681
• https://safibank.atlassian.net/wiki/spaces/ITArch/pages/31260689

UI requirements:

• Ability to provide manual input about payment and occurrence
• The client can define the occurrence of payment: daily, weekly, monthly, or annually
  • Weekly: require specifying the day in a week
  • Monthly: require specifying the day in a specific month
  • Bimonthly
  • Annually: require specifying the exact month and day

Process flow:

• n/a

Execution steps:

• The client can create a standard payment from the master account
• Key information for payment must be provided by the client as in the manual input
• Fulfilled payment must offer an option to convert the one-time payment into a scheduled payment
• All fulfilled information will be re-used, and users can on top of it provide information on how often this payment will re-occur (specific date, weekly, monthly, annually, etc.)
• Selected occurrence model to be stored in the system
• When scheduled payment occurs, the client must be notified
  • Notifications required for Transactions: here
• In case that scheduled payment fails, the client must be notified, and payment can be executed manually with original data

Internal dependencies:

• Internal Payments (TM)
• Internal Ledger
• Notification System (Push, SMS, Email)
• https://safibank.atlassian.net/wiki/spaces/ITArch/pages/32964609
• https://safibank.atlassian.net/wiki/spaces/ITArch/pages/32669735
• https://safibank.atlassian.net/wiki/spaces/ITArch/pages/32964639

External dependencies:

• n/a

Alternative scenarios: n/a

Acceptance criteria:

• The client can convert one-time payment to scheduled payment
• The client can update already created scheduled payment with new values/data
• The client can delete already created scheduled payment
• The client will be notified about the status (positive/negative) of the scheduled payment