[taler-docs] branch master updated: document cash-out (#8174)

[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 eb0bc54f document cash-out (#8174)
eb0bc54f is described below

commit eb0bc54fe15afd548ab1617be37616ac826b9c7a
Author: Christian Grothoff <christian@grothoff.org>
AuthorDate: Sun Feb 4 11:36:20 2024 +0100

    document cash-out (#8174)
---
 libeufin/regional-manual.rst | 56 ++++++++++++++++++++++++++++++++++----------
 1 file changed, 44 insertions(+), 12 deletions(-)

diff --git a/libeufin/regional-manual.rst b/libeufin/regional-manual.rst
index 0a13f997..3a00a011 100644
--- a/libeufin/regional-manual.rst
+++ b/libeufin/regional-manual.rst
@@ -294,26 +294,58 @@ dialogue.
 Cash-In
 -------
 
-After starting the withdraw process and specifying the desired amount, the 
wallet
-should show you the details of the fiat wire transfer that must be made for 
the cash
-in to be completed.  Once the money has arrived at the fiat bank account, 
Nexus will
+Next, start the withdraw process in the Taler wallet for the respective
+currency and specify the desired amount.  The wallet will then show you the
+details of the fiat wire transfer that must be made for the cash-in to be
+completed.  Once the money has arrived at the fiat bank account, Nexus will
 obtain the transaction data and the regional currency bank will create the
-corresponding amount in regional currency, crediting the GNU Taler exchange 
account.
-In turn, the exchange will issue the respective amount to your wallet.
+corresponding amount in regional currency, crediting the GNU Taler exchange
+account.  In turn, the exchange will issue the respective amount to your
+wallet.
+
+.. note::
+
+   Cash-in operations may be subject to conversion rates, conversion fees and
+   minimum amounts to be transferred.
 
-.. FIXME: bad english below
 
-For testing, you should be able to *deposit* regional currency directly
-into your LibEuFin Bank account from the Taler wallet.  Note: the wallet 
relies on the
-exchange to perform such deposit.  So once the exchange has credited the 
regional
-currency account to your account and assuming the cash out rules are 
satisfied, you
-should then be able to start a cash out operation.
+Making payments
+---------------
+
+For testing, you should be able to *deposit* regional currency directly into
+your regional currency libeufin-bank account directly from the Taler wallet.
+For this, you primarily need to know your bank account details (which should
+be accessible by clicking on your name in the bank Web site after logging in).
+
+.. note::
+
+  There may be a short delay between the wallet making the deposit and
+  the exchange crediting your bank account. This is because the wallet
+  uses a small wire transfer delay by default when initiating a deposit
+  into a bank account.
+
+For production, it is more common for a shop to configure a :ref:`Taler
+merchant backend <taler-merchant-backend-operator-manual>` or at least use an
+instance within such a setup. To configure an instance, you primarily need
+again the bank account details to :ref:`setup instance bank accounts
+<instance-bank-account>`.
 
 
 Cash-Out
 --------
 
-.. FIXME: #8174
+Regional currency accounts that have a positive balance could be eligible for
+cash-out.  Cash-out operations may again be restricted by the regional
+currency operator and will *only* be made to the respective pre-configured
+fiat currency bank account.  To cash-out, simply log into your regional
+currency account, select cash-out, specify the desired amount and pass the
+second-factor authorization challenge by entering the TAN you receive at the
+registered e-mail address or mobile phone number.
+
+.. note::
+
+   Cash-out operations may be subject to conversion rates, conversion fees and
+   minimum amounts to be transferred.
 
 
 Alternative Podman-based Deployment

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