commit 7bdff12a38e5276dd5438013337fd2702a56597e
parent 8c15fb22511d8d536190aaddb720a8de82b3a8a3
Author: Christian Grothoff <grothoff@gnunet.org>
Date: Sun, 17 Mar 2024 12:17:15 +0100
update DD23 requirements
Diffstat:
1 file changed, 17 insertions(+), 0 deletions(-)
diff --git a/design-documents/023-taler-kyc.rst b/design-documents/023-taler-kyc.rst
@@ -49,9 +49,11 @@ There are many different possible KYC/AML flows:
* In-person validation by AML staff
* Validation involving local authorities and post-office
* Online validation
+
* Forms to be supplied by user
* Interactive video
* Documents to be supplied
+
* Forms to be filled by AML staff
Additionally, the process is dynamic and conditional upon various decisions:
@@ -89,6 +91,21 @@ disclosed).
Proposed Solution
=================
+We allow certain **conditions** to trigger a single specific **measures**.
+For the different measures, we define:
+
+* Who has to do something (AML staff, user, nobody)
+* The specific operational mode (normal, held on staff, held on user, frozen)
+ the account is to transition to
+* What to show to the user (normal, information required, pending, etc.)
+* For a user:
+
+ * Web page template with instructions to render
+ * The check to run (if any) and measures on failure
+ * An external helper to run on success to determine the next measure
+ based on data provided in the measure
+
+
Terminology
^^^^^^^^^^^
