[taler-docs] branch master updated: add user type to kyc-check

[gnunet]

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

grothoff pushed a commit to branch master
in repository docs.

The following commit(s) were added to refs/heads/master by this push:
     new 63e2c73  add user type to kyc-check
63e2c73 is described below

commit 63e2c739aeccd743cb4e9741153963a0da9e4d27
Author: Christian Grothoff <christian@grothoff.org>
AuthorDate: Fri Aug 19 09:32:06 2022 +0200

    add user type to kyc-check
---
 core/api-exchange.rst     |  8 +++++---
 manpages/taler.conf.5.rst | 21 +++++++++++++++++++++
 2 files changed, 26 insertions(+), 3 deletions(-)

diff --git a/core/api-exchange.rst b/core/api-exchange.rst
index 86b12ad..ed63cb2 100644
--- a/core/api-exchange.rst
+++ b/core/api-exchange.rst
@@ -1843,7 +1843,7 @@ exchange.
     interface KycNeededRedirect {
       // Legitimization target that the merchant should
       // use to check for its KYC status using
-      // the ``/kyc-check/$LEGITIMIZATION_UUID`` endpoint.
+      // the ``/kyc-check/$LEGITIMIZATION_UUID/...`` endpoint.
       legitimization_uuid: Integer;
 
     }
@@ -3318,7 +3318,7 @@ typically also view the balance.)
 
       // Legitimization target that the merchant should
       // use to check for its KYC status using
-      // the ``/kyc-check/$LEGITIMIZATION_UUID`` endpoint.
+      // the ``/kyc-check/$LEGITIMIZATION_UUID/...`` endpoint.
       // Optional, not present if the deposit has not
       // yet been aggregated to the point that a KYC
       // need has been evaluated.
@@ -4227,7 +4227,7 @@ KYC status updates
      }
 
 
-.. http:GET:: /kyc-check/$LEGITIMIZATION_UUID/$H_PAYTO
+.. http:GET:: /kyc-check/$LEGITIMIZATION_UUID/$H_PAYTO/$USERTYPE
 
   Check or update KYC status of a particular payment target.
   Returns the current KYC status of the account and, if
@@ -4236,6 +4236,8 @@ KYC status updates
   returned previously from an exchange API endpoint that
   determined that KYC was needed.  The H_PATYO must be
   the hash of the payto:// URI of the payment target.
+  The USERTYPE states whether the entity to perform
+  the KYC is an "individual" or "business".
 
   **Request:**
 
diff --git a/manpages/taler.conf.5.rst b/manpages/taler.conf.5.rst
index f34e2a5..510fd87 100644
--- a/manpages/taler.conf.5.rst
+++ b/manpages/taler.conf.5.rst
@@ -170,6 +170,8 @@ EXCHANGE KYC OAUTH2 OPTIONS
 The following options must be in the section "[kyc-provider-XXX]" sections 
with "LOGIC = oauth2".
 
 
+KYC_OAUTH2_VALIDITY
+  Duration (e.g. "12 months") of the validity of the performed KYC check. Can 
be "forever".
 
 KYC_OAUTH2_AUTH_URL
   URL of the OAuth2 endpoint to be used for KYC checks. Requires KYC_ENABLED 
to be "OAUTH2". Example: "http://localhost:8888/oauth/v2/login"; (or "/token")
@@ -190,6 +192,25 @@ KYC_OAUTH2_POST_URL
   URL to which the exchange will redirect the client's browser after 
successful authorization/login for the KYC process.
 
 
+EXCHANGE KYC KYCAID OPTIONS
+^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+The following options must be in the section "[kyc-provider-XXX]" sections 
with "LOGIC = kycaid".
+
+
+KYC_KYCAID_VALIDITY
+  Duration (e.g. "12 months") of the validity of the performed KYC check. Can 
be "forever".
+
+KYC_KYCAID_AUTH_TOKEN
+  Authentication token to access the KYC service.
+
+KYC_KYCAID_FORM_ID
+  ID that specifies the form to use for the KYC process.
+
+KYC_KYCAID_POST_URL
+  URL to which the exchange will redirect the client's browser after 
successful authorization/login for the KYC process.
+
+
 
 EXCHANGE OFFLINE SIGNING OPTIONS
 --------------------------------

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