[taler-exchange] 02/03: edits

[gnunet]

This is an automated email from the git hooks/post-receive script.

grothoff pushed a commit to branch master
in repository exchange.

commit c6e3cba61dee3b9578d3adcee9c76b5c7ca60b02
Author: Christian Grothoff <christian@grothoff.org>
AuthorDate: Sun Jul 2 14:52:36 2023 +0200

    edits
---
 contrib/gana           |  2 +-
 doc/flows/proc-kyb.tex | 12 ++++++++----
 doc/flows/proc-kyc.tex | 10 +++++-----
 3 files changed, 14 insertions(+), 10 deletions(-)

diff --git a/contrib/gana b/contrib/gana
index 31b74264..3e5591a7 160000
--- a/contrib/gana
+++ b/contrib/gana
@@ -1 +1 @@
-Subproject commit 31b74264e62c4a7f4a671033e214c43fa2f304c0
+Subproject commit 3e5591a7e3fd93ba46fc2b538c63f0c16336283d
diff --git a/doc/flows/proc-kyb.tex b/doc/flows/proc-kyb.tex
index fa7761b8..fa63976f 100644
--- a/doc/flows/proc-kyb.tex
+++ b/doc/flows/proc-kyb.tex
@@ -43,9 +43,13 @@
 \end{figure}
 
 At the beginning of the KYB process, the user needs to specify whether they
-are an {\bf individual} (not incorporated) or a {\bf business}. This then
+are an {\bf individual} (not incorporated) or a {\bf business}.\footnote{ In
+pratice, we expect most owners of bank accounts crossing the KYB threshold to
+be businesses, but in principle such a bank account could be owned by an
+individual operating a business without a separate legal entity.}  This then
 determines which types of attributes are collected in the KYB process
-(Table~\ref{table:proc:kyb:individual} vs. 
Table~\ref{table:proc:kyb:business}).
+(Table~\ref{table:proc:kyb:individual}
+vs. Table~\ref{table:proc:kyb:business}).
 
 \begin{table}
   \caption{Information collected for unincorporated individuals}
@@ -77,7 +81,7 @@ determines which types of attributes are collected in the KYB 
process
       {\bf Type}                      & {\bf Required} & {\bf Example}        
\\ \hline \hline
       Company name                    & yes        & Mega AG \\
       Registered office               & yes        & Seestrasse 4, 8008 
Zuerich \\
-      Company identification document & yes        & PDF file \\ 
+      Company identification document & yes        & PDF file \\
       Power of attorney arrangement   & yes        & PDF file  \\
       Business registration number    & yes        &  \\
       Business registration document  & yes        & PDF file \\
@@ -85,7 +89,7 @@ determines which types of attributes are collected in the KYB 
process
       Contact person name             & yes        & Max Mustermann \\
       Identification document         & yes        & JPG image \\
       Date of birth                   & yes        & 1.1.1980  \\
-      Nationality                     & yes        & Swiss     \\ 
+      Nationality                     & yes        & Swiss     \\
       E-mail                          & yes        & me@example.com \\
       Phone number                    & no         & +41-123456789  \\
   \end{tabular}
diff --git a/doc/flows/proc-kyc.tex b/doc/flows/proc-kyc.tex
index 006a0556..c279052f 100644
--- a/doc/flows/proc-kyc.tex
+++ b/doc/flows/proc-kyc.tex
@@ -42,10 +42,11 @@
   \label{fig:proc:kyc}
 \end{figure}
 
-At the beginning of the KYC process, the user needs to specify
-whether they are an {\bf individual} or a {\bf business}. This
-then determines which types of attributes are collected in the
-KYC process (Table~\ref{table:proc:kyc:individual} vs.
+At the beginning of the KYC process, the user needs to specify whether they
+are an {\bf individual} or a {\bf business}.\footnote{ In pratice, we expect
+most wallet-users to be individuals, but in principle a wallet could be owned
+by a business.}  This then determines which types of attributes are collected
+in the KYC process (Table~\ref{table:proc:kyc:individual} vs.
 Table~\ref{table:proc:kyc:business}).
 
 \begin{table}
@@ -66,7 +67,6 @@ Table~\ref{table:proc:kyc:business}).
   \end{center}
 \end{table}
 
-
 \begin{table}
   \caption{Information collected for businesses}
   \label{table:proc:kyc:business}

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.