[taler-docs] branch master updated: explain DEFAULT_EXCHANGE

[gnunet]

This is an automated email from the git hooks/post-receive script.

grothoff pushed a commit to branch master
in repository docs.

The following commit(s) were added to refs/heads/master by this push:
     new 93327c75 explain DEFAULT_EXCHANGE
93327c75 is described below

commit 93327c7583bd4d16ee66a2ef2a471e1a7f7d92ea
Author: Christian Grothoff <christian@grothoff.org>
AuthorDate: Sun Feb 4 10:52:25 2024 +0100

    explain DEFAULT_EXCHANGE
---
 libeufin/bank-manual.rst | 24 +++++++++++++++++++++++-
 1 file changed, 23 insertions(+), 1 deletion(-)

diff --git a/libeufin/bank-manual.rst b/libeufin/bank-manual.rst
index f8f2dd28..c557aa60 100644
--- a/libeufin/bank-manual.rst
+++ b/libeufin/bank-manual.rst
@@ -253,4 +253,26 @@ up the exchange account. See the section on 
:ref:`conversion setup <regional-con
 Withdrawing e-cash to a Taler wallet
 ====================================
 
-TODO.
+.. note::
+
+   This step is fully automated if you use the :ref:`guided automated setup 
<automated-regional-currency-setup>`.
+
+Users can withdraw digital cash from their bank account starting from their
+online banking as implemented by the libeufin-bank. However, in this scenario,
+the Taler wallet may not already know about an exchange that works with the
+respective currency.  Thus, the protocol includes the possibility of the bank
+*recommending* an exchange service to the wallet, thus providing a sane
+default for the wallet to suggest to the user.  To do so, the base URL of the
+exchange API must be specified in the libeufin-bank configuration:
+
+.. code-block:: ini
+
+  [libeufin-bank]
+  DEFAULT_EXCHANGE=${PROTO}://exchange.${DOMAIN_NAME}
+
+After changing this value, the libeufin-bank service needs to be restarted
+to make the change effective.
+
+.. note::
+
+  The user may change the default exchange from within the wallet, assuming 
they know of an alternative exchanges for the currency.

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.