summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMS <ms@taler.net>2021-05-21 20:01:53 +0200
committerMS <ms@taler.net>2021-05-21 20:01:53 +0200
commit8ff943438779ecde4f04c12a9f7e3505540eea5a (patch)
tree68e7061d12c8a956b0e400f2cf8616412c6cc806
parent8b2d459dfdc263973f3890baebf159ab047b55f2 (diff)
downloaddocs-8ff943438779ecde4f04c12a9f7e3505540eea5a.tar.gz
docs-8ff943438779ecde4f04c12a9f7e3505540eea5a.tar.bz2
docs-8ff943438779ecde4f04c12a9f7e3505540eea5a.zip
explain merchant default auth
-rw-r--r--core/api-merchant.rst7
1 files changed, 6 insertions, 1 deletions
diff --git a/core/api-merchant.rst b/core/api-merchant.rst
index 56a9187f..e15ab035 100644
--- a/core/api-merchant.rst
+++ b/core/api-merchant.rst
@@ -34,7 +34,12 @@ This is useful when multiple businesses want to share the same payment
infrastructure.
Merchant backends have one special ``default`` instance. This ``default``
-instance is used when no explicit instance is specified.
+instance is used when no explicit instance is specified. Despite its name,
+this instance must be created after the installation. In case *no* default
+instance is found - or its credentials got lost -, the administrator can use
+the default instance's rights by resorting on the ``--auth`` command line option,
+or by restarting the service by providing a environment variable called
+``TALER_MERCHANT_TOKEN``.
Each instance (default and others) has a base URL. The resources under
this base URL are divided into to categories: