From c85c9893e9c958e22dbb5d80f8d85bc686fc0f29 Mon Sep 17 00:00:00 2001 From: Florian Dold Date: Wed, 17 Feb 2016 05:09:46 +0100 Subject: note --- example-essay-store.rst | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/example-essay-store.rst b/example-essay-store.rst index 1da9eb62..74a25990 100644 --- a/example-essay-store.rst +++ b/example-essay-store.rst @@ -23,9 +23,10 @@ payment page. 2. The server checks if the `tid` and `timestamp` query parameters are present - * If `tid` and `timestamp` are present, restore the contract for the essay (using `tid` as - transaction id in the contract and `timestamp` as timestamp) and emit the `taler-execute-contract` DOM - event in the user agent. + * If `tid` and `timestamp` are present, restore the contract for the essay + (using `tid` as transaction id in the contract, `timestamp` as timestamp + and `timestamp+REFUND_DELTA` as refund deadline) and emit the + `taler-execute-contract` DOM event in the user agent. * Otherwise proceed with step 3 3. The server generates a new contract and emits the `taler-confirm-contract` DOM event in the user agent, @@ -43,3 +44,6 @@ In step 2, the `taler-execute-contract` event has the following parameters: page, without the `tid` parameter. +Note that we assume that all essays cost the same (otherwise the amount would have to be included in +the restoration information in the /essay fulfillment URL). The refund deadline is computed +by adding the merchant-specific constant `REFUND_DELTA` to the contract's timestamp. -- cgit v1.2.3