commit 5aa48cdbccb89c350b0d96fde0431fcae9c0599f
parent 564f9a34383e2980ac8ebff5626504e9f73835dc
Author: Martin Schanzenbach <schanzen@gnunet.org>
Date: Tue, 14 Oct 2025 11:22:47 +0200
dd70 more user stories, error corrections
Diffstat:
1 file changed, 18 insertions(+), 6 deletions(-)
diff --git a/design-documents/070-alias-directory-mailbox.rst b/design-documents/070-alias-directory-mailbox.rst
@@ -120,7 +120,7 @@ Send Payment Request
Prerequisites: Bob has installed Taler Wallet, Bob knows one of Alice's aliases
Bob wants to request money from Alice.
-He opens his Taler wallet and opens ``Taler Button->Send`` screen from the menu.
+He opens his Taler wallet and opens ``Taler Button->Receive`` screen from the menu.
A screen that allows to create a payment request is shown to Bob.
Once Bob has entered all necessary details, a payment request (:ref:`DD 13 <dd-13>`) is
created and the screen with QR code is shown.
@@ -148,7 +148,7 @@ The new payment request by Bob is received by the Wallet and it notifies Alice.
**Technical Note**: Notice request is *NEW*. This requires requests to have unique IDs. Also, maybe notifications should happen even if the ID is already seen, but the message is new.
-Alice interacts with the notification or manually browses to ``Mailbox``.
+Alice interacts with the notification or manually browses to ``Settings->Mailbox``.
**TODO**: Does this exist / make sense?
@@ -189,11 +189,11 @@ Send Money
Prerequisites: Alice has installed Taler Wallet, Alice has registered an Alias.
Bob wants to directly send money to Alice (e.g. PayPal style).
-He opens his Taler wallet and opens ``Taler Button->Receive``.
+He opens his Taler wallet and opens ``Taler Button->Send``.
A screen that allows to create a payment offer is shown to Bob.
Once Bob has entered all necessary details, the payment offer is created and the screen with the QR code is shown.
-There, he selects the *Receive from Friend*.
-The *Receive from Friend* screen consists of a search input and an Alias type selector.
+There, he selects the *Send to Friend*.
+The *Send to Friend* screen consists of a search input and an Alias type selector.
This screen now also allows to send the request to a friend by using the friend list.
Bob selects *Send to Friend*.
The *Send to Friend* screen brings up the friends list to select a friend.
@@ -208,7 +208,19 @@ This request may fail, for example if Alice's Mailbox is full.
**Note**: Sending messages via Mailbox API may incur fees. So does creating a purse in the offer. This should probably be done in a single user action.
- **Note**: Should mailbox be used to notify Alice of payment? A: Yes
+Resend Payment Request
+----------------------
+
+ Prerequisites: Bos has already sent a payment request to Alice
+
+Bob may want to resend a payment request if it expired or if Alice lost the request.
+
+ **Technical Note**: This does not mean that the request can get lost in transit. It means that it is possible that Alice lost her phone and needed to setup her Wallet again.
+
+Bob opens ``Settings->Mailbox`` and selects a payment request he wants to send again.
+Bob can initiate to resend this payment request with a button.
+
+ **Technical Note**: This likely implies the creation of a new payment request, with the same detail of the already sent request. Sending the same request again is probably not a good idea. This, however, requires a new field to the contract terms (``idempotency_nonce``?) that we keep identical between both requests. That way, the receiving wallet can detect that it is a duplicate and act accordingly --- if already paid, ignore, if hard-rejected/banned ignore, and if merely expired show again.
Open Questions
