summaryrefslogtreecommitdiff
path: root/core
diff options
context:
space:
mode:
authorChristian Grothoff <christian@grothoff.org>2020-11-08 11:39:35 +0100
committerChristian Grothoff <christian@grothoff.org>2020-11-08 11:39:47 +0100
commit32e8e736f6707761ace157f515a55063a8814b07 (patch)
treedccc9aacd7bbe8bca7de8329d2d8db785ed40907 /core
parent2218d5b9f845bbb52b11c68d117838a811107adb (diff)
downloaddocs-32e8e736f6707761ace157f515a55063a8814b07.tar.gz
docs-32e8e736f6707761ace157f515a55063a8814b07.tar.bz2
docs-32e8e736f6707761ace157f515a55063a8814b07.zip
comments on 009
Diffstat (limited to 'core')
-rw-r--r--core/api-merchant.rst18
1 files changed, 18 insertions, 0 deletions
diff --git a/core/api-merchant.rst b/core/api-merchant.rst
index 77e347e..25f7c15 100644
--- a/core/api-merchant.rst
+++ b/core/api-merchant.rst
@@ -193,6 +193,9 @@ Making the payment
The client might want to try later again.
This includes failures like the denomination key of a coin not being
known to the exchange as far as the merchant can tell.
+ :http:statuscode:`504 Gateway timeout`:
+ The merchant's interaction with the exchange took too long.
+ The client might want to try later again.
The backend will return verbatim the error codes received from the exchange's
:ref:`deposit <deposit>` API. If the wallet made a mistake, like by
@@ -461,6 +464,9 @@ are for incomplete payments for an order and never for established contracts.
:http:statuscode:`502 Bad gateway`:
The merchant's interaction with the exchange failed in some way.
The error from the exchange is included.
+ :http:statuscode:`504 Gateway timeout`:
+ The merchant's interaction with the exchange took too long.
+ The client might want to try later again.
The backend will return an `abort response <AbortResponse>`, which includes
verbatim the error codes received from the exchange's
@@ -1614,6 +1620,9 @@ Inspecting orders
The order or instance is unknown to the backend.
:http:statuscode:`502 Bad gateway`:
We failed to obtain a response from the exchange (about the wire transfer status).
+ :http:statuscode:`504 Gateway timeout`:
+ The merchant's interaction with the exchange took too long.
+ The client might want to try later again.
.. ts:def:: MerchantOrderStatusResponse
@@ -1940,6 +1949,9 @@ Informing the backend about incoming wire transfers
:http:statuscode:`502 Bad gateway`:
The exchange returned an error when we asked it about the "GET /transfer" status
for this wire transfer. Details of the exchange error are returned.
+ :http:statuscode:`504 Gateway timeout`:
+ The merchant's interaction with the exchange took too long.
+ The client might want to try later again.
**Details:**
@@ -2250,6 +2262,9 @@ funds to the exchange.
The exchange does not support the requested wire method.
:http:statuscode:`502 Bad gateway`:
We could not obtain /wire details from the specified exchange base URL.
+ :http:statuscode:`504 Gateway timeout`:
+ The merchant's interaction with the exchange took too long.
+ The client might want to try later again.
.. ts:def:: ReserveCreateRequest
@@ -2352,6 +2367,9 @@ Query funds remaining
This is only returned if there was actual trouble with the exchange, not
if the exchange merely did not respond yet or if it responded that the
reserve was not yet filled.
+ :http:statuscode:`504 Gateway timeout`:
+ The merchant's interaction with the exchange took too long.
+ The client might want to try later again.
.. ts:def:: ReserveDetail