diff options
author | Christian Grothoff <christian@grothoff.org> | 2015-03-28 17:10:39 +0100 |
---|---|---|
committer | Christian Grothoff <christian@grothoff.org> | 2015-03-28 17:10:39 +0100 |
commit | 15b362373ff01ec9205ac921bdcdbb627455081a (patch) | |
tree | ab3d4eeb68363943d4c4c1192fe045ac6f1ccc93 /src/include/taler_mintdb_plugin.h | |
parent | d61dbb310995476ff977bb5da30d8f87dd161b6f (diff) |
fix use of struct TALER_DepositRequestPS (unfinished)
Diffstat (limited to 'src/include/taler_mintdb_plugin.h')
-rw-r--r-- | src/include/taler_mintdb_plugin.h | 22 |
1 files changed, 22 insertions, 0 deletions
diff --git a/src/include/taler_mintdb_plugin.h b/src/include/taler_mintdb_plugin.h index 0cf8ba848..67ef3895b 100644 --- a/src/include/taler_mintdb_plugin.h +++ b/src/include/taler_mintdb_plugin.h @@ -240,6 +240,28 @@ struct TALER_MINTDB_Deposit uint64_t transaction_id; /** + * Time when this request was generated. Used, for example, to + * assess when (roughly) the income was achieved for tax purposes. + * Note that the Mint will only check that the timestamp is not "too + * far" into the future (i.e. several days). The fact that the + * timestamp falls within the validity period of the coin's + * denomination key is irrelevant for the validity of the deposit + * request, as obviously the customer and merchant could conspire to + * set any timestamp. Also, the Mint must accept very old deposit + * requests, as the merchant might have been unable to transmit the + * deposit request in a timely fashion (so back-dating is not + * prevented). + */ + struct GNUNET_TIME_Absolute timestamp; + + /** + * How much time does the merchant have to issue a refund request? + * Zero if refunds are not allowed. After this time, the coin + * cannot be refunded. + */ + struct GNUNET_TIME_Absolute refund_deadline; + + /** * Fraction of the coin's remaining value to be deposited, including * depositing fee (if any). The coin is identified by @e coin_pub. */ |