taler-docs

commit 91083aa92e79a57993696778d453335d056499ed
parent 5cec148323aa37293ca0773802a2fc340c309d8b
Author: Christian Grothoff <christian@grothoff.org>
Date:   Sat, 25 May 2024 19:30:29 +0200

clarifications

Diffstat:
M
core/api-exchange.rst
 | 
4
+++-
M
taler-exchange-manual.rst
 | 
6
+++++-

2 files changed, 8 insertions(+), 2 deletions(-)
diff --git a/core/api-exchange.rst b/core/api-exchange.rst
@@ -5249,9 +5249,11 @@ regulatory compliance.
     The exchange is not configured to perform KYC and thus
     the legal requirements are already satisfied.
   :http:statuscode:`403 Forbidden`:
-    The provided signature is not acceptable for the requirement row.
+    The provided signature is not acceptable for the requirement row.  The (base32) encoding of the public key we expect signatures to be made with is returned in the ``detail`` field.
   :http:statuscode:`404 Not found`:
     The requirement row is unknown.
+  :http:statuscode:`409 Conflict`:
+    The bank account is not (yet) associated with a public key. The account owner must do a wire transfer to the exchange with the account public key in the wire transfer subject to enable authentication.
 
   **Details:**
 
diff --git a/taler-exchange-manual.rst b/taler-exchange-manual.rst
@@ -1885,7 +1885,7 @@ a decision.
   measures dynamically, usually by selecting checks, an AML program, and
   providing context.
 
-  
+
 
 Setup Linting
 =============
@@ -2079,6 +2079,10 @@ table is of type `LegitimizationMeasures`:
     // True if the client is expected to eventually satisfy all requirements.
     // Default (if missing) is false.
     is_and_combinator?: boolean;
+
+    // True if the requested operation is categorically forbidden.
+    // The measures array will be empty in this case.
+    verboten: boolean;
   }