commit 3626faf5e7b37ff564b5723f2ff6bb51cbbeea92
parent cef627216591ed8da7f4b21279019b7306bf390b
Author: Christian Grothoff <christian@grothoff.org>
Date: Sat, 27 Jun 2026 22:56:17 +0200
doc fixes
Diffstat:
2 files changed, 14 insertions(+), 1 deletion(-)
diff --git a/core/exchange/post-kyc-upload-ID.rst b/core/exchange/post-kyc-upload-ID.rst
@@ -35,7 +35,7 @@
The upload conflicts with a previous upload.
This response comes with a standard `ErrorDetail` response with
a code of ``TALER_EC_EXCHANGE_KYC_FORM_ALREADY_UPLOADED`` or
- ``TALER_EC_EXCHANGE_INVALID_FORM_SUBMITTED``.
+ ``TALER_EC_EXCHANGE_KYC_INVALID_FORM_SUBMITTED``.
:http:statuscode:`413 Request Entity Too Large`:
The body is too large.
:http:statuscode:`500 Internal Server Error`:
diff --git a/taler-merchant-manual.rst b/taler-merchant-manual.rst
@@ -160,6 +160,19 @@ merchant's bank account with the orders that are being settled.
This documentation exclusively uses the term *account* for the bank
accounts of a merchant or shop that may be associated with an instance.
+.. note::
+
+ When an instance has **more than one** bank account configured, there is
+ no notion of a "default" or "primary" account: *any* of the configured
+ accounts may receive the funds for a given transaction, and which one is
+ used is **not predictable from the merchant UI**. The account is chosen
+ per transaction based on what the settling exchange supports — i.e. the
+ wire method and account restrictions of that exchange. For example, if an
+ instance offers both a CH-IBAN and a DE-IBAN account, one exchange may
+ settle to the CH account while another settles to the DE account; adding an
+ ``x-taler-bank`` account introduces yet another possibility. If you need
+ funds to arrive in a specific account, configure only that account.
+
Inventory
---------
