commit 18ce41f9594286fb08aaf36827d2283775a8b2bf
parent f92967cc5f6d46025dabba45c5abf767bdbd57c8
Author: Sebastian <sebasjm@taler-systems.com>
Date: Thu, 5 Feb 2026 15:15:03 -0300
tester
Diffstat:
1 file changed, 7 insertions(+), 11 deletions(-)
diff --git a/design-documents/074-merchant-backend-simplification.rst b/design-documents/074-merchant-backend-simplification.rst
@@ -77,17 +77,19 @@ Personas
Persona Definitions
^^^^^^^^^^^^^^^^^^^
-* ``Developer``
+* ``Beta tester``
- * Every feature flag on, developer mode on
+ * Every feature flag on
* Should come last in the drop-down
* ``Expert``
- * Every feature flag on, developer mode off
+ * All basic features
* Second to last in dropdown
* No Age restriction
* No token families
+ * No product taxes
+ * No refreshable scopes
* ``Unattended in-person offline vending`` (minimal farm shop) showing:
@@ -217,7 +219,7 @@ account, we can simplify it into one ``Bank accounts`` page.
When adding a bank account, we should only show the simplified
dialog (IBAN, account owner information) and not the
- WireGateway part *unless* in "show everything" and/or "developer"
+ WireGateway part *unless* in "show everything" and/or "beta tester"
mode. In terms of entering account owner information, we should
allow entering more data, like ZIP code, City name, etc. as these
are becoming more-and-more required. So not just "receiver-name".
@@ -422,11 +424,5 @@ Discussion / Q&A
* Is the chosen persona persistent?
- * Not for now, it's stored per session. We could make it persistent
- in the future, but there are no plans for that presently.
+ * Not for now, it's stored per local-storage.
-* Should developer mode be a separate persona, or should there always be a developer mode toggle
- for every persona?
-
- * Problem with "developer as persona": The developer mode already affects the behavior
- *before* login, such as when choosing a different backend base URL.
