@@ -14,19 +14,22 @@ Document used for research management.
## Tasks
-**Dan, Dimitrije** - research on business, law, and compliance
-**Eric, Jason** - OBP integration with the database, AML, and KYC
-**Patryk** - SEPA Connector and admin panel, wallet app design
-**Adam** - wallet implementation
-**Ola, Konrad** - bank communication layer (DIS) and testing for certification
**Eric and Jason** will try to deploy OBP instance and database instance with a schema based on exchange app. They will also write mapper to connect OBP to the database and configure OBP instance to use our own KYC and AML systems instead of the built-in ones.
In the meantime **Konrad and Ola** will continue to implement the DIS system for bank messages and prepare that layer for the certification process.
At the same time **I'll** continue my research on wallets and try to come up with some GUI layout and general app architecture and tech stack for the Banking UI. I believe that **Adam** will work with me on this. Later I'll get additional 1-2 devs for the wallet app and move to Bank Connector, admin panel, and managing wallet app.
- 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)**
- 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 (???)
## Goals
...
...
@@ -34,7 +37,6 @@ At the same time **I'll** continue my research on wallets and try to come up wit
-**Future goal:** create multi-currency eWallet with FX and international transfers
## Notes
-*PCS Transfers* is the name of our company in Lithuania
...
...
@@ -54,7 +56,7 @@ At the same time **I'll** continue my research on wallets and try to come up wit
- Current MVP for the Banking layer is - working SEPA transfers and account creation (IBAN generation).
- Wallet app should be universal with possibility to add crypto support in later versions (added 09.09.2019)
## Questions
...
...
@@ -118,43 +120,39 @@ A: Maybe in the future, we will apply for membership. There is also the possibil
**Q: What is our target audience (initially and later on)?**
A:
A: [for later - when core systems are implemented] (added 09.09.2019)
**Q: What unique value do we want to provide for the users? As a user why would I create an account with this wallet?**
A:
A: [for later - when core systems are implemented] (added 09.09.2019)
**Q: How do we want to make money out of it, what is our business model?**
A:
**Q: How long can we wait before we start making money with it?**
A:
A: [for later - when core systems are implemented] (added 09.09.2019)
**Q: What exactly does passporting do for us, what it allows us to do?**
A:
A: We can provide accounts without passporting. But for financing services (e-money) you have to be complient with local law. You can apply for passport license to other states throught central EU institiution. (added 09.09.2019)
**Q: What is the next most likely transfer scheme that we want to provide, IACH? Do we know anything about integration plan (technical guides)?**
A:
A: This is currently under investigation. SWIFT is very likely but via 3rd party provider. We are aming to connect to many domestic schemas and use cheap/free domenstic transfers to move money between borders. (added 09.09.2019)
**Q: What does PCS in PCS Transfers stands for?**
A:
A: PCS doesn't necessarily stand for anything in "PCS Transfer", but we have another company called "Peer Consensus Software" and this is a lightly-related company. We are not planning on using this name for marketing/branding. (added 09.09.2019)
**Q: What is the name for the eWallet, do we have one yet?**
A:
A: [this is for future discussion, should be resolved before next meeting] (added 09.09.2019)
**Q: Do we have any specific branding (colour, style) in mind for the app?**
A:
A: No, developers responsible for wallet design can take care of that. (added 09.09.2019)
**Q: Are the accounts we generate insured, like the accounts in [N26](https://n26.com/en-us/security-at-n26) for example (via FDIC)?**
A:
A: Settlement account is insured we are not sure about customers' accounts. Probably not. For future research. (added 09.09.2019)
