summaryrefslogtreecommitdiff
path: root/api-merchant.rst
diff options
context:
space:
mode:
authorJeff Burdges <burdges@gnunet.org>2015-11-02 17:15:53 +0100
committerJeff Burdges <burdges@gnunet.org>2015-11-02 17:15:53 +0100
commit7df646855907cfe68e3fcceca64c83e4a296688f (patch)
treed05c5e5dcd068a86c48f1734e537129f9667f772 /api-merchant.rst
parentb0bba207481826b1503288ccbddb924125d82ea9 (diff)
downloaddocs-7df646855907cfe68e3fcceca64c83e4a296688f.tar.gz
docs-7df646855907cfe68e3fcceca64c83e4a296688f.tar.bz2
docs-7df646855907cfe68e3fcceca64c83e4a296688f.zip
Minor correction and cross linking
Diffstat (limited to 'api-merchant.rst')
-rw-r--r--api-merchant.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/api-merchant.rst b/api-merchant.rst
index 6be78c14..426f49a7 100644
--- a/api-merchant.rst
+++ b/api-merchant.rst
@@ -473,7 +473,7 @@ The following API are made available by the merchant's `backend` to the merchant
:reqheader Content-Type: application/json
- The `frontend` passes the deposit permission received from the wallet, by adding the field `max_fee` (see `contract`) and optionally adding a field named `edate`, indicating a deadline by which he would expect to receive the bank transfer for this deal
+ The `frontend` passes the deposit permission received from the wallet, by adding the field `max_fee` (see :ref:`contract`) and 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**
@@ -481,5 +481,5 @@ The following API are made available by the merchant's `backend` to the merchant
**Failure Responses:**
- The `backend` will return error codes received from the mint verbatim (see `/deposit` documentation for the mint API for possible errors). If the wallet made a mistake, like by double-spending for example, the `frontend` should pass the reply verbatim to the browser/wallet. This should be the expected case, as the `frontend` cannot really make mistakes; the only reasonable exception is if the `backend` is unavailable, in which case the customer might appreciate some reassurance that the merchant is working on getting his systems back online.
+ The `backend` will return verbatim the error codes received from the mint's :ref:`deposit` API. If the wallet made a mistake, like by double-spending for example, the `frontend` should pass the reply verbatim to the browser/wallet. This should be the expected case, as the `frontend` cannot really make mistakes; the only reasonable exception is if the `backend` is unavailable, in which case the customer might appreciate some reassurance that the merchant is working on getting his systems back online.