commit aef35986458ccedd71dc1532d80943efb1866b4f
parent c448fec3f70eaf102a24ac5cda9c4347891c6c6f
Author: Florian Dold <florian@dold.me>
Date: Wed, 24 Sep 2025 16:48:26 +0200
dd68: document donau user experience
Diffstat:
1 file changed, 34 insertions(+), 0 deletions(-)
diff --git a/design-documents/068-tokens-roadmap.rst b/design-documents/068-tokens-roadmap.rst
@@ -84,6 +84,40 @@ Plan for Donau
* Needs to packaged
+User Experience
+===============
+
+Donau MVP
+^^^^^^^^^
+
+MVP flow:
+
+1. User opens Taler wallet, goes to ``Settings -> Donations``
+2. In the initial state, user can enter a donau base URL and tax ID.
+3. Subsequently, the ``Settings -> Donations`` screen shows:
+
+ * Currently configured donation authority
+ * Currently configured tax ID
+ * Navigation link ``Show donation statements``
+
+4. User makes a payment with a merchant that offers donation receipts.
+ If the merchant supports the same donau service as configured in the wallet,
+ the wallet UI shows some notice (e.g. ``This payment provides a donation receipt``).
+
+5. User can view their current donation statement via ``Settings -> Donations -> Show donation statements``.
+
+Donau Next Iteration
+^^^^^^^^^^^^^^^^^^^^
+
+In the post-MVP iteration, we want to improve the onboarding experience. The
+wallet should ask *during* a payment that supports a donation receipt if the
+user wants to set up donation receipts.
+
+As the merchant might offer multiple donau URLs (each for their own financial domain),
+the user needs to be shown all possible donaus with their respective financial domain.
+After choosing the donau, the user needs to enter their tax payer identifier.
+
+
Test Plan
=========
