commit b6dfc23613b33f1277b3710638e3a93cacf93aab
parent 90e8e8f819282986e5de7f176309d35f24cdc605
Author: Christian Grothoff <grothoff@gnunet.org>
Date: Sat, 22 Nov 2025 08:39:01 +0100
document TERMS/PP options for merchant
Diffstat:
1 file changed, 36 insertions(+), 2 deletions(-)
diff --git a/manpages/taler-merchant.conf.5.rst b/manpages/taler-merchant.conf.5.rst
@@ -179,8 +179,42 @@ STRICT_PROTOCOL_V19
PAYMENT_TARGET_TYPES
Space-separated list of allowed payment target types (like bitcoin, iban or x-taler-bank).
- Defaults to "*" which means no restrictions if not specified.
-
+ Defaults to "\*" which means no restrictions if not specified.
+
+TERMS_DIR
+ Directory where the terms of service of the merchant operator can be fund.
+ The directory must contain sub-directories for every supported language,
+ using the two-character language code in lower case, e.g. "en/" or "fr/".
+ Each subdirectory must then contain files with the terms of service in
+ various formats. The basename of the file of the current policy must be
+ specified under ``TERMS_ETAG``. The extension defines the mime type.
+ Supported extensions include "html", "htm", "txt", "pdf", "jpg", "jpeg",
+ "png" and "gif". For example, using a ``TERMS_ETAG`` of "0", the structure
+ could be the following:
+
+ - $TERMS_DIR/en/0.pdf
+ - $TERMS_DIR/en/0.html
+ - $TERMS_DIR/en/0.txt
+ - $TERMS_DIR/fr/0.pdf
+ - $TERMS_DIR/fr/0.html
+ - $TERMS_DIR/de/0.txt
+
+TERMS_ETAG
+ Basename of the file(s) in the ``TERMS_DIR`` with the current terms of service.
+ The value is also used for the "Etag" in the HTTP request to control
+ caching. Whenever the terms of service change, the ``TERMS_ETAG`` MUST also
+ change, and old values MUST NOT be repeated. For example, the date or
+ version number of the terms of service SHOULD be used for the Etag. If
+ there are minor (e.g. spelling) fixes to the terms of service, the
+ ``TERMS_ETAG`` probably SHOULD NOT be changed. However, whenever users must
+ approve the new terms, the ``TERMS_ETAG`` MUST change.
+
+PRIVACY_DIR
+ Works the same as ``TERMS_DIR``, just for the privacy policy.
+
+PRIVACY_ETAG
+ Works the same as ``TERMS_ETAG``, just for the privacy policy.
+
DEFAULT_PERSONA
Which "Persona" should be chosen by default for new clients
using the SPA? The setting can always changed locally in the
