gnunet-svn
[Top][All Lists]
Advanced

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

[GNUnet-SVN] [taler-merchant] branch master updated: doc: explain last_s


From: gnunet
Subject: [GNUnet-SVN] [taler-merchant] branch master updated: doc: explain last_session_id
Date: Sun, 11 Mar 2018 16:55:18 +0100

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

dold pushed a commit to branch master
in repository merchant.

The following commit(s) were added to refs/heads/master by this push:
     new 8e515cf  doc: explain last_session_id
8e515cf is described below

commit 8e515cfa7f4c22b7c2d711001108e30e396e3b93
Author: Florian Dold <address@hidden>
AuthorDate: Sun Mar 11 16:55:11 2018 +0100

    doc: explain last_session_id
---
 doc/merchant-api.content.texi | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/doc/merchant-api.content.texi b/doc/merchant-api.content.texi
index 9233c33..88b96b3 100644
--- a/doc/merchant-api.content.texi
+++ b/doc/merchant-api.content.texi
@@ -644,6 +644,10 @@ fulfillment page, but include an additional 
@code{session_sig} parameter.  The
 frontend can query @code{/check-payment} with both the @code{session_id} and
 the @code{session_sig} again to verify that the signature is correct.
 
+The last session ID that was successfuly used to prove that the payment
+receipt is in the user's wallet is also available as @code{last_session_id} in
+the response to @code{/check-payment}.
+
 In some situations the user has paid for some digital good, but the frontend
 does not know the exact order ID, and thus can't instruct the wallet to show
 the existing payment receipt.  This is common for simple shops without a login

-- 
To stop receiving notification emails like this one, please contact
address@hidden



reply via email to

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