taler-docs

commit 8c6a4d4ef0818af0b6f179bf54f2fee325199331
parent 602687cdc761f53ba7104ea5858ab25aa4ccf577
Author: Christian Grothoff <christian@grothoff.org>
Date:   Thu, 19 Feb 2026 19:37:21 +0100

specify extra-wire-subject

Diffstat:
M
core/exchange/get-config.rst
 | 
2
+-
M
core/exchange/post-batch-deposit.rst
 | 
13
+++++++++++++

2 files changed, 14 insertions(+), 1 deletion(-)
diff --git a/core/exchange/get-config.rst b/core/exchange/get-config.rst
@@ -4,7 +4,7 @@
   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 **v31**.
+  This specification corresponds to ``current`` protocol being **v32**.
 
   **Response:**
 
diff --git a/core/exchange/post-batch-deposit.rst b/core/exchange/post-batch-deposit.rst
@@ -83,6 +83,19 @@
       // merchant for refund requests.
       merchant_pub: EddsaPublicKey;
 
+      // Additional text to include in the wire transfer subject when
+      // settling the payment. Note that the merchant MUST use this
+      // consistently for the same ``merchant_pub`` and ``merchant_payto_uri``
+      // as during aggregation *any* of these values may be selected
+      // for the actual aggregated wire transfer. If a merchant wants
+      // to use different ``extra_subject`` values for the same IBAN,
+      // it should thus create multiple instances (with different
+      // ``merchant_pub`` values). When changing the ``extra_subject``,
+      // the change may thus not be immediately reflected in the
+      // settlements.
+      // Since **v32**.
+      extra_wire_subject?: string;
+
       // Date until which the merchant can issue a refund to the customer via the
       // exchange, to be omitted if refunds are not allowed.
       //