taler-docs

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

commit 66fcd69b1e80c4fdb034668ced6175c97aff070e
parent ab1db7765d2367df84b3158c50979d02d123c7e8
Author: Florian Dold <florian@dold.me>
Date:   Wed, 19 Mar 2025 16:48:35 +0100

TOPS WIP

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

diff --git a/deployments/tops.rst b/deployments/tops.rst @@ -256,10 +256,12 @@ Properties * Values: * ``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? + * ``INVESTIGATION_COMPLETED``: 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) - * ``INVESTIGATION_FAILED``: Failed according to Art. 6 GwG - * ``INVESTIGATION_COMPLETED``: Completed according to Art. 6 GwG Events ------ @@ -293,8 +295,8 @@ MROS Reporting (see ``AML_MROS_STATE`` property): * ``ACCOUNT_MROS_REPORTED_SUSPICION_SIMPLE`` * ``ACCOUNT_MROS_REPORTED_SUSPICION_SUBSTANTIATED`` +* ``ACCOUNT_INVESTIGATION_STARTED`` * ``ACCOUNT_INVESTIGATION_COMPLETED`` -* ``ACCOUNT_INVESTIGATION_FAILED`` PIN Letter @@ -310,9 +312,8 @@ The KYC SPA should also specify which documents are still needed. Implementation notes: * The letter is sent and generated via ``challenger`` -* FIXME: How do we keep track of required documents? - - if partial document collection arrives: update context (later!) +* We keep track of required documents via an ``INFO`` measure, + where the context is updated based on documents still required. AML/KYC Forms