taler-docs

commit 00cfe7f8cf3be3d8f4c9133820649ad8563d9b85
parent c0fcbd3287019d2b14a2cd6db124eea53235af1b
Author: Christian Grothoff <christian@grothoff.org>
Date:   Mon, 27 Jul 2020 10:47:27 +0200

syntax fix

Diffstat:
M
core/api-merchant.rst
 | 
6
+++---

1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/core/api-merchant.rst b/core/api-merchant.rst
@@ -1375,10 +1375,10 @@ Payment processing
 
   **Request:**
 
-  :query h_contract: hash of the order's contract terms (this is used to authenticate the wallet/customer in case $ORDER_ID is guessable). Either this field or *token* is *mandatory*.
+  :query h_contract=HASH: hash of the order's contract terms (this is used to authenticate the wallet/customer in case $ORDER_ID is guessable). Either this field or *token* is *mandatory*.
   :query token=TOKEN: *Optional*. Authorizes the request via the claim token that was returned  in the `PostOrderResponse`.  Either this field or *h_contract* is *mandatory*.
-  :query session_id: *Optional*. Session ID that the payment must be bound to.  If not specified, the payment is not session-bound.
-  :query timeout_ms: *Optional.*  If specified, the merchant backend will
+  :query session_id=STRING: *Optional*. Session ID that the payment must be bound to.  If not specified, the payment is not session-bound.
+  :query timeout_ms=NUMBER: *Optional.*  If specified, the merchant backend will
     wait up to ``timeout_ms`` milliseconds for completion of the payment before
     sending the HTTP response.  A client must never rely on this behavior, as the
     merchant backend may return a response immediately.