taler-docs

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

commit 81b308749881012a5e665711ea18dd3e03011028
parent 23d76b7c93c478a0958308967ffcf2801984e0bc
Author: Christian Grothoff <christian@grothoff.org>
Date:   Sun, 30 Mar 2025 10:09:44 +0200

clarify how investigations are started

Diffstat:
Mdeployments/tops.rst | 7+++++--
1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/deployments/tops.rst b/deployments/tops.rst @@ -258,8 +258,11 @@ Properties * ``NONE`` / undefined: No MROS reporting for that account * ``INVESTIGATION_PENDING``: Pending investigation. The AML officer should - submit ``vqf_902_14`` to conclude investigation. - FIXME: Also have a form to *start* investigation? + submit ``vqf_902_14`` to conclude investigation. Usually the property + would be set by the sanction list tool or some AML program that detects + an account crossing a threshold or an SQL trigger doing transaction + monitoring. The ``vqf_902_14`` form can *also* be used to *start* an + investigation. * ``INVESTIGATION_COMPLETED_WITHOUT_SUSPICION``: Completed according to Art. 6 GwG * ``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)