taler-docs

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

commit 37eaa7d811086e6929b977f3d49a6057acac64c2
parent f0129a27580fd611d8ddc4f1c59e08b19c912ce6
Author: Florian Dold <florian@dold.me>
Date:   Fri, 14 Mar 2025 23:51:11 +0100

tops notes

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

diff --git a/deployments/tops.rst b/deployments/tops.rst @@ -11,6 +11,8 @@ Definitions / Glossary * VQF: Verein für Qualitätssicherung im Finanzwesen, self-regulatory organization that Taler Operations AG is a member of and thus needs to stick to their rules +* TmeR: Transaktion mit erhöhtem Risiko +* GmeR: Geschäftsbeziehung m.e.R. Regulatory Requirements Introduction ------------------------------------ @@ -84,6 +86,8 @@ Monitoring a Business Relationship as negative press reports, unusual transactions and activities, etc. FIXME: Further define AML officer vs AML advisor. +advisor/Berater: Bankberater, ro +AML officer: official AML officer, rw Terminating a Business Relationship ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ @@ -134,7 +138,11 @@ PIN Letter FIXME: Clarify the following points: * how is the PIN letter generated? How is the PIN generated/stored? + * Challenger generates PIN letter * What exactly are the contents? + * asking to send certified copies of certain documents + +important point: after / when sending PIN letter, specify which documents are still needed AML/KYC Forms ------------- @@ -292,9 +300,11 @@ to document the risk profile of a customer. RISK_CLASIFICATION_LEVEL :: 'WITH' | 'WITHOUT' RISK_CLASIFICATION_ACCEPTANCE_DATE :: Date // FIXME: We need to define our own risk criteria here + // => Refine existing one // ... // FIXME: We need to define our own criteria for // monitoring of high-risk transactions. + // => Fixed, not per customer vqf_902_5 ^^^^^^^^^ @@ -339,6 +349,8 @@ vqf_902_9 FIXME: Is it really okay for the AML officer to fill this out? The original form requires a signature from the customer. +=> For officer, require PDF to be attached + **Purpose:** Establish the identity of the beneficial owner. **Attributes:** @@ -507,8 +519,13 @@ Open Questions entity and the beneficial owner? Clarify! * How do we deal with the "Aktennotiz"? Is that a property? + => Usually as Attribute, but we could also have a property + for notes about the account. + => Modeled as a form filled out only by the AML officer * Do we need a form to upload arbitrary PDF documents (also as the AML officer)? What other fields does this form need? + => Aktennotiz or Besondere Abklärung * When do we need VQF document 902.14 ("Besondere Abklärung")? + => On demand / after alerting