taler-docs

Documentation for GNU Taler components, APIs and protocols
Log | Files | Refs | README | LICENSE

commit 2d7c598e0095efcc599959f74d82a3d324b2b891
parent 9b305c33502df68b9edaa26d1670ac742cb8e36f
Author: Christian Grothoff <christian@grothoff.org>
Date:   Sun, 30 Mar 2025 10:43:12 +0200

elaborate on properties and sanction lists

Diffstat:
Mdeployments/tops.rst | 24++++++++++++++++++++++++
1 file changed, 24 insertions(+), 0 deletions(-)

diff --git a/deployments/tops.rst b/deployments/tops.rst @@ -211,6 +211,8 @@ profiles: Properties ---------- +FIXME-#9678: we should put these into GANA. + * ``FILE_NOTE :: Text``: * Current note on the GWG file. @@ -268,6 +270,28 @@ Properties * ``REPORTED_SUSPICION_SIMPLE``: Reported under Art. 305 StGB (German "einfacher Verdacht", simple suspicion) * ``REPORTED_SUSPICION_SUBSTANTIATED``: Reported under Art. 9 GwG (German "begründeter Verdacht", substantiated suspicion) +* ``AML_INVESTIGATION_TRIGGER :: Text`` + + * Informal reason why the AML investigation was triggered; + examples include suspicious transaction or (automated) + sanction list match + +* ``SANCTION_LIST_BEST_MATCH :: Text`` + + * Identifies the sanction list entry that the account matched against + (best match, does not mean it was a good match) + +* ``SANCTION_LIST_RATING :: float`` + + * [0,1] score for how good the sanction list match was + (0: none, 1: perfect match) + +* ``SANCTION_LIST_CONFIDENCE :: float`` + + * [0,1] score for how much supporting data we had for + the sanction list match (0: none, 1: all fields available) + + Events ------