[taler-docs] 01/02: KYC process illustration

[gnunet]

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

grothoff pushed a commit to branch master
in repository docs.

commit 7fef4557d0dcda50d6fa7f4da49902caec1f1752
Author: Christian Grothoff <grothoff@gnunet.org>
AuthorDate: Mon Dec 18 15:55:03 2023 +0800

    KYC process illustration
---
 kyc-process.pdf           | Bin 0 -> 24633 bytes
 kyc-process.png           | Bin 0 -> 44435 bytes
 kyc-process.tex           |  58 ++++++++++++++++++++++++++++++++++++++++++++++
 taler-exchange-manual.rst |   9 +++++++
 4 files changed, 67 insertions(+)

diff --git a/kyc-process.pdf b/kyc-process.pdf
new file mode 100644
index 00000000..8b178c02
Binary files /dev/null and b/kyc-process.pdf differ
diff --git a/kyc-process.png b/kyc-process.png
new file mode 100644
index 00000000..563418b1
Binary files /dev/null and b/kyc-process.png differ
diff --git a/kyc-process.tex b/kyc-process.tex
new file mode 100644
index 00000000..c10dd8d9
--- /dev/null
+++ b/kyc-process.tex
@@ -0,0 +1,58 @@
+\documentclass[fleqn]{article}
+\usepackage{amsmath}
+\usepackage{multimedia}
+\usepackage[utf8]{inputenc}
+\usepackage{framed,color,ragged2e}
+\usepackage[absolute,overlay]{textpos}
+\usepackage{xcolor}
+\usepackage{relsize}
+\usepackage{graphicx}
+\usepackage{tikz,eurosym,calc}
+\usetikzlibrary{tikzmark}
+\usetikzlibrary{shapes,arrows,arrows.meta}
+\usetikzlibrary{positioning,fit,patterns}
+\usetikzlibrary{calc}
+\usepackage{pgf-umlsd}
+\usepackage{relsize}
+
+\pagestyle{empty}
+\begin{document}
+
+\begin{sequencediagram}
+    \newinst{customer}{Customer}
+    \newinst[4]{ex}{Exchange}
+    \newinst[4]{kyc}{KYC Provider}
+    \postlevel
+    \mess[0]{customer}{POST: payment request}{ex}
+    \mess[0]{ex}{POST: initiate KYC}{kyc}
+    \mess[0]{kyc}{KYC-Start-URL}{ex}
+    \mess[0]{ex}{KYC-Start-URL}{customer}
+    \postlevel
+    \mess[0]{customer}{GET: KYC-Start-URL}{kyc}
+    \mess[0]{kyc}{KYC Web Form}{customer}
+    \mess[0]{customer}{POST: KYC data}{kyc}
+    \mess[0]{kyc}{redirect URL or pending}{customer}
+    \postlevel
+    \begin{sdblock}{alternative}{}
+    \mess[0]{customer}{GET: redirect URL}{ex}
+    \mess[0]{ex}{Thanks!}{customer}
+    \end{sdblock}
+    \prelevel
+    \prelevel
+    \prelevel
+    \prelevel
+    \prelevel
+    \begin{sdblock}{alternative}{}
+      \mess[0]{kyc}{Async validation finished Webhook}{ex}
+      \mess[0]{ex}{Thanks!}{kyc}
+    \end{sdblock}
+    \postlevel
+    \mess[0]{ex}{GET: KYC status?}{kyc}
+    \mess[0]{kyc}{KYC data}{ex}
+    \mess[0]{customer}{POST: payment request}{ex}
+    \mess[0]{ex}{normal response}{customer}
+\end{sequencediagram}
+
+\end{document}
+
+    
diff --git a/taler-exchange-manual.rst b/taler-exchange-manual.rst
index f663a63c..72a4418f 100644
--- a/taler-exchange-manual.rst
+++ b/taler-exchange-manual.rst
@@ -1308,6 +1308,15 @@ Taler permits an exchange to require KYC data under the 
following circumstances:
   * Merchant receives money over a threshold
   * Reserve is "opened" for invoicing or rewards (**planned feature**)
 
+Any of the above requests can trigger the KYC process,
+which can be illustrated as follows:
+
+.. image:: kyc-process.png
+
+At the end of the KYC process, the wallet re-tries the
+original request, and assuming KYC was successful, the
+request should then succeed.
+
 
 Taler KYC Terminology
 ---------------------

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