commit eb66b96d0ad84ce161080900ac79f7c6ece3f350
parent 7908d795127586b317e8ea6f796af15fe68ddd80
Author: Christian Grothoff <christian@grothoff.org>
Date: Sun, 16 Nov 2025 21:25:49 +0100
document new DEFAULT_PERSONA option
Diffstat:
2 files changed, 16 insertions(+), 0 deletions(-)
diff --git a/core/api-merchant.rst b/core/api-merchant.rst
@@ -203,6 +203,13 @@ such as the implemented version of the protocol and the currency used.
// supported currencies and how to render them.
currency: string;
+ // Which Persona should be used by default by new clients in the SPA.
+ // Can be changed locally per browers under "Personalization".
+ // Possible values include "expert", "offline-vending-machine",
+ // "point-of-sale", "digital-publishing", "e-commerce" and "developer".
+ // @since **v23**.
+ default_persona: string;
+
// How services should render currencies supported
// by this backend. Maps
// currency codes (e.g. "EUR" or "KUDOS") to
diff --git a/manpages/taler-merchant.conf.5.rst b/manpages/taler-merchant.conf.5.rst
@@ -181,6 +181,15 @@ 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.
+DEFAULT_PERSONA
+ Which "Persona" should be chosen by default for new clients
+ using the SPA? The setting can always changed locally in the
+ browser, but new clients without a setting stored locally will
+ use this value.
+ Possible values include: "expert", "offline-vending-machine",
+ "point-of-sale", "digital-publishing", "e-commerce" and "developer".
+ Defaults to "expert", which means all stable features are enabled.
+
PAYMENT_TARGET_REGEX
POSIX regular expression imposing additional restrictions on the "payto://"-URIs allowed
for bank accounts of instances of this system. For example, "payto://iban/CH.*" would
