commit a0a23c5fc06b0637c0a7930a41f393228a7c4858
parent 844cfb89acce03b1524344ab000a9e0da2134c6c
Author: Christian Grothoff <christian@grothoff.org>
Date: Fri, 17 Nov 2023 10:05:55 +0100
make KYC section more prominent in exchange manual
Diffstat:
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/taler-exchange-manual.rst b/taler-exchange-manual.rst
@@ -1300,7 +1300,7 @@ Legal conditions for using the service
KYC Configuration
------------------
+=================
To legally operate, Taler exchange operators may have to comply with KYC
regulation that requires financial institutions to identify parties involved
@@ -1316,7 +1316,7 @@ Taler permits an exchange to require KYC data under the following circumstances:
Taler KYC Terminology
-^^^^^^^^^^^^^^^^^^^^^
+---------------------
* **Check**: A check establishes a particular attribute of a user, such as
their name based on an ID document and lifeness, mailing address, phone
@@ -1355,7 +1355,7 @@ Taler KYC Terminology
KYC Configuration Options
-^^^^^^^^^^^^^^^^^^^^^^^^^
+-------------------------
The KYC configuration determines the *legitimization rules*, and specifies
which providers offer which *checks* at what *cost*.
@@ -1412,7 +1412,7 @@ per configuration section:
OAuth 2.0 specifics
-^^^^^^^^^^^^^^^^^^^
+-------------------
In terms of configuration, the OAuth 2.0 logic requires the respective client
credentials to be configured apriori to enable access to the legitimization
@@ -1479,7 +1479,7 @@ configuration above and an exchange running on the host
Persona specifics
-^^^^^^^^^^^^^^^^^
+-----------------
We use the hosted flow. The Persona endpoints return a ``request-id``, which
we log for diagnosis.
@@ -1540,7 +1540,7 @@ based on the attributes collected by the specific template.
KYC AID specifics
-^^^^^^^^^^^^^^^^^
+-----------------
We use the hosted flow.
