[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[taler-docs] branch master updated: major updates to taler-merchant-manu
|
From: |
gnunet |
|
Subject: |
[taler-docs] branch master updated: major updates to taler-merchant-manual |
|
Date: |
Wed, 31 Jan 2024 21:16:13 +0100 |
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 60b07109 major updates to taler-merchant-manual
60b07109 is described below
commit 60b071096b1b26da6b2aa5810ae906a27467bcce
Author: Christian Grothoff <christian@grothoff.org>
AuthorDate: Wed Jan 31 21:16:08 2024 +0100
major updates to taler-merchant-manual
---
design-documents/039-taler-browser-integration.rst | 10 +-
libeufin/bank-manual.rst | 21 ++
libeufin/index.rst | 20 ++
libeufin/nexus-manual.rst | 21 ++
libeufin/regional-manual.rst | 35 ++-
taler-merchant-manual.rst | 245 ++++++++++-----------
taler-merchant-pos-terminal.rst | 6 +-
taler-wallet.rst | 42 ++++
8 files changed, 257 insertions(+), 143 deletions(-)
diff --git a/design-documents/039-taler-browser-integration.rst
b/design-documents/039-taler-browser-integration.rst
index b7cd346c..980f3f25 100644
--- a/design-documents/039-taler-browser-integration.rst
+++ b/design-documents/039-taler-browser-integration.rst
@@ -112,7 +112,7 @@ To enable additional communication features between a
website and the GNU Taler
include the following meta tag:
.. code::
-
+
<meta name="taler-support" content="$features">
where ``$features`` is a comma-separated list of features.
@@ -129,8 +129,8 @@ Caveats and Comments
^^^^^^^^^^^^^^^^^^^^
* Anchor tag hijacking does not work in all use-cases, for example when a
navigation
-to a ``taler://`` URI is initiated programmatically or by pasting
-the URI in the browser's address bar.
+ to a ``taler://`` URI is initiated programmatically or by pasting
+ the URI in the browser's address bar.
* The ``window.taler`` API injection may break some websites
(https://github.com/brave/browser-laptop/issues/13711).
@@ -148,8 +148,8 @@ the URI in the browser's address bar.
* The execution of the websites onclick handler if no Taler Wallet
webextension is installed
* Triggering the webextension wallet to handle the ``taler://`` URI.
-* Future ``window.taler`` injection should be based on user preferences on
- sites where the user has explicitly accepted to disclose that is owner of a
+* Future ``window.taler`` injection should be based on user preferences on
+ sites where the user has explicitly accepted to disclose that is owner of a
Taler wallet.
Other Alternatives
diff --git a/libeufin/bank-manual.rst b/libeufin/bank-manual.rst
index af977492..a61c7429 100644
--- a/libeufin/bank-manual.rst
+++ b/libeufin/bank-manual.rst
@@ -1,5 +1,26 @@
+..
+ This file is part of GNU TALER.
+ Copyright (C) 2014-2023 Taler Systems SA
+
+ TALER is free software; you can redistribute it and/or modify it under the
+ terms of the GNU Affero General Public License as published by the Free
Software
+ Foundation; either version 2.1, or (at your option) any later version.
+
+ TALER is distributed in the hope that it will be useful, but WITHOUT ANY
+ WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR
+ A PARTICULAR PURPOSE. See the GNU Affero General Public License for more
details.
+
+ You should have received a copy of the GNU Affero General Public License
along with
+ TALER; see the file COPYING. If not, see <http://www.gnu.org/licenses/>
+
+ @author Florian Dold
+ @author Marcello Stanisci
+ @author Christian Grothoff
+
.. target audience: operator, developer
+.. _libeufin-bank:
+
Bank Setup Manual
#################
diff --git a/libeufin/index.rst b/libeufin/index.rst
index 042388dc..5e4ca054 100644
--- a/libeufin/index.rst
+++ b/libeufin/index.rst
@@ -1,3 +1,23 @@
+..
+ This file is part of GNU TALER.
+ Copyright (C) 2014-2023 Taler Systems SA
+
+ TALER is free software; you can redistribute it and/or modify it under the
+ terms of the GNU Affero General Public License as published by the Free
Software
+ Foundation; either version 2.1, or (at your option) any later version.
+
+ TALER is distributed in the hope that it will be useful, but WITHOUT ANY
+ WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR
+ A PARTICULAR PURPOSE. See the GNU Affero General Public License for more
details.
+
+ You should have received a copy of the GNU Affero General Public License
along with
+ TALER; see the file COPYING. If not, see <http://www.gnu.org/licenses/>
+
+ @author Florian Dold
+ @author Marcello Stanisci
+ @author Christian Grothoff
+
+
LibEuFin
########
diff --git a/libeufin/nexus-manual.rst b/libeufin/nexus-manual.rst
index 0fab068b..c4ed2cbc 100644
--- a/libeufin/nexus-manual.rst
+++ b/libeufin/nexus-manual.rst
@@ -1,5 +1,26 @@
+..
+ This file is part of GNU TALER.
+ Copyright (C) 2014-2023 Taler Systems SA
+
+ TALER is free software; you can redistribute it and/or modify it under the
+ terms of the GNU Affero General Public License as published by the Free
Software
+ Foundation; either version 2.1, or (at your option) any later version.
+
+ TALER is distributed in the hope that it will be useful, but WITHOUT ANY
+ WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR
+ A PARTICULAR PURPOSE. See the GNU Affero General Public License for more
details.
+
+ You should have received a copy of the GNU Affero General Public License
along with
+ TALER; see the file COPYING. If not, see <http://www.gnu.org/licenses/>
+
+ @author Florian Dold
+ @author Marcello Stanisci
+ @author Christian Grothoff
+
.. target audience: operator, developer
+.. _libeufin-nexus:
+
Nexus Manual
############
diff --git a/libeufin/regional-manual.rst b/libeufin/regional-manual.rst
index 441f6599..ca355a49 100644
--- a/libeufin/regional-manual.rst
+++ b/libeufin/regional-manual.rst
@@ -1,3 +1,23 @@
+..
+ This file is part of GNU TALER.
+ Copyright (C) 2014-2023 Taler Systems SA
+
+ TALER is free software; you can redistribute it and/or modify it under the
+ terms of the GNU Affero General Public License as published by the Free
Software
+ Foundation; either version 2.1, or (at your option) any later version.
+
+ TALER is distributed in the hope that it will be useful, but WITHOUT ANY
+ WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR
+ A PARTICULAR PURPOSE. See the GNU Affero General Public License for more
details.
+
+ You should have received a copy of the GNU Affero General Public License
along with
+ TALER; see the file COPYING. If not, see <http://www.gnu.org/licenses/>
+
+ @author Florian Dold
+ @author Marcello Stanisci
+ @author Christian Grothoff
+
+
.. target audience: operator
Regional Currency Setup Manual
@@ -116,9 +136,10 @@ desired setup, in particular:
IP address of the system on which you are running the
installation (before you execute the installer)).
-The information you entered as well as the generated bank admin password will
be stored in a file called ``config/user.conf``.
-Should you run the script in the future (for example, to upgrade the
installation),
-you will not be asked these questions a second time.
+The information you entered as well as the generated bank admin password will
+be stored in a file called ``config/user.conf``. Should you run the script in
+the future (for example, to upgrade the installation), you will not be asked
+these questions a second time.
After answering all of the questions, the actual installation will start. The
scripts will download and configure various packages, which may take some time.
@@ -167,14 +188,14 @@ Enable regional currency conversion
===================================
Prerequisites
--------------
++++++++++++++
This step assumes that you already have a working regional currency bank
and have successfully connected to a backing fiat bank account.
Follow the instructions from :ref:`EBICS setup <regional-ebics-setup>`.
Configuration
--------------
++++++++++++++
Then you have to enable conversion and at least one TAN channel for cashout in
the configuration file.
@@ -204,13 +225,13 @@ Then the following command would start the server with
conversion API enabled :
libeufin-bank serve -c $config_file
Web-based Configuration
------------------------
++++++++++++++++++++++++
Now you should be able to setup conversion rates and ``admin`` debt limit
though the Web
interface of the bank as the ``admin`` user.
Conversion ON!
---------------
+++++++++++++++
The last step is to run Nexus to import incoming bank
transactions (cash in) and to trigger outgoing bank transactions (cash out).
diff --git a/taler-merchant-manual.rst b/taler-merchant-manual.rst
index 072f4ad7..dcf518e7 100644
--- a/taler-merchant-manual.rst
+++ b/taler-merchant-manual.rst
@@ -396,6 +396,28 @@ This chapter describes how to install the GNU Taler
merchant backend.
.. _Generic-instructions:
+Installing the GNU Taler binary packages on Debian
+--------------------------------------------------
+
+.. include:: frags/installing-debian.rst
+
+.. include:: frags/apt-install-taler-merchant.rst
+
+
+Installing the GNU Taler binary packages on Trisquel
+----------------------------------------------------
+
+.. include:: frags/installing-trisquel.rst
+
+
+Installing the GNU Taler binary packages on Ubuntu
+--------------------------------------------------
+
+.. include:: frags/installing-ubuntu.rst
+
+.. include:: frags/apt-install-taler-merchant.rst
+
+
Installing from source
----------------------
@@ -433,30 +455,9 @@ libraries!
.. include:: frags/install-before-check.rst
-Installing the GNU Taler binary packages on Debian
---------------------------------------------------
-
-.. include:: frags/installing-debian.rst
-
-.. include:: frags/apt-install-taler-merchant.rst
-
-
-Installing the GNU Taler binary packages on Trisquel
-----------------------------------------------------
-
-.. include:: frags/installing-trisquel.rst
-
-Installing the GNU Taler binary packages on Ubuntu
---------------------------------------------------
-
-.. include:: frags/installing-ubuntu.rst
-
-.. include:: frags/apt-install-taler-merchant.rst
-
-
-How to configure the merchant’s backend
-=======================================
+How to configure the merchant backend
+=====================================
.. index:: taler.conf
@@ -747,7 +748,7 @@ Launching the backend
.. index:: taler-merchant-httpd
Assuming you have configured everything correctly, you can launch the
-merchant backend as ``$USER`` using
+merchant backend as ``$USER`` using (to provide a trivial example):
.. code-block:: console
@@ -757,12 +758,7 @@ merchant backend as ``$USER`` using
$ taler-merchant-depositcheck &
$ taler-merchant-exchange &
-You only need to run ``taler-merchant-webhook`` if one of the instances is
-configured to trigger web hooks. Similarly, ``taler-merchant-wirewatch`` is
-only required if instances have accounts configured with automatic import of
-wire transfers via a bank wire gateway.
-
-To ensure these processes runs always in the background and also after
+To ensure these processes run always in the background and also after
rebooting, you should use systemd, cron or some other init system of your
operating system to launch the process. You should also periodically re-start
these services to prevent them from exhausing the memory utilization of the
@@ -782,7 +778,6 @@ how to start and stop daemons.
should be able to visit the merchant backend at the respective
HTTP(S) endpoint.
-
If everything worked as expected, the command
.. code-block:: console
@@ -794,7 +789,7 @@ should return some basic configuration status data about
the service.
Please note that your backend might then be globally reachable without
any access control. You can either:
- * Use the ``--auth=$TOKEN`` command-line option to set an access token to be
provided in an ``Authorize: Bearer $TOKEN`` HTTP header. Note that this can be
used at anytime to override access control, but remains only in effect until a
first instance is created or an existing instance authentication setting is
modified.
+ * Use the ``--auth=$TOKEN`` command-line option to **taler-merchant-httpd**
to set an access token to be provided in an ``Authorize: Bearer $TOKEN`` HTTP
header. Note that this can be used at anytime to override access control, but
remains only in effect until a first instance is created or an existing
instance authentication setting is modified.
* Set the ``TALER_MERCHANT_TOKEN`` environment variable to ``$TOKEN`` for
the same effect. This method has the advantage of ``$TOKEN`` not being visible
as a command-line interface to other local users on the same machine.
* Set up an instance with an authentication token before some unauthorized
person has a chance to access the backend. As the backend is useless without
any instance and the chances of remote attackers during the initial
configuration is low, this is probably sufficient for most use-cases. Still,
keep the first two scenarios in mind in case you ever forget your access token!
@@ -809,15 +804,14 @@ and use TLS for improved network privacy, see
:ref:`Secure setup <Secure-setup>`
Instance setup
==============
-First of all, we recommend the use of the single-page administration
-application (SPA) that is served by default at the base URL of the merchant
-backend. You can use it to perform all steps described in this section (and
-more!), using a simple Web interface instead of the ``wget`` commands given
-below.
+We recommend the use of the single-page administration application (SPA) that
+is served by default at the base URL of the merchant backend. You can use it
+to perform all steps described in this section (and more!), using a simple Web
+interface. Alternatively, you can also use the ``wget`` commands given below.
-Regardless of which tool you use, the first step for using the backend
+Regardless of which approach you use, the first step for using the backend
involves the creation of a ``default`` instance. The ``default`` instance can
-also create / delete / configure other instances, similar to the ``root``
+also create, configure or delete other instances, similar to the ``root``
account on UNIX. When no instance exists and ``taler-merchant-httpd`` was
started without the ``--auth`` option, then the backend is reachable without
any access control (unless you configured some in the reverse proxy).
@@ -836,36 +830,29 @@ times, once for each instance.
:ref:`reverse proxy <reverse-proxy-configuration>`.
-
Instance setup with the SPA
---------------------------
-In order to setup a shop, you need a merchant backend to run. The guided
-setup installs and sets one backend up, but the user is required to complete
-the shop configuration via the Web browser.
-
-One fundamental piece of information are the banking details, to allow merchant
-receive payments from the exchange. If you don't have a bank account at the
regional
-bank, contact the administrator and get one. After being able to login to the
new
-bank account, you can see your IBAN by clicking on the ``Welcome, $USERNAME``
message
-in the profile page. The IBAN is shown under the ``Internal IBAN`` box.
+In order to setup an instance, you need the merchant backend to already be
+running, and you must either have the credentials for the "default" instance,
+or no instance must be configured at all yet.
-Next, point your browser to ``$proto://backend.$domain_name/``. You should
-be welcomed by the following merchant backoffice page:
+To start, point your browser to ``$PROTO://backend.$DOMAIN_NAME/``, replacing
+"$PROTO" with "https" or (rarely) "http" and "$DOMAIN_NAME" with your
+organizations DNS domain or subdomain.
-.. image:: screenshots/merchant_first_login.png
+.. note::
-Such page offers to create a merchant profile: fill any required field
(including
-your access token) and click to ``confirm``. It should now be possible to
associate
-the banking details to the profile just created: click to ``Bank account`` at
the
-left of the page. The following page should be shown:
+ The label "backend" here is also just a suggestion, your administrator
+ can in principle choose any name.
-.. image:: screenshots/no_default_account_yet.png
+You should be welcomed by the following merchant backoffice page:
-Click on the blue "+" sign on the top right of the page, and expect the
following
-page to appear:
+.. image:: screenshots/merchant_first_login.png
-.. image:: enter_instance_details.png
+After supplying the required fields, primarily the name of your organization
+and the desired access token, click ``confirm``. You can change the instance
+settings later via the ``Settings`` entry in the menu on the left.
Instance setup without the Web interface
@@ -912,6 +899,7 @@ Endpoints to modify (reconfigure), permanently disable
(while keeping the data)
or purge (deleting all associated data) instances exist as well and are
documented
in the :ref:`Merchant Backend API documentation <merchant-api>`.
+.. _instance-account-setup:
Instance account setup
======================
@@ -922,29 +910,48 @@ operator to tell it where to wire the income from your
sales. Every bank
account has an associated *wire method* which determines how an exchange can
transfer the funds. The most commonly supported wire method is *iban*, which
implies that bank accounts are identified by IBAN numbers and wire transfers
-are to be executed between IBAN accounts.
+are to be executed between IBAN accounts. For regional currency setups, the
+wire method could also be *x-taler-bank*.
+
+.. note::
+
+ When using a regional currency, you need to first create a bank account at
+ the regional bank. You may need to contact the respective administrator who
+ can set one up. After being able to login to the new bank account, you can
+ see your bank account number by clicking on the ``Welcome, $USERNAME``
+ message in the profile page. Next to the bank account number, you can find
+ a convenient button to copy the number to the clipboard.
Not every exchange will support every *wire method*, and if you do not add a
bank account with a wire method that is supported by a particular exchange,
then you will not be able to receive payments via that exchange even if you
configured the merchant backend to trust that exchange.
-The simplest way to configure an account is to use the Web interface which
-has specific forms for different wire methods. Specifying the revenue gateway
-with username and password is optional and discussed below.
+The simplest way to configure an account is to use the Web interface which has
+specific forms for different wire methods. First, select ``Bank account`` at
+the left of the page. The following page should be shown:
+
+.. image:: screenshots/no_default_account_yet.png
+
+Click on the blue "+" sign on the top right of the page to add a new
+bank account. The following page should appear:
-This tutorial is focused on IBAN, so choose ``iban`` as the account type, and
-expect the following page to appear:
+.. image:: screenshots/enter_instance_details.png
+
+First, you should select the wire method, after which the dialog will show you
+additional fields specific to the wire method. For example, if youchoose
+``iban`` as the account type, the following page should appear:
.. image:: screenshots/instance_iban_config.png
+Specifying the revenue gateway with username and password is optional and
+discussed in section :ref:`automatic-settlement-data-import` below.
+
After providing the details and confirming, the shop is ready to generate
orders
and accept payments.
-
-
Detecting Settlement: Manually Adding Transfers
-----------------------------------------------
@@ -962,75 +969,54 @@ information, the merchant backend will inquire with the
exchange which
individual payments were aggregated, check that the total amount is correct,
and will then flag the respective contracts as wired.
+You can manually enter wire transfers under ``Transfers``. However, this is
+tedious, and so if your banking setup supports it, we highly recommend
+using the automatic settlement data import.
+
+.. _automatic-settlement-data-import:
+
Automatic Settlement Data Import
--------------------------------
-To automatically import settlement data, you can provide the merchant backend
-with the address and access credentials of a Taler revenue API for each bank
-account of an instance. The revenue API endpoint will allow the merchant
-backend to observe all incoming wire transfers into your bank account and
-automatically import them into the list of wire transfers.
+To automatically import settlement data, you need to provide the merchant
+backend with the address and access credentials of a
+:ref:`taler-bank-merchant-http-api` for each bank account of an instance. The
+revenue API endpoint will allow the merchant backend to obtain a list of all
+incoming wire transfers into your bank account and automatically import them
+into the list of confirmed wire transfers.
Note that setting up a revenue API endpoint will usually require you to first
-ask your bank for EBICS access and to setup libeufin to provide the revenue
-API endpoint. The taler-bank used by regional currency setups also provides
-a revenue API endpoint at ``$BANK_URL/accounts/$ACCOUNT_NAME/taler-revenue/``.
+ask your bank for EBICS access and to set up :ref:`libeufin-nexus` to provide
+the revenue API endpoint. The :ref:`libeufin-bank` used by regional currency
+setups also provides a revenue API endpoint at
+``$BANK_URL/accounts/$ACCOUNT_NAME/taler-revenue/``. Thus, when using a
+regional currency setup, simply use the ``$BANK_URL`` of your bank and specify
+your bank login name and password in the :ref:`instance-account-setup` dialog.
-Make an order
-=============
+Manually creating an order using the SPA
+========================================
Click on ``Orders`` at the top left corner of the merchant backoffice page; the
following page should appear
.. image:: screenshots/create_orders.png
-After having filled the required fields, the interface should show the
following
-page with the related links to check the status of the order and let wallets
pay
-for it. Take note of the link beside ``Payment URI`` (we'll call it
``$payUri``).
+After having filled the required fields, the interface should show the
+following page with the related links to check the status of the order and let
+wallets pay for it.
.. image:: screenshots/payment_links.png
In order to test the setup, it should be now possible to use the command line
wallet
-to withdraw Taler coins and spend them to buy the order we just created.
-
-
-.. _withdraw-simulation:
-
-Pay for the order
-=================
-
-This section explains how to pay for the order in a scenario where the fiat
bank
-is simulated. The simulation takes place by crafting ad-hoc XML files as if
the
-bank would have issued them. Such XML files carry information about incoming
payments
-to the regional currency master bank account. Finally, the XML files are
passed
-to LibEuFin nexus via a convenient CLI method. The responsible script for such
-simulation is ``withdraw.sh``.
-
-Run ``./withdraw.sh`` without any arguments. Assuming that you ran the command
-as the ``test-user``, after the execution, 5 units of the regional currency
should
-be found in the CLI wallet owned by ``test-user``.
-
-
-Check it with:
-
-.. code-block:: console
-
- $ taler-wallet-cli balance
-
-If so, call the wallet in the following way to finally pay for the order just
created:
-
-.. code-block:: console
-
- $ taler-wallet-cli handle-uri $TALER_PAY_URI
-
-.. note::
-
- Reset the state before going to production, as it impacts the way nexus
- asks records to the bank. In particular, delete: any database and the
- files ``config/user.conf`` and ``config/internal.conf``, and finally run
- ``./main.sh`` again.
+to withdraw Taler coins and spend them to pay for the order we just created.
+In practice, you will rarely if ever setup orders manually like this. Instead,
+a `GNU Taler e-commerce front-end
+<https://taler.net/en/docs.html#extensions>`_ or the
+:ref:`taler-merchant-pos-app` will do this on-demand. Here, you will only need
+to provide the respective front-ends with the URL of your instance
+(e.g. ``https://backend.$DOMAIN/instances/$NAME``) and your access token.
.. _Secure-setup:
@@ -1041,11 +1027,12 @@ Secure setup
.. index:: security
.. index:: TLS
-The Taler backend does not include even the most basic forms of access control
-or transport layer security. Thus, production setups **must** deploy the
-Taler backend behind an HTTP(S) server that acts as a *reverse proxy*,
-performs TLS termination and authentication and then forwards requests to the
-backend.
+The Taler backend is deliberately simple in terms of support for access
+control or transport layer security (TLS). Thus, production setups **must**
+deploy the Taler backend behind an HTTP(S) server that acts as a *reverse
+proxy*, performs TLS termination and authentication and then forwards requests
+to the backend.
+
Using UNIX domain sockets
-------------------------
@@ -1305,6 +1292,7 @@ runtime by the setup logic provided by
``taler-unified-setup.sh``.
See :ref:`Taler Exchange Manual <Benchmark-choose-bank>` for how to use
``taler-unified-setup.sh`` to setup the system and in particular on how to
specify the bank to be used.
+
Running taler-merchant-benchmark
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
@@ -1341,8 +1329,10 @@ second gives the chance to leave some payments
unaggregated, and also to
use merchant instances other than the default (which is, actually, the
one used by default by the tool).
-Note: the ability of driving the aggregation policy is useful for testing
-the back-office facility.
+.. note::
+
+ The ability to drive the aggregation policy is useful for testing
+ the back-office facility.
Any subcommand is also equipped with the canonical ``--help`` option, so
feel free to issue the following command in order to explore all the
@@ -1369,9 +1359,6 @@ option:
-
-
-
Temporarily Abandoned Features
==============================
diff --git a/taler-merchant-pos-terminal.rst b/taler-merchant-pos-terminal.rst
index b5833369..0cca1d52 100644
--- a/taler-merchant-pos-terminal.rst
+++ b/taler-merchant-pos-terminal.rst
@@ -15,8 +15,10 @@
@author Torsten Grote
-GNU Taler Merchant POS Manual
-#############################
+.. _taler-merchant-pos-app:
+
+GNU Taler Merchant POS App
+##########################
The GNU Taler merchant POS (point of sale) terminal allows sellers to
diff --git a/taler-wallet.rst b/taler-wallet.rst
index 04a77e7d..3ea1dbea 100644
--- a/taler-wallet.rst
+++ b/taler-wallet.rst
@@ -207,6 +207,48 @@ is functional:
# The "deposit group id" can be found in the output of the transactions list.
$ taler-wallet-cli deposit track $DEPOSIT_GROUP_ID
+.. _withdraw-simulation:
+
+
+Paying for an order
+===================
+
+.. note::
+
+ This section is in dire need for some editing...
+
+This section explains how to pay for an order in a scenario where the fiat bank
+is simulated. The simulation takes place by crafting ad-hoc XML files as if
the
+bank would have issued them. Such XML files carry information about incoming
payments
+to the regional currency master bank account. Finally, the XML files are
passed
+to LibEuFin nexus via a convenient CLI method. The responsible script for such
+simulation is ``withdraw.sh``.
+
+Run ``./withdraw.sh`` without any arguments. Assuming that you ran the command
+as the ``test-user``, after the execution, 5 units of the regional currency
should
+be found in the CLI wallet owned by ``test-user``.
+
+
+Check it with:
+
+.. code-block:: console
+
+ $ taler-wallet-cli balance
+
+If so, call the wallet in the following way to finally pay for the order just
created:
+
+.. code-block:: console
+
+ $ taler-wallet-cli handle-uri "$TALER_PAY_URI"
+
+.. note::
+
+ Reset the state before going to production, as it impacts the way nexus
+ asks records to the bank. In particular, delete: any database and the
+ files ``config/user.conf`` and ``config/internal.conf``, and finally run
+ ``./main.sh`` again.
+
+
--
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- [taler-docs] branch master updated: major updates to taler-merchant-manual,
gnunet <=