commit 9b305c33502df68b9edaa26d1670ac742cb8e36f
parent c934046d422da48fe21e484909e783f258d6bd44
Author: Christian Grothoff <christian@grothoff.org>
Date: Sun, 30 Mar 2025 10:35:53 +0200
elaborate on sanction lists
Diffstat:
1 file changed, 21 insertions(+), 3 deletions(-)
diff --git a/deployments/tops.rst b/deployments/tops.rst
@@ -1890,9 +1890,27 @@ Sanction Lists
When a new customer is onboarded, they are checked against a sanction list.
-FIXME: How is this refleced in the forms? Or is it a property?
-
-https://bugs.taler.net/n/9053
+Three properties are set:
+
+* ``SANCTION_LIST_BEST_MATCH`` identifies the position of the entry in
+ the sanctions list that matches the new customer the best
+* ``SANCTION_LIST_RATING`` is set to a numeric score ``[0,1]`` that
+ identifies how well the available data matches (with 1.0 being a perfect
+ match)
+* ``SANCTION_LIST_CONFIDENCE`` is set to a numeric score ``[0,1]`` that
+ indicates how confident we are that the rating is accurate, with 0
+ indicating no data available, and 1 indicating that all possible
+ fields could be evaluated
+* ``AML_INVESTIGATION_STATE`` is set to ``INVESTIGATION_PENDING``
+ if the rating and confidence are sufficiently high
+* ``AML_INVESTIGATION_TRIGGER`` is set to ``SANCTION_LIST_MATCH``
+
+Finally, sanction list hits trigger one of two possible events:
+
+* ``sanction-list-hit-account-frozen`` is set if the hit was so clear
+ that the system immediately froze the account
+* ``sanction-list-hit-partial-account-investigated`` is set if the hit
+ requires the account to be investigated
Implementation Gaps