summaryrefslogtreecommitdiff
path: root/example-essay-store.rst
diff options
context:
space:
mode:
authorFlorian Dold <florian.dold@gmail.com>2016-02-17 05:09:46 +0100
committerFlorian Dold <florian.dold@gmail.com>2016-02-17 05:09:46 +0100
commitc85c9893e9c958e22dbb5d80f8d85bc686fc0f29 (patch)
treef53a2767f262ec0fcb81c0034236c8536b7235b7 /example-essay-store.rst
parent524387973f4aae3ee4cf5813131b504b039622a9 (diff)
downloaddocs-c85c9893e9c958e22dbb5d80f8d85bc686fc0f29.tar.gz
docs-c85c9893e9c958e22dbb5d80f8d85bc686fc0f29.tar.bz2
docs-c85c9893e9c958e22dbb5d80f8d85bc686fc0f29.zip
note
Diffstat (limited to 'example-essay-store.rst')
-rw-r--r--example-essay-store.rst10
1 files 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.