aboutsummaryrefslogtreecommitdiff
path: root/articles/ui/ui.tex
diff options
context:
space:
mode:
authorFlorian Dold <florian.dold@gmail.com>2016-08-16 16:48:06 +0200
committerFlorian Dold <florian.dold@gmail.com>2016-08-16 16:48:06 +0200
commit62dbcba15c3290113fc98782ed2f0ddb1f4b392f (patch)
treef9ccb3f4b6694b6571fe3393cc79b2d6a53a9099 /articles/ui/ui.tex
parent939036432256e267c536158a0cdabeb2ca5a7996 (diff)
downloadwallet-core-62dbcba15c3290113fc98782ed2f0ddb1f4b392f.tar.xz
remove redundant description
Diffstat (limited to 'articles/ui/ui.tex')
-rw-r--r--articles/ui/ui.tex8
1 files changed, 0 insertions, 8 deletions
diff --git a/articles/ui/ui.tex b/articles/ui/ui.tex
index 283cbb86d..229763453 100644
--- a/articles/ui/ui.tex
+++ b/articles/ui/ui.tex
@@ -800,16 +800,8 @@ Various failure modes are considered:
% that saves Taler from being "blamed"
been out-of-date, updates the database and allows the user to retry
the transaction.
-\item If the payment succeeded, the JavaScript on the
- client side triggers effectively a ``reload'' of the fulfillment
- page, triggering case (B) detailed below.
\end{itemize}
-{\bf (B)} Upon subsequent visits, the server detects that the payment
-has already been processed and directly generates a fulfillment page
-either confirming the payment, or---in the case of payments for a
-digital article---transmits the digital artifact to the client.
-
\subsection{Bookmarks and deep links}
Taler's architecture also enables smooth use of payment