From a61621982aa6d77dbeff5fe98b22c7ab2e37bed4 Mon Sep 17 00:00:00 2001 From: Florian Dold Date: Sun, 9 Aug 2020 00:24:07 +0530 Subject: problem --- design-documents/007-payment.rst | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) (limited to 'design-documents') diff --git a/design-documents/007-payment.rst b/design-documents/007-payment.rst index b4b41a9c..4a0998b0 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 though. 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 case. -- cgit v1.2.3