taler-docs

commit ff649e17cb2f9d60fa451b23df7762a7e196fde3
parent c90828f6e4f7c617e89ddfb4ffb4dd007f1fe0d4
Author: Christian Grothoff <christian@grothoff.org>
Date:   Wed, 11 Jun 2025 22:31:57 +0200

spec new exchange GET /aml//transfers-kycauth endpoint for #10031; new protocol version is v29

Diffstat:
M
core/api-exchange.rst
 | 
11
+++++++----

1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/core/api-exchange.rst b/core/api-exchange.rst
@@ -60,7 +60,7 @@ possibly by using HTTPS.
   as well as the list of possible KYC requirements.  This endpoint is largely
   for the SPA for AML officers. Merchants should use ``/keys`` which also
   contains the protocol version and currency.
-  This specification corresponds to ``current`` protocol being **v28**.
+  This specification corresponds to ``current`` protocol being **v29**.
 
   **Response:**
 
@@ -5830,16 +5830,19 @@ and freeze or unfreeze accounts suspected of money laundering.
 
 .. http:get:: /aml/$OFFICER_PUB/transfers-credit
 .. http:get:: /aml/$OFFICER_PUB/transfers-debit
+.. http:get:: /aml/$OFFICER_PUB/transfers-kycauth
 
   Obtain exchange's bank account wire transfer history data. Shows effective
-  incoming wire transfers or (credit) effective outgoing (aggregated, closed)
-  wire transfers (debit).  Note that KYC auth wire transfers, bounced incoming
+  incoming wire transfers (credit), incoming wire transfers for KYC
+  authorization (kycauth), or effective outgoing (aggregated, closed)
+  wire transfers (debit).  Note that bounced incoming
   wire transfers and drain outgoing wire transfers requests are excluded (as
   they are not relevant for AML processes and would just distract). The
   wire transfer subject is also not given as in all cases it will just
   be some cryptographic data that is meaningless for humans.
 
-  This endpoint was introduced in protocol **v25**.
+  The first two endpoints were introduced in protocol **v25**.
+  ``transfers-kycauth`` was added in protocol **v29**.
 
   **Request:**