path: root/design-documents/007-payment.rst
diff options
authorFlorian Dold <>2020-08-09 00:24:07 +0530
committerFlorian Dold <>2020-08-09 00:24:07 +0530
commita61621982aa6d77dbeff5fe98b22c7ab2e37bed4 (patch)
tree420d5c6e39609483bb6c23d2fd83d91a1bc9e9bb /design-documents/007-payment.rst
parent1e2cd1b56cdee70b84a499dbff83eca9421aa700 (diff)
Diffstat (limited to 'design-documents/007-payment.rst')
1 files changed, 16 insertions, 0 deletions
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 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.