taler-docs

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

commit 2898af2abf088209361c92fd91e806e05bf612a9
parent 8d375620a6001120ac4f0e9dd924967900314619
Author: Christian Grothoff <christian@grothoff.org>
Date:   Tue,  4 Nov 2025 16:10:59 +0100

fix-up reporting requirements

Diffstat:
Mcore/api-auditor.rst | 11++++++++---
Mdeployments/tops.rst | 16++++++++--------
2 files changed, 16 insertions(+), 11 deletions(-)

diff --git a/core/api-auditor.rst b/core/api-auditor.rst @@ -751,9 +751,12 @@ properly. This endpoint is still experimental. The endpoint will be further developed as needed. +Early Aggregations +------------------ .. _early-aggregation-list: + This endpoint returns cases in which wire transfers are encountered before their justifications. This can be harmless, if the justifications appear shortly afterwards. @@ -815,6 +818,8 @@ justifications. This can be harmless, if the justifications appear shortly after +Pending Deposits +---------------- .. _pending-deposits-list: @@ -864,15 +869,15 @@ This can be harmless, if the wire transfers appear shortly afterwards. // Row identifier in the exchange's batch deposit table batch_deposit_serial_id : Integer; + // Amount that was aggregated early. + total_amount : Amount; + // Hash of the bank account that should have received the funds. h_wire : HashCode; // When was the deadline for the transfer. deadline : Timestamp; - // Amount that was aggregated early. - total_amount : Amount; - // True if this diagnostic was suppressed. suppressed : boolean; diff --git a/deployments/tops.rst b/deployments/tops.rst @@ -358,7 +358,7 @@ Wallet User: Onboarding and Withdrawal that the user has to complete a KYC process for the withdrawal, it notifies the user. 4. User follows instructions to send money to the TOPS exchange -5. The wallet waits until the exchange knows about the +5. The wallet waits until the exchange knows about the user's wire transfer. 6. The user's wallet checks with the exchange whether the withdrawal would cross the balance threshold. The key/identifier for is the wallet ID for @@ -576,7 +576,7 @@ The following subsections define the contents of the forms. The corresponding field names are registered via `GANA <https://git.taler.net/gana.git/tree/gnu-taler-form-attributes>`_. The the UI for the forms is defined in `taler-typescript-core <https://git.taler.net/taler-typescript-core.git/tree/packages/web-util/src/forms/gana>`_ -When the customer or officer submit the information throught the client software it must +When the customer or officer submit the information throught the client software it must include the fields FORM_ID and FORM_VERSION attributed as defined in GANA. @@ -2148,12 +2148,12 @@ VQF requires a list of all open and closed GwG files. To satisfy this requirement, we need a *table* of all AML accounts with the following colums (see VQF 902.8): -* File number (for us, probably the payto hash sufficies, otherwise we need to take some row ID) -* Contracting party (internal alias is also okay, but we don't have an internal alias anyway) -* Notes -* PEP status (yes/no) -* Creation date -* Closing date +* File number (should take some row ID) +* Customer (internal designation is also okay); use payto:// data +* Comments +* Increased risk business relationship (yes/no) +* Acquisition date +* Exit date Event Reporting (VQF) ^^^^^^^^^^^^^^^^^^^^^