Update use cases authored by Aleksandra Grabowska's avatar Aleksandra Grabowska
**Meeting summary – 14.01.2019, 21.01.2019**
**Questions:**
# Meeting summary – 14.01.2019, 21.01.2019
## Questions:
1. What should a user do to receive IBAN account in Dan's bank? Is a user country important?
2. Which system should be responsible for account management – IBAN generation, keeping balance, operation history?
3. Can a user, who is not registered in the Exchange, make a Fiat (Euro) transactions?
4. Should Simple trade mechanism be available for Euro?
5. Is it possible, conversion for other bank than Dan bank to Fiat (Euro)? (A user has fiat and wants cryptocurrency). Should a user be registered?
*6. How will the GUI look like? Will additional authorization be required for sending Euro via Exchange interface?*
6. How will the GUI look like? Will additional authorization be required for sending Euro via Exchange interface?
**Notes:**
1. **CBS** - central banking system. Responsible for:
## Notes
### 1. CBS - central banking system.
Responsible for:
a) allocating IBAN numbers for bank customers
b) discrimination between different transfer types: internal, SEPA, non-internal non-SEPA. Internal ones should be immediately booked by the system and SEPA should be executed via DIS, while all the others should be rejected as not supported
c) executing transactions incoming from SEPA
......@@ -24,7 +25,8 @@ j) calculating fees (blockchain transaction fees equivalent).
There should be separate CBS -plugin for each fiat currency and separate instance of CBS for each fiat currency. The CBS should consist of modules responsible for e.g. managing user accounts, communication with CBS-plugin, communication with Bank, queuing transactions. It should be possible to turn off some modules.
Each CBS-plugin will have separate configuration in the Exchange that defines available functionality in CBS(e.g. opening account).
2. **IB** - Internet banking. Allows a user:
### 2. IB - Internet banking.
Allows a user:
a. Create a transfer order
b. Check account balance
c. Check operation history (what debit or credit his account)
......@@ -32,13 +34,17 @@ d. Check order history (i.e. rejected transfer order)
e. Authorize his transfer order (SMS, token…)
Additionally user should have a possibility to editing his data (phone number), choose authorization method.
3. **DIS** (shortcut based on BoL documentation) consists of:
a CDR reposible for processing documents ((more see na najlepszej stronie stworzonej przez Konrada)
b CPR responsible for processing messages (more see na najlepszej stronie stworzonej przez Konrada)
### 3. DIS (shortcut based on BoL documentation)
Consists of:
a CDR reposible for processing documents (see more [CDR](Architecture/CDR))
b CPR responsible for processing messages (see more [CPR](Architecture/CPR))
c XML- signature (signing and verifying a signature)
d PAS Gateway (sending signed messages to PAS)
4. **PAS** - Bank of Lithuania system managing message exchange between various bank and external systems (more https://gitlab.syncad.com/blocktrades/SEPA/wikis/Architecture/PAS)
### 4. PAS
Bank of Lithuania system managing message exchange between various bank and external systems (see more [PASS](Architecture/PAS))
## Use cases
**I. Sending cryptocurrency and receiving EURO**
......
......