commit 2b10944551b48e7a679f4d1146116ecb1721f9b6 parent 4ca7116ec73a6149080a26eef4dbbb5de7fab63e Author: Marcello Stanisci <marcello.stanisci@inria.fr> Date: Wed, 28 Oct 2015 17:38:23 +0100 specing edate on merchant side Diffstat:
| M | api-merchant.rst | | | 6 | +++--- |
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/api-merchant.rst b/api-merchant.rst @@ -440,11 +440,11 @@ The following API are made available by the merchant's `backend` to the merchant :reqheader Content-Type: application/json - The JSON that is to be sent from the frontend is just a `contract` object which misses the fields + The `proposition` that is to be sent from the frontend is a `contract` object without the fields * `merchant_pub` * `mints` - + The `backend` then completes this information based on its configuration. **Success Response** @@ -464,7 +464,7 @@ The following API are made available by the merchant's `backend` to the merchant :reqheader Content-Type: application/json - The `frontend` should just pass the deposit permission information it received from the wallet verbatim. + The `frontend` passes the deposit permission received from the wallet, by optionally adding a field named `edate`, indicating a deadline by which he would expect to receive the bank transfer for this deal **Success Response: OK**