taler-docs

commit c7ed711f741d80fad556c7edce01e008665ace86
parent 6128cfaf346480621be80da963a60e56b9db0988
Author: Florian Dold <florian@dold.me>
Date:   Tue, 18 Mar 2025 14:05:44 +0100

tops

Diffstat:
M
deployments/tops.rst
 | 
15
+++++++++++----

1 file changed, 11 insertions(+), 4 deletions(-)
diff --git a/deployments/tops.rst b/deployments/tops.rst
@@ -1006,12 +1006,13 @@ vqf_902_9
 
 **Filled out by:** AML officer or customer
 
-FIXME: Is it really okay for the AML officer to fill this out?
-The original form requires a signature from the customer.
+**Purpose:** Establish the identity of the beneficial owner.
 
-=> For officer, require PDF to be attached
+**Differences from VQF form 902.9:**
 
-**Purpose:** Establish the identity of the beneficial owner.
+* The VQF form can only be filled out by the customer. We also
+  allow the AML officer to fill out this form, but then require
+  an attached version signed by the customer.
 
 **Attributes:**
 
@@ -1490,6 +1491,12 @@ Open Questions
   
   * Why is there a counter for failed investigations according to one, but not the other?
 
+* Do we use ``Boolean`` attributes or always ``'YES' | 'NO'`` to be extensible
+  in the future?
+
+* General forms question: Are attributes *first* stored and *then* validated or the
+  other way around? If first stored: What if the AML program fails to run?
+
 FAQ
 ---