Merge branch 'master' of git+ssh://git.taler.net/netzbon

1 files changed, 47 insertions, 11 deletions

diff --git a/doc/concept.tex b/doc/concept.tex
index 90b271e..ff7bcab 100644
--- a/doc/concept.tex
+++ b/doc/concept.tex
@@ -548,27 +548,63 @@ only if their balance is zero.
 
 \subsection{NB bank with account management}
 
-Setup accounts for merchants via SPA/REST API.
-Associate IBAN account with merchant by admin.
-Associate e-mail/phone number with merchant.
-Validation of e-mails.
-Password change (by user or admin).
-Send money back to IBAN account.
-(Send NB to other merchant directly already exists!).
-(Withdraw NB by sending to exchange already exists!).
-Delete account (with 0 balance only).
+\begin{itemize}
+  \item Setup accounts for merchants via SPA/REST API.
+  \item Associate IBAN account with merchant by admin.
+  \item Associate e-mail/phone number with merchant.
+  \item Validation of e-mails.
+  \item Password change (by user or admin).
+  \item Send money back to IBAN account.
+  \item (Send NB to other merchant directly already exists!).
+  \item (Withdraw NB by sending to exchange already exists!).
+  \item Delete account (with 0 balance only).
+\end{itemize}
 
 \subsection{Conversion service NB/CHF}
 
 With exchange rate. Both directions of money transfers.
+The conversion will be made configurable, to allow different
+policies being applied over time.
 
 \subsection{CHF bank integration}
 
-EBICS-CH adaptations or even new bank integration.
+Adapt current EBICS implementation to Swiss variant.  In case
+the Verein Soziale Ökonomie won't find a bank that supports EBICS,
+this milestone will require to implement the bank's own protocol
+from scratch.  Concerning the banking protocol, there are three
+possible cases regarding the banking payloads: (1) the bank uses
+ISO20022, (2) the banking records are embedded into their own protocol,
+(3) another format is used.  If (1), then we'll likely need to adapt
+our ISO20022 logic, since different banks use the standard differently.
+In the other cases, the payload generation and parsing will be implemented
+from scratch.  In any case, we'll first implement a simulation of
+such protocol in the libEufin Sandbox to ease the testing.  As a
+consequence, the Verein Soziale Ökonomie will only need to subscribe to
+their commercial bank shortly before production, cutting some costs
+related to the bank fees.
+
+\subsection{Monitor API}
+
+Administrative API to allow having a global view on the
+state of the currency.  Namely, how much currency has been
+created, how much lies into bank accounts, and how much
+in Taler wallets.
+
+\subsection{Performance}
+
+Change the current implementation to allow long polling
+from Taler exchanges.  Currently, the exchange requests
+banking records at fixed intervals, resulting in significant
+bandwidth and log data being used.
 
 \subsection{Actual deployment}
 
-Documentation, instructions, backup, packaging.
+\begin{itemize}
+  \item Documentation of the new API 
+  \item Instruction for system administrators about installing the services
+  \item Debian packaging of Taler and libEufin
+  \item Docker based deployment
+\end{itemize}
 
 \section{Development milestones (for Priscilla)}