@@ -16,20 +16,16 @@ Document used for research management.
- Research on other schemas and transfer options **(Dimitrij)**
- Choose name for wallet/bank-ui **(Dan)**
-Deploy OBP instance with official docker images for testing **(Jason)**
-Test OBP against our CBS requirements **(Łukasz)**
- Prepare list of requirements and views for the wallet app **(Patryk, Adam)**
- Continued implementation and testing of the DIS layer **(Konrad, Ola)**
**Later**
- Test if OBP meets our functional requirements (Patryk, Jason)
- Adapt database schema from Exchange to work with OBP (Jason/Eric)
- Extract AML and KYC modules from Exchange codebase (Eric/Roman)
- Connect extracted AML/KYC modules to the OBP (Eric/Roman)
- Prepare wireframe/mocks and components list for wallet app (Patryk/Adam)
- Design and implement core system for wallet app in React (Patryk/Adam)
- Design and implement core of server for wallet app (Patryk/Adam)
- Design and implement CBS system for functionalities not cover by OBP (???)
- Design and implement CBS system for functionalities not covered by OBP (Łukasz)
## Goals
...
...
@@ -58,6 +54,12 @@ Document used for research management.
- Wallet app should be universal with possibility to add crypto support in later versions (added 09.09.2019)
- We have new employee from Lithuania - a junior Java and Python developer. Currently tasked with AML requirements research on Lithuanian websites. (added 23.09.2019)
- Aplication to European Payment Council (EPC) for SEPA membership registration has been submitted. After testing we will be able to sign agreement with BoL for inderect SEPA access. Date for being operational on the form is moveble and initially set to early 01.2019. Dimitrij knows exact date. (added 23.09.2019)
- We want to use most of Exchange modules in this project, especially auditing one. (added 23.09.2019)
## Questions
Question asked during the meeting that may prove useful in the future.
...
...
@@ -154,6 +156,24 @@ A: No, developers responsible for wallet design can take care of that. (added 09
A: Settlement account is insured we are not sure about customers' accounts. Probably not. For future research. (added 09.09.2019)
**Q: What about SWIFT access? (added 23.09.2019)**
We probably won't have direct corresponded banking account because it's hard for FI to get it. Outsourcing seems more likely. This is ongoing research.
**Q: What about other currencies? (added 23.09.2019)**
For every currency that we want to support we need deposit account in a given currency via the partnership with a bank. When we have better idea about currencies that we want to support initailly we can start negotiations with the bank.
**Q: What abount 2FA? Are we required to provide it from the beggining? (added 23.09.2019)**
We don't now about complience with SCA. Google Authenticator supports both TOTP and HOTP tokens for 2FA and there are quite a few similar apps so we should be fine. This is for further research later on when we get to it.
**Q: Where do we get currency rates from? (added 23.09.2019)**
Exchange has a modules responsible for that. It can extract and analyse currencies from multiple sources like Forex.
**Q: Do you plan to refactor exchange intro microservice in the near future (AML, KYC, Ledger)? (added 23.09.2019)**
No. We will use most of the modules of the current Exchange backend so deploying everything shouldn't be a problem.
**Q: TransferWise allows for fast payments for transaction with Credit Cards via Adyen. Do we plan something similar? (added 23.09.2019)**
We will want to support that in the future. It's not part of the MVP.
## Resources
All links and resources that could be useful in the SEPA project implementation.
...
...
@@ -351,6 +371,8 @@ Resources and research about Open Bank Project.
[OBP - API Sandbox](https://apisandbox.openbankproject.com/)