commit 8ff943438779ecde4f04c12a9f7e3505540eea5a parent 8b2d459dfdc263973f3890baebf159ab047b55f2 Author: MS <ms@taler.net> Date: Fri, 21 May 2021 20:01:53 +0200 explain merchant default auth Diffstat:
| M | core/api-merchant.rst | | | 7 | ++++++- |
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git 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: