Goals
We define a digital wallet as a payment instrument that is typically loaded with money transferred from a bank account or a credit card. The funds available in the wallet is then used for transactions like bill payments and transferring funds to other wallets within the platform
- Define and track the completion of features that are critical for supporting a basic wallet on Fineract-CN.
Requirements
# | Module | Title | Overview | Importance | Fineract CN support | Notes |
---|---|---|---|---|---|---|
1 | Office and staff | Manage offices | Support for creating, editing and deleting offices and their associated hierarchy | Must Have | Yes | An error message is shown when creating the head office using the community App. Need to investigate further. |
2 | Manage staff | Ability to manage staff within offices and associate user logins with fine-grained access control to them | Must Have | Yes | ||
3 | Customers | Customer Management | Ability to create and manage customers along with organization specific structured data | Must Have | Yes (needs QA) | |
4 | KYC | Ability to associate KYC documents with customers | Must Have | Yes (needs QA) | ||
5 | Deposits | Transactional accounts | A transactional account having support for deposits and withdrawals | Must Have | ??? | |
6 | Documentation and additional data | Ability to capture documents and additional (organization specific) structured data associated with deposit accounts | Should Have | |||
7 | Accounting | COA | Accounting module with support for creating an organizations COA | Must Have | Yes (needs QA) | |
8 | Integrated accounting | Integrated accrual accounting for deposits and withdrawals linked to transactional accounts | Must Have | ??? | ||
Customer Access API Gateway | View account details | Ability of authenticated customers to query organization defined (fine-grained control) details of their wallet accounts. Typical details include associated schedules, payment history & breakdown and details of upcoming payments | Must Have | Yes | ||
10 | Transfers | Allow customers to make transfers between their accounts and payments to third parties. | Must Have | ??? | ||
11 | Third Party processors | Allow customers to authorize third parties to act on their behalf. These third parties need to be registered with the customer access gateway along with details of their associated permissions. | Should Have | ??? |
Questions
Below is a list of questions to be addressed as a result of this requirements document:
Question | Comments | Outcome |
---|---|---|