commit 8e515cfa7f4c22b7c2d711001108e30e396e3b93
parent f411cb7e8cd548dfc23322cbf110e4f33efe3519
Author: Florian Dold <florian.dold@gmail.com>
Date: Sun, 11 Mar 2018 16:55:11 +0100
doc: explain last_session_id
Diffstat:
1 file changed, 4 insertions(+), 0 deletions(-)
diff --git 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
