[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[taler-docs] branch master updated: problem

From: gnunet
Subject: [taler-docs] branch master updated: problem
Date: Sat, 08 Aug 2020 20:54:12 +0200

This is an automated email from the git hooks/post-receive script.

dold pushed a commit to branch master
in repository docs.

The following commit(s) were added to refs/heads/master by this push:
     new a616219  problem
a616219 is described below

commit a61621982aa6d77dbeff5fe98b22c7ab2e37bed4
Author: Florian Dold <>
AuthorDate: Sun Aug 9 00:24:07 2020 +0530

 design-documents/007-payment.rst | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/design-documents/007-payment.rst b/design-documents/007-payment.rst
index b4b41a9..4a0998b 100644
--- a/design-documents/007-payment.rst
+++ b/design-documents/007-payment.rst
@@ -140,6 +140,9 @@ Covered Scenarios
 Problematic Scenarios
+Bookmarks of Lost Purchases
 Let's say I bought some article a few months ago and I lost my wallet. I still 
have the augmented fulfillment URL
 for the article bookmarked.  When I re-visit the URL, I will be prompted via 
QR code, but I can *never* prove
 that I already paid, because I lost my wallet!
@@ -149,3 +152,16 @@ It's not clear if this is a common/important scenario 
 But we might want to make clear on the client order status page that it's 
showing a QR code for something
 that was already paid.
+The Back Button
+The following steps lead to unintuitive navigation:
+1. Purchase a paywalled URL for the first time via a detached wallet
+2. Marvel at the fulfillment page
+3. Press the back button
+This will display an error message, as the authentication via the claim token 
on the
+``/orders/{order-ID}`` page is not valid anymore.
+We could consider still allowing authentication with the claim token in this 

To stop receiving notification emails like this one, please contact

reply via email to

[Prev in Thread] Current Thread [Next in Thread]