diff options
Diffstat (limited to 'taler-merchant-manual.rst')
| -rw-r--r-- | taler-merchant-manual.rst | 7 |
1 files changed, 3 insertions, 4 deletions
diff --git a/taler-merchant-manual.rst b/taler-merchant-manual.rst index 9a3c94f4..5301cc28 100644 --- a/taler-merchant-manual.rst +++ b/taler-merchant-manual.rst @@ -806,7 +806,7 @@ Setup ------ With the knowledge of the ``payto://``-URI, instances can be configured by POSTing -a request to :http:post:`/management/instances`. To create a first instance, +a request to ``/management/instances``. To create a first instance, create a file ``instance.json`` with an `InstanceConfigurationMessage` .. code-block:: json @@ -1241,8 +1241,7 @@ Authorize a tip When your frontend has reached the point where a client is supposed to receive a tip, it needs to first authorize the tip. For this, the frontend must use -the :http:post:`/private/reserves/$RESERVE_PUB/authorize-tip` -API of the backend. To authorize a +a POST to ``/private/reserves/$RESERVE_PUB/authorize-tip``. To authorize a tip, the frontend has to provide the following information in the body of the POST request: @@ -1272,7 +1271,7 @@ Picking up of the tip --------------------- The wallet will POST a JSON object to the shop’s -:http:post:`/tips/$TIP_ID/pickup` handler. +``/tips/$TIP_ID/pickup`` handler. The frontend must then forward this request to the backend. The response generated by the backend can then be forwarded directly to the wallet. |