commit 5bacf0624caaa59f2f7fb3a08d1101b80008d273
parent 2a099a13b2024da454e26f6df2f969731e163d21
Author: Marcello Stanisci <marcello.stanisci@inria.fr>
Date: Sun, 25 Sep 2016 21:59:09 +0200
how to add exchanges for a merchant
Diffstat:
2 files changed, 17 insertions(+), 0 deletions(-)
diff --git a/api-exchange.rst b/api-exchange.rst
@@ -23,6 +23,7 @@ The API specified here follows the :ref:`general conventions <http-common>`
for all details not specified in the individual requests. The :ref:`glossary`
defines all specific terms used in this section.
+.. _keys:
-----------------------
Obtaining Exchange Keys
-----------------------
diff --git a/operate-merchant.rst b/operate-merchant.rst
@@ -79,6 +79,22 @@ possible in two ways:
Exchanges
---------
+The options `uri` and `master_key`, under section `[merchant-exchange-MYEXCHANGE]`, let
+the merchant add the exchange `MYEXCHANGE` among the exchanges the merchant wants to work
+with. `MYEXCHAGE` is just a mnemonic name chosen by the merchant (which is not currently used
+in any computation), and the merchant can add as many exchanges as it is needed.
+`uri` is the exchange's base URL. Please note that a valid `uri` complies with the following
+pattern::
+
+ schema://hostname/
+
+`master_key` is the base32 encoding of the exchange's master key (see :ref:`/keys <keys>`).
+In our demo, we use the following configuration::
+
+ [merchant-exchange-test]
+ URI = https://exchange.test.taler.net/
+ MASTER_KEY = CQQZ9DY3MZ1ARMN5K1VKDETS04Y2QCKMMCFHZSWJWWVN82BTTH00
+
------
Keying
------
